-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
В Thu, 28 May 2015 11:41:27 -0700
Roger Binns rog...@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
Am 28.05.2015 um 07:24 schrieb Martin Pitt:
Reindl Harald [2015-05-28 1:00 +0200]:
Am 27.05.2015 um 23:03 schrieb Roger Binns:
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)
sounds like
On Thu, May 28, 2015 at 8:46 AM, Andrei Borzenkov arvidj...@gmail.com wrote:
Apr 24 14:18:41 workstation systemd[1]: Job
dev-disk-by\x2duuid-3ff68715\x2d0daa\x2d4e44\x2d8de2\x2d0997f36d8ab6.device/start
timed out.
systemd times out waiting for UUID alias. Neither sda1 nor sdb1 are
-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
В Thu, 28 May 2015 08:27:30 +0300
Andrei Borzenkov arvidj...@gmail.com пишет:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
В Wed, 27 May 2015 14:03:10 -0700
Roger Binns rog...@rogerbinns.com пишет:
-BEGIN PGP SIGNED MESSAGE-
-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
Reindl Harald [2015-05-28 1:00 +0200]:
Am 27.05.2015 um 23:03 schrieb Roger Binns:
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)
sounds like
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
В Thu, 28 May 2015 08:34:07 +0300
Andrei Borzenkov arvidj...@gmail.com пишет:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
В Thu, 28 May 2015 08:27:30 +0300
Andrei Borzenkov arvidj...@gmail.com пишет:
-BEGIN PGP SIGNED MESSAGE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
В Wed, 27 May 2015 14:03:10 -0700
Roger Binns rog...@rogerbinns.com пишет:
-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
Am 27.05.2015 um 23:03 schrieb Roger Binns:
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)
sounds like https://bugzilla.redhat.com/show_bug.cgi?id=1217969
signature.asc
Description: OpenPGP
12 matches
Mail list logo