| 1 |
On Sun, Jul 31, 2011 at 5:06 AM, Florian Philipp <lists@×××××××××××.net> wrote: |
| 2 |
> Am 30.07.2011 16:01, schrieb Michael Mol: |
| 3 |
>> On Sat, Jul 30, 2011 at 5:42 AM, Florian Philipp <lists@×××××××××××.net> wrote: |
| 4 |
>>> Hello list! |
| 5 |
>>> |
| 6 |
>>> I've noticed the following in my rc.log file: |
| 7 |
>>> [file system mounting ...] |
| 8 |
>>> opt: clean, 3127/6496 files, 108510/209920 blocks |
| 9 |
>>> fsck.ext4: Unable to resolve »LABEL=backup« |
| 10 |
>>> * Operational error |
| 11 |
>>> |
| 12 |
>>> The backup disk is the only one (besides boot and root) which is mounted |
| 13 |
>>> by label. After booting, I find that the backup disk was mounted |
| 14 |
>>> correctly. If I then try to run |
| 15 |
>>> `fsck.ext4 "LABEL=backup"`, it works as expected. |
| 16 |
>>> |
| 17 |
>>> Does anyone have an explanation for this? |
| 18 |
>> |
| 19 |
>> Could it be that the volume 'backup' is on isn't available yet? (i.e. |
| 20 |
>> brought up by lvm later in the boot process) |
| 21 |
>> |
| 22 |
> |
| 23 |
> I thought of this, as well, especially because it is a firewire disk. |
| 24 |
> But then why is it mounted correctly? |
| 25 |
|
| 26 |
It might be brought up by an automounter later on. You might try |
| 27 |
removing the entry from fstab, and see if it still gets mounted. |
| 28 |
|
| 29 |
-- |
| 30 |
:wq |
Archives