| LinHES Forums http://forums.linhes.org/ |
|
| fsck problem http://forums.linhes.org/viewtopic.php?f=5&t=18072 |
Page 1 of 1 |
| Author: | rkshack [ Wed Mar 19, 2008 7:27 am ] |
| Post subject: | fsck problem |
Almost everytime I boot my myth box I get the following issues. Fsck runs gives the messages: myth: superblock last mount time in the future. Fixed. myth: superblock last write time in the future. Fixed. myth has gone 48537 days without being checked, check forced ... and then it checks the drive which can take a very long time. How can I get it to not have these problem? Rkshack |
|
| Author: | Kirk [ Wed Mar 19, 2008 5:45 pm ] |
| Post subject: | |
It's appears to be a bug related to your clock and the checking of the root filesystem. Since the system clock is not set correctly at the time of the fsck'ing you get these strange errors. There seems to be two thoughts on fixing this; 1. moving /etc/rcS.d/S50hwclock.sh to S8hwclock.sh so it runs before checkroot.sh 2. tune2fs -i 0 /dev/hdX to disable checks based on time Regards, Kirk. |
|
| Author: | rkshack [ Thu Mar 20, 2008 1:44 am ] |
| Post subject: | |
Thank you. It worked great. I used the tunefs method. rkshack |
|
| Author: | warchildx [ Thu Mar 20, 2008 7:07 am ] |
| Post subject: | |
Another thought is the clock is skewing. You can run the following 2 commands which will update the box via atomic clocks. ntpdate time.nist.gov hwclock --systohc The first sets the clock to a good time (sort of like windows "net time" command) the second syncs the system time to the realtime clock on the motherboard. thus when the box is rebooted, the clock will hold time. I have several mailservers that have issues if the filesystem time doesnt match the clock time. usually nfs mounted volumes where the 2 systems clocks are not in sync. |
|
| Page 1 of 1 | All times are UTC - 6 hours |
| Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |
|