Отправлено с iPhone
26 авг. 2015 г., в 16:35, Koenraad Lelong
написал(а): Op 26-08-15 om 14:41 schreef Carlos E. R.:
If you can not tell the BIOS to boot from sdb (not sdb1, that goes later), then you have to boot from sda. I think that in that case you need a /boot partition in sda, containing grub, and which then load sdb (either the kernel or another grub).
Carlos,
I'm sure OS 12.3 could boot from sdb1.
More likely that 12.3 was set to boot from sda with grub2 in MBR of sda; and grub2 looked for /boot on sdb1. If "from scratch" means you made new install, you probably created file system which of course changed UUID. In addition, grub2 installed in MBR of sda no more matches its modules installed in /boot, which explains why you cannot do insmod. Quick fix is to do "grub2-install /dev/sda" from chroot. This will make system bootable; and we can fix yast configuration later.
And sda1 is/was swap. Actually sda is completely untouched by the new install.
If only I could tell the MBR to look for another UUID.
I'm using this to try to get grub rescue to boot the new os : https://www.linux.com/learn/tutorials/776643-how-to-rescue-a-non-booting-gru... Unfortunately when I get to 'insmod normal' I get an error : symbol 'grub_term_highlight_color' not found
'insmod linux' gives the same. And then the 'linux' command is unknown, so I'm stuck.
Koenraad
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org