Comment 29 for bug 63175

Sorry it's taken me a while to get back to this. As of right now, I'm thoroughly confused.

I left the Edgy box up for the past couple weeks (no need to reboot, and was tired of the fsck action). But I rebooted now just to generate the bootchart - and fsck didn't run. Also, I've checked the tune2fs output, and it looks like now the last fsck check has been updated in the output to reflect 28-Feb (my last reboot prior to todays).

My system clock appears to be behaving normally. The "future" date from my previous attachment was because sudo was giving me grief (date too far in the future). I ran sudo for some stuff, then I enabled NTP which changed my clock to +8GMT (I'm in Singapore). So to avoid rebooting I had thrown my clock even further ahead manually in order to get sudo to behave without rebooting.

I'll attach the bootchart anyways, as well as /var/log/udev.

The output for cat /var/log/fsck/* is small, so I'll paste:

daniel@daniel-desktop:~$ cat /var/log/fsck/*
Log of fsck -C -R -A -a
Tue Mar 13 08:51:23 2007

fsck 1.39 (29-May-2006)
/dev/md0: clean, 11216/19546112 files, 4482325/39072064 blocks

Tue Mar 13 08:51:23 2007
----------------
Log of fsck -C -a -t ext3 /dev/hda1
Tue Mar 13 08:51:23 2007

fsck 1.39 (29-May-2006)
/dev/hda1: clean, 155148/9371648 files, 1243005/18731782 blocks

Tue Mar 13 08:51:23 2007
----------------
daniel@daniel-desktop:~$