1 |
On Wednesday 14 May 2014 20:29:46 Nikos Chantziaras wrote: |
2 |
> I have this weird problem where a filesystem (Ext4) refuses to mount |
3 |
> automatically after something like a power loss or forced shutdown. |
4 |
> |
5 |
> The fstab entry for it is: |
6 |
> |
7 |
> LABEL=Data /mnt/Data ext4 defaults,relatime,exec 0 2 |
8 |
> |
9 |
> During boot, this is what OpenRC tells me: |
10 |
> |
11 |
> Root: clean, 805088/6553600 files, 9129899/26214400 blocks |
12 |
> Data: recovering journal |
13 |
> Data: clean, 364344/61546496 files, 137312260/246156800 blocks [ ok ] |
14 |
> * Mounting local filesystems ... [ ok ] |
15 |
> * Remounting root filesystem read/write ... [ ok ] |
16 |
> * Remounting filesystems ... [ ok ] |
17 |
> * Updating /etc/mtab ... [ ok ] |
18 |
|
19 |
It doesn't show that it failed to mount / |
20 |
|
21 |
What does syslog show? |
22 |
|
23 |
|
24 |
> If I reboot the system again, then all works fine and the FS is mounted |
25 |
> automatically. So this is a one-time thingy, happening only on the first |
26 |
> boot after an unclean power-off. |
27 |
> |
28 |
> It would seem that I've stumbled across an OpenRC bug? There's no errors |
29 |
> anywhere to be seem. According to the log output above, everything |
30 |
> should be fine. I suspect that the "recovering journal" step is what |
31 |
> causes this, but I don't know why. |
32 |
> |
33 |
> Anyone else encountered this? |
34 |
|
35 |
I don't know why your system does this. I have had a few forced shutdowns |
36 |
with root on ext4 and the system mounts / after it recovers and cleans messed |
37 |
up inodes. |
38 |
|
39 |
However this is how fstab looks in my case: |
40 |
|
41 |
/dev/sda7 / ext4 noatime 0 1 |
42 |
|
43 |
|
44 |
Could your problem be related to your relatime mount option? |
45 |
|
46 |
-- |
47 |
Regards, |
48 |
Mick |