Mailinglist Archive: opensuse-factory (926 mails)

< Previous Next >
Re: [opensuse-factory] snapshot 20180427: Failed to mount /sysroot
Hello list,

I updated to the snapshot today and that broke something in all the initrds.
The sysroot.mount unit fails and the boot process stops. When booting into the
dracut console with `rd.shell rd.break=mount` added to the kernel command line,
I apparently found the issue.

The root file system is mounted for a file system check under /kdump/mnt0 by
the kdump-mnt0.mount unit. The sysroot.mount unit then fails.

(The log seems a bit out of order to me)

Apr 30 15:03:53 tw systemd[1]: Found device /dev/vg0/lvroot.
Apr 30 15:03:53 tw systemd[1]: Found device /dev/mapper/vg0-lvroot.
Apr 30 15:03:53 tw systemd[1]: Reached target Initrd Root Device.
Apr 30 15:03:53 tw systemd[1]: Started dracut initqueue hook.
Apr 30 15:03:53 tw systemd[1]: Reached target Remote File Systems (Pre).
Apr 30 15:03:53 tw systemd[1]: Reached target Remote File Systems.
Apr 30 15:03:53 tw systemd[1]: Starting File System Check on
/dev/mapper/vg0-lvroot...
Apr 30 15:03:53 tw systemd-fsck[573]: /dev/mapper/vg0-lvroot: recovering journal
Apr 30 15:03:53 tw systemd-fsck[573]: /dev/mapper/vg0-lvroot: clean,
609445/30367744 files, 41275075/121440256 blocks
Apr 30 15:03:53 tw systemd[1]: Started File System Check on
/dev/mapper/vg0-lvroot.
Apr 30 15:03:53 tw systemd[1]: Mounting /sysroot...
Apr 30 15:03:53 tw systemd[1]: Starting File System Check on /dev/vg0/lvroot...
Apr 30 15:03:53 tw mount[585]: mount: /sysroot: /dev/mapper/vg0-lvroot already
mounted or mount point busy.
Apr 30 15:03:53 tw systemd[1]: sysroot.mount: Mount process exited, code=exited
status=32
Apr 30 15:03:53 tw systemd[1]: sysroot.mount: Failed with result 'exit-code'.
Apr 30 15:03:53 tw systemd[1]: Failed to mount /sysroot.
Apr 30 15:03:53 tw systemd[1]: Dependency failed for Initrd Root File System.
Apr 30 15:03:53 tw systemd[1]: Dependency failed for Reload Configuration from
the Real Root.
...
some initrd.target stuff failing
...
Apr 30 15:03:53 tw systemd[1]: Reached target Initrd File Systems.
Apr 30 15:03:53 tw systemd-fsck[586]: /dev/mapper/vg0-lvroot: clean,
609445/30367744 files, 41275075/121440256 blocks
Apr 30 15:03:53 tw systemd[1]: Started File System Check on /dev/vg0/lvroot.
Apr 30 15:03:53 tw systemd[1]: Mounting /kdump/mnt0...
Apr 30 15:03:53 tw systemd[1]: Mounted /kdump/mnt0.
Apr 30 15:03:53 tw systemd[1]: Reached target Local File Systems.
Apr 30 15:03:53 tw systemd[1]: Reached target System Initialization.
Apr 30 15:03:53 tw systemd[1]: Reached target Basic System.
Apr 30 15:03:53 tw systemd[1]: Starting dracut mount hook...
Apr 30 15:03:53 tw kernel: EXT4-fs (dm-0): mounted filesystem with ordered data
mode. Opts: acl,user_xattr
Apr 30 15:03:53 tw dracut-mount[596]: Warning: Break mount

In the dracut console I can then unmount the root device, redo the mount and
restart a failed service

umount /dev/vg0/lvroot
systemctl restart sysroot.mount
systemctl restart initrd-parse-etc

after which exiting the dracut console twice (second one for switch_root step)
continues the boot into a seemingly running system. The log then shows that the
kdump-mnt0.mount failed

mount: /kdump/mnt0: /dev/mapper/vg0-lvroot already mounted on /sysroot.

When I had a system running, I disabled kdump with yast2-kdump and build a new
initrd with dracut -f, but that didn't help.

I actually have a very similar issue (cannot mount root during boot) on a Void
Linux box that I did not debug yet, because that machine still has some older,
working initrd.

Any ideas? If you need further information, I'll try to provide it.

Cheers

PS: I think the reason that all my kernels broke is that xfsprogs' posttrans
script rebuild all versions that were present. Could this have been prevented
in some way?

--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups