Hang during ext3 journal replay

[Jacques]

Hi,

I'm running intrepid with the latest patches on an EEEPC with a self-installed OCZ core 2 120GB SSD disk. I experienced a hard crash that needed hard reboot (pressing 5 seconds the power button) when trying some features of iwpriv with the ralink wireless driver. But this is not my main concern. The most annoying follows.

When I rebooted, the boot hang. The disk LED was continuously on but nothing happened, the boot sequence was stuck.

I rebooted on the intrepid live CD : same problem. It seems that the live CD tries to automatically mount every filesystem that it knows.

I hid the ext3 filesystem and rebooted on a rescuecd distribution. I tried to mount the partition manually. The command worked without error message but never went back. There was no kernel panic or crash. I could switch to another virtual console with CTRL ALT Fn. I tried dmesg, but nothing was to see in the kernel messages. I waited more than 5 minutes to see if a especially long journal replay was running but with no luck. I tried also to fsk.ext3. The process was also stuck into the kernel replaying stage.

This is a serious issue. I don't know if it is linked with the rather high bandwidth SSD disk I'm using. I had to do a full reinstall. Very bad. Since then, nothing special appeared.

Thanks for your help,
Jacques

[^_Pepe_^ (jose-angel-fernandez-freire)]

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 Karmic 9.10 release of Ubuntu? ISO CD images are
available from http://cdimage.ubuntu.com/releases/ .

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

apport-collect -p linux 308161

Thanks in advance

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

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