Ext4 root system requires fsck on every reboot.

[pacanukeha]

Lucid beta. After every reboot I need to load into a live cd to run fsck on my ext4 / partition. If I don't the boot simply stops at one of two places -
either with all five of the red dots red
or
at 33-40% of a forced check repeating endlessly with no key press doing anything

If it is the five red dots thing then the fsck detects that the root node has a write time in the future.
If it is the endlessly repeating forced check then a number of inodes and other errors are found that can be fixed.

[pacanukeha (c-launchpad-pacanukeha-net)]

The system is an alienware dual core laptop. The / fs is on an SSD HD.

[Jeremy Foshee (jeremyfoshee)]

Hi pacanukeha,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 564015

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[pacanukeha (c-launchpad-pacanukeha-net)]

Hi Jeremy,

I think we can probably close it. It hasn't occurred since about a week before release. Sorry for not reporting back.