Yast2 boot loader issue after upgrade 13.1->13.2 with dual boot

English Install/Boot/Login
1

Hi,

After upgrade 13.1->13.2 on a 64-bit installation which also has Win7 dual boot, the GUI Yast2 boot loader quits with an error message:

“Internal error: Please report a bug report with logs.
Details: Unknown udev device /dev/disk/by-id/ata-INTEL…[my SSD drive]…-part3
Caller: /usr/share/YaST2/lib/bootloader/device_mapping.rb:42:in ‘to_kernel_device’”

I can start and run the 13.2 system and it seems stable, although the grub2 start screen refers to 13.1.
The system is a ThinkPad X200s with DualCore, so no UEFI BIOS. part1 and part2 are Win7, part3 is / and part4 is swap.
The above error occurs if I try to use the GUI Yast2 boot loader tool to enter the grub2 configuration (in my case to rename 13.1).
I have made one change to the system: I installed the gcc4.9 packages using the Yast2 tool, but I don’t think this would affect the Yast2 boot loader tool.

Any advice on how to fix this?

Thanks in advance.

Niclas

2

First of all try this

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

What is the result of

uname -a

How was the upgrade done?

3

This part – that it says “13.1” – is not a real problem. You can fix that yourself by editing (as root) the file “/etc/default/grub”. It is considered a local configuration file, so the install won’t change that “13.1” to “13.2”.

4

On my system, the yast2 bootloader configuration tool fails similarly, although with a different message:

Internal error. Please report a bug report with logs.
Details: Unknown device tmpfs
Caller: /usr/share/YaST2/lib/bootloader/device_mapping.rb:65:in `to_mountby_device’

I have the impression that there are other problems in yast2 as well (selected boxes do not show that they are selected).

5

That’s 902385 – Yast2-Bootloader module does not start with error 'Unknown device'

Removing all NFS mounts from /etc/fstab should “fix” it, the bug report also contains a patch you could try (open the file /usr/share/YaST2/modules/Storage.rb in a text editor and change it accordingly).

I have the impression that there are other problems in yast2 as well (selected boxes do not show that they are selected).

Haven’t noticed any problems here. Which checkboxes do you mean in particular? Can you post a screenshot?
Maybe it’s cause by your theme/color scheme settings for root, have a look here: 902057 – Artwork: QT YaST2 black background in overview screen, unusable checkboxes
(i.e. try to delete /root/.kde4 and /root/.config)