-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/28/2015 08:40 PM, Andrei Borzenkov wrote:
Try booting with udev.log-priority=debug
rd.udev.log-priority=debug, this may give some hint what happens.
Wow did that produce a lot of output!
No. You can set nofail in which case boot will
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My immediate problem is a boot failure with systemd on Ubuntu 15.04
because of fsck issues (systemd timing out fscking something it
shouldn't). Prior Ubuntu releases and upstart work just fine. Martin
Pitt @ Ubuntu said I should bring the issue here
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/27/2015 04:00 PM, Reindl Harald wrote:
sounds like https://bugzilla.redhat.com/show_bug.cgi?id=1217969
Thanks for the pointer. I think my situation is different but it does
show that I should test with fsck.mode=skip and hopefully systemd
