William Kenworthy wrote: > > On 16/3/25 13:04, Dale wrote: >> eric wrote: >>> On 3/15/25 13:42, Dale wrote: >>>> The biggest thing that slows that system is that the CPU doesn't have >>>> AES support for my encryption on the drives. Still, I wanted to play >>>> with it and see if it would go any faster. I kinda hate having a >>>> nice SSD drive laying on the shelf doing nothing. I got a good deal >>>> but still, needs to get some exercise. >>>> >>>> I know I'm missing a step somewhere. What I may do, start over and >>>> put a DOS partition table on it and just copy over /etc and the world >>>> file. Then let it rebuild everything. If I do that, I got to wait >>>> until this storm is gone and may have to wait until we finish that >>>> last tree. We got one finished yesterday and got the last one cut up >>>> and ready to split, haul to the barn and stack. It's a LOT of wood. >>>> He said it will last him two years at least. He keeps 3 to 5 years >>>> worth on hand. I think he is at about the 6 year mark now. He loves >>>> working with wood. Oh, trees were dead or dying for those who hate >>>> to read about wood being cut up. The two we cut was a danger to the >>>> guys home and outbuildings, depending on where the wind took it. The >>>> first tree was dead. It had no leaves last year and was rotting at >>>> the bottom. The two trees had insect damage and were starting to die >>>> as well. When it fell, the trunk actually broke in a couple places >>>> since it was weakening. Most of the trees he cuts, storms put them >>>> on the ground. Cutting down a tree isn't something he does a whole >>>> lot of unless a tree is dead. >>>> >>>> Anyway, I may just do a quick reinstall and change partition tables. >>>> Maybe that has something to do with it. One reason I'd like to >>>> figure it out tho, may help some other poor soul who is trying to use >>>> some older hardware and runs into this problem. >>> The only thing I can think of that you may have missed is to rebuild >>> your initrd.img or what ever ram disk you may be using to boot up. You >>> would have to do this while chrooted. As others have stated, make sure >>> your fstab file is updated correctly as well as the grub.cfg. >>> >>> Regards, >>> Eric >>> >>> >> >> Now that lead to something. First, I hadn't rebuilt the init thingy. >> So, I booted up, mounted, chrooted and all that. I then created a new >> init thingy and replaced the old one. Second. Then I also noticed >> something else. There was very little in /boot. I don't know if I >> accidentally erased it or if the copy process failed without telling >> me. I know I mounted it and copied it. I actually copied /boot first, >> then did a ls / and went down the list skipping /dev, /proc and such. I >> also did a ls /boot while in the chroot to be sure things matched up to >> the original. Plus, when I did the grub update to find kernels, init >> thingys and the firmware image, it showed it found them. What happened >> in between, no clue. Now here's another strange thing, sda1 is /boot. >> When I'm booted from the SSD, I can't mount sda1 for /boot. It >> complains about file system type. It's ext2 by the way. I need to look >> into that. I'll go back to the old drive and see what I can figure out. >> >> So, I forgot to update fstab, but it failed before it got that far >> anyway. I also didn't know I needed to rebuild the init thingy. Then >> there is the weird missing files in /boot. Then there is the inability >> to mount /boot while booted from the SSD, which shows not file system at >> all. lsblk says the same. Weird. >> >> Extra question. On my main rig, I have the GPT tools installed with >> package sys-apps/gptfdisk. It is installed and it even works. I've >> used it on my new rig to set up several drives including the m.2 stick >> for the OS but others for my LVM drives. Check this out tho. >> >> >> root@Gentoo-1 / # which cgdisk >> /usr/bin/cgdisk >> root@Gentoo-1 / # equery b /usr/bin/cgdisk >> * Searching for /usr/bin/cgdisk ... >> root@Gentoo-1 / # equery list sys-apps/gptfdisk >> * Searching for gptfdisk in sys-apps ... >> [IP-] [ ] sys-apps/gptfdisk-1.0.10-r1:0 >> root@Gentoo-1 / # equery f sys-apps/gptfdisk >> * Searching for gptfdisk in sys-apps ... >> * Contents of sys-apps/gptfdisk-1.0.10-r1: >> /usr >> /usr/sbin >> /usr/sbin/cgdisk >> /usr/sbin/fixparts >> /usr/sbin/gdisk >> /usr/sbin/sgdisk >> /usr/share >> /usr/share/doc >> /usr/share/doc/gptfdisk-1.0.10-r1 >> /usr/share/doc/gptfdisk-1.0.10-r1/NEWS.bz2 >> /usr/share/doc/gptfdisk-1.0.10-r1/README.bz2 >> /usr/share/man >> /usr/share/man/man8 >> /usr/share/man/man8/cgdisk.8.bz2 >> /usr/share/man/man8/fixparts.8.bz2 >> /usr/share/man/man8/gdisk.8.bz2 >> /usr/share/man/man8/sgdisk.8.bz2 >> root@Gentoo-1 / # >> >> >> As you can see, the package is installed, the cgdisk command is >> installed by emerge and all. Thing is, equery b and equery list doesn't >> find it but equery f does. I'm scratching my head here. The equery b >> should show the package it belongs too and equery list should list it as >> installed. Did I mess up something or is there some sort of bug in >> equery? >> >> Now to reboot and see what is up with /boot on the SSD. :/ >> >> Thanks. >> >> Dale >> >> :-) :-) >> >> >> > Depending how you built the initrd, it will likely use the current > fstab and /etc/conf.d/modules as to what will be included. If you > make changes to the system, you should rebuild the initrd (especially > important if dracut is used in hostonly mode). > > You can use lsinitrd to make sure it actually includes what you think > it does (its really only a file system after all) > > BillK
Well, this got interesting. I booted the spinning rust drive again and redone the /boot from the old system. I rebuilt the init thingy because the one that was there was for the old drive. I then ran the usual grub commands to generate the config file and even reinstalled grub just to be sure. When I tried to reboot the SSD drive, I was back to the original screen at the start of this thread. While I'd like to fix this and perhaps that fix help someone else in the future, this is just getting annoying. I should have put a DOS partition on the thing and it could be that is the problem despite the parted trick that I've used in the past. I dunno. So I'm just going to start over and use a DOS partition table this time. That may fix it. If that fails, I'll just reinstall from scratch. That should fix it for sure. I got all the config files, world file and such that I need. I just wish it was colder outside. That little mobo creates some heat. LOL In the future, if someone runs into this thread, try rebuilding the init thingy and all the grub update commands. It should work. It did here once. Thanks to all for helping. Dale :-) :-) Hmmm. I usually use dd or shred to erase a spinning rust drive. How in the heck do I do this on a SSD and not affect it in a negative way? I never thought about erasing one of those before. :-|
