SSD Cache Drive mounted Read-Only

[Phil Wilson]

This is the second time it's happened...it's always just random, while the array is running and everything else appears normal. The SSD and cables are brand new so I doubt that's the problem. I've include the diagnostics zipfile if anyone can help me.

 

My Wife is about to throw me and UnRaid out the door because it interrupts her TV viewing.

tower-diagnostics-20190302-2052.zip

[JorgeB]

Next times grab the diags before rebooting, not much to see on those.

[Phil Wilson]

It happened again this morning. 

 

Also, the Dashboard has NO indication there is anything wrong. No notifications or any other indicators. I just know because Emby stops working.

 

tower-diagnostics-20190303-0802.zip

[JorgeB]

SSD dropped offline:

Mar  3 04:19:31 Tower kernel: ata1.00: status: { DRDY }
Mar  3 04:19:31 Tower kernel: ata1: hard resetting link
Mar  3 04:19:36 Tower kernel: ata1: link is slow to respond, please be patient (ready=0)
Mar  3 04:19:41 Tower kernel: ata1: COMRESET failed (errno=-16)
Mar  3 04:19:41 Tower kernel: ata1: hard resetting link
Mar  3 04:19:46 Tower kernel: ata1: link is slow to respond, please be patient (ready=0)
Mar  3 04:19:51 Tower kernel: ata1: COMRESET failed (errno=-16)
Mar  3 04:19:51 Tower kernel: ata1: hard resetting link
Mar  3 04:19:56 Tower kernel: ata1: link is slow to respond, please be patient (ready=0)
Mar  3 04:20:26 Tower kernel: ata1: COMRESET failed (errno=-16)
Mar  3 04:20:26 Tower kernel: ata1: limiting SATA link speed to 3.0 Gbps
Mar  3 04:20:26 Tower kernel: ata1: hard resetting link
Mar  3 04:20:31 Tower kernel: ata1: COMRESET failed (errno=-16)
Mar  3 04:20:31 Tower kernel: ata1: reset failed, giving up
Mar  3 04:20:31 Tower kernel: ata1.00: disabled

Most likely a cable issue, replace both cables.

[limetech]

On 3/3/2019 at 8:10 AM, johnnie.black said:

SSD dropped offline:

Mar  3 04:19:31 Tower kernel: ata1.00: status: { DRDY }
Mar  3 04:19:31 Tower kernel: ata1: hard resetting link
Mar  3 04:19:36 Tower kernel: ata1: link is slow to respond, please be patient (ready=0)
Mar  3 04:19:41 Tower kernel: ata1: COMRESET failed (errno=-16)
Mar  3 04:19:41 Tower kernel: ata1: hard resetting link
Mar  3 04:19:46 Tower kernel: ata1: link is slow to respond, please be patient (ready=0)
Mar  3 04:19:51 Tower kernel: ata1: COMRESET failed (errno=-16)
Mar  3 04:19:51 Tower kernel: ata1: hard resetting link
Mar  3 04:19:56 Tower kernel: ata1: link is slow to respond, please be patient (ready=0)
Mar  3 04:20:26 Tower kernel: ata1: COMRESET failed (errno=-16)
Mar  3 04:20:26 Tower kernel: ata1: limiting SATA link speed to 3.0 Gbps
Mar  3 04:20:26 Tower kernel: ata1: hard resetting link
Mar  3 04:20:31 Tower kernel: ata1: COMRESET failed (errno=-16)
Mar  3 04:20:31 Tower kernel: ata1: reset failed, giving up
Mar  3 04:20:31 Tower kernel: ata1.00: disabled

Most likely a cable issue, replace both cables.

Which in turn is causing btrfs I/O to fail.

 

@johnnie.black - with HDD's this logging pattern is almost always due to controller/cable issues (and rarely HDD itself), but with SSD's could it also be less rare issue is with the SSD itself?

[JorgeB]

44 minutes ago, limetech said:

but with SSD's could it also be less rare issue is with the SSD itself?

Yes, but large majority of cases is a cable problem.