Updates did shoot my Bootloader

Hi everyone!

The machine this time is desktop PC with core-i5 and onchip graphics,
used to be multiboot openSUSE 13.1, openSUSE 13.2, win7,
MBR disk label, no EFI or secure boot enabled.

I made the updates yesterday.
It was a whole bunch of them.
And an update of grub2 came along with them.

Cold starting the PC today - the first time after the updates - I don’t get no grub menu anymore.
The system boots the 13.2 without giving me any choice.

In the Linux that you boot into, reinstalling the bootloader should re-create a multiple loader. Use Yast ==> System ==> bootloader to reinstall and and make sure that “bootloader options” tab has a tick in “probe foreign OS” (for windows).

Thanks!

Will try that and report back.

(currently busy with sth else)

Are you using the “btrfs” file system?

If you are, try removing the file “/boot/grub2/grubenv”.

Hi everybody!

I’m currently using ext3 and/or ext4 on every partition (except for the windows partitions …) whatever the openSUSE installer might propose.

The setup of my partitions is as follows:

Model: ATA ST2000NM0033-9ZM (scsi)
Disk /dev/sda: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type      File system     Flags
 1      1049kB  106MB   105MB   primary   ntfs            type=07
 2      106MB   429GB   429GB   extended                  boot, lba, type=0f
 5      107MB   17.3GB  17.2GB  logical   linux-swap(v1)  type=82
 6      17.3GB  51.6GB  34.4GB  logical   ext3            type=83
 7      51.6GB  86.0GB  34.4GB  logical   ext4            type=83
 8      86.0GB  258GB   172GB   logical   ext3            type=83
 9      258GB   429GB   172GB   logical                   type=83
 3      429GB   704GB   275GB   primary   ntfs            type=07
 4      704GB   2000GB  1296GB  primary   ntfs            type=07


Model: Linux device-mapper (crypt) (dm)
Disk /dev/mapper/cr_home: 172GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags: 

Number  Start  End    Size   File system  Flags
 1      0.00B  172GB  172GB  ext4

root of openSUSE 13.1 is on sda6
/home of openSUSE 13.1 is on sda8

root of openSUSE 13.2 is on sda7
/home of openSUSE 13.2 (encrypted) is on sda9

Now when I make a cold start I get the grub2 menu of sda7.

I select booting from sda6, which works.

Running Yast->Bootloader a new grub.cfg is created in /boot/grub2/ on sda6, which looks reasonable and by default would boot 13.1 from sda6.

However if I make a restart then, again grub2 from sda7 is loaded having boot from sda7 as default.

So, running Yast->Bootloader from sda6 obviously had no effect other than the change of grub.cfg on sda6.

Should I try to delete “/boot/grub2/grubenv” anyway?
Its contents are

# GRUB Environment Block
saved_entry=openSUSE
##################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################

Because I do want 13.1 from sda6 to boot by default, I’ll probably try to modify grub.cfg on sda7 accordingly, as a quick solution.

Thanks everybody!
Mike

Suit yourself. That “grubenv” is what causes the menu to be skipped. However, when grub does that, it is supposed to delete that entry.

My “grubenv” contains:


# GRUB Environment Block
# WARNING: Do not edit this file other than by grub2-editenv
saved_entry=0
########### (repeated)

I’m using Leap 42.1. But maybe check whether the “grub2-editenv” command exists on your system.

Well need to run

grub2-mkconfig -o /boot/grub2/grub.cfg

grub2-install /dev/sdX

where sdX is the drive you wish to install too

Hi nrickert!

Yes, I have grub2-editenv:

lHost:/boot/grub2 # grub2-editenv grubenv list
saved_entry=openSUSE 13.1
lHost:/boot/grub2 # 
lHost:/boot/grub2 # 
lHost:/boot/grub2 # grub2-editenv grubenv set saved_entry=0
lHost:/boot/grub2 # grub2-editenv grubenv list
saved_entry=0
lHost:/boot/grub2 #

Rebooting now …

That didn’t solve it.

But hi gogalthorp,

that worked out fine.
Booting 13.1 by default works fine again now.

Many thanks
Mike