http://bugzilla.opensuse.org/show_bug.cgi?id=911584 --- Comment #3 from Ulrich Windl --- (In reply to Michael Chang from comment #2 "Could you please test...") Please be a little bit more verbose: What after I installed the package? Run "mkinitrd" or what? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=911584 --- Comment #5 from Ulrich Windl --- (In reply to Steffen Winterfeldt from comment #1)

+ $sys_dev =~ s#/#!#;

I wonder: Shouldn't it be "$sys_dev =~ s#^.*/##;"? If the device is "/dev/md123" your command would make "!dev/md123" from it, while my command would make "md123". I didn't watch the whole context, but in /sys/block there are entries like "md123"... While at it, also fix the comment, because the code does something different than the comment suggests. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=911584 --- Comment #7 from Ulrich Windl --- (In reply to comment #2 and comment #4) The suggested commands take quite some time, and the first one finished without output, while the second one (what is it supposed to do?) gave this output: Perl-Bootloader: 2015-01-08 20:01:00 <3> pbl-2016.2 Core::RunCommand.1658: Error: '/usr/sbin/grub2-install --target=i386-pc --force --skip-fs-probe "/dev/system/root"' failed with exit code 1, output: <<<<<<<<<<<<<<<< i386-pc wird für Ihre Plattform installiert. WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it! WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it! WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it! WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it! WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it! /usr/sbin/grub2-install: Warnung: Dateisystem »ext2« unterstützt keine Einbettungen. /usr/sbin/grub2-install: Warnung: Einbettung ist nicht möglich. GRUB kann in dieser Konfiguration nur mittels Blocklisten installiert werden. Blocklisten sind allerdings UNZUVERLÄSSIG und deren Verwendung wird daher nicht empfohlen.. /usr/sbin/grub2-install: Fehler: diskfilter writes are not supported.

...

...

...

...

...

>>>>>>>>>>

Was that the command to ruin my boot configuration? ;-) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=911584 --- Comment #8 from Michael Chang --- (In reply to Ulrich Windl from comment #7)

(In reply to comment #2 and comment #4) The suggested commands take quite some time, and the first one finished without output, while the second one (what is it supposed to do?) gave this output:

It (update-bootloader --reinit) is supposed to reintall your bootloader and also recreate bootloader config.

Perl-Bootloader: 2015-01-08 20:01:00 <3> pbl-2016.2 Core::RunCommand.1658: Error: '/usr/sbin/grub2-install --target=i386-pc --force --skip-fs-probe "/dev/system/root"' failed with exit code 1, output: <<<<<<<<<<<<<<<<

That's odd, the /dev/system/root definitely can't be the install device. And if it was how could it pass the installation and booted. What is your content of /etc/default/grub_installdevice ? Could you please attach it. And also please attach /var/log/pbl.log. Thanks.

Was that the command to ruin my boot configuration? ;-)

I suppose Not, because it was failed and aborted .. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=911584 --- Comment #11 from Ulrich Windl --- Created attachment 619661 --> http://bugzilla.opensuse.org/attachment.cgi?id=619661&action=edit Relevant part of pbl.log -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=911584 Michael Chang changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(Ulrich.Windl@rz.u | |ni-regensburg.de) --- Comment #13 from Michael Chang --- (In reply to Ulrich Windl from comment #12)

# cat /etc/default/grub_installdevice /dev/disk/by-id/md-uuid-2047fabb:aa594b5d:ff1519a1:7d0ff516 Fine, this is mbr disk devce on Intel Firmware Raid.

/dev/system/root

Did your yast2 bootloader settings have enabled root partition as install device for grub2? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=911584 --- Comment #15 from Michael Chang --- (In reply to Ulrich Windl from comment #14)

(In reply to Michael Chang from comment #13)

...

Did your yast2 bootloader settings have enabled root partition as install device for grub2?

Yes.

Did you enable it manually? If yes, why ? MBR is unable to chain-load loader image from lvm blocks. If the setting was not explicitly enabled by user, I wonder YaST did a wrong location proposal here. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=911584 Ulrich Windl changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(Ulrich.Windl@rz.u | |ni-regensburg.de) | --- Comment #17 from Ulrich Windl --- In reply to comment #15: I selected (it was allowed) to install the boot loader in the root partition (with the intention to chain-start that from the Windows bootloader), but during installation Yast also installed the bootloader to MBR, replacing the Windows boot loader. As said in comment #10, I managed to chain-load GRUB2 from Windows boot loader, and I want to keep it that way. I only wish a kernel update would not replace the windows bootloader again. I'm not sure what the requirements for a working configuration are (maybe a boot partition is OK, while a boot Logical Volume ist not). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=911584 --- Comment #19 from Michael Chang --- If no one objects, I'll push the patch in test package (comment#2) to Steffen and close this one. -- You are receiving this mail because: You are on the CC list for the bug.