[arch-general] Installation: after first reboot ext3 superblock mount time in future
gerhard.brauer at web.de
Sat Mar 29 09:12:35 EDT 2008
i've noticed this meanwhile quiet often after many installations.
Currently after a test with 2008.03-0.3, but also with older ISOs:
After install and first reboot i got such fsck notice during rc:
| /dev/sda3: Superblock last mount time is in the future. FIXED
| /dev/sda3 has gone 49710 days without being checked, check forced.
Here¹ you could download a screenshot from such a situation where also a
reboot is required after fsck.
Cause this is the *first* reboot after installation users will get a bad
impression about Arch.
First i thought this comes from vmware, but i also get it in virtualbox
and i've seen this also during real installations.
I have a suspicion: During (c)fdisk and formatting the disks current locale
and timezone is set to US values (don't know at the moment the initial
settings presented in rc.conf).
During configuration i set my locale and timezone always to de_DE.utf8
and Europe/Berlin. And when first reboot is made that from umounting /
there is a time difference that could cause such and flag it on ext3
Or with the order in rc scripts?
Maybe also that the hwclock is changed during/after installation...
Have others also seen such?
Don't drink and root!
More information about the arch-general