http://bugzilla.suse.com/show_bug.cgi?id=1059169 http://bugzilla.suse.com/show_bug.cgi?id=1059169#c5 Thomas Blume <thomas.blume@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jjletho67-esus@yahoo.it, | |thomas.blume@suse.com Flags| |needinfo?(jjletho67-esus@ya | |hoo.it) --- Comment #5 from Thomas Blume <thomas.blume@suse.com> --- (In reply to Marco M. from comment #3)

Created attachment 745020 [details] file /etc/fstab

/etc/fstab on the system where I experienced and reproduced the issue.

There seems to be a problem with the softraid device naming. The rdsosreport shows 2 softraid devices, md0 and md2: --> [ 33.259180] linux-owe6 mdadm[784]: mdadm: started array /dev/md2 [ 33.386220] linux-owe6 kernel: md2: detected capacity change from 0 to 16104947712 [ 33.261113] linux-owe6 systemd[1]: Started Activate md array even though degraded. [ 33.263144] linux-owe6 mdadm[785]: mdadm: started array /dev/md0 [ 33.390096] linux-owe6 kernel: md0: detected capacity change from 0 to 1077870592 [ 33.266270] linux-owe6 systemd[1]: Started Activate md array even though degraded. [ 33.511023] linux-owe6 systemd[1]: Stopped Timer to wait for more drives before activating degraded array.. [...] --< but the boot parameters show a resume device on /dev/md1: --> BOOT_IMAGE=/vmlinuz-4.4.87-25-default root=/dev/mapper/systemVG-rootLV ro resume=/dev/md1 showopts --< Since dracut cannot find md1, the boot fails. There is no error message referring to md1, so it seems that this device name is not present in the mdadm.conf file of the initrd or the devices where md1 resides on are not present. Can you find the devicename md1 in /etc/mdadm.conf of your running system? If so, what are the device names from which md1 should be assembled? -- You are receiving this mail because: You are on the CC list for the bug.