Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Why the shell show "/dev/sda2 has gone 49710 days without being checked, check forced." at centos start and then reboot?


/dev/sda2: Superblock last mount time is in the future. FIXED.

/dev/sda2: Superblock last write time is in the future. FIXED.

/dev/sda2 has gone 49710 days without being checked, check forced.

/dev/sda2: REBOOT LINUX

share|improve this question

migrated from serverfault.com Sep 28 '11 at 8:26

This question came from our site for system and network administrators.

This indicates that the date recorded for the last check on that filesystem is in the near future (49710 days is very nearly 232 seconds, so it looks like a signed 32-bit number is being interpreted as ungisned).

Looks like you have clock issues. It may be your BIOS battery dead. On the software side, compare hwclock and date outputs. You might need to set the hardware clock (using hwclock tool for example), but first verify the battery state and replace if needed.

Edit: The issue looks to be well known. Google for "49710 days" "check forced" - it reveals links like this, or this one that clearly indicate the connection with system clock settings. The solution might be as simple as setting the hardware clock to UTC (as suggested in the second link), if the battery is ok.

share|improve this answer
@Gilles Thanks for the edit - yes, it looks more clear that way. I didn't mention the near future earlier because the observation was already made in the other answer. – rozcietrzewiacz Sep 29 '11 at 6:15

49710 days = 4294944000 seconds - which is eerily close to a round number, if you count in binary.

2^32 seconds is 49710.27 days - sounds like a timestamp for your filesystem's last check exploded somewhere along the line. That may be a symptom of an issue with your drive - I'd recommend investigating further.

share|improve this answer
I'm with shane, I'd guess that last time your system fsck'ed the drive, the clock was somewhat in the future, and that "-0.27 days since last fsck, oh well" is being (rightly and properly) interpreted as "+49710 days, better do it now!". – MadHatter Sep 28 '11 at 7:48
Uhm... Google for "49710 days" "check forced". It is not a coincidence. I bet the drive has nothing to do with it. – rozcietrzewiacz Sep 28 '11 at 12:30

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.