Super User is a question and answer site for computer enthusiasts and power users. 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

I keep getting errors messages about my Superblock mount time being in the future, and insisting on doing fsck on every other boot, Im worried it will mess up my SSD.

Where is the last time coming from? Its off 7 hours, could that be the cause?

hwclock from util-linux 2.20.1
Using /dev interface to clock.
Last drift adjustment done at 0 seconds after 1969
Last calibration done at 0 seconds after 1969
Hardware clock is on unknown time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick... clock tick
Time read from Hardware Clock: 2013/09/18 21:28:18
Hw clock time : 2013/09/18 21:28:18 = 1379539698 seconds since 1969
Wed Sep 18 14:28:18 2013  -0.411186 seconds
share|improve this question
Are you dual-booting Windows? Linux usually assumes the hardware clock is set to UTC, whereas Windows generally wants it to be local time - maybe one or the other is changing it unexpectedly. – user55325 Sep 19 '13 at 5:05
Yes, I am running windows although I have not booted into it for a while and not at all since I installed linux. – Bob R Sep 19 '13 at 5:34
Where is the second time "Wed Sep 18 14:28:18 2013 -0.411186 seconds " coming from? The time on my panel matches my Hw Time. – Bob R Sep 19 '13 at 7:12
You don't happen to live in UTC-7, do you? – user55325 Sep 20 '13 at 2:36
Actually yes I do, and my hardware clock is exactly -7 hours off of that second line. The Hw clock time is correct, the last line is not. I have UTC=no – Bob R Sep 20 '13 at 3:43

With the help of user55325 and some work on the terminal myself I think I have got this fixed:

First I did what user55325 recommended:

  1. set /etc/default/rcS utc=yes and adjtime last line back to UTC
  2. Set bios time to utc time.
  3. hwclock -s -u
  4. boot into recovery mode and selected clean
  5. reboot back into Mint
  6. date, verifying everything was ok
  7. Boot into Windows synced time with ntp server
  8. Checked bios time, it was now set to localtime
  9. booted into Mint again
  10. hwclock -s -u set /etc/default/rcS utc=n0 and adjtime last line back to LOCAL
  11. from recovery mode ran clean and fsck

Result: After many reboots and general use, Now both Mint and Windows 8 are showing localtime and boot without errors.

share|improve this answer

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.