Parity Disk Error - Dead Drive?

[Chris20xX]

Hi, 

 

Hoping someone might be able to help me figure out what's going on/what happened. I got a notification that one of my parity disks had an error and then disabled in the array. I'm guessing it's dead? The error count in the main tab says 2038. Logs below

 

 

Thanks,

 

May 17 20:23:19 Neatflicks kernel: sd 3:0:0:0: [sdk] 35156656128 512-byte logical blocks: (18.0 TB/16.4 TiB)
May 17 20:23:19 Neatflicks kernel: sd 3:0:0:0: [sdk] 4096-byte physical blocks
May 17 20:23:19 Neatflicks kernel: sd 3:0:0:0: [sdk] Write Protect is off
May 17 20:23:19 Neatflicks kernel: sd 3:0:0:0: [sdk] Mode Sense: 00 3a 00 00
May 17 20:23:19 Neatflicks kernel: sd 3:0:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 17 20:23:19 Neatflicks kernel: sd 3:0:0:0: [sdk] Preferred minimum I/O size 4096 bytes
May 17 20:23:19 Neatflicks kernel: sdk: sdk1
May 17 20:23:19 Neatflicks kernel: sd 3:0:0:0: [sdk] Attached SCSI disk
May 17 20:23:43 Neatflicks  emhttpd: ST18000NM000J-2TV103_ZR52MTYG (sdk) 512 35156656128
May 17 20:23:43 Neatflicks kernel: mdcmd (1): import 0 sdk 64 17578328012 0 ST18000NM000J-2TV103_ZR52MTYG
May 17 20:23:43 Neatflicks kernel: md: import disk0: (sdk) ST18000NM000J-2TV103_ZR52MTYG size: 17578328012 
May 17 20:23:43 Neatflicks  emhttpd: read SMART /dev/sdk
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=55s
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#0 Sense Key : 0x2 [current] 
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#0 ASC=0x4 ASCQ=0x21 
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 4b 70 c5 00 00 00 03 f8 00 00
May 17 20:35:07 Neatflicks kernel: I/O error, dev sdk, sector 1265681664 op 0x0:(READ) flags 0x0 phys_seg 127 prio class 0
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=55s
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#2 Sense Key : 0x2 [current] 
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#2 ASC=0x4 ASCQ=0x21 
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#2 CDB: opcode=0x88 88 00 00 00 00 00 4b 70 c1 08 00 00 03 f8 00 00
May 17 20:35:07 Neatflicks kernel: I/O error, dev sdk, sector 1265680648 op 0x0:(READ) flags 0x0 phys_seg 127 prio class 0
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=55s
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#3 Sense Key : 0x2 [current] 
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#3 ASC=0x4 ASCQ=0x21 
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#3 CDB: opcode=0x88 88 00 00 00 00 00 4b 70 bd 10 00 00 03 f8 00 00
May 17 20:35:07 Neatflicks kernel: I/O error, dev sdk, sector 1265679632 op 0x0:(READ) flags 0x0 phys_seg 127 prio class 0
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=23s
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#4 Sense Key : 0x2 [current] 
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#4 ASC=0x4 ASCQ=0x21 
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#4 CDB: opcode=0x88 88 00 00 00 00 00 3a 3a 95 d8 00 00 00 08 00 00
May 17 20:35:07 Neatflicks kernel: I/O error, dev sdk, sector 976917976 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=55s
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#5 Sense Key : 0x2 [current] 
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#5 ASC=0x4 ASCQ=0x21 
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#5 CDB: opcode=0x88 88 00 00 00 00 00 4b 70 b9 18 00 00 03 f8 00 00
May 17 20:35:07 Neatflicks kernel: I/O error, dev sdk, sector 1265678616 op 0x0:(READ) flags 0x0 phys_seg 127 prio class 0
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=55s
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#6 Sense Key : 0x2 [current] 
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#6 ASC=0x4 ASCQ=0x21 
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#6 CDB: opcode=0x88 88 00 00 00 00 00 4b 70 b5 20 00 00 03 f8 00 00
May 17 20:35:07 Neatflicks kernel: I/O error, dev sdk, sector 1265677600 op 0x0:(READ) flags 0x0 phys_seg 127 prio class 0
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=55s
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#7 Sense Key : 0x2 [current] 
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#7 ASC=0x4 ASCQ=0x21 
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#7 CDB: opcode=0x88 88 00 00 00 00 00 4b 70 b1 28 00 00 03 f8 00 00
May 17 20:35:07 Neatflicks kernel: I/O error, dev sdk, sector 1265676584 op 0x0:(READ) flags 0x0 phys_seg 127 prio class 0
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#25 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=24s
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#25 Sense Key : 0x2 [current] 
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#25 ASC=0x4 ASCQ=0x21 
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#25 CDB: opcode=0x88 88 00 00 00 00 02 80 03 b7 08 00 00 00 10 00 00
May 17 20:35:07 Neatflicks kernel: I/O error, dev sdk, sector 10737661704 op 0x0:(READ) flags 0x0 phys_seg 2 prio class 0
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#26 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=24s
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#26 Sense Key : 0x2 [current] 
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#26 ASC=0x4 ASCQ=0x21 
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#26 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 c0 00 00 00 20 00 00
May 17 20:35:07 Neatflicks kernel: I/O error, dev sdk, sector 192 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 0
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#27 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=24s
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#27 Sense Key : 0x2 [current] 
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#27 ASC=0x4 ASCQ=0x21 
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] tag#27 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 58 00 00 00 10 00 00
May 17 20:35:07 Neatflicks kernel: I/O error, dev sdk, sector 88 op 0x0:(READ) flags 0x0 phys_seg 2 prio class 0
May 17 20:35:07 Neatflicks kernel: sd 3:0:0:0: [sdk] Synchronizing SCSI cache
May 17 20:35:08 Neatflicks kernel: sd 3:0:0:0: [sdk] Stopping disk
May 17 20:37:00 Neatflicks  emhttpd: error: hotplug_devices, 1730: No such file or directory (2): Error: tagged device ST18000NM000J-2TV103_ZR52MTYG was (sdk) is now (sdm)

** Press ANY KEY to close this window ** 

 

[itimpi]

The log snippet you posted does not look ideal    However it is still possible it is something other than the drive itself

 

I would suggest that you:

• Take current diagnostics so we can see what lead up to that snippet.
• Power cycle the server to reset all the hardware
• Wen the server comes back take new diagnostics
• Post both sets of diagnostics so we can get a more complete view of what is happening

You might want to also consider clicking on the drive on the Main tab to run an extended SMART test.   That can take some time so from there disable spindown while the test is running.   If the drive fails the SMART test then it definitely has a problem.  Passing it is less prescriptive but indicative of a factor external to the drive itself.

[Chris20xX]

Thanks for the reply. I noticed after restarting that the disk wasn't appearing so I looked inside the server and noticed that the nvme/sata extension card wasn't lighting up on that port. I kinda jiggled it and it turned on so it looks like either a bad adapter or bad cable. 

[itimpi]

5 hours ago, Chris20xX said:

Thanks for the reply. I noticed after restarting that the disk wasn't appearing so I looked inside the server and noticed that the nvme/sata extension card wasn't lighting up on that port. I kinda jiggled it and it turned on so it looks like either a bad adapter or bad cable. 

This could simply mean that the card was nor properly seated in the expansion slot rather than the card being faulty.