View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 4 posts ] 
Print view Previous topic   Next topic  
Author Message
Search for:
 Post subject: fsck problem
PostPosted: Wed Mar 19, 2008 7:27 am 
Offline
Joined: Sat Oct 29, 2005 6:57 am
Posts: 176
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

_________________
5.5
6150k8ma-8ekrs
Athlon64 3200+
1gb ram
250gb hda
750gb sda
nvidia 6200
central time


Top
 Profile  
 
 Post subject:
PostPosted: Wed Mar 19, 2008 5:45 pm 
Offline
Joined: Mon Mar 13, 2006 2:28 am
Posts: 143
Location: Brisbane, Australia
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.

_________________
MBE/FE ~ R5F27 ~ Asus A8N-VM-CSM ~ AMD64 3500+ ~ 1GB RAM ~ 1.5TB Storage ~ Nova-T-500 ~ SH-S183A DVDRW ~ LC20M Case ~ iMON-Pad Remote
FE ~ Diskless ~ Asus M2NPV-VM ~ AMD X2 BE-2350 (45w) ~ 1GB RAM ~ TT Lanbox Lite ~ iMON-Pad Remote


Top
 Profile  
 
 Post subject:
PostPosted: Thu Mar 20, 2008 1:44 am 
Offline
Joined: Sat Oct 29, 2005 6:57 am
Posts: 176
Thank you. It worked great. I used the tunefs method.

rkshack

_________________
5.5
6150k8ma-8ekrs
Athlon64 3200+
1gb ram
250gb hda
750gb sda
nvidia 6200
central time


Top
 Profile  
 
 Post subject:
PostPosted: Thu Mar 20, 2008 7:07 am 
Offline
Joined: Sat Mar 11, 2006 4:01 pm
Posts: 61
Location: Tobaccoville, NC, USA
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.


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 4 posts ] 


All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 4 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu