http://bugzilla.suse.com/show_bug.cgi?id=997641
http://bugzilla.suse.com/show_bug.cgi?id=997641#c15
--- Comment #15 from Thomas Blume
It is actually my root device.
# fdisk -l ... Gerät Boot Anfang Ende Sektoren Größe Kn Typ /dev/mapper/PLEXTOR_PX-256M5M_P02326105165-part1 2048 4208639 4206592 2G 82 Linux Swap /dev/mapper/PLEXTOR_PX-256M5M_P02326105165-part2 * 4208640 500117503 495908864 236,5G 83 Linux
Ah, now I see the problem. You have multipathing activated which gets added to the initrd. At reboot, multipathing is taking sda and creates the multipath device: [ 5.775808] linux-izwb multipathd[180]: sda: add path (uevent) [ 5.775936] linux-izwb multipathd[180]: PLEXTOR_PX-256M5M_P02326105165: load table [0 500118192 multipath 1 retain_attached_hw_handler 0 1 1 service-time 0 1 1 8:0 1] [ 5.776078] linux-izwb multipathd[180]: PLEXTOR_PX-256M5M_P02326105165: event checker started [ 5.776218] linux-izwb multipathd[180]: sda [8:0]: path added to devmap PLEXTOR_PX-256M5M_P02326105165 But systemd still tries to access /dev/sda instead of the multipath device, which is dommed to fail: [ 5.794475] linux-izwb systemd-fsck[432]: /dev/sda2 is in use. [ 5.794524] linux-izwb systemd-fsck[432]: e2fsck: Cannot continue, aborting. [ 5.794639] linux-izwb mount[444]: mount: /dev/sda2 is already mounted or /sysroot busy Reason is most probably that the root= boot parameter and the root mount entry in /etc/fstab don't match. Normally, the installer should take care of this. -- You are receiving this mail because: You are on the CC list for the bug.