Nobody else has responded, so I'll give it a try:
On Wed, 19 Jun 2013 23:50:19 +0200
cagsm
12.3 boot woes, vanishing everything except memtest, how does grub2 populate the /boot/grub2/grub.cfg
Normally, that is done by running: grub2-mkconfig -o /boot/grub2/grub.cfg
I wonder about how grub2 decides what to show in its bootmenu, as I am going insane for the past few hours. This previous 12.2 box was tried to be updated to 12.3 via remote (zypper dup) but the problems only started then.
Usually, "/etc/default/grub" gives the defaults for the main boot line. And scripts in "/etc/grub.d" are used when probing other operating systems. I have probably oversimplified that. There is probably something left behind from your 12.2 that is causing problems. I'm not sure what that is.
I did this silly game a few times over and over, and eventually figured the first time it booted with the normally looking grub2 menu, inside the machine running, there was some task being executed (top) that was called /sbin/update-bootloader .... and the parameter I think was remove and then some string probably the menu string that was being displayed in the grub2.
With multi-version kernel support, there is possibly something running to delete the old 12.2 kernels, and perhaps that is messing up grub.cfg. I'm not sure I have helped. I have never seen the behavior you describe. But then I usually do a clean install of the new version, instead of an update install. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org