linux - superblock is in the future bios time -


sometimes, when reboot system, have error : /dev/sda1 "superblock last mount time in future /dev/sda1 "run fsck manually"

to correct it, have go bios system , set date/time (generally it's 1 year later). after no problem pc reboot correctly.

but cause of production condition, problem go bios change date/time. there way ignore error ? because don't understand why linux doesn't want start because bios date/time wrong ?

see man e2fsck.conf :

...

[options] stanza contains general configuration parameters e2fsck's behavior

...

broken_system_clock e2fsck(8) program has heuristics assume system clock correct. in addition, many system programs make similar assumptions. example, uuid library depends on time not going backwards in order able make guarantees issuing universally unique id's. systems broken system clocks, well, broken. however, broken system clocks, particularly in embedded systems, exist. e2fsck attempt use heuristics determine if time can not trusted; , skip time-based checks if true. if boolean set true, e2fsck assume system clock can not trusted.

son in /etc, create file e2fsck.conf :

 [options]   broken_system_clock = true 

best regard, emmanuel


Comments

Popular posts from this blog

html - Firefox flex bug applied to buttons? -

html - Missing border-right in select on Firefox -

c# - two queries in same method -