On Friday, May 16, 2014 01:12:52 PM Peter Humphrey wrote:
> On Wednesday 14 May 2014 22:29:46 Nikos Chantziaras wrote:
> > I have this weird problem where a filesystem (Ext4) refuses to mount
> > automatically after something like a power loss or forced shutdown.
> > 
> > The fstab entry for it is:
> >    LABEL=Data /mnt/Data ext4 defaults,relatime,exec 0 2
> > 
> > During boot, this is what OpenRC tells me:
> >    Root: clean, 805088/6553600 files, 9129899/26214400 blocks
> >    Data: recovering journal
> >    Data: clean, 364344/61546496 files, 137312260/246156800 blocks  [ ok ]
> >    * Mounting local filesystems ...                                [ ok ]
> >    * Remounting root filesystem read/write ...                     [ ok ]
> >    * Remounting filesystems ...                                    [ ok ]
> >    * Updating /etc/mtab ...                                        [ ok ]
> > 
> > If I reboot the system again, then all works fine and the FS is mounted
> > automatically. So this is a one-time thingy, happening only on the first
> > boot after an unclean power-off.
> > 
> > It would seem that I've stumbled across an OpenRC bug? There's no errors
> > anywhere to be seem. According to the log output above, everything
> > should be fine. I suspect that the "recovering journal" step is what
> > causes this, but I don't know why.
> > 
> > Anyone else encountered this?
> 
> No, I can't say I have. I do occasionally have to use the reset button to
> reboot (because the KDM shutdown process had hung), and the system just
> restarts as Mick says.
> 
> This is my root fstab entry:
> 
>       /dev/md5                /       ext4    relatime        1 1
> 
> The other partitions are similar except for being mounted from /dev/md7.

My (2.5 y/o) daughter occasionally presses the reset-button while sitting on 
my chair... (yes, the button is on a really bad location on the case). So it 
gets reset unintentionally regularly.
Using 2 disks with 2 partitions. 1 with RAID-1 for /boot and the other with 
RAID-0 with LVM ontop where all the other partitions are inside LVM. Not had a 
bad start in a very long time.
Last time it stopped for a manual fix was after the reset happened during a big 
emerge-session.

--

Joost

Reply via email to