Comment 7 for bug 209346

I can also confirm this happens in jaunty. I cannot say exactly what causes it, but it happens after a few minutes whenever I boot my computer, thus rendering my computer unusable. There is nothing physically wrong with the hard drive as I've for one tried another one, and the computer is only half a year old. fsck fixes the disk (supposedly), but it won't let me remount with read-write, even after running "blockdev --setrw /dev/sda1".

Dmesg has the exact same output as already reported numerous times in this bug report. I'm under 64-bit jaunty running 2.6.28-11-generic, and the computer in question is an HP EliteBook 8730w. I've tried a re-install and same thing happened. I'll leave this installation as is until jaunty is up to release, so if more information is needed, please provide instructions of how I obtain said information.