Startup Message that Superblock Last Mount Time is in the Future

rickster1006 · 2022-04-02 21:02:26

Good afternoon. I have a cranky old HP Pavilion that used to dual boot between Bunsenlabs Linux & Slackware 14.2 without issue. I recently did a fresh install of Slackware 15, & made two mistakes that now seem to impact booting into Bunsenlab Linux. For starters, I selected the swap partition allocated to Bunsenlabs Linux, & allocated it to Slackware. The other stupid thing I did is select UTC for time instead of the standard use of local time. Once done with the Slackware install, & attempting to boot back into Bunsenlabs Linux, I noticed repeatedly the message "Superblock last mount time is in the future" at startup. I also noticed startup time took a bit longer than usual while it fsck on startup. In looking at the logs, I noticed a message there is a time out waiting for device to startup. As far as I can tell, the device not being mounted is associated with the device dedicated to Slackware. Based on all of this, how do I stop the fsck being run at startup?

Thanks in advance,
-Rick

My fstab:
# / was on /dev/sda1 during installation
UUID=64484524-d762-4d15-9ecb-418ddd5ea68d / ext4 errors=remount-ro 0 1
# /home was on /dev/sda3 during installation
UUID=7910697f-3712-4df8-b530-60a7aab00321 /home ext4 defaults 0 2
# /tmp was on /dev/sda6 during installation
UUID=2fbd2ea1-7c71-449f-962e-9f70f7f33477 /tmp ext4 defaults 0 2
# /var was on /dev/sda5 during installation
UUID=71e6f617-4105-43bc-9b28-b5432250460a /var ext4 defaults 0 2
# swap was on /dev/sda4 during installation
UUID=b08632da-4c7b-40cc-ab5b-15c0624eb574 none swap sw 0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0

Mounted:
/dev/sda1 on / type ext4 (rw,relatime,errors=remount-ro)
/dev/sda5 on /var type ext4 (rw,relatime)
/dev/sda3 on /home type ext4 (rw,relatime)
/dev/sda6 on /tmp type ext4 (rw,relatime)

Journalctl output:
syslog:Mar 27 11:09:16 hostname systemd-fsck[392]: /dev/sda5: Superblock last mount time is in the future.
syslog:Mar 27 11:09:16 hostname systemd-fsck[392]: /dev/sda5: Superblock last write time is in the future.
syslog:Mar 27 11:09:16 hostname systemd-fsck[389]: /dev/sda6: Superblock last mount time is in the future.
syslog:Mar 27 11:09:16 hostname systemd-fsck[389]: /dev/sda6: Superblock last write time is in the future.
syslog:Mar 27 11:09:16 hostname systemd-fsck[394]: /dev/sda3: Superblock last mount time is in the future.

Mar 27 11:41:50 hostname systemd[1]: Dependency failed for /dev/disk/by-uuid/efbd299a-b3d8-4839-a18d-a6c5c16667d6.
Mar 27 11:41:50 hostname systemd[1]: dev-disk-by\x2duuid-efbd299a\x2db3d8\x2d4839\x2da18d\x2da6c5c16667d6.swap: Job dev-disk-by\x2duuid-efbd299a\x2db3d8\x2d4839\x2da18d\x2da6c5c16667d6.swap/start failed with result 'dependency'.
Mar 27 11:41:50 hostname systemd[1]: dev-disk-by\x2duuid-efbd299a\x2db3d8\x2d4839\x2da18d\x2da6c5c16667d6.device: Job dev-disk-by\x2duuid-efbd299a\x2db3d8\x2d4839\x2da18d\x2da6c5c16667d6.device/start failed with result 'timeout'.

Bearded_Blunder · 2022-04-02 21:12:27

Reconfigure the time settings and swap in your slackware install?

nobody · 2022-04-02 21:26:36

Regarding the systemd dependency issues, I think they are separate from your superblock timing issues. SWAP partitions do not contain superblocks.

If you assigned the swap to slackware as well, slackware may have, during the install process, re-initialized the swap space, changing its UUID. In order to fix this part of the issue, I think the correct thing would be:

On your BL system, execute

lsblk -o +UUID

in the output, find your SWAP partition and note down the UUID from the UUID column. Edit your /etc/fstab and update the UUID of the SWAP partition:

# swap was on /dev/sda4 during installation
UUID=<your new UUID here> none  swap    sw              0       0

Then restart BL; the error about the dependency on the SWAP partition should disappear. If you're unsure, back up the /etc/fstab to your home directory before saving the edited version.

johnraff · 2022-04-03 00:56:02

Slightly off-topic, but:

rickster1006 wrote:

The other stupid thing I did is select UTC for time instead of the standard use of local time.

UTC hardware time is considered the best choice (Linux will adjust your clock to local time), unless you're dual-booting with Windows.

Bearded_Blunder · 2022-04-03 01:26:30

There isn't a "best choice" given the possibility of dual-boot with Windows, there's either a correct choice "both systems match" or you've messed up..
Like Duck said in Thomas the tank engine.. there's the GWR way.. or the WRONG way.

johnraff · 2022-04-03 01:54:25

Even if there's no Windows involved, a Linux user still has the choice of setting their hardware to local time. It's not recommended though.

deleted0 · 2022-04-03 02:16:59

Windows can be set to use UTC time. Quick registry hack; search the web. I'm currently set up that way.

#1 2022-04-02 21:02:26

Startup Message that Superblock Last Mount Time is in the Future

#2 2022-04-02 21:12:27

Re: Startup Message that Superblock Last Mount Time is in the Future

#3 2022-04-02 21:26:36

Re: Startup Message that Superblock Last Mount Time is in the Future

#4 2022-04-03 00:56:02

Re: Startup Message that Superblock Last Mount Time is in the Future

#5 2022-04-03 01:26:30

Re: Startup Message that Superblock Last Mount Time is in the Future

#6 2022-04-03 01:54:25

Re: Startup Message that Superblock Last Mount Time is in the Future

#7 2022-04-03 02:16:59

Re: Startup Message that Superblock Last Mount Time is in the Future

Board footer