SSD failure? COMRESET failed (errno=-16); reset failed, giving up

hobn · 2015-12-16 21:15:01

I had read-only filesystem errors on my / so I rebooted, but this looks like hardware failure. BIOS detects the SSD as a device I can try to boot from, but of course that doesn't work. When booting off USB it hangs a while trying to get the SSD to work but ultimately fails, leaving me with no /dev/sd* for that device. The SSD is not removable so little I can do there, and no there is nothing that I changed recently.

lspci

00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09)
00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09)
00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #3 (rev e3)
00:1f.0 ISA bridge: Intel Corporation Wildcat Point-LP LPC Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] (rev 03)
00:1f.6 Signal processing controller: Intel Corporation Wildcat Point-LP Thermal Management Controller (rev 03)
01:00.0 Network controller: Intel Corporation Wireless 7260 (rev cb)

dmesg | grep ata1 with default edd=on

[    2.149771] ata1: SATA max UDMA/133 abar m32768@0xe1210000 port 0xe1210100 irq 42
[    7.486145] ata1: link is slow to respond, please be patient (ready=0)
[   12.183266] ata1: COMRESET failed (errno=-16)
[   17.520905] ata1: link is slow to respond, please be patient (ready=0)
[   22.217994] ata1: COMRESET failed (errno=-16)
[   27.555670] ata1: link is slow to respond, please be patient (ready=0)
[   57.286299] ata1: COMRESET failed (errno=-16)
[   57.286335] ata1: limiting SATA link speed to 3.0 Gbps
[   62.303675] ata1: COMRESET failed (errno=-16)
[   62.303708] ata1: reset failed, giving up

with edd=off

[    2.159750] ata1: SATA max UDMA/133 abar m32768@0xe1210000 port 0xe1210100 irq 42
[    2.479164] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    2.479379] ata1.00: ATA-10: KINGSTON RBU-SUS151S364GD, S9FM01.8, max UDMA/133
[    2.479380] ata1.00: 125045424 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[    2.479699] ata1.00: configured for UDMA/133
[   34.435047] ata1.00: exception Emask 0x0 SAct 0x8000000 SErr 0x0 action 0x6 frozen
[   34.435090] ata1.00: failed command: READ FPDMA QUEUED
[   34.435118] ata1.00: cmd 60/08:d8:00:00:00/00:00:00:00:00/40 tag 27 ncq 4096 in
[   34.435179] ata1.00: status: { DRDY }
[   34.435199] ata1: hard resetting link
[   34.755246] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[   39.759318] ata1.00: qc timeout (cmd 0xec)
[   39.759334] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[   39.759339] ata1.00: revalidation failed (errno=-5)
[   39.759401] ata1: hard resetting link
[   45.096971] ata1: link is slow to respond, please be patient (ready=0)
[   49.794107] ata1: COMRESET failed (errno=-16)
[   49.794172] ata1: hard resetting link
[   55.131717] ata1: link is slow to respond, please be patient (ready=0)
[   59.828879] ata1: COMRESET failed (errno=-16)
[   59.828942] ata1: hard resetting link
[   65.166526] ata1: link is slow to respond, please be patient (ready=0)
[   94.897224] ata1: COMRESET failed (errno=-16)
[   94.897289] ata1: limiting SATA link speed to 3.0 Gbps
[   94.897294] ata1: hard resetting link
[   99.914611] ata1: COMRESET failed (errno=-16)
[   99.914677] ata1: reset failed, giving up
[   99.914721] ata1.00: disabled
[   99.914731] ata1.00: device reported invalid CHS sector 0
[   99.914776] ata1: EH complete

I guess the first question which I think I already know the answer to is, is this SSD dead dead? And is there any way to tell how it died? As in is this any way my fault or just defective hardware?

alphaniner · 2015-12-16 21:35:46

In best case something like that would be a connection issue. Are you sure it's actually non-removable (eg. soldered in place) rather than just not intended to be removed?

hobn · 2015-12-16 21:48:49

Yes, this is a laptop and the SSD is just a little chip on the motherboard. No plugging action I'm afraid.

alphaniner · 2015-12-16 22:08:42

Are you absotively, posilutely certain about that? I find it very hard to believe that a SATA device would be soldered on. In a tablet, maybe, but a laptop... I'd have to see it to believe it.

hobn · 2015-12-16 22:17:12

Yep. This is the Chromebook Pixel we're talking about specifically. You know, with the pathetically small amounts of internal storage because apparently nothing else fits inside.

alphaniner · 2015-12-16 22:43:44

And now I've seen it and must believe it.

Unless the thing's under warranty, you're probably out of luck.

Arch Linux

#1 2015-12-16 21:15:01

SSD failure? COMRESET failed (errno=-16); reset failed, giving up

#2 2015-12-16 21:35:46

Re: SSD failure? COMRESET failed (errno=-16); reset failed, giving up

#3 2015-12-16 21:48:49

Re: SSD failure? COMRESET failed (errno=-16); reset failed, giving up

#4 2015-12-16 22:08:42

Re: SSD failure? COMRESET failed (errno=-16); reset failed, giving up

#5 2015-12-16 22:17:12

Re: SSD failure? COMRESET failed (errno=-16); reset failed, giving up

#6 2015-12-16 22:43:44

Re: SSD failure? COMRESET failed (errno=-16); reset failed, giving up

Board footer