On Sun, Mar 30, 2008 at 12:22:37AM +0200, Roman Kyrylych wrote:
2008/3/30, Roman Kyrylych <roman.kyrylych@gmail.com>:
2008/3/29, Grigorios Bouzakis <grbzks@gmail.com>:
On Sat, Mar 29, 2008 at 02:12:35PM +0100, Gerhard Brauer wrote:
Hello,
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 partition? Or with the order in rc scripts?
Maybe also that the hwclock is changed during/after installation...
Have others also seen such?
¹ http://users.archlinux.de/~gerbra/screen.png
-- Don't drink and root!
Yes i used to get that all the time. I think its somehow related to changes in tzdata that happened around a year ago. This only appears if you set the HARDWWARECLOCK to UTC as far as i can tell. Even though i dont have Widnows installed localtime works better for me, no such issues and plus the clock uses the correct time. UTC is 2 hours ahead.
Hmmm... I thought this was fixed long ago... I will try to reproduce the issue in virtual machine. It would be nice if you could provide the time set in your BIOS before install, output of `date` before and after running /arch/setup and after the first install.
FYI, see http://bugs.archlinux.org/task/5445
I dont remember having trouble at the time of the bug you posted. I think this started happening around the time tzdata was splitted from glibc or/and some changes happened with US timezones. I seem to have a memory of those two events combined with time issues in the back of my head but i cant be 100% sure. I am sure about the following. When installing from a 2007-08* or 2007-11 base/core iso , with BIOS time set properly & set HARDWWARECLOCK to UTC i get what gebra posted in the screenshot. If i set it to localtime it works normally. And as i said before Archlinux is the only OS on this PC. The only way of getting correct time with UTC is having the BIOS time set to actual time -2 hours. Setting USEDIRECTISA to yes or no doesnt affect anything of the above. Greg