[systemd-devel] fsck, /home, btrfs, multiple partitions/drives, boot failure [Ubuntu 15.04]
arvidjaar at gmail.com
Thu May 28 20:40:20 PDT 2015
-----BEGIN PGP SIGNED MESSAGE-----
В Thu, 28 May 2015 11:41:27 -0700
Roger Binns <rogerb at rogerbinns.com> пишет:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On 05/28/2015 02:37 AM, Andrei Borzenkov wrote:
> > I was wrong here, device is opened by btrfs driver so there should
> > be no collision here. Still obviously scanning fails (and it fails
> > actively, setting ID_BTRFS_READY). This needs some debugging on
> > udev side.
> I just tried booting with fsck.mode=skip and that didn't make any
> difference, seemingly supporting your diagnosis (it being the device
> stage rather than fsck stage where the problem lies).
> Is there any more information I can gather to make progress on this
Try booting with udev.log-priority=debug rd.udev.log-priority=debug,
this may give some hint what happens.
You can also try to enable debug logging after boot (udevadm control
- -l debug) and trigger event by issuing
echo add > /sys/block/sda/sda1/uevent
> Does systemd support any flags in /etc/fstab where I can tell
> it just go ahead and mount instead of waiting for devices?
No. You can set "nofail" in which case boot will proceed and you can
mount it manually later.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
-----END PGP SIGNATURE-----
More information about the systemd-devel