CentOS disable filesystem check: superblock last mount time is in the future

Solution 1:

buggy_init_scripts=1 only works if the time difference is smaller than 1 hour.

Try that int /etc/e2fsck.conf:

[problems]

# Superblock last mount time is in the future (PR_0_FUTURE_SB_LAST_MOUNT).
0x000031 = {
    preen_ok = true
    preen_nomessage = true
}

# Superblock last write time is in the future (PR_0_FUTURE_SB_LAST_WRITE).
0x000032 = {
    preen_ok = true
    preen_nomessage = true
}

This should remove the message, and correct the datas.

Solution 2:

It is better that you fix the vm datetime. It is quite a complicated issue actually if by vm you mean vmware.

http://www.vmware.com/files/pdf/Timekeeping-In-VirtualMachines.pdf

if it is some other vm system, i think the issue would be similar.

turning off consistency check etc. is not advisable because they are there for a reason. a system with time being inconsistent will affect integrity in many other ways.

Solution 3:

Build the hwclock time set into your kickstart/build process.