Am 30.07.2011 16:01, schrieb Michael Mol: > On Sat, Jul 30, 2011 at 5:42 AM, Florian Philipp <li...@binarywings.net> > wrote: >> Hello list! >> >> I've noticed the following in my rc.log file: >> [file system mounting ...] >> opt: clean, 3127/6496 files, 108510/209920 blocks >> fsck.ext4: Unable to resolve »LABEL=backup« >> * Operational error >> >> The backup disk is the only one (besides boot and root) which is mounted >> by label. After booting, I find that the backup disk was mounted >> correctly. If I then try to run >> `fsck.ext4 "LABEL=backup"`, it works as expected. >> >> Does anyone have an explanation for this? > > Could it be that the volume 'backup' is on isn't available yet? (i.e. > brought up by lvm later in the boot process) >
I thought of this, as well, especially because it is a firewire disk. But then why is it mounted correctly? Regards, Florian Philipp
signature.asc
Description: OpenPGP digital signature
