GRUB's boot menu is the same as before, but booting works for all entries now, including those on /dev/sdb. My fix has been to manually edit /boot/grub2/grub.cfg (egad, explicitly discouraged in file header!) and to replace all instances of " hd1" by " hd2". If it is the first partition on the first hard drive, you should type the following command: ls. Now type ls and the disk and partition you want to boot. To find out what kernels are on your system select the partition you want to boot and click c to get to a grub command line. Upon selecting a different kernel than 4.19 (tried 5.10, which I newly installed, and 5. You will now have to load a different kernel at boot time. I'm wondering whether the empty SATA Port 2 is causing the problem? I prefer using LTS kernels because I’m not very experienced with Linux, especially not on kernel level. F2 at startup shows these entries in BIOS (old machine, no EFI): Main: boot/grub2/grub.cfg showed the two hard disks as " hd0" and " hd1". To load the kernel forward with the following commands: insmod linux linux /vmlinuz root/dev/sda2 initrd /initrd.img boot. Booting entries from /dev/sda worked fine, choosing one from /dev/sdb gave the error Next, you can repair GRUB and/or the boot directory. The GRUB boot menu showed all operating systems installed in various partitions on /dev/sda and /dev/sdb (Windows, SuSE 15.3 and earlier). You can boot from a LiveUSB and chroot to your Debian thats on the harddisk. Upon grub2-mkconfig -o /boot/grub2/grub.cfg Describing my own fix here, as found by trial and error: Encountered the same error on a workstation with bootable partitions on both of two fixed disks ( /dev/sda, /dev/sdb) couldn't find a solution here or elsewhere.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |