mountall fails with "mountall: fsck /home [369] terminated with status 8"/ Non-existent device - Possible race ?
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mountall (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: e2fsprogs
On each boot I get the following message from fsck, which interrupts the boot.
fsck.ext4: No such file or directory while trying to open /dev/disk/
Possibly non-existent device?
mountall: fsck /home [369] terminated with status 8
mountall: Unrecoverable fsck error: /home
If I press 'I' the the boot continues and the device is correctly mounted.
mountall doesn't fail when:
- quiet splash is not present on the boot command line
- mountall verbose mode is on (-v to the exec line in /etc/init/
- small delay before starting mountall (sleep .1 before exec line in /etc/init/
$ ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 2011-02-04 00:05 0cf40974-
lrwxrwxrwx 1 root root 10 2011-02-04 00:05 30fc9e49-
lrwxrwxrwx 1 root root 10 2011-02-04 00:05 87833b0f-
lrwxrwxrwx 1 root root 10 2011-02-04 00:05 a14daa42-
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: e2fsprogs 1.41.14-1ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-1-generic x86_64
Architecture: amd64
Date: Fri Feb 4 00:09:53 2011
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, user)
LANG=en_US.UTF-8
LC_MESSAGES=
SHELL=/bin/bash
SourcePackage: e2fsprogs
My guess is that /dev/disk/by-uuid wasn't properly populated at the time that fsck was run.
I've always thought the /dev/disk/by-uuid was a horribly bug, and its use should be stamped out. Fortunately with the blkid library now being incorporated into util-linux-ng, and this is what is being used in all major distributions, it *can* be stamped out. Don't use /dev/disk/by-uuid; it's horribly fragile and not guaranteed to work all the time.
The far better thing to use is to put the following in /etc/fstab instead:
UUID=a14daa42- 496b-425a- bc9f-d59cca6a02 16
Its use is documented in the fstab man page.
-- Ted