Comment 26 for bug 1318218

So, I used gparted to format the drive with a single ext4 partition, rebooted the system, mounted it, and the errors came back.

It's not a hardware issue. It's some combination of the OS, chipset, file system in use, and maybe (?) drive type. I can use the same drive on a Gigabyte board that uses the B85 chipset and have zero issues, so it doesn't seem to be the entire lynx point chipset family. The Z87 on this board is the revised C2 stepping.

Anecdotal evidence from web searches might indicate some relation to ASrock Z87 boards in particular, but then, user reports of the error go back several years, and earlier reports were oftentimes hardware issues. And obviously, in the case of the initial bug report here, it was a Macbook Pro.

I'm attaching dmesg output from the same system, this is from a fresh boot to a live environment and mounting the drive by clicking it in nautilus. The errors were back, just as they were before.

After reinstalling the Windows 8 Trial on the system, it's back to working without any errors in a live ubuntu environment. Not really sure what to make of this, aside from it not being a hardware problem.