fscking problems
 

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
It then stops booting, and tells me I need to manually fix it. So I give the root password, and run
How do I make it so that I won't get this error any more? I haven't done anything to the disk.

Make sure your hardware clock (BIOS) and OS (Debian) clock and time zone are the same.

. . . 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.

I do dual boot, but I haven't booted windows in...quite some time. I'll check both possibilities though.

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 ..

I have tried the syncing solution to no avail

Very odd. Could you please post back if/when you find a solution? I'm curious.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=343645

We believe that the bug you reported is fixed in the latest version...

Source-Version: 1.38+1.39-WIP-2005.12.10-2

:twocents:

so how long until the newest version get't to etch? Is it worth waiting, or should I compile from source?

ok, that's the version I'm running. I'll get back to this thread in a while, after I've had some time to see if this is the problem.

nx5000, thanks for the info. :)

...
which has been reassigned here:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=342887

This page contains a patch if you can't wait ..

btw http://packages.debian.org/ is down

I'm running the version I'm running, but I'm still having this problem. It seems only to be happening if I reboot from linux, into linux. Or boot into linux shortly after having shut down. At lesat I'm pretty sure I've got that version(is it in etch?).

I was about to ask for a solution to this problem as well, but fortunately discovered this thread before making a nuisance duplication.

Reading thru the last bug report conversation in the previous post, it appears that the final solution has not yet arrived. Whenever anyone gets a chance to try the patch mentioned in the previous post, I would like to hear whether or not it fixed the problem.

My /usr directory IS on a separate partition which the bug report convos suggest may complicate the problem.

actually, I was wrong. I'm running
not
When will it come into etch?

I am also having this problem and have yet to find a solution to it. Strange thing is that it doesent stop the booting process ? and only occurs on the root parttion ??
Im using LFS and this is the first time ive seen this issue before. Ive built this version 6.1 before with no messages like this so Im wondering if there maybe something to do with sata drives.