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:
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