http://bugzilla.opensuse.org/show_bug.cgi?id=1017695 Cedric Simon changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|openSuse 42..2: Boot on |openSuse 42.2: Boot on |broken RAID 1 with missing |broken RAID 1 with missing |disk fails. Looks linked to |disk fails. Looks linked to |dracut premount hook script |dracut premount hook script |(start job running with |(start job running with |nolimit timeout) |nolimit timeout) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1017695 Cedric Simon changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on|1010852 | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1017695 http://bugzilla.opensuse.org/show_bug.cgi?id=1017695#c3 --- Comment #3 from Cedric Simon --- I am gone cry.... Looks like 2nd (empty) disk and waitdev parameter do NOT solve. I think that some way I got the array broken and did test with a (already broken) RAID disk... So issue is still present: I am not able to boot completely openSuse 42.2 with a system on RAID1 with missing, new, or damaged disk. I also tested specifying RAID devices on command line: linux .... root=/dev/md1 md=1 /dev/sda2,/dev/sdb2 (see picture), but did not help. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1017695 http://bugzilla.opensuse.org/show_bug.cgi?id=1017695#c5 --- Comment #5 from Cedric Simon --- Created attachment 708156 --> http://bugzilla.opensuse.org/attachment.cgi?id=708156&action=edit Boot screen after specifying RAID devices in GRUB2 line -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1017695 http://bugzilla.opensuse.org/show_bug.cgi?id=1017695#c7 Andrei Borzenkov changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED Assignee|bnc-team-screening@forge.pr |hare@suse.com |ovo.novell.com | --- Comment #7 from Andrei Borzenkov --- The problem seems to be this patch Fri Oct 14 14:20:51 CEST 2016 - hare@suse.de - 90mdraid: Use stock MD rules to assemble RAID arrays (bsc#998860) *add 0313-90mdraid-Use-stock-MD-rules-to-assemble-RAID-arrays.patch Stock MD rules require /usr/lib/systemd/system/mdadm-last-resort@.{service,timer} to trigger start of degraded array. These are missing in initrd. Workaround is to add /etc/dracut.conf.d/mdadm.conf with content install_optional_items+=" /usr/lib/systemd/system/mdadm-last-resort@.service /usr/lib/systemd/system/mdadm-last-resort@.timer " and rebuild initrd. If system is already stuck, boot with rd.break=pre-mount and manually run "mdadm --manage --run /dev/mdX" for all mdX (root and resume). You may need to do it once more after boot for all other arrays after entering emergency mode. This is actually upstream bug. Files are missing upstream as well. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1017695 http://bugzilla.opensuse.org/show_bug.cgi?id=1017695#c13 Giacomo Comes changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |comes@naic.edu --- Comment #13 from Giacomo Comes --- I have tested the rpm from https://build.opensuse.org/project/show/home:dmolkentin:dracut:1017695 and it fixes the problem. A PC with a raid1 root disk boots successfully even with a missing disk. -- You are receiving this mail because: You are on the CC list for the bug.