DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've been having this problem off and on for like, the past 2 weeks. Sometimes when I boot(40% of the time?), It get's to the fsck part, and I get this error
Code:
Checking root filesystem.../: Superblock last write time is in the future
It then stops booting, and tells me I need to manually fix it. So I give the root password, and run
Code:
fsck.ext3 -y /dev/hda3
How do I make it so that I won't get this error any more? I haven't done anything to the disk.
. . . and if you dual/multiple boot, make sure both/all operating systems are in the right time zone, because as each OS's NTP client "corrects" the hardware clock, it will screw up interpretation of timestamps when you boot to Linux.
could there be another explanation? I have same error and multiboot but hw and os times and time zones are same. I run Sarge upgraded to Etch with last upgrade several days ago and today. I have to do chk manually wc shows 2.1% of files are non-contiguous and must fsck on every boot into Etch for a week or more.
Have done re-install 3X in last few months. That is enough if avoidable.
I am having the same problem on 2 different machines both running debian testing. One machine only runs testing and the other tri-boots testing, ubuntu and xp.
Mine it running etch, and windows XP. It may be the clocks are out of sync, as we recently moved. But like I said, I haven't booted windows in a long time.
I got same problem thought its my mobo battery giving up .. I too updated from sarge to etch, and haven't booted XP in a long time .. I'll try the time sync'ing solution as it sounds most reasonable ..
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.