Strange superblock boot message (mount time in future)

wrc1944 · Last edited by wrc1944 on Wed Aug 16, 2006 10:16 pm; edited 1 time in total

I've suddenly been getting random boot messages like this on all my ext3 partitions:

superblock last mount time in future FIXED

I read about a possible cause on a slackware forum:

suicidal_orange_II · Apprentice Joined: 04 Sep 2004 Posts: 299

I'm guessing you live somewhere where the timezone is gmt +x, in which case if you reboot in less than x hours you will see this message.

It is not going to do any damage to your data so I wouldnt worry about it (although a fix would be nice

)

Suicidal_Orange

wrc1944 · Posted: Mon Aug 07, 2006 7:07 pm Post subject:

Nope- I'm in Florida, gmt -5. This is only happening on one of my three boxes (so far).

I thought maybe one of these kernels was the culprit, but I compiled then on all boxes, and that's not it, so it's a local thing on one box. All the systems are identical, i.e. config files are all the same- no clue there. Guess I'll check the bios time settings and see if that has somehow gone out of whack. These are pretty new boards, so the battery should be perfectly fine.
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.9.1 USE=experimental python3_11

Section_8 · l33t Joined: 22 May 2004 Posts: 627

I noticed that message rebooting lastnight. I am in CST (gmt-6). I also have my hardware clock set to local time, for windows dual boot of course.

Ivar_Y · n00b Joined: 29 Jun 2004 Posts: 25

Look at https://bugs.gentoo.org/show_bug.cgi?id=142850.

Ivar

wrc1944 · Posted: Thu Aug 17, 2006 12:36 pm Post subject:

Hmmm- I read through bug 142850, and the last comment #11 by Ivar seems like it's probably the solution.

Section_8 · l33t Joined: 22 May 2004 Posts: 627

My understanding from reading that bug is that e2fsprogs 1.39 does a last mount time sanity check that earlier versions didn't do. So the startup local/UTC time confusion was always there, it just never produced an error message.

I'll try that fix when I get home tonight.

Ivar_Y · n00b Joined: 29 Jun 2004 Posts: 25

To add to Apprentice's post:

From the "e2fsprogs-1.39" RELEASE-NOTES:

yabbadabbadont · Posted: Thu Aug 17, 2006 10:22 pm Post subject:

Instead of modifying /sbin/rc, I created /etc/runlevels/boot/.critical and put the new service order there. It is used if it exists. I then had to move the clock service before checkroot as the root check would always show the error (while the other filesystems wouldn't). As was stated earlier, clock doesn't rely on any other services and the root filesystem is already mounted. Also, I removed the depend() function from the clock service. The change to /etc/init.d/clock is the only thing I will have to be sure gets preserved whenever baselayout is updated.
_________________

Ivar_Y · n00b Joined: 29 Jun 2004 Posts: 25

Putting "clock" at the front of the CRITICAL_SERVICES list is a good idea. Putting it after checkroot and before checkfs means that "last mount time" and "last write time" are still set to wrong values for the root file system. This is probably unimportant but starting the list off with clock assures that these values are accurate.

I do not need to remove the depend() function in clock.

I suspect that keeping the CRITICAL_SERVICES list in /sbin/rc is a better idea than keeping it as /etc/runlevels/boot/.critical. I assume that users will have to maintain and update the list in the latter location and this is likely to confuse many of them. /sbin/rc is a part of baselayout, which is a Gentoo package maintained by the Gentoo Developers. It seems safer to let them keep things straight.

Ivar

yabbadabbadont · Posted: Fri Aug 18, 2006 7:56 pm Post subject:

I removed the depend function since it only contained "need localmount". (which it doesn't)

Regarding maintaining the .critical file after baselayout updates. I guess it's a "six of one and half a dozen of the other" situation. Either you will have to maintain the .critical file if the list of services changes, or you will have to keep editing the /sbin/rc file after each baselayout update that doesn't have the clock service in the correct place. Take your pick. (of course, once baselayout has a correct /sbin/rc, neither option will be needed)
_________________

csab · Posted: Fri Sep 22, 2006 1:37 am Post subject:

Developers screwing us... with the new baselayout (1.12.5) the following lines were added to /sbin/rc:

yabbadabbadont · Posted: Fri Sep 22, 2006 2:07 am Post subject:

Yeah. I ended up doing the same thing.
_________________

UberLord · Posted: Fri Sep 22, 2006 6:42 am Post subject:

csab · Posted: Fri Sep 22, 2006 2:55 pm Post subject:

csab · Posted: Sun Mar 16, 2008 10:49 pm Post subject:

overkll · Posted: Sun May 10, 2009 5:11 am Post subject:

Too funny, thought I'd be the only one digging this up again. I had to dig this up out of my email to find this bug/thread again. Indeed it's still an issue. I use UTC on machines when I can, but my lappy needs "local". I couldn't remember what I did the last time. This fix works for me: