You are not logged in.
Pages: 1
Well, after rebooting earlier, I got to where it does it's normal filesystem check and it failed to my surpise. Apparently something is wrong, I pressed Ctrl+D because I didn't know how to fix what was wrong and it booted because it didn't check the filesystem that time. But I am sure when it checks again it will say that same, How do I go about finding whats wrong and fixing it?
Offline
Well, after rebooting earlier, I got to where it does it's normal filesystem check and it failed to my surpise. Apparently something is wrong... ...But I am sure when it checks again it will say that same.
That's protective measure. Fsck will refuese to check mounted filesystem, it is too dangerous. And until the filesystem is flagged clean, fsck will allways try to check it. But it won't check it while it's mounted.. sort of chicken and egg thing, if your root is corrupted
Do NOT ever try to force fsck of mounted partition unless you are Chuck Norris!
Good way to check root filesystem is to use some live distro and fsck it from there (prior to check, you should umount that filesystem, if the live distro mounts by default. most of them do)
-Miky.
What happened to Arch's KISS? systemd sure is stupid but I must have missed the simple part ...
... and who is general Failure and why is he reading my harddisk?
Offline
I get the same with my / partition (ext3). Every time there is a scheduled fsck, the check fails on first run. After a reboot, it succeeds but it offsets the clock.
It is quite annoying, since my machine is usually scheduled to boot itself up for mythtv recordings. Coming home to a failed fsck prompt and no mythtv recordings is no fun.
Offline
Offline
After a reboot, it succeeds but it offsets the clock.
There maybe a software bug somewhere, I get the same thing on both my arch and gentoo box.
Offline
everytime I log on I get a failure. It says something to the effect that my last write time is in the future, and says it fixed it.
Offline
Same issue here - I've seen mention of it on the mailing list, too.
Unthinking respect for authority is the greatest enemy of truth.
-Albert Einstein
Offline
i got the same problem
Linux can run on any thing...
look at me
[img]http://img53.imageshack.us/img53/8413/indexol8.png[/img]
Offline
Did anyone figure out what the problem was?
I am having this same issue after a recent re-install. It's irritating not being able to figure it out!
I've checked my hardware clock which is set to local time.....I can't figure it out.......
Anyone have better luck?
McRae
Offline
Good way to check root filesystem is to use some live distro and fsck it from there (prior to check, you should umount that filesystem, if the live distro mounts by default. most of them do)
Or create the file /forcefsck. If the system finds it on boot, it will force a check of all filesystems, removing the need to get a livecd or rescue disc. Handy
As for the time issue, I only get it on my computer that has time set to localtime, it's fine on my UTC boxes. I'm personally blaming Windows
Desktop: AMD Athlon64 3800+ Venice Core, 2GB PC3200, 2x160GB Maxtor DiamondMax 10, 2x320GB WD Caviar RE, Nvidia 6600GT 256MB
Laptop: Intel Pentium M, 512MB PC2700, 60GB IBM TravelStar, Nvidia 5200Go 64MB
Offline
Pages: 1