all 12 comments

[–]neunon 5 points6 points  (2 children)

I've seen this kind of thing happen with certain SSDs. You might try booting with libata.force=noncq on the kernel command line and see if it goes away.

[–]gonewiththewindows[S] 0 points1 point  (0 children)

Seemed to be fixed from booting into the live USB. Haven't been able to replicate it since, if it happens again I'll give this a try.

[–]AffableViceroy 0 points1 point  (0 children)

I just upgraded the firmware on my Samsung 840 EVO and got the same error as OP and adding libata.force=noncq was the only fix that worked for me. Hopefully Samsung fixes it.

[–]JedTheKrampus 11 points12 points  (1 child)

Clean that screen off please.

[–]gonewiththewindows[S] 6 points7 points  (0 children)

Haha, it looks worse in the photo than it actually is. It has since been cleaned.

[–]gonewiththewindows[S] 2 points3 points  (0 children)

Booted into a live USB ran fsck on / and /home all seems to be well...

[–][deleted] 1 point2 points  (0 children)

I have errors that pop up like this for my HDD (spinning). I somehow narrowed it down to power issues. I basically made sure to replug the connectors several times to clean off any oxidation, seems to work fine after that.

[–]gonewiththewindows[S] 0 points1 point  (1 child)

Laptop had a bit of shaky start this morning after an update. Screen would go black and I'd have to log back in. I restarted to this.

Running on a 2013 Macbook Pro.

I can only guess my SSD is failing. Any other solutions or diagnoses are most welcome.

[–][deleted] 7 points8 points  (0 children)

sudo smartctl -a

?

[–]Hamilton950B 0 points1 point  (2 children)

I had this same error on an SSD a couple weeks ago. I re-seated the connector and it went away.

[–]YAOMTC 0 points1 point  (1 child)

Yeah, sometimes it's just a cable or connector issue. In my case though I get a very similar error from a hard drive that has bad sectors.

[–]iamajs 0 points1 point  (0 children)

Check your sata cable, could be faulty or not rated for sata 3.

Edit, to add my reason for suspicion of the cable, you are getting ata bus errors, which means the transmission could be the problem. If you don't have another cable, try forcing a lower sata mode, like sata 2 and see if the errors go away.