[Bug 997641] New: Unable to mount root on boot
http://bugzilla.suse.com/show_bug.cgi?id=997641 Bug ID: 997641 Summary: Unable to mount root on boot Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: adrian@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Using openSUSE Leap 42.2, but IIRC also with SLE 12 SP2 on other hardware, I am unable to boot. The root filesystem can't be mounted in the initrd, the message is "/dev/sda2 or /sysroot is busy" (written out of my head). A manual mount is indeed failing as well. I can boot when I remove the root=UUID=.... parameter in grub. However, the used UUID there is the same as in /dev/disk/by-uuid/ The setup is simple, just two paritions on my SSD in my notebook. Not sure where to look next, any hint? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=997641
http://bugzilla.suse.com/show_bug.cgi?id=997641#c1
--- Comment #1 from Takashi Iwai
http://bugzilla.suse.com/show_bug.cgi?id=997641
http://bugzilla.suse.com/show_bug.cgi?id=997641#c2
Takashi Iwai
http://bugzilla.suse.com/show_bug.cgi?id=997641
http://bugzilla.suse.com/show_bug.cgi?id=997641#c3
--- Comment #3 from Adrian Schröter
http://bugzilla.suse.com/show_bug.cgi?id=997641
http://bugzilla.suse.com/show_bug.cgi?id=997641#c4
Takashi Iwai
http://bugzilla.suse.com/show_bug.cgi?id=997641
http://bugzilla.suse.com/show_bug.cgi?id=997641#c5
Takashi Iwai
http://bugzilla.suse.com/show_bug.cgi?id=997641
http://bugzilla.suse.com/show_bug.cgi?id=997641#c6
Thomas Blume
http://bugzilla.suse.com/show_bug.cgi?id=997641
http://bugzilla.suse.com/show_bug.cgi?id=997641#c7
--- Comment #7 from Adrian Schröter
http://bugzilla.suse.com/show_bug.cgi?id=997641
http://bugzilla.suse.com/show_bug.cgi?id=997641#c8
--- Comment #8 from Adrian Schröter
http://bugzilla.suse.com/show_bug.cgi?id=997641
Adrian Schröter
http://bugzilla.suse.com/show_bug.cgi?id=997641
http://bugzilla.suse.com/show_bug.cgi?id=997641#c9
Thomas Blume
Created attachment 692620 [details] debug file
Something is pretty strange here. The dracut command line shows 2 time the root parameter: [ 5.029445] linux-izwb dracut-cmdline[129]: Using kernel command line parameters: rd.driver.pre=virtio_pci rd.driver.pre=virtio_blk rd.driver.pre=loop rd.driver.pre=binfmt_misc rd.driver.pre=xennet rd.driver.pre=xenblk rd.driver.pre=scsi_dh_alua rd.driver.pre=scsi_dh_emc rd.driver.pre=scsi_dh_rdac root=/dev/mapper/PLEXTOR_PX-256M5M_P02326105165_part2 rootfstype=ext4 rootflags=rw,relatime,discard,data=ordered BOOT_IMAGE=/boot/vmlinuz-4.7.4-1.g6a5bbb1-default root=UUID=4d9f3330-17e6-4bbd-a92c-d2f4c0b48e91 quiet splash=silent rd.debug I guess: root=/dev/mapper/PLEXTOR_PX-256M5M_P02326105165_part2 isn't the desired one. Could you attach the content of /var/log/YaST2/? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=997641
http://bugzilla.suse.com/show_bug.cgi?id=997641#c10
--- Comment #10 from Adrian Schröter
http://bugzilla.suse.com/show_bug.cgi?id=997641
Adrian Schröter
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.
http://bugzilla.suse.com/show_bug.cgi?id=997641
http://bugzilla.suse.com/show_bug.cgi?id=997641#c16
--- Comment #16 from Adrian Schröter
http://bugzilla.suse.com/show_bug.cgi?id=997641
http://bugzilla.suse.com/show_bug.cgi?id=997641#c17
--- Comment #17 from Thomas Blume
JFYI, I have it installed, but according to "systemctl status multipathd" it was disabled.
That doesn't really matter in your case. The multipath device was already set up in the initrd and a path check for a local disk is redundant anyway. The problem is apparently that /dev/disk/by-uuid didn't point to the multipath device at installation time. I guess this is a race condition, because I couldn't reproduce in my local vm. bug#986734 shows pretty similar symptoms. If you still can reproduce the issue, it would be good if you can test wheter bug 986734 comment#166 fixes it. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=997641
http://bugzilla.suse.com/show_bug.cgi?id=997641#c18
Franck Bui
http://bugzilla.suse.com/show_bug.cgi?id=997641
http://bugzilla.suse.com/show_bug.cgi?id=997641#c19
Franck Bui
participants (1)
-
bugzilla_noreply@novell.com