Jump to content

New Samsung 860 PRO SSD Errors

dlandon

By dlandon
in General Support

Recommended Posts

dlandon Veteran

dlandon

Posted
Posted

I just installed a new Samsung PRO 1TB SSD in my server as a Pool device to hold VMs and Docker image.  After a day of operation I got some errors this morning: 

Jul 3 20:38:51 MediaServer kernel: ata10: SATA max UDMA/133 abar m512@0x61400000 port 0x61400180 irq 137
Jul 3 20:38:51 MediaServer kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jul 3 20:38:51 MediaServer kernel: ata10.00: supports DRM functions and may not be fully accessible
Jul 3 20:38:51 MediaServer kernel: ata10.00: ATA-11: Samsung SSD 860 PRO 1TB, S5G8NC0N500080A, RVM02B6Q, max UDMA/133
Jul 3 20:38:51 MediaServer kernel: ata10.00: 2000409264 sectors, multi 1: LBA48 NCQ (depth 32), AA
Jul 3 20:38:51 MediaServer kernel: ata10.00: supports DRM functions and may not be fully accessible
Jul 3 20:38:51 MediaServer kernel: ata10.00: configured for UDMA/133
Jul 3 20:38:51 MediaServer kernel: ata10.00: Enabling discard_zeroes_data
Jul 3 20:38:51 MediaServer kernel: sd 11:0:0:0: [sdk] 2000409264 512-byte logical blocks: (1.02 TB/954 GiB)
Jul 3 20:38:51 MediaServer kernel: sd 11:0:0:0: [sdk] Write Protect is off
Jul 3 20:38:51 MediaServer kernel: sd 11:0:0:0: [sdk] Mode Sense: 00 3a 00 00
Jul 3 20:38:51 MediaServer kernel: sd 11:0:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jul 3 20:38:51 MediaServer kernel: ata10.00: Enabling discard_zeroes_data
Jul 3 20:38:51 MediaServer kernel: sdk: sdk1
Jul 3 20:38:51 MediaServer kernel: ata10.00: Enabling discard_zeroes_data
Jul 3 20:38:51 MediaServer kernel: sd 11:0:0:0: [sdk] Attached SCSI disk
Jul 3 20:39:05 MediaServer emhttpd: Samsung_SSD_860_PRO_1TB_S5G8NC0N500080A (sdk) 512 2000409264
Jul 3 20:39:05 MediaServer emhttpd: import 31 cache device: (sdk) Samsung_SSD_860_PRO_1TB_S5G8NC0N500080A
Jul 3 20:39:15 MediaServer emhttpd: shcmd (48): mount -t xfs -o noatime,nodiratime /dev/sdk1 /mnt/sysdata
Jul 3 20:39:15 MediaServer kernel: XFS (sdk1): Mounting V5 Filesystem
Jul 3 20:39:15 MediaServer kernel: XFS (sdk1): Ending clean mount
Jul 4 05:30:34 MediaServer kernel: ata10.00: exception Emask 0x0 SAct 0x7ff071 SErr 0x0 action 0x6 frozen
Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED
Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 61/40:00:a0:a5:d7/00:00:1d:00:00/40 tag 0 ncq dma 32768 out
Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED
Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 61/40:20:a0:a5:f7/00:00:1d:00:00/40 tag 4 ncq dma 32768 out
Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED
Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 61/08:28:98:15:bc/00:00:1f:00:00/40 tag 5 ncq dma 4096 out
Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED
Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 61/08:30:98:15:3c/00:00:20:00:00/40 tag 6 ncq dma 4096 out
Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED
Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 61/08:60:f8:40:d9/00:00:59:00:00/40 tag 12 ncq dma 4096 out
Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED
Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 61/08:68:80:41:d9/00:00:59:00:00/40 tag 13 ncq dma 4096 out
Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED
Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 64/01:70:00:00:00/00:00:00:00:00/a0 tag 14 ncq dma 512 out
Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED
Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 64/01:78:00:00:00/00:00:00:00:00/a0 tag 15 ncq dma 512 out
Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED
Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 64/01:80:00:00:00/00:00:00:00:00/a0 tag 16 ncq dma 512 out
Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED
Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 64/01:88:00:00:00/00:00:00:00:00/a0 tag 17 ncq dma 512 out
Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED
Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 64/01:90:00:00:00/00:00:00:00:00/a0 tag 18 ncq dma 512 out
Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED
Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 64/01:98:00:00:00/00:00:00:00:00/a0 tag 19 ncq dma 512 out
Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED
Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 61/08:a0:20:8b:6a/00:00:00:00:00/40 tag 20 ncq dma 4096 out
Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED
Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 61/08:a8:a8:8b:6a/00:00:00:00:00/40 tag 21 ncq dma 4096 out
Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:30:34 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED
Jul 4 05:30:34 MediaServer kernel: ata10.00: cmd 61/00:b0:80:bb:1a/01:00:63:00:00/40 tag 22 ncq dma 131072 out
Jul 4 05:30:34 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:30:34 MediaServer kernel: ata10: hard resetting link
Jul 4 05:30:34 MediaServer kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jul 4 05:30:34 MediaServer kernel: ata10.00: supports DRM functions and may not be fully accessible
Jul 4 05:30:34 MediaServer kernel: ata10.00: supports DRM functions and may not be fully accessible
Jul 4 05:30:34 MediaServer kernel: ata10.00: configured for UDMA/133
Jul 4 05:30:34 MediaServer kernel: ata10: EH complete
Jul 4 05:31:05 MediaServer kernel: ata10.00: exception Emask 0x0 SAct 0xffcd00 SErr 0x0 action 0x6 frozen
Jul 4 05:31:05 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED
Jul 4 05:31:05 MediaServer kernel: ata10.00: cmd 61/08:40:20:8b:6a/00:00:00:00:00/40 tag 8 ncq dma 4096 out
Jul 4 05:31:05 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:31:05 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED
Jul 4 05:31:05 MediaServer kernel: ata10.00: cmd 64/01:50:00:00:00/00:00:00:00:00/a0 tag 10 ncq dma 512 out
Jul 4 05:31:05 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:31:05 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED
Jul 4 05:31:05 MediaServer kernel: ata10.00: cmd 64/01:58:00:00:00/00:00:00:00:00/a0 tag 11 ncq dma 512 out
Jul 4 05:31:05 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:31:05 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED
Jul 4 05:31:05 MediaServer kernel: ata10.00: cmd 64/01:70:00:00:00/00:00:00:00:00/a0 tag 14 ncq dma 512 out
Jul 4 05:31:05 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:31:05 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED
Jul 4 05:31:05 MediaServer kernel: ata10.00: cmd 64/01:78:00:00:00/00:00:00:00:00/a0 tag 15 ncq dma 512 out
Jul 4 05:31:05 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:31:05 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED
Jul 4 05:31:05 MediaServer kernel: ata10.00: cmd 64/01:80:00:00:00/00:00:00:00:00/a0 tag 16 ncq dma 512 out
Jul 4 05:31:05 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:31:05 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED
Jul 4 05:31:05 MediaServer kernel: ata10.00: cmd 64/01:88:00:00:00/00:00:00:00:00/a0 tag 17 ncq dma 512 out
Jul 4 05:31:05 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:31:05 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED
Jul 4 05:31:05 MediaServer kernel: ata10.00: cmd 61/08:90:80:41:d9/00:00:59:00:00/40 tag 18 ncq dma 4096 out
Jul 4 05:31:05 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:31:05 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED
Jul 4 05:31:05 MediaServer kernel: ata10.00: cmd 61/08:98:f8:40:d9/00:00:59:00:00/40 tag 19 ncq dma 4096 out
Jul 4 05:31:05 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:31:05 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED
Jul 4 05:31:05 MediaServer kernel: ata10.00: cmd 61/08:a0:98:15:3c/00:00:20:00:00/40 tag 20 ncq dma 4096 out
Jul 4 05:31:05 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:31:05 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED
Jul 4 05:31:05 MediaServer kernel: ata10.00: cmd 61/08:a8:98:15:bc/00:00:1f:00:00/40 tag 21 ncq dma 4096 out
Jul 4 05:31:05 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:31:05 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED
Jul 4 05:31:05 MediaServer kernel: ata10.00: cmd 61/40:b0:a0:a5:f7/00:00:1d:00:00/40 tag 22 ncq dma 32768 out
Jul 4 05:31:05 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:31:05 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED
Jul 4 05:31:05 MediaServer kernel: ata10.00: cmd 61/40:b8:a0:a5:d7/00:00:1d:00:00/40 tag 23 ncq dma 32768 out
Jul 4 05:31:05 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:31:05 MediaServer kernel: ata10: hard resetting link
Jul 4 05:31:05 MediaServer kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jul 4 05:31:05 MediaServer kernel: ata10.00: supports DRM functions and may not be fully accessible
Jul 4 05:31:05 MediaServer kernel: ata10.00: supports DRM functions and may not be fully accessible
Jul 4 05:31:05 MediaServer kernel: ata10.00: configured for UDMA/133
Jul 4 05:31:05 MediaServer kernel: ata10: EH complete
Jul 4 05:31:05 MediaServer kernel: ata10.00: Enabling discard_zeroes_data
Jul 4 05:31:35 MediaServer kernel: ata10.00: exception Emask 0x0 SAct 0xff0000 SErr 0x0 action 0x6 frozen
Jul 4 05:31:35 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED
Jul 4 05:31:35 MediaServer kernel: ata10.00: cmd 61/08:80:80:41:d9/00:00:59:00:00/40 tag 16 ncq dma 4096 out
Jul 4 05:31:35 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:31:35 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED
Jul 4 05:31:35 MediaServer kernel: ata10.00: cmd 64/01:88:00:00:00/00:00:00:00:00/a0 tag 17 ncq dma 512 out
Jul 4 05:31:35 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:31:35 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED
Jul 4 05:31:35 MediaServer kernel: ata10.00: cmd 64/01:90:00:00:00/00:00:00:00:00/a0 tag 18 ncq dma 512 out
Jul 4 05:31:35 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:31:35 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED
Jul 4 05:31:35 MediaServer kernel: ata10.00: cmd 64/01:98:00:00:00/00:00:00:00:00/a0 tag 19 ncq dma 512 out
Jul 4 05:31:35 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:31:35 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED
Jul 4 05:31:35 MediaServer kernel: ata10.00: cmd 64/01:a0:00:00:00/00:00:00:00:00/a0 tag 20 ncq dma 512 out
Jul 4 05:31:35 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:31:35 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED
Jul 4 05:31:35 MediaServer kernel: ata10.00: cmd 64/01:a8:00:00:00/00:00:00:00:00/a0 tag 21 ncq dma 512 out
Jul 4 05:31:35 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:31:35 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED
Jul 4 05:31:35 MediaServer kernel: ata10.00: cmd 64/01:b0:00:00:00/00:00:00:00:00/a0 tag 22 ncq dma 512 out
Jul 4 05:31:35 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:31:35 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED
Jul 4 05:31:35 MediaServer kernel: ata10.00: cmd 61/08:b8:20:8b:6a/00:00:00:00:00/40 tag 23 ncq dma 4096 out
Jul 4 05:31:35 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:31:35 MediaServer kernel: ata10: hard resetting link
Jul 4 05:31:36 MediaServer kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jul 4 05:31:36 MediaServer kernel: ata10.00: supports DRM functions and may not be fully accessible
Jul 4 05:31:36 MediaServer kernel: ata10.00: supports DRM functions and may not be fully accessible
Jul 4 05:31:36 MediaServer kernel: ata10.00: configured for UDMA/133
Jul 4 05:31:36 MediaServer kernel: ata10: EH complete
Jul 4 05:32:06 MediaServer kernel: ata10.00: NCQ disabled due to excessive errors
Jul 4 05:32:06 MediaServer kernel: ata10.00: exception Emask 0x0 SAct 0xff800 SErr 0x0 action 0x6 frozen
Jul 4 05:32:06 MediaServer kernel: ata10.00: failed command: READ FPDMA QUEUED
Jul 4 05:32:06 MediaServer kernel: ata10.00: cmd 60/40:58:78:78:78/00:00:5f:00:00/40 tag 11 ncq dma 32768 in
Jul 4 05:32:06 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:32:06 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED
Jul 4 05:32:06 MediaServer kernel: ata10.00: cmd 61/08:60:20:8b:6a/00:00:00:00:00/40 tag 12 ncq dma 4096 out
Jul 4 05:32:06 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:32:06 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED
Jul 4 05:32:06 MediaServer kernel: ata10.00: cmd 64/01:68:00:00:00/00:00:00:00:00/a0 tag 13 ncq dma 512 out
Jul 4 05:32:06 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:32:06 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED
Jul 4 05:32:06 MediaServer kernel: ata10.00: cmd 64/01:70:00:00:00/00:00:00:00:00/a0 tag 14 ncq dma 512 out
Jul 4 05:32:06 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:32:06 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED
Jul 4 05:32:06 MediaServer kernel: ata10.00: cmd 64/01:78:00:00:00/00:00:00:00:00/a0 tag 15 ncq dma 512 out
Jul 4 05:32:06 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:32:06 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED
Jul 4 05:32:06 MediaServer kernel: ata10.00: cmd 64/01:80:00:00:00/00:00:00:00:00/a0 tag 16 ncq dma 512 out
Jul 4 05:32:06 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:32:06 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED
Jul 4 05:32:06 MediaServer kernel: ata10.00: cmd 64/01:88:00:00:00/00:00:00:00:00/a0 tag 17 ncq dma 512 out
Jul 4 05:32:06 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:32:06 MediaServer kernel: ata10.00: failed command: SEND FPDMA QUEUED
Jul 4 05:32:06 MediaServer kernel: ata10.00: cmd 64/01:90:00:00:00/00:00:00:00:00/a0 tag 18 ncq dma 512 out
Jul 4 05:32:06 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:32:06 MediaServer kernel: ata10.00: failed command: WRITE FPDMA QUEUED
Jul 4 05:32:06 MediaServer kernel: ata10.00: cmd 61/08:98:80:41:d9/00:00:59:00:00/40 tag 19 ncq dma 4096 out
Jul 4 05:32:06 MediaServer kernel: ata10.00: status: { DRDY }
Jul 4 05:32:06 MediaServer kernel: ata10: hard resetting link
Jul 4 05:32:06 MediaServer kernel: ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jul 4 05:32:06 MediaServer kernel: ata10.00: supports DRM functions and may not be fully accessible
Jul 4 05:32:06 MediaServer kernel: ata10.00: supports DRM functions and may not be fully accessible
Jul 4 05:32:06 MediaServer kernel: ata10.00: configured for UDMA/133
Jul 4 05:32:06 MediaServer kernel: sd 11:0:0:0: [sdk] tag#11 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=30s
Jul 4 05:32:06 MediaServer kernel: sd 11:0:0:0: [sdk] tag#11 Sense Key : 0x5 [current]
Jul 4 05:32:06 MediaServer kernel: sd 11:0:0:0: [sdk] tag#11 ASC=0x21 ASCQ=0x4
Jul 4 05:32:06 MediaServer kernel: sd 11:0:0:0: [sdk] tag#11 CDB: opcode=0x28 28 00 5f 78 78 78 00 00 40 00
Jul 4 05:32:06 MediaServer kernel: blk_update_request: I/O error, dev sdk, sector 1601730680 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0
Jul 4 05:32:06 MediaServer kernel: ata10: EH complete
Jul 4 05:32:06 MediaServer kernel: ata10.00: Enabling discard_zeroes_data
Jul 4 05:33:08 MediaServer root: /mnt/sysdata: 752.7 GiB (808155463680 bytes) trimmed on /dev/sdk1

I have the trim operation set for 5:30 AM which is about the time of these errors.  Any disk expert out there have any ideas on this?

dlandon Veteran

dlandon

Posted
  • Author
Posted
2 minutes ago, johnnie.black said:

What controller is it connected to? If possible use an Intel AHCI SATA port.

Looks like ASMedia controller same as my cache SSD: 

1b21:0612] 04:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)
[10:0:0:0]   disk    ATA      Samsung SSD 850  4B6Q  /dev/sdj   1.02TB
[11:0:0:0]   disk    ATA      Samsung SSD 860  2B6Q  /dev/sdk   1.02TB

 

dlandon Veteran

dlandon

Posted
  • Author
Posted
4 minutes ago, johnnie.black said:

I would try the Intel controller, some Samsung SSDs can be weird with some controllers, mostly from AMD, but also Asmedia.

I'll try that if it happens again.  Just a matter of moving a few cables.

dlandon Veteran

dlandon

Posted
  • Author
Posted

It seems like it happened again this morning when the trim was scheduled.  I've moved cables so the SSD is on the Intel controller.

 

@johnnie.black So it seems this new Samsung 960 SSD has problems with trim on the ASMedia controller?  Is this a common thing?

CS01-HS Enthusiast

CS01-HS

Posted
Posted

I saw sporadic CRC errors on my parity drive connected to the same ASM1062 (rev 2) controller, which forced multiple rebuilds.

 

I'm pretty sure it wasn't a poorly-seated cable because I got the error again after swapping the drive to the other ASM1062 port. Right now I'm running parity off my HBA card to rule out a defective drive. Another possibility in my setup is defective cables (I used the same model cable for both ASM ports and only those ports.) I've changed out the cables for a known good model and if I don't see another CRC error in the next few weeks I'll swap parity back to the ASM and wait and see.

 

I haven't ever had an error with the cache drives which are running off the integrated Intel controller.

I really hope the problem isn't ASM/unRAID compatibility because correcting that will require a new MB.

JorgeB Grand Master

JorgeB

Posted
Posted
1 hour ago, dlandon said:

So it seems this new Samsung 960 SSD has problems with trim on the ASMedia controller? 

I remember seeing trim issues (and other connections issues) with some Samsung SSDs on some controllers, IIRC it's a general Linux issue, and if it's that it should be solved by using an Intel controller, they are also very picky with cable quality, but that doesn't appear to be the problem here.

Zonediver Community Regular

Zonediver

Posted
Posted (edited)

I am using a 860 PRO as Cache-SSD on an internal Intel-SATA Port since 06.2018 - no issues with the SSD.

Avoid SATA-Ports other then Intel for this SSD.

Edited by Zonediver
dlandon Veteran

dlandon

Posted
  • Author
Posted

I opted to go with a nvme device instead.  I prefer to stay away from these kinds of issues since this SSD holds my VMs and Docker image.  It's also a lot faster than a sata SSD.

dlandon Veteran

dlandon

Posted
  • Author
Posted
10 hours ago, johnnie.black said:

Just out of curiosity were the errors still happening on the Intel controller or you didn't test?

I put it on the Intel controller, ran the fstrim command and didn't have any issues.

  • Thanks 2
dlandon Veteran

dlandon

Posted
  • Author
Posted

The nvme that I installed is tucked against the motherboard and is overheating at times.  What is the recommended temperature settings for the nvme?  And should I provide additional cooling for the nvme?  My disks (average around 25 C), and motherboard (around 27 C) are all pretty cool.  My Samsung 950 sata cache runs about 25 C.

JorgeB Grand Master

JorgeB

Posted
Posted

NVMe devices usually run hotter than 2.5 SATA devices, even when idle, after some writes they can easily go to 70C or more, some boards include a cooler on one or more m.2 slots, mine usually idle at about 40/45C and go to 65C+ during sustained writes, I have the warning set at 70C.

 

imagem.thumb.png.7991b4564eaacbfe58851b7a868d4502.png

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
Go to topic listing
×
×
  • Create New...