How do I reenable automatic filesystem repair during boot?

aniruddha · 2009-10-25 09:19:49

I keep getting "filesystem check failed", In the past I rebooted and on the second boot Arch used to autmatically repair the filesystem and minor issues like 'superblock last mount time was in the future' and continued booting. Now it stops with the message "filesystem check failed' and expects a manual check. How do I reenable filesystem repair during boot?

# cat /etc/fstab

# 
# /etc/fstab: static file system information
#
# <file system>        <dir>         <type>    <options>          <dump> <pass>
none                   /dev/pts      devpts    defaults            0      0
none                   /dev/shm      tmpfs     defaults            0      0

#/dev/cdrom             /media/cd   auto    ro,user,noauto,unhide   0      0
#/dev/dvd               /media/dvd  auto    ro,user,noauto,unhide   0      0
#/dev/fd0               /media/fl   auto    user,noauto             0      0

LABEL=swap     swap         swap     defaults         0     0
LABEL=root     /         ext3     relatime,barrier=1     0     1
LABEL=home     /home         ext3     relatime,barrier=1     0     1

Last edited by aniruddha (2009-10-25 09:58:15)

graysky · 2009-10-25 11:17:33

I'm guessing you don't have your HARDWARECLOCK="localtime" in your /etc/rc.conf which probably caused this problem.

Just give it your root password, then type

# umount /
# fsck -f -v /dev/sdxY

Where sdxY is the location of your root partition (for example sda1 or sdb2 etc.) That'll fix the time errors and when you reboot the system (type reboot) everything should be fine.

vacant · 2009-10-25 11:21:42

graysky wrote:

I'm guessing you don't have your HARDWARECLOCK="localtime" in your /etc/rc.conf which probably caused this problem.

I like my BIOS clock set to UTC. I got that yesterday after rebooting from running kubuntu 9.10. The fix was as you said (umount / and force a file check).

aniruddha · 2009-10-25 11:24:02

graysky wrote:

I'm guessing you don't have your HARDWARECLOCK="localtime" in your /etc/rc.conf which probably caused this problem.
Just give it your root password, then type
# umount /
# fsck -f -v /dev/sdxY
Where sdxY is the location of your root partition (for example sda1 or sdb2 etc.) That'll fix the time errors and when you reboot the system (type reboot) everything should be fine.

Thanks, the problem is that this is a lengthy process. And I don't want to do this manually for each disk. Normally small problems such as 'superblock last mount time was in the future' are fixed during boot without requiring manual intervention. I wonder how I turn on this option to fix small problem automatically during boot.

Last edited by aniruddha (2009-10-25 11:25:57)

aniruddha · 2009-10-25 11:29:07

vacant wrote:

graysky wrote:
I'm guessing you don't have your HARDWARECLOCK="localtime" in your /etc/rc.conf which probably caused this problem.
I like my BIOS clock set to UTC. I got that yesterday after rebooting from running kubuntu 9.10. The fix was as you said (umount / and force a file check).

I am dual booting with windows therefor my system clock is set to localtime. Unfortunately each time after I boot into windows I get this superblock error, which is no problem if it is fixed automatically.

$ grep CLOCK /etc/rc.conf
# HARDWARECLOCK: set to "UTC" or "localtime"
HARDWARECLOCK="localtime"

Last edited by aniruddha (2009-10-25 11:30:23)

lucke · 2009-10-25 11:35:26

It is indeed a regression. Seems to work okay with e2fsprogs 1.41.8 - 1.41.9 made that "mounted in the future" message more verbose, maybe that's the reason it "breaks".

-edit-

https://bugs.launchpad.net/ubuntu/+sour … bug/373409
http://launchpadlibrarian.net/29173837/ … f-bu.patch

That's apparently the change which causes the regression (the regression being that it used to fix those "wrong mount time" without demanding manual check). I'm too sleepy to debug that stuff right now.

Last edited by lucke (2009-10-25 11:46:05)

aniruddha · 2009-10-25 12:32:43

lucke wrote:

It is indeed a regression. Seems to work okay with e2fsprogs 1.41.8 - 1.41.9 made that "mounted in the future" message more verbose, maybe that's the reason it "breaks".
-edit-
https://bugs.launchpad.net/ubuntu/+sour … bug/373409
http://launchpadlibrarian.net/29173837/ … f-bu.patch
That's apparently the change which causes the regression (the regression being that it used to fix those "wrong mount time" without demanding manual check). I'm too sleepy to debug that stuff right now.

Thanks I can confirm it's a regression, I installed e2fsprogs 1.41.8, uncommented 2 hard drives in fstab and rebooted. I got the following message:

/dev/sda1 contains a file system with errors, check forced

I filed a bugreport here:
http://bugs.archlinux.org/task/16838?pr … pened=5337

Last edited by aniruddha (2009-10-25 12:37:39)

legolas558 · 2009-10-26 07:05:29

Same issue here

MindTooth · 2009-10-26 17:47:18

Thank you for this Solved my problem after installing OpenNTPD.

Birger

cb474 · 2009-11-10 02:47:12

I was also having the problem of being force to do manual file system checks with the "superblock last mount time was in the future" error. (I actually get this error surprisingly frequently. The last update of the tzdata package set my clock ahead eight hours for some reason.)

Downgrading from e2fsprogs 1.41.9-1 to 1.41.8-2 also solved the problem for me.

kalpik · 2009-11-17 02:44:05

Yeah.. I have also lost the ability to do automated filesystem checks.. Waiting for a fix for e2fxprogs..

legolas558 · 2009-11-17 10:24:07

looks like this issue is fixed when using 2.6.32 kernel

skipio · 2009-11-17 10:36:58

from man fstab:

The  sixth  field,  (fs_passno), is used by the fsck(8) program to determine the order in which filesystem checks are done at reboot time.  The root filesystem should be specified with a fs_passno of 1, and other filesystems
       should have a fs_passno of 2.  Filesystems within a drive will be checked sequentially, but filesystems on different drives will be checked at the same time to utilize parallelism available in the  hardware.   If  the  sixth
       field is not present or zero, a value of zero is returned and fsck will assume that the filesystem does not need to be checked.

legolas558 · 2009-11-17 11:21:24

skipio how does that help? did you just discover warm water?

kalpik · 2009-11-17 11:22:39

But kernel 2.6.32 is neither in [core], nor in [testing].. Anyway, waiting for the update

legolas558 · 2009-11-17 11:26:44

kalpik wrote:

But kernel 2.6.32 is neither in [core], nor in [testing].. Anyway, waiting for the update

please test yourself with a 2.6.32 kernel if you can, and tell us if it also fixed the issue for you - this way we will have a confirm of my findings

kalpik · 2009-11-17 11:28:13

legolas558 wrote:

please test yourself with a 2.6.32 kernel if you can, and tell us if it also fixed the issue for you - this way we will have a confirm of my findings

Oh! I'm sorry but i cannot risk running a RC Kernel

legolas558 · 2009-11-17 13:36:35

kalpik wrote:

legolas558 wrote:
please test yourself with a 2.6.32 kernel if you can, and tell us if it also fixed the issue for you - this way we will have a confirm of my findings
Oh! I'm sorry but i cannot risk running a RC Kernel

If you are able to compile it, you could put it in your bootloader as second choice, so that if it does not work you can boot with the other one.

lucke · 2009-11-18 19:42:24

2.6.32 indeed seems to fix it. A baffling issue - seemed to me that userspace was at fault.

flowheat · 2009-12-14 00:46:58

I was having an issue with this due to some time problems with a Windows 7 dual boot. I managed to fix the time issue so I'm not seeing it, but a .32 kernel did not cause automatic checks to start happening.

legolas558 · 2009-12-14 00:51:28

it must have been something in the ext kernel modules, but I cannot track back what specific patch fixed it

Arch Linux

#1 2009-10-25 09:19:49

How do I reenable automatic filesystem repair during boot?

#2 2009-10-25 11:17:33

Re: How do I reenable automatic filesystem repair during boot?

#3 2009-10-25 11:21:42

Re: How do I reenable automatic filesystem repair during boot?

#4 2009-10-25 11:24:02

Re: How do I reenable automatic filesystem repair during boot?

#5 2009-10-25 11:29:07

Re: How do I reenable automatic filesystem repair during boot?

#6 2009-10-25 11:35:26

Re: How do I reenable automatic filesystem repair during boot?

#7 2009-10-25 12:32:43

Re: How do I reenable automatic filesystem repair during boot?

#8 2009-10-26 07:05:29

Re: How do I reenable automatic filesystem repair during boot?

#9 2009-10-26 17:47:18

Re: How do I reenable automatic filesystem repair during boot?

#10 2009-11-10 02:47:12

Re: How do I reenable automatic filesystem repair during boot?

#11 2009-11-17 02:44:05

Re: How do I reenable automatic filesystem repair during boot?

#12 2009-11-17 10:24:07

Re: How do I reenable automatic filesystem repair during boot?

#13 2009-11-17 10:36:58

Re: How do I reenable automatic filesystem repair during boot?

#14 2009-11-17 11:21:24

Re: How do I reenable automatic filesystem repair during boot?

#15 2009-11-17 11:22:39

Re: How do I reenable automatic filesystem repair during boot?

#16 2009-11-17 11:26:44

Re: How do I reenable automatic filesystem repair during boot?

#17 2009-11-17 11:28:13

Re: How do I reenable automatic filesystem repair during boot?

#18 2009-11-17 13:36:35

Re: How do I reenable automatic filesystem repair during boot?

#19 2009-11-18 19:42:24

Re: How do I reenable automatic filesystem repair during boot?

#20 2009-12-14 00:46:58

Re: How do I reenable automatic filesystem repair during boot?

#21 2009-12-14 00:51:28

Re: How do I reenable automatic filesystem repair during boot?

Board footer