Comment 22 for bug 1318218

I was able to recreate this same problem on an ASrock Z87E-ITX with an mSATA SSD and both Ubuntu 12.04.5 and 14.04.1. Same series of errors in dmesg. I did manage to get a full install done - not sure how - but when the system boots it's prone to frequent lockups (also, occasionally, at boot, it claims it can't find /tmp).

In fact, I've found that if I boot the system into a live environment and just try mounting the SSD, I can see the same errors in dmesg. I can even get into gparted and create an empty ext4 partition on the drive, and see the errors. Even rebooting and trying to mount the empty partition causes the errors.

All of the "help" I"ve seen directs users to try different SATA cables or ports, but I can't put the mSATA SSD anywhere else, except in another system (where it works just fine). I did see one reference to disabling an ASMEDIA controller on a different ASrock motherboard, but the one I have doesn't include such a controller - it's just the Intel ICH.

For S&G I installed the Windows 8.1 trial on this system, on the mSATA SSD, and it runs without issue. No stutters, no lockups, no drive errors, no SMART errors, nothing.

The really strange thing: now that I've installed Windows on it, I have the system sitting in an Ubuntu live environment, with the windows install mounted., I've even written a few files to it, and I'm not seeing any errors at all.

I'm attaching output from lspci, lsusb, lshw-short and dmesg on the system - this dmesg output comes after I mounted the windows partition and wrote a file with some random text in it to the drive (this was enough to cause the errors previously). Unfortunately I didn't think to capture a dmesg prior to installing Windows 8.1 - it didn't occur to me that the problem might go away by doing so.

I'm going to try to install Ubuntu on the drive again and see what happens, however, if I can't duplicate the error, I'm going to be kicking myself for not getting a dmesg from before for comparison.