Comment 0 for bug 672751

Revision history for this message
Chris MacDonald (chris-fourthandvine) wrote :

I have both Intel D945GCLF and D510MO motherboards which produce I/O errors after running for a variable amount of time (usually inside of 72 hours). These motherboards are running with 1GB of RAM and a 4GB Micron eUSB SSD installed with Ubuntu 10.10. The Ubuntu installation is a server installation (no X) with Postgres and the OpenJDK JDK running my application (both Postgres and the application run as a non-root user).

After the device has been up for a certain amount of time, I/O errors and filesystem errors are printed to the terminal and each time the offending sector(s) is/are different. After this, I no longer have access to the file system and the vast majority of commands simply drop me back to the bash prompt without any output. These errors aren't logged in any system logs (the error attached was captured using serial output), there is no kernel oops or panic, nor does the system reboot but the system is rendered more or less unusable.

These errors started occurring for me with 10.04. I have several of these devices in the field and rolling them back to 9.10 has mitigated these errors. Since then, I've tried with 10.10 and the same errors have occurred. It is also worth noting that I've tried with both EXT3 and EXT4, both produce the same results. I've also set up a test case using a SATA hard drive connected to a SATA-to-USB bridge (05e3:0718 in lsusb) with the same results, which leads me to believe this isn't strictly a problem with the Micron eUSB modules I'm using.

If more information is required, please let me know. I have access to many of these devices so testing suggestions or fixes is not a problem. I started a thread on the Ubuntu Users list a while ago, for reference it can be found here: https://lists.ubuntu.com/archives/ubuntu-users/2010-November/233693.html