https://bugzilla.novell.com/show_bug.cgi?id=785226 https://bugzilla.novell.com/show_bug.cgi?id=785226#c2 --- Comment #2 from Frank Ansari 2012-10-16 07:47:51 UTC --- Created an attachment (id=509652) --> (http://bugzilla.novell.com/attachment.cgi?id=509652) by-id -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=785226 https://bugzilla.novell.com/show_bug.cgi?id=785226#c4 --- Comment #4 from Frank Ansari 2012-10-16 07:48:34 UTC --- Created an attachment (id=509655) --> (http://bugzilla.novell.com/attachment.cgi?id=509655) grub.cfg -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=785226 https://bugzilla.novell.com/show_bug.cgi?id=785226#c Frank Ansari changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P1 - Urgent -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=785226 https://bugzilla.novell.com/show_bug.cgi?id=785226#c5 Alexander van Kaam changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |a.vankaam@chello.nl --- Comment #5 from Alexander van Kaam 2012-10-16 08:53:30 UTC --- I am not sure if this is of any help or not I had a similar weird issues after the 3.4.11-2.16 update (and several other items got updated at that time) my system has 2 identical HDD (sda and sdb), after the patch run the system did boot but all sorts of weird things where happening (no sound, no network, things like that), after searching a bit more I noticed that grub2 had mounted sdb2 instead of sda2 as / and thus booted still the previous kernel which was on the sdb hdd. sda1 sda3 and sda4 where mounted as normal. only way I could solve this was yast, booloader, set it to boot from root partition (this was checked before but was not now) and also check custom boot partition sda2. after that it rebooted with sda2. somewhere during that big patch round something got grub2 mixed up with hdd, I can only imagine what this does with a raid setup :/ -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=785226 https://bugzilla.novell.com/show_bug.cgi?id=785226#c7 --- Comment #7 from Frank Ansari 2012-10-16 12:39:08 UTC --- This issue has nothing todo with the grub.cfg! Regardless what I put in this file or when I even remove it completely the error message is always the same. Seems that the bootloader has some hardcoded path where it looks for the *.mod files and config. And if this path is wrong (as it seems to be) nothing is working. How can we fix this? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=785226 https://bugzilla.novell.com/show_bug.cgi?id=785226#c9 --- Comment #9 from Michael Chang 2012-10-17 06:23:26 UTC --- (In reply to comment #7)

Seems that the bootloader has some hardcoded path where it looks for the *.mod files and config. And if this path is wrong (as it seems to be) nothing is working.

The prefix is hardcoded to core.img when creating it by grub2-mkimage, however on i386-pc it's LZMA compressed so you cannot observe the hardcoded path in it by hexdump -C or other means.

How can we fix this?

There's an --compression=none to not use compression, but unfortunately that option is not work for i386-pc, in any case it would be forced to use LZMA compression. Thus I would suggest to create the image with other format (i386-multiboot) which --compression=none should work on, and observe the prefix is correctly coded in it or not via hexdump. Before trying above approach, it'd be better to know the parameters from the below outputs $ grub2-probe --target=drive /boot $ grub2-probe --target=fs /boot $ grub2-probe --target=partmap /boot $ grub2-probe --target=abstraction /boot Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=785226 https://bugzilla.novell.com/show_bug.cgi?id=785226#c10 --- Comment #10 from Frank Ansari 2012-10-17 12:21:00 UTC --- This is my output: (mduuid/7ecdf7e0b684abb0776c2c25004bd7b2) ext2 msdos msdos msdos msdos diskfilter mdraid09 diskfilter mdraid09 What should I do next? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=785226 https://bugzilla.novell.com/show_bug.cgi?id=785226#c12 --- Comment #12 from Michael Chang 2012-10-18 05:00:19 UTC --- Could you try set prefix and root in rescue mode like this set prefix=(mduuid/7ecdf7e0b684abb0776c2c25004bd7b2)/grub2 set root=mduuid/7ecdf7e0b684abb0776c2c25004bd7b2 insmod normal to see if normal module could be inserted. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=785226 https://bugzilla.novell.com/show_bug.cgi?id=785226#c14 --- Comment #14 from Michael Chang 2012-10-18 05:10:14 UTC --- Try to create a multiboot image (non-compressed) this way and use "hexdump -C" to examine the resultant image. It looks to me that prefix was written to it without problem. $ grub2-mkimage -d /boot/grub2/i386-pc -O i386-multiboot --output=/tmp/grub2.elf --prefix="(mduuid/7ecdf7e0b684abb0776c2c25004bd7b2)/grub2" biosdisk ext2 part_msdos diskfilter mdraid09 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=785226 https://bugzilla.novell.com/show_bug.cgi?id=785226#c16 --- Comment #16 from Frank Ansari 2012-10-18 07:36:40 UTC --- (In reply to comment #13)

(In reply to comment #8)

...

prefix=(mduuid/7e...b2/grub2

The prefix format is incorrect, the closing ')' was missing. It should be of form like (device)path.

This was just a type of mine. The closeing ')' was there of course. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=785226 https://bugzilla.novell.com/show_bug.cgi?id=785226#c18 --- Comment #18 from Michael Chang 2012-10-18 11:01:15 UTC --- Frank, In rescue mode, is there any output by ls? grub rescue> ls And is it possible to get the output of grub rescue> ls (md/1) grub rescue> ls (md/1)/ And did the set command output like below exactly? grub rescue> set prefix=(mduuid/7ecdf7e0b684abb0776c2c25004bd7b2)/grub2 root=mduuid/7ecdf7e0b684abb0776c2c25004bd7b2 I've set software raid installation mimic your setup, things all went fine so far. I will try to update the system to see if could catch the same problem as yours. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=785226 https://bugzilla.novell.com/show_bug.cgi?id=785226#c20 --- Comment #20 from Frank Ansari 2012-10-18 12:27:58 UTC --- ls (md/md2) (md/md1) (md/md3) (hd0) (hd0,msdos5) (hd0,msdos4) (hd0,msdos3) (hd0,msdos2) (hd0,msdos1) ls (md/1) error: disk `md/1' not found. ls (md/1)/ error: disk `md/1' not found. set prefix=(mduuid/7ecdf7e0b684abb0776c2c25004bd7b2)/grub2 root=mduuid/7ecdf7e0b684abb0776c2c25004bd7b2 insmod (md/1)/grub2/i386-pc/normal.mod error: disk `md/1' not found. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=785226 https://bugzilla.novell.com/show_bug.cgi?id=785226#c22 --- Comment #22 from Frank Ansari 2012-10-18 12:59:56 UTC --- Created an attachment (id=510046) --> (http://bugzilla.novell.com/attachment.cgi?id=510046) mdadm info -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=785226 https://bugzilla.novell.com/show_bug.cgi?id=785226#c24 --- Comment #24 from Michael Chang 2012-10-19 06:43:00 UTC --- (In reply to comment #23)

I had problems too after updating a server at Hetzner today.

I saved the errors when I did a zypper up, maybe it helps: Perl-Bootloader: 2012-10-18 10:30:07 ERROR: Command '/usr/sbin/grub2-install --force --skip-fs-probe /dev/sda2 >/var/log/YaST2/y2log_bootloader 2>&1' failed with code 256 and output: /usr/sbin/grub2-bios-setup: warning: File system `ext2' doesn't support embedding. /usr/sbin/grub2-bios-setup: error: embedding is not possible, but this is required for RAID and LVM install.

For raid you'd better use mbr (/dev/sda). Because only when core image (core.img) loaded could provide access to the raid device. It has to be embedded in raw consecutive sectors not managed(mapped) by raid. The mbr hole (the sectors falls between mbr and starting of first partition) is the only right place for it. That error was complaining about that. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=785226 https://bugzilla.novell.com/show_bug.cgi?id=785226#c26 --- Comment #26 from Michael Chang 2012-10-19 10:08:09 UTC --- This seems to be 0.9 metadata specific problem, as your mdadm info and Richard's report are all on 0.9. They are handled by different grub2 modules (mdraid09.mod mdraid1x.mod). I can't reproduce on either 0.9 or 1.0 metadata and no idea on how to fix. You can go back to grub legacy. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=785226 https://bugzilla.novell.com/show_bug.cgi?id=785226#c28 Jeffrey Cheung changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |CLOSED CC| |jcheung@suse.com InfoProvider|mail@frank-ansari.de | Resolution| |WONTFIX --- Comment #28 from Jeffrey Cheung 2014-02-11 04:00:56 UTC --- With the release of the gnumeric on January 27th, 2014 the SUSE sponsored maintenance of openSUSE 12.2 has ended. openSUSE 12.2 is now officially discontinued and out of support by SUSE. If encountered the same problem, please create a new bugzilla againist openSUSE 13.1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.