Comment 4 for bug 405828

Revision history for this message
Alexander Hartl (alx321) wrote :

Sorry that I couldn't respond earlier. I had some trouble with my instalation: As I recognized that /dev/sda1 was displayed as ext3 in mount I thought maybe an update-initramfs will help, but afterwards grub couldn't start this kernel at all. Thus I reinstalled it using aptitude (it was updated to a slightly newer version). As it didn't help I restored the boot directory which made grub not start anymore as well. So I downloaded a ubuntu jaunty cd to be able to read and write ext4. Using this cd I did an fsck.ext4 on the partition but it just told me that it restored the journal. I then found out that I had to update to grub2 - after I had done this everything worked again - the bug suddenly didn't occur anymore.

I tried to reproduce it to be able to develop a fix by setting the date to a point in the future, booting and setting it back, but against my expectations fsck was not run on startup. So I ran it manually. It gave me "restoring journal" and found some other things that it fixed, no error concerning the superblock time BUT I then rebooted and suddenly the bug occured again on every bootup.

mount now gives me the right filesystem of /dev/sda1.

TZ=UTC date
gives me the same as
hwclock --show