Comment 15 for bug 487744

I just saw something similar - a scheduled fsck which proceeded nice and fast up to 70% and then very slowly, with no disk activity and apparently a lot of CPU activity (fan going, laptop warming up). I rebooted at 83% having got tired of waiting, and no fsck was scheduled on the next boot. Pressing "C to cancel" did not work. This is a machine that was originally (re-)installed as Karmic with ext4 and upgraded to Lucid one day before the first beta.

Not surprisingly there was no information about that particular boot in the syslog. Please let me know if I can provide any useful information though.