On Saturday, 15 March 2025 07:29:32 Greenwich Mean Time Dale wrote: > Howdy, > > I have a Samsung SSD 500GB drive that I ended up not using in my new > build, went with the m.2 stick thingy. I decided that I would put it in > the NAS box and replace the spinning rust drive. I booted a sysrescue > image. I created and mounted both drives, creating directories as > needed. I then one at a time used cp -av to copy /bin, /boot and so on > skipping /dev, /proc and such that is created on the fly so to speak. I > did create /sys and /proc tho. I even copied the home directory, not > that there is much in there that I need. Once I got it all copied, I > chrooted into the new drive.
The Handbook states you should -rbind the /dev of the host before you chroot. Did you do this? > I installed grub on it using grub-install > /dev/sdb, since it is the second drive at this point. Did you check if 'ls -l /dev/disk/by-id' within the chroot was mapping the correct disk to /dev/sdb? I'll assume your NAS is a legacy BIOS not an EFI MoBo and grub-install /dev/ sdb did not throw up any errors. > I went back and > looked at the install docs to be sure I didn't need to run anything > else. Since I already had a config file and all, it should just work. > > When I try to boot with the SSD drive, I get this on the screen, pardon > my having to type it in. This comes up right after the BIOS screen. > > > loading operating system . . . > GRUB > > > That's it. It can't be the BIOS because if I connect the old drive as > first drive, it boots just fine. I've missed a command somewhere. I'm > sure it isn't the OS itself since it is a clone basically. I am almost > certain I missed a grub command somewhere but can't figure out what it > is. Searching for the error got other hits but not what I'm seeing. You did not mention if you ran 'grub-mkconfig -o /boot/grub/grub.cfg' within the chroot. This would read UUID and PARTUID of the new disk and its / partition and add these to your grub.cfg file. Unless you used dd to clone the partitions from the old to the new, the new disk partitions and fs IDs will be different to the old disk. > Has someone seen this before and recall how to fix it? Remember what > command it is that I missed? I think if you follow the Handbook to chroot into your new drive and update your grub.cfg it /should/ work. While you're at it don't forget to edit your fstab, if you are specifying filesystems in it using UUIDs. > I'm not sure this SSD drive is going to make that old NAS mobo go any > faster. LOL It is kinda old. I have found SSDs even when installed on old SATA 2.0 MoBos give a performance boost - but it depends how slow the spinning disk was. Replacing a 10,000RPM disk with an SSD would not provide any celebratory performance difference. PS. Check the MoBo BIOS is set to use AHCI for the SATA port you're connecting this SSD on, or TRIM/discard won't work.
signature.asc
Description: This is a digitally signed message part.
