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