Hello, just to prevent people from having an unbootable system like I did: it seems that the recent update of mdadm to 3.3 no longer scans metadata at boot if you use FakeRAID from Intel (IMSM or Intel Matrix Storage Manager), therefore the RAID is not assembled and the root device is not found (drops to emergency shell). I found this the hard way when my RAID 1 set was not assembled and the system could not boot. In this case checking /proc/mdstat only shows the metadata device (like /dev/md/imsm0) and not the RAID: md127 : inactive sda[1](S) sdb[0](S) 5928 blocks super external:imsm A workaround is to manually scan the metadata and assemble in the emergency shell: $ mdadm -I /dev/<metadata_device> [on my system it's /dev/md127; creates the RAID device node] $ mdadm --assemble --scan [partitions are also scanned and device nodes generated] Afterwards boot resumes once the emergency shell is quit, as / can be mounted. This behavior does not occur at all with mdadm 3.2 so I would suggest to lock it in place if you use it (I did). I filed https://bugzilla.novell.com/838777 just in case. -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: 6E1A4E79 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org