https://bugzilla.novell.com/show_bug.cgi?id=811830 https://bugzilla.novell.com/show_bug.cgi?id=811830#c1 Arvin Schnell changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aschnell@suse.com, | |snwint@suse.com AssignedTo|aschnell@suse.com |nfbrown@suse.com --- Comment #1 from Arvin Schnell 2013-03-27 09:29:32 UTC --- Neil, please have a look at problem 1. The logs show that md0 was correctly created on sda1 and sdb1. /proc/mdstat during installation also looks good. Problem 2 is for Steffen Winterfeldt. Problem 3 could also be for Neil. mdadm was called with chunk=32, but the chunk size is not meaningful for RAID1 (according to mdadm man-page). So maybe not a bug. Problem 4 is completely unclear to me. -- 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=811830 https://bugzilla.novell.com/show_bug.cgi?id=811830#c3 Andrey Borzenkov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arvidjaar@gmail.com --- Comment #3 from Andrey Borzenkov 2013-03-27 16:40:58 UTC --- (In reply to comment #1)

Problem 2 is for Steffen Winterfeldt.

Note that the only configuration where it is safe to do is embedding grub2 in post-MBR gap (or in case of UEFI where it goes to ESP anyway). Anything else is error prone. -- 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=811830 https://bugzilla.novell.com/show_bug.cgi?id=811830#c5 --- Comment #5 from Andrey Borzenkov 2013-03-27 17:12:46 UTC --- (In reply to comment #4)

I think problem 2 is actually for Michael (grub2-install).

How can grub-install know that it should install on multiple devices? We can discuss whether "grub-install /dev/sda /dev/sdb" makes sense (IMHO it does not add anything in this case), but YaST2 still has to invoke it with correct parameters. It is YaST2 task to build list of devices where grub2 has to be installed. Does it build such list now? And if it has this list, it can simply call "grub-install /dev/sda", "grub-install /dev/sdb" for every device in list. -- 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=811830 https://bugzilla.novell.com/show_bug.cgi?id=811830#c7 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #7 from Neil Brown 2013-03-28 04:28:51 UTC --- The answer to problem 2 is definitely that 'chunk size' isn't meaningful for RAID1, so it is ignored. The chunk size you see listed as 64M is the "bitmap chunk size", which is how much of the array corresponds to each bit in the write-intent bitmap. It is unfortunate that we used the name "chunk size" for both :-( Problem 1 is strange. I can't see a good reason why one array would come through degraded while the others survived. Have you tried multiple times or did this only happen once? I'll see if I can reproduce it. If I can it shouldn't be hard to isolate the problem. -- 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=811830 https://bugzilla.novell.com/show_bug.cgi?id=811830#c9 Neil Brown changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nfbrown@suse.com AssignedTo|nfbrown@suse.com |mchang@suse.com --- Comment #9 from Neil Brown 2013-04-29 04:52:42 UTC --- I just tried an install from the 12.3 dvd with your partitioning in a KVM instance, and it worked perfectly :-( Looking at the "--examine" output it strongly suggests that initial resync did complete. In any case, the only way that grub files could be missing from sda1 is if sda1 were removed before the grub files were written. The most likely explanation is that sda1 reported a write error sometime before the grub files were installed onto /boot. Maybe if there are kernel logs in the same place as the yast logs, they might show something. Possibly yast could check that no arrays are degraded before rebooting... I think Problem 2 - grub only being install on one MBR, not both, is the main problem here. So reassigning to Michael for 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=811830 https://bugzilla.novell.com/show_bug.cgi?id=811830#c11 --- Comment #11 from Michael Chang 2013-05-08 11:10:24 UTC --- (In reply to comment #10)

The problem number 2 instead (grub2 only installed onto sda MBR) was present in an identical way.

I couldn't reproduce this problem when testing perl bootloader of this pull request. https://github.com/openSUSE/perl-bootloader/pull/16/commits Using sw raid1 created by mdadm on /dev/vda1 and /dev/vdb1, grub2 was successfully installed to /dev/vda and /dev/vdb respectively. Those commits are not likely to fix this problem directly so I'm surprised about the result. -- 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=811830 https://bugzilla.novell.com/show_bug.cgi?id=811830#c13 --- Comment #13 from Michael Chang 2013-05-09 03:51:55 UTC --- Created an attachment (id=538494) --> (http://bugzilla.novell.com/attachment.cgi?id=538494) /boot/grub2/device.map requested by comment#12 -- 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=811830 https://bugzilla.novell.com/show_bug.cgi?id=811830#c Michael Chang changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #538494|application/octet-stream |text/plain mime type| | -- 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=811830 https://bugzilla.novell.com/show_bug.cgi?id=811830#c16 --- Comment #16 from Andrey Borzenkov 2013-05-09 05:41:53 UTC --- (In reply to comment #14)

Created an attachment (id=538495) --> (http://bugzilla.novell.com/attachment.cgi?id=538495) [details] /etc/default/grub_installdevice

The main difference is that your grub_installdevice contains already /dev/vda and /dev/vdb and grub_installdevice of reported contains just (hd0). But perl-Bootloader does not change this file - so I guess something has changed in YaST2 bootloader module. -- 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=811830 https://bugzilla.novell.com/show_bug.cgi?id=811830#c18 --- Comment #18 from Andrey Borzenkov 2013-05-09 08:20:26 UTC --- (In reply to comment #17)

It could be. My impression is YaST seems to not offer "Enable Redundancy for MD Array" loader location options for grub2 before but this time I notice it appeared in yast2 bootloader.

But as always my memory could serve me wrong ..

I made installation of 12.3 on MD1 with default settings and bootloader was installed on the first disk only and grub_installdevice contained (hd0) only. Looking in y2log: 2013-05-09 02:43:56 <1> 10.0.2.15(2962) [YCP] BootCommon.ycp:1252 boot_md_mbr includes 2 disks: ["/dev/sda", "/dev/sdb"] ... 2013-05-09 02:43:56 <1> 10.0.2.15(2962) [YCP] bootloader/routines/lib_iface.ycp:136 Storing global settings $["activate":"true", "append":" nomodeset resume=/dev/md0 splash=silent quiet showopts", "append_failsafe":"showopts apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe", "boot_boot":"false", "boot_extended":"false", "boot_mbr":"true", "boot_root":"false", "default":"0", "distributor":"openSUSE 12.3", "generic_mbr":"true", "gfxmode":"auto", "gfxtheme":"/boot/grub2/themes/openSUSE/theme.txt", "os_prober":"true", "terminal":"gfxterm", "timeout":"8", "vgamode":""] boot_md_mbr disappeared. This is due to this modules/BootCommon.ycp:Save if (VerifyMDArray()) { if ((enable_md_array_redundancy != true) && (haskey(my_globals, "boot_md_mbr"))) my_globals = remove(my_globals, "boot_md_mbr"); if ((enable_md_array_redundancy == true ) && (!haskey(my_globals, "boot_md_mbr"))) my_globals["boot_md_mbr"] = BootStorage::addMDSettingsToGlobals(); } else { if (haskey(globals, "boot_md_mbr")) my_globals = remove(my_globals, "boot_md_mbr"); } enable_md_array_redundancy is set only by UI as far as I can tell and UI is present in GRUB only. ./include/bootloader/grub/options.ycp: BootCommon::enable_md_array_redundancy = (boolean)UI::QueryWidget(`id("enable_redundancy"), `Value);

From perl-Bootloader side it should work already, but YaST2 part is missing.

-- 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=811830 https://bugzilla.novell.com/show_bug.cgi?id=811830#c20 --- Comment #20 from Andrey Borzenkov 2013-05-10 04:37:24 UTC --- (In reply to comment #19)

dangerous. pbl just calls grub2-install two times. If grub2 could be embedded in both cases, that's OK. If grub2 could *not* be embedded, openSUSE forces it to use blocklists.

Correction - grub2 should refuse installation if it cannot be embedded even with "--force --skip-fs-probe" as long as /boot/grub2 is on MD raid. -- 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=811830 https://bugzilla.novell.com/show_bug.cgi?id=811830#c22 --- Comment #22 from Michael Chang 2013-05-10 09:27:33 UTC --- (In reply to comment #20)

(In reply to comment #19)

...

dangerous. pbl just calls grub2-install two times. If grub2 could be embedded in both cases, that's OK. If grub2 could *not* be embedded, openSUSE forces it to use blocklists.

Correction - grub2 should refuse installation if it cannot be embedded even with "--force --skip-fs-probe" as long as /boot/grub2 is on MD raid.

Agree with you and yes. :) -- 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=811830 https://bugzilla.novell.com/show_bug.cgi?id=811830#c24 --- Comment #24 from Marco M. 2013-05-16 15:28:56 UTC --- (In reply to comment #10)

(In reply to comment #9)

...

I just tried an install from the 12.3 dvd with your partitioning in a KVM instance, and it worked perfectly :-(

:-( this is completely unexpeted to me! So vmware is involved in the problem! I'm very sorry, i was absolutely sure the problem was not hw related. In the next few days i'll do a test on a real hardware (or on kvm) and i'll post the results.

I did a test using kvm and i did NOT suffer the problem n. 1, so Neil's conclusion is definitely double confirmed. Problem N.1 is correlated to vmware. I'm now trying to figure out why opensuse 12.3 has this behavior while opensuse 12.2 works fine on exactly the same virtual hardware. I would like to see the kernel log while the installation goes on, but on the virtual terminal 4 I can see the kernel log only until yast is started. After that nothing more is logged. Could you suggest a way to see kernel log during the whole installation process ? -- 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=811830 https://bugzilla.novell.com/show_bug.cgi?id=811830#c26 --- Comment #26 from Marco M. 2013-06-26 02:24:16 UTC --- (In reply to comment #25)

Hi, I experience the same issue with some differences: 2 x 3T discs

sda1, sdb1 => md126 /boot sda2, sdb2 => mds127 LVM LVM: /, /home, etc.

During the setup at the partition step and the end it complain that there is no /boot partition (well, yes there is one I have set md126 format ext4 and mounted on /boot) I have tried to forget this error and let setup finish (so I can fix the boot after).

I also experienced a similar issue, and the problem resided in the disks that were already partitioned and with raid volume already created. That situation causes confusion in yast which seems to prefer fully zeroed disks. In your case, when you started yast to install the SO, were your disks already partitioned ? -- 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=811830 https://bugzilla.novell.com/show_bug.cgi?id=811830#c27 --- Comment #27 from Marco M. 2013-10-16 15:55:32 UTC --- The problem is still present in opensuse 13.1 rc1 -- 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=811830 https://bugzilla.novell.com/show_bug.cgi?id=811830#c29 --- Comment #29 from Marco M. 2013-10-16 21:38:53 UTC --- (In reply to comment #28)

Which one? Bug report lists 4 problems. Which one is still present?

The problem number 2 is still present in 13.1 rc1. Grub2 has been installed only on the mbr of the first disk, leaving the system in an unbootable state if the first disk of the raid volume fails. (other problems were assessed and they weren't real bugs) thanks to the forum, i've just discovered this bugs: https://bugzilla.novell.com/show_bug.cgi?id=842919 which looks very connected to this one -- 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=811830 https://bugzilla.novell.com/show_bug.cgi?id=811830#c31 --- Comment #31 from Marco M. 2013-11-26 18:17:37 UTC --- The problem is still present in 13.1 final release Furthermore i discovered that systemd is NOT able to boot a system with /boot on a raid1 partition with a failing disk. It complains it cannot mount /boot and it is NOT able to launch the emergency shell (in 12.3 systemd can boot the system with a degraded raid1 without any problem) I think this is a different bug, I'm going to further investigate and to open a different bug -- 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=811830 https://bugzilla.novell.com/show_bug.cgi?id=811830#c33 --- Comment #33 from Marco M. 2013-11-28 09:40:21 UTC --- (In reply to comment #32)

Hi Marco, please check bug 832501 to see if it matches your "degraded RAID1 for /boot" issue.

Hi Neil, yes the bug you mentioned looks very similar to the issue i'm facing. I posted some information in that bug. Thank you. -- 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=811830 https://bugzilla.novell.com/show_bug.cgi?id=811830#c35 --- Comment #35 from Steffen Winterfeldt 2014-02-21 14:44:59 CET --- No. Unchecked private flag. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=811830 --- Comment #37 from Andrei Borzenkov --- Created attachment 609575 --> http://bugzilla.novell.com/attachment.cgi?id=609575&action=edit Screenshot of bootloader settings during installation (In reply to Marco M. from comment #36)

The bug is tragically still present in 13.2 beta1 and the workaround of manually install grub2 on the second mbr does not work anymore! The boot stops because can't find the root file system (can't understand why).

I tested installation of 13.2 RC1 with manually created /boot, swap and / on RAID1. yast correctly detected this but defaulted to installing bootloader on the first disk only (see screenshot). If you check "Enable redundancy for MD array" it installs bootloader on both disks.

At this point what do you suggest ? Do i need to open a new bug ?

I think yes. At this point the question is whether current behavior is intentional or not. This bug became rather long and confusing. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=811830 --- Comment #39 from Marco M. --- In my case the "enable redundancy for md array" option has never appeared! (tested in 12.3, 13.1 and 13.2 beta1) I attached a Screenshot showing the bootloader options. I tried to manually install grub2 on sdb, but the system was still unable to boot with sda pulled out. The boot process stops in the initrmfs phase, before root mounting, saying it can't mount root. A very limited emergency shell comes out after a couple of minute and, from this shell, i was able to see that the raid arrays were available (degraded but available) and the lvm logical volumes for root var and home were ready, so i can't understand why it was not able to complete the boot phase. I suspect that also the bug 832501 could be still present. What do you think ? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=811830 --- Comment #41 from Neil Brown --- Can you attach the initrd for the system that fails to boot if one device is missing please. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=811830 --- Comment #43 from Marco M. --- I'm sorry, the initrd is too big, I can't attach it -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=811830 --- Comment #45 from Neil Brown --- Thanks for the initrd - successfully downloaded it. It'll be a little while before I have a change to look at it and comment. -- You are receiving this mail because: You are on the CC list for the bug.