Brand new 525 SSD (120GB) stops responding on write

[ANiel2]

Hi all,

I am just setting up a brand new 525-series SSD (SSDMCEAC12) and as soon as I try to write more than a few MB of data to it it stops responding. I can't even use smartctl to get any details out of the drive, and if I reset the PC it locks up at the BIOS logo (motherboard is an Intel DH87MC.)

If I power off the board for a few minutes then everything seems fine until I write more than a few MB to the SSD and then it stops responding again. Am I doing something wrong? I'm just booting Linux off a USB stick and copying files onto the SSD over the network (so that I can then boot off the SSD instead.) The SSD is not warm at all so it's not a temperature issue. Before it locks up smartctl reports a normal temperature (33 degrees.)

Here are some of the kernel messages I get when things break:

Sep 07 16:07:52 archiso kernel: ata6.00: exception Emask 0x0 SAct 0xfffffff SErr 0x0 action 0x6 frozen Sep 07 16:07:52 archiso kernel: ata6.00: failed command: READ FPDMA QUEUED Sep 07 16:07:52 archiso kernel: [135B blob data] Sep 07 16:07:52 archiso kernel: ata6.00: status: { DRDY } Sep 07 16:07:52 archiso kernel: ata6.00: failed command: WRITE FPDMA QUEUED Sep 07 16:07:52 archiso kernel: [138B blob data] Sep 07 16:07:52 archiso kernel: ata6.00: status: { DRDY } Sep 07 16:07:52 archiso kernel: ata6.00: failed command: WRITE FPDMA QUEUED Sep 07 16:07:52 archiso kernel: [138B blob data] Sep 07 16:07:52 archiso kernel: ata6.00: status: { DRDY } Sep 07 16:07:52 archiso kernel: ata6.00: failed command: WRITE FPDMA QUEUED Sep 07 16:07:52 archiso kernel: [138B blob data] Sep 07 16:07:52 archiso kernel: ata6.00: status: { DRDY } Sep 07 16:07:52 archiso kernel: ata6.00: failed command: WRITE FPDMA QUEUED Sep 07 16:07:52 archiso kernel: [138B blob data] Sep 07 16:07:52 archiso kernel: ata6.00: status: { DRDY } Sep 07 16:07:52 archiso kernel: ata6.00: failed command: WRITE FPDMA QUEUED Sep 07 16:07:52 archiso kernel: [138B blob data] Sep 07 16:07:52 archiso kernel: ata6.00: status: { DRDY } ... Sep 07 16:07:52 archiso kernel: ata6: hard resetting link Sep 07 16:07:58 archiso kernel: ata6: link is slow to respond, please be patient (ready=0) Sep 07 16:08:02 archiso kernel: ata6: COMRESET failed (errno=-16) Sep 07 16:08:02 archiso kernel: ata6: hard resetting link Sep 07 16:08:08 archiso kernel: ata6: link is slow to respond, please be patient (ready=0) Sep 07 16:08:12 archiso kernel: ata6: COMRESET failed (errno=-16) Sep 07 16:08:12 archiso kernel: ata6: hard resetting link Sep 07 16:08:18 archiso kernel: ata6: link is slow to respond, please be patient (ready=0) ... Sep 07 16:08:47 archiso kernel: ata6: COMRESET failed (errno=-16) Sep 07 16:08:47 archiso kernel: ata6: limiting SATA link speed to 3.0 Gbps Sep 07 16:08:47 archiso kernel: ata6: hard resetting link Sep 07 16:08:52 archiso kernel: ata6: COMRESET failed (errno=-16) Sep 07 16:08:52 archiso kernel: ata6: reset failed, giving up Sep 07 16:08:52 archiso kernel: ata6.00: disabled Sep 07 16:08:52 archiso kernel: ata6.00: device reported invalid CHS sector 0 Sep 07 16:08:52 archiso kernel: ata6.00: device reported invalid CHS sector 0

[idata]

I just bought an Intel 525 240GB and attached it to a machine and I just encountered the same issue. The motherboard is a GIGABYTE M4HM87P-00 with BIOS F2 (latest available AFAIK). Is there a firmware issue or something?

[ 2140.580025] ata5.00: exception Emask 0x10 SAct 0x7fffffff SErr 0x4890000 action 0xe frozen

[ 2140.580056] ata5.00: irq_stat 0x08400040, interface fatal error, connection status changed

[ 2140.580082] ata5: SError: { PHYRdyChg 10B8B LinkSeq DevExch }

[ 2140.580100] ata5.00: failed command: WRITE FPDMA QUEUED

[ 2140.580118] ata5.00: cmd 61/00:00:00:10:7d/04:00:01:00:00/40 tag 0 ncq 524288 out

res 40/00:28:00:a8:7c/00:00:01:00:00/40 Emask 0x10 (ATA bus error)

[ 2140.580164] ata5.00: status: { DRDY }

[ 2140.580176] ata5.00: failed command: WRITE FPDMA QUEUED

[ 2140.580193] ata5.00: cmd 61/00:08:00:14:7d/04:00:01:00:00/40 tag 1 ncq 524288 out

res 40/00:28:00:a8:7c/00:00:01:00:00/40 Emask 0x10 (ATA bus error)

[ 2140.580238] ata5.00: status: { DRDY }

[ 2140.580250] ata5.00: failed command: WRITE FPDMA QUEUED

[ 2140.580267] ata5.00: cmd 61/00:10:00:18:7d/04:00:01:00:00/40 tag 2 ncq 524288 out

res 40/00:28:00:a8:7c/00:00:01:00:00/40 Emask 0x10 (ATA bus error)

[ 2140.580311] ata5.00: status: { DRDY }

[ 2140.580323] ata5.00: failed command: WRITE FPDMA QUEUED

[ 2140.580340] ata5.00: cmd 61/00:18:00:a0:7c/04:00:01:00:00/40 tag 3 ncq 524288 out

res 40/00:28:00:a8:7c/00:00:01:00:00/40 Emask 0x10 (ATA bus error)

[ 2140.580384] ata5.00: status: { DRDY }

[ 2140.580396] ata5.00: failed command: WRITE FPDMA QUEUED

[ 2140.580413] ata5.00: cmd 61/00:20:00:a4:7c/04:00:01:00:00/40 tag 4 ncq 524288 out

res 40/00:28:00:a8:7c/00:00:01:00:00/40 Emask 0x10 (ATA bus error)

[ 2140.580457] ata5.00: status: { DRDY }

[ 2140.580469] ata5.00: failed command: WRITE FPDMA QUEUED

[ 2140.580486] ata5.00: cmd 61/00:28:00:a8:7c/04:00:01:00:00/40 tag 5 ncq 524288 out

res 40/00:28:00:a8:7c/00:00:01:00:00/40 Emask 0x10 (ATA bus error)

[ 2140.580531] ata5.00: status: { DRDY }

[ 2140.580543] ata5.00: failed command: WRITE FPDMA QUEUED

[ 2140.580560] ata5.00: cmd 61/00:30:00:ac:7c/04:00:01:00:00/40 tag 6 ncq 524288 out

res 40/00:28:00:a8:7c/00:00:01:00:00/40 Emask 0x10 (ATA bus error)

[ 2140.580604] ata5.00: status: { DRDY }

[ 2140.580616] ata5.00: failed command: WRITE FPDMA QUEUED

[ 2140.580633] ata5.00: cmd 61/00:38:00:b0:7c/04:00:01:00:00/40 tag 7 ncq 524288 out

res 40/00:28:00:a8:7c/00:00:01:00:00/40 Emask 0x10 (ATA bus error)

[ 2140.580678] ata5.00: status: { DRDY }

[ 2140.580689] ata5.00: failed command: WRITE FPDMA QUEUED

[ 2140.580706] ata5.00: cmd 61/00:40:00:b4:7c/04:00:01:00:00/40 tag 8 ncq 524288 out

res 40/00:28:00:a8:7c/00:00:01:00:00/40 Emask 0x10 (ATA bus error)

[ 2140.580751] ata5.00: status: { DRDY }

[ 2140.580762] ata5.00: failed command: WRITE FPDMA QUEUED

[ 2140.580780] ata5.00: cmd 61/00:48:00:b8:7c/04:00:01:00:00/40 tag 9 ncq 524288 out

res 40/00:28:00:a8:7c/00:00:01:00:00/40 Emask 0x10 (ATA bus error)

[ 2140.580824] ata5.00: status: { DRDY }

[ 2140.580836] ata5.00: failed command: WRITE FPDMA QUEUED

[ 2140.580854] ata5.00: cmd 61/00:50:00:bc:7c/04:00:01:00:00/40 tag 10 ncq 524288 out

res 40/00:28:00:a8:7c/00:00:01:00:00/40 Emask 0x10 (ATA bus error)

[ 2140.580898] ata5.00: status: { DRDY }

[ 2140.580910] ata5.00: failed command: WRITE FPDMA QUEUED

[ 2140.580927] ata5.00: cmd 61/00:58:00:c0:7c/04:00:01:00:00/40 tag 11 ncq 524288 out

res 40/00:28:00:a8:7c/00:00:01:00:00/40 Emask 0x10 (ATA bus error)

[ 2140.580972] ata5.00: status: { DRDY }

[ 2140.580983] ata5.00: failed command: WRITE FPDMA QUEUED

[ 2140.581000] ata5.00: cmd 61/00:60:00:c4:7c/04:00:01:00:00/40 tag 12 ncq 524288 out

res 40/00:28:00:a8:7c/00:00:01:00:00/40 Emask 0x10 (ATA bus error)

[ 2140.581045] ata5.00: status: { DRDY }

[ 2140.581056] ata5.00: failed command: WRITE FPDMA QUEUED

[ 2140.581074] ata5.00: cmd 61/00:68:00:c8:7c/04:00:01:00:00/40 tag 13 ncq 524288 out

res 40/00:28:00:a8:7c/00:00:01:00:00/40 Emask 0x10 (ATA bus error)

[ 2140.581118] ata5.00: status: { DRDY }

[ 2140.581130] ata5.00: failed command: WRITE FPDMA QUEUED

[ 2140.581148] ata5.00: cmd 61/00:70:00:cc:7c/04:00:01:00:00/40 tag 14 ncq 524288 out

res 40/00:28:00:a8:7c/00:00:01:00:00/40 Emask 0x10 (ATA bus error)

[ 2140.581193] ata5.00: status: { DRDY }

[ 2140.581204] ata5.00: failed command: WRITE FPDMA QUEUED

[ 2140.581221] ata5.00: cmd 61/00:78:00:d0:7c/04:00:01:00:00/40 tag 15 ncq 524288 out

res 40/00:28:00:a8:7c/00:00:01:00:00/40 Emask 0x10 (ATA bus error)

[ 2140.581266] ata5.00: status: { DRDY }

[ 2140.581278] ata5.00: failed command: WRITE FPDMA QUEUED

[ 2140.581295] ata5.00: cmd 61/00:80:00:d4:7c/04:00:01:00:00/40 tag 16 ncq 524288 out

res 40/00:28:00:a8:7c/00:00:01:00:00/40 Emask 0x10 (ATA bus error)

[ 2140.581339] ata5.00: status: { DRDY }

[ 2140.581351] ata5.00: failed command: WRITE FPDMA QUEUED

[ 2140.582430] ata5.00: cmd 61/00:88:00:d8:7c/04:00:01:00:00/40 tag 17 ncq 524288 out

res 40/00:28:00:a8:7c/00:00:01:00:00/40 Emask 0x10 (ATA bus error)

[ 2140.584674] ata5.00: status: { DRDY }

[ 2140.585760] ata5.00: failed command: WRITE FPDMA QUEUED

[ 2140.586843] ata5.00: cmd 61/00:90:00:dc:7c/04:00:01:00:00/40 tag 18 ncq 524288 out

res 40/00:28:00:a8:7c/00:00:01:00:00/40 Emask 0x10 (ATA bus error)

[ 2140.588985] ata5.00: status: { DRDY }

[ 2140.590050] ata5.00: failed command: WRITE FPDMA QUEUED

[ 2140.591120] ata5.00: cmd 61/00:98:00:e0:7c/04:00:01:00:00/40 tag 19 ncq 524288 out

res 40/00:28:00:a8:7c/00:00:01:00:00/40 Emask 0x10 (ATA bus error)

[ 2140.593277] ata5.00: status: { DRDY }

[ 2140.594338] ata5.00: failed command: WRITE FPDMA QUEUED

[ 2140.595402] ata5.00: cmd 61/00:a0:00:e4:7c/04:00:01:00:00/40 tag 20 ncq 524288 out

res 40/00:28:00:a8:7c/00:00:01:00:00/40 Emask 0x10 (ATA bus error)

[ 2140.597536] ata5.00: status: { DRDY }

[ 2140.598598] ata5.00: failed command: WRITE FPDMA QUEUED

[ 2140.599664] ata5.00: cmd 61/00:a8:00:e8:7c/04:00:01:00:00/40 tag 21 ncq 524288 out

res 40/00:28:00:a8:7c/00:00:01:00:00/40 Emask 0x10 (ATA bus error)

[ 2140.601800] ata5.00: status: { DRDY }

[ 2140.602882] ata5.00: failed command: WRITE FPDMA QUEUED

[ 2140.603973] ata5.00: cmd 61/00:b0:00:ec:7c/04:00:01:00:00/40 tag 22 ncq 524288 out

res 40/00:28:00:a8:7c/00:00:01:00:00/40 Emask 0x10 (ATA bus error)

[ 2140.606644] ata5.00: status: { DRDY }

[ 2140.607973] ata5.00: failed command: WRITE FPDMA QUEUED

[ 2140.609304] ata5.00: cmd 61/00:b8:00:f0:7c/04:00:01:00:00/40 tag 23 ncq 524288 out

res 40/00:28:00:a8:7c/00:00:01:00:00/40 Emask 0x10 (ATA bus error)

[ 2140.611527] ata5.00: status: { DRDY }

[ 2140.612599] ata5.00: failed command: WRITE FPDMA QUEUED

[ 2140.613691] ata5.00: cmd 61/00:c0:00:f4:7c/04:00:01:00:00/40 tag 24 ncq 524288 out

res 40/00:28:00:a8:7c/00:00:01:00:00/40 Emask 0x10 (ATA bus error)

[ 2140.615841] ata5.00: status: { DRDY }

[ 2140.616909] ata5.00: failed command: WRITE FPDMA QUEUED

[ 2140.617982] ata5.00: cmd 61/00:c8:00:f8:7c/04:00:01:00:00/40 tag 25 ncq 524288 out

...

[idata]

Also, I tried doing a long SMART test via 'smartctl -t long /dev/sdb', and eventually this happened and the device dropped off the SATA bus:

[ 407.025624] ata5: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen

[ 407.025652] ata5: irq_stat 0x00400040, connection status changed

[ 407.025672] ata5: SError: { HostInt PHYRdyChg 10B8B DevExch }

[ 407.025693] ata5: hard resetting link

[ 407.770332] ata5: SATA link down (SStatus 0 SControl 300)

[ 412.774313] ata5: hard resetting link

[ 413.124594] ata5: SATA link down (SStatus 0 SControl 300)

[ 413.124600] ata5: limiting SATA link speed to 1.5 Gbps

[ 418.128590] ata5: hard resetting link

[ 418.478858] ata5: SATA link down (SStatus 0 SControl 310)

[ 418.478865] ata5.00: disabled

[ 418.478884] ata5: EH complete

[ 418.478889] ata5.00: detaching (SCSI 4:0:0:0)

[ 418.479096] sd 4:0:0:0: [sdb] Synchronizing SCSI cache

[ 418.479111] sd 4:0:0:0: [sdb]

[ 418.479113] Result: hostbyte=0x04 driverbyte=0x00

[ 418.479129] sd 4:0:0:0: [sdb] Stopping disk

[ 418.479133] sd 4:0:0:0: [sdb] START_STOP FAILED

[ 418.479149] sd 4:0:0:0: [sdb]

[ 418.479150] Result: hostbyte=0x04 driverbyte=0x00

[ANiel2]

Is there a firmware issue or something?

Don't take this the wrong way, but maybe you should read the thread first before posting - you would have already found your answer if you did!

[idata]

Malvineous wrote:

Is there a firmware issue or something?

Don't take this the wrong way, but maybe you should read the thread first before posting - you would have already found your answer if you did!

I haven't seen an answer, only an unconfirmed theory that it's not drawing enough power from the motherboard.

[ANiel2]

It's not a theory, it's what Intel engineering believe the problem is. So it looks like your only options are to somehow try getting a bit more power to the board (assuming the 3.3V rail on the mSATA slot comes from the PSU and you have one with an adjustable 3.3V rail) or to return the SSD and try another one.