Superblock…date is in the future…system clock is wrong

[Member schproodle]

Startup messages flashing by…
I noticed file system check… Superblock output mentions that its date is in the future…probably because the system clock is wrong. Something like that.

What to do?

• This topic was modified 1 year, 4 months ago by schproodle.

EeePC, ASUSTek 1000HE - Atom N280, 1667 MHz, 32 bit - RAM 992.2 MiB
Kernel: 4.9.0-279-antix.1-486-smp i686 bits: 32 compiler: gcc v: 10.2.1
Desktop: IceWM 2.9.3 & zzzfm
Distro: antiX-21_386-full Grup Yorum 31 October 2021

[Moderator christophe]

Helpful

Up

0

::

Maybe your cmos battery died?

Maybe this will point you in the right direction:
https://serverfault.com/questions/71613/superblock-last-mount-time-is-in-the-future

Perhaps use the control centre to set the time: system -> set date & time -> use internet time server…
See if that keeps the time & removes the error.

• This reply was modified 1 year, 4 months ago by christophe.

confirmed antiX frugaler, since 2019

[Member ModdIt]

Helpful

Up

1

::

Pls check in BIOS and set correct system time. If you have regular provblems of same nature you will need to replace BIOS Battery.
For your model good info on below.
https://www.ifixit.com/Device/Asus_Eee_PC_1000HE

Should you have to open the device, ensure fan and heat exchanger are cleaned. Fitting an SSD highly recommended, the rotating disk
is much slower.

• This reply was modified 1 year, 4 months ago by ModdIt.
• This reply was modified 1 year, 4 months ago by ModdIt.

[Member schproodle]

Helpful

Up

0

::

Since BIOS was set for correct system time and remains set, is the superblock message still a problem?

Thanks for the link.

EeePC, ASUSTek 1000HE - Atom N280, 1667 MHz, 32 bit - RAM 992.2 MiB
Kernel: 4.9.0-279-antix.1-486-smp i686 bits: 32 compiler: gcc v: 10.2.1
Desktop: IceWM 2.9.3 & zzzfm
Distro: antiX-21_386-full Grup Yorum 31 October 2021

[Moderator christophe]

Helpful

Up

0

::

I’m trying to think of when I’ve seen that before on my own systems.

Do you dual boot? If so, maybe another OS changed your bios clock.

A reboot may help, to see if you keep getting the warning.

I want to say in my case, the little CMOS bios battery was not keeping my settings, which matches that link’s basic view.

• This reply was modified 1 year, 4 months ago by christophe. Reason: Typo

confirmed antiX frugaler, since 2019

[Member schproodle]

Helpful

Up

0

::

Thanks. The conditions and remedies you mention are not relevant in my case.

I believe issue started with the recent installation and has persisted. I merely did not get around to addressing it.

I wonder if there are any practical consequences. Although the system has been improperly shut down several times, the file system messages at startup show the file system repair process with no errors.

EeePC, ASUSTek 1000HE - Atom N280, 1667 MHz, 32 bit - RAM 992.2 MiB
Kernel: 4.9.0-279-antix.1-486-smp i686 bits: 32 compiler: gcc v: 10.2.1
Desktop: IceWM 2.9.3 & zzzfm
Distro: antiX-21_386-full Grup Yorum 31 October 2021

[Forum Admin Dave]

Helpful

Up

1

::

christophe wrote:

I’m trying to think of when I’ve seen that before on my own systems.

Do you dual boot? If so, maybe another OS changed your bios clock.

Aside from a dual boot with windows, I have seen this error when my linux installation has the incorrect time zone set. Then on boot up the files written / modified by the OS appear in the future due to the bios clock (correct time) time being used before the ntp service starts and changes the time based on the incorrect time zone (future time). I am not sure on the graphical way but you should be able to verify / change this with dpkg-reconfigure tz-data.

Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown

[Member schproodle]

Helpful

Up

0

::

Caught the relevant start-up message with Ctrl-S. 🙂

rootantiX21: Superblock last mount time is in the future (probably due to the hardware clock being incorrectly set)

It is set UTC correctly. I had completed sudo dpkg-reconfigure tzdata. The dialog default was correct with country and city already chosen. I re-entered the same to complete re-setting.

The system earlier froze after return from suspension. The file system repair was completed successfully.

I don’t really know if this is important or not. Everything else seems fine. 🙂

EeePC, ASUSTek 1000HE - Atom N280, 1667 MHz, 32 bit - RAM 992.2 MiB
Kernel: 4.9.0-279-antix.1-486-smp i686 bits: 32 compiler: gcc v: 10.2.1
Desktop: IceWM 2.9.3 & zzzfm
Distro: antiX-21_386-full Grup Yorum 31 October 2021

[Member schproodle]

Helpful

Up

1

::

My superblock issue can probably be traced to the installation dialog where one declares the setting of the BIOS clock. I probably had the bios set for local and then chose UTC or vice versa.

New installation on SSD – carefully selected time status – no more superblock complaints.

• This reply was modified 1 year, 4 months ago by schproodle.
• This reply was modified 1 year, 4 months ago by schproodle.
• This reply was modified 1 year, 4 months ago by schproodle.

EeePC, ASUSTek 1000HE - Atom N280, 1667 MHz, 32 bit - RAM 992.2 MiB
Kernel: 4.9.0-279-antix.1-486-smp i686 bits: 32 compiler: gcc v: 10.2.1
Desktop: IceWM 2.9.3 & zzzfm
Distro: antiX-21_386-full Grup Yorum 31 October 2021

[Author]

Posts