Comment 117 for bug 1063354

Just a follow up... My problem is fixed or at least figured out. Although many with this bug have similar log output mine was definitely hardware. SATA hard drives have extremely fragile connectors and the connector to this particular drive with the read only problem was slightly pushed down by another connector. It finally broke the HD plug socket just enough to make a bad connection. It's practically imperceptible until you remove the connector as see the slight movement of the HD plug component. I reconnected the plug and put slight pressure underneath the component, started the computer and it fired right up. The system did a forced fsck and it is working with all data present and permissions corrected. Now I just need to dump all the data to a new HD.

This may be an issue for some and not for others but the outcome and the dmesg logs show ata errors on that drive. It would be very easy to miss the breakage since it's a very small variance, and it's bizaar that it causes the read only problem as stated above but nothing else.