-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-08-26 13:20, Koenraad Lelong wrote:

Hi,

After ugrading OS12.3 to OS13.2 (from scratch), the PC fails to boot. I get to the grub2 rescue console. After booting with the rescue mode of the DVD/stick I ran the bootinfoscript. The result is here : http://susepaste.org/3633045

I can't look at this now, but...

It's a laptop with a small SSD (sdb) and a HD (sda). / is on the SSD. /home is on the HD. The PC should boot from sdb1. It seems not possible to tell the BIOS which drive to boot first. The boot-mode is legacy (other options : EUFI with or without CSM).

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).

Is it possible I should wipe the MBR of sda ? Grub2-rescue says it can't find disk 0e89e408-341d-41d6-b6c5-d6653e270240. That disk is referenced in the MBR of sda.

Yes, you can erase it. Or rather, write generic code to it. I did it about a month ago, so I should be able to find somewhere the notes of what I did ;-) - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlXdtBcACgkQja8UbcUWM1yR+wEAhHq1vj/I6JPoR7Oxi/vSup7W DK2vkmhYGWrm0UHjRx0A/AtYmFpidB5lx4rY+T+BYy7Cow6If0cJ5VJazpEPpYi0 =SPV2 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Op 26-08-15 om 14:29 schreef Anton Aylward:

A rescue-mount-chroot puts you back on the "/" and you can re-run yast as

Anton, Can you give some information about 'rescue-mount-chroot' ? Is this the procedure : In the rescue-system : mount /dev/sdb1 /mnt mount --bind /sys /mnt/sys mount --bind /proc /mnt/proc mount --bind /dev /mnt/dev chroot /mnt There I can run yast2 bootloader But I don't find 'by-name', or do you mean modify 'Optional kernel commandline parameter' ? There I have a UUID, but that's of sda1, wich is swap. I tried to modify that UUID to that of sdb1, but it does not 'stick'. Running yast2 again gives the old value. Koenraad -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 08/26/2015 10:17 AM, Koenraad Lelong wrote:

Op 26-08-15 om 14:29 schreef Anton Aylward:

...

A rescue-mount-chroot puts you back on the "/" and you can re-run yast as

Anton, Can you give some information about 'rescue-mount-chroot' ?

Is this the procedure : In the rescue-system : mount /dev/sdb1 /mnt mount --bind /sys /mnt/sys mount --bind /proc /mnt/proc mount --bind /dev /mnt/dev chroot /mnt

Correct.

There I can run yast2 bootloader

That's my recall, it may be incorrect. perhaps the listmembers know better. Perhaps you should also have LABELed you partitions. I have mine all labelled so that under /dev/disk/-by-label there is very clearly BOOT ROOT SWAP TMP HOME "Obviously", if you don't have labels you can have root=/dev/disk/by-label/ROOT resume=/dev/disk/by-label/SWAP in your config.

But I don't find 'by-name', or do you mean modify 'Optional kernel commandline parameter' ? There I have a UUID, but that's of sda1, wich is swap.

I tried to modify that UUID to that of sdb1, but it does not 'stick'. Running yast2 again gives the old value.

To build the grub you should use 'grub2-mkconfig' How you set that up I'm not sure. Anyone? Oh, and I'd recommend the persistent use of 'apropos'. It throws up lots of clues in this regard.

From those clues you get to read man pages. After reading man pages ... you get to ask questions here asking what it all means :-)

-- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Отправлено с 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

27.08.2015 09:27, Koenraad Lelong пишет:

Op 26-08-15 om 21:18 schreef Andrei Borzenkov:

...

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.

Thanks Andrei,

That fixed it. Now I can boot.

Last step would be to fix bootloader location so subsequent updates work as expected. Edit /etc/default/grub_installdevice and replace and old device reference with name for /dev/sda. If in doubt, post content of this file and.

Unfortunately, I get no screen, and the PC stops, meaning no more shift-lock. I booted in safe-mode and then I get the graphical system. I more or less expected this, it's a radeon video-card. But that's another problem.

Koenraad.

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org