SSD Errors

Post Reply
nickc
Posts: 1
Joined: Wed Mar 11, 2015 12:12 pm

SSD Errors

Post by nickc »

For what it is worth here is a solution to a problem that had me tearing my hair out for a while.


I bought a USVR and 4xSSD because to me this is the holy grail of servers, no moving parts and no noise. One of the things I use this server for is recording TV using a HDHomerun and MythTV. Unlike my old server I was getting glitches in the recordings and it was slowly driving me mad trying to track down the cause. Recordings come from the HDHomerun as UDP packets so that any issues packets get dropped causing the glitches. Was it the reception, the tuners, the software, the filesystem or the SSD themselves????

As it turns out, there is a hardware issue. The Samsung EVO 840s when trying to run at 6.0 Gbps cause this kind of error as seen in the dmesg logs:

[ 4.304745] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 4.306898] ata1.00: supports DRM functions and may not be fully accessible
[ 4.306980] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
[ 4.307680] ata1.00: supports DRM functions and may not be fully accessible
[ 4.307899] ata1.00: failed to get NCQ Send/Recv Log Emask 0x1
[ 4.307914] ata1.00: configured for UDMA/133
[ 4.307963] ata1: EH complete
[ 4.309564] ata1.00: exception Emask 0x10 SAct 0x8 SErr 0x400000 action 0x6 frozen
[ 4.309574] ata1.00: irq_stat 0x08000000, interface fatal error
[ 4.309580] ata1: SError: { Handshk }
[ 4.309587] ata1.00: failed command: WRITE FPDMA QUEUED
[ 4.309597] ata1.00: cmd 61/08:18:a0:0a:84/00:00:0b:00:00/40 tag 3 ncq 4096 out
[ 4.309597] res 40/00:18:a0:0a:84/00:00:0b:00:00/40 Emask 0x10 (ATA bus error)
[ 4.309602] ata1.00: status: { DRDY }
[ 4.309612] ata1: hard resetting link

The solution is to limit the links to 3.0 Gbps by passing the kernel option libata.force=1:3.0G,2:3.0G,3:3.0G,4:3.0G

Plenty fast enough for me. Hope this helps someone.

Post Reply

Return to “General uSVR questions”