[SOLVED] "Unexpected inconsistancy run fsck manually" at every boot.

[meganoob]

I feel like my question is pretty basic, but hey, my name says it, i'm a noob, so here it is:

after a hardware problem, my computer closed in an unproper way, so now, when I boot, I get this message saying Unexpected insconsistancy, run fsck manually. (I'll print the whole message later, but for now I'm at work, so I don't have it)

I ran fsck -f /dev/sda5. (the disk on which my fedora system is)

The only two errors that popped up were some dates that were in the future, so I said yes to everything. But every time I reboot, I still get that message. Why?

Thanks in advance

Meganoob

P.S. I scanned through the web for someone with a similar problem, but in every thread I found, people were doing fine once they had ran fsck.

[DBelton]

Your system clock is wrong (are you booting into Windows by chance? it can mess up the system clock if you have Fedora set to use UTC, and Windows using local time). Yo may need to run fsck on more than just the filesystem that your Fedora system is on as well.

From the Fedora common bugs:

If you set back your system time for more than one day into the past, Fedora will not boot on next system restart. It will complain about your disk mount time being too far in the future. Typically the error message looks like this (dracut shell):

/dev/mapper/VolGroup-lv_root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
dracut Warning: e2fsck returned with 4
dracut Warning: /dev/mapper/VolGroup-lv_root: Superblock last mount time (Tue
Oct 25 14:40:08 2011,
dracut Warning: now = Sun Sep 25 14:41:50 2011) is in the future.
dracut Warning: *** An error occurred during the file system check.
dracut Warning: *** Dropping you to a shell; the system will try
dracut Warning: *** to mount the filesystem(s), when you leave the shell.

Or it can look like this (emergency mode shell):

systemd-fsck[605]: /dev/sda2: Superblock last mount time (Tue Oct 25 10:40:12
2011,
systemd-fsck[605]: now = Sun Sep 25 10:41:59 2011) is in the future.
systemd-fsck[605]: /dev/sda2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
systemd-fsck[605]: (i.e., without -a or -p options)
[ 13.652068] systemd-fsck[605]: fsck failed with error code 4.
Welcome to emergency mode. Use "systemctl default" or ^D to activate default
mode.
Give root password for maintenance
(or type Control-D to continue):

You have to use the shell to correct the filesystem that is claimed to be "inconsistent". If you have multiple partitions you may need to do the following procedure for all of them. The easiest approach is:

Note that partition name in the error message (/dev/mapper/VolGroup-lv_root and /dev/sda2 in our examples).
Run this command

fsck <partition name>

For example:

fsck /dev/sda2

and confirm you want to fix it.
Run

reboot

It may happen that you are presented with the error message, but you are not given any emergency shell. In that case please boot from the Fedora installation media and select Troubleshooting -> Rescue a Fedora system. After the rescue tool mounts your system disks you can just reboot, everything should be corrected.

[PabloTwo]

systemd-fsck[605]: now = Sun Sep 25 10:41:59 2011) is in the future.

Well, if Sun Sep 25 10:41:59 2011 is in the future, I'll eat my shorts. Looks to me like someone never set the system time, at all.

[Chilly Willy]

PabloTwo

...I'll eat my shorts...

If / when you do, let me know, I wanna see that!

[DBelton]

Originally Posted by PabloTwo

systemd-fsck[605]: now = Sun Sep 25 10:41:59 2011) is in the future.

Well, if Sun Sep 25 10:41:59 2011 is in the future, I'll eat my shorts. Looks to me like someone never set the system time, at all.

That was quoted from the F16 common bugs Now.. When was F16 in the testing stages and released?

[PabloTwo]

Oh... OK... I ate my shorts. Too bad I didn't video the event for your entertainment.
I'll chalk this one up to "another senior moment".

[meganoob]

ok here's the message:

_Fedora-16-x86_6: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
dracut Warning: e2fsck returned with 4
dracut Warning: _Fedora-16-x86_6: Superblock last mount time is in the future.
dracut Warning: (by less than a day, probably due to the hardware clock being incorrectly set) FIXED
dracut Warning: _Fedora-16-x86_6: Superblock last write time is in the future.
dracut Warning: (by less than a day, probably due to the hardware clock being incorrectly set) FIXED
dracut Warning: _Fedora-16-x86_6 contains a file system with errors, check forced.
dracut Warning: _Fedora-16-x86_6: Inodes that were part of a corrupted orphan linked list found
dracut Warning: *** An error occurred during the file system check.
dracut Warning: *** Dropping you to a shell; the system will try
dracut Warning: *** to mount the filesystem(s), when you leave the shell.

so first of all: _Fedora-16-x86_6 is not the name of any partition that I know of.
that's why I ran it on /dev/sda5

Yes, I am dual-booting with windows
but when I tried to run fsck on /dev/sda1 (the windows partition), it told me that it wasn't an ext2 filesystem.

[PabloTwo]

"_Fedoraa-16-x86_6" is the LABEL of one of your Fedora partitions. Run the blkid command and you will see it, and which /dev/sdxx it belongs to. From my Fedora install and taken from the blkid command output:

/dev/sda7: LABEL="_Fedora-16-x86_6" UUID="7f83c155-bb22-40cc-b213-479e96734d7b" TYPE="ext4"

[meganoob]

Problem solved.
Many thanks to all of you.
The problematic partition was /dev/mapper/VolGroup-lv_root.

[Chilly Willy]

Originally Posted by PabloTwo

Oh... OK... I ate my shorts. Too bad I didn't video the event for your entertainment.
I'll chalk this one up to "another senior moment".

AHH, SHOOT! I missed it!
Made me laugh, though...
Thanks! - I needed that.
(it's been one of those days when I NEEDED a good laugh)