Hello, today my server emailed me to say that one of my drives was disabled. I have had drives fail in the past and so am not too unfamiliar with the process but just wanting to make sure I am following the proper protocols to do things right. From what I can tell the drive has lost communication entirely, so it could be simply a cable issue etc although the drive has been running for almost 5 years now so I'm more leaning towards just a straight up failure.

I'm attaching the server diagnostic file, but here is the part which I guess is most important in regards to what happened.

Sep 18 00:33:23 Tower kernel: sd 7:0:2:0: attempting task abort!scmd(0x00000000f8267ac8), outstanding for 15363 ms & timeout 15000 ms

Sep 18 00:33:23 Tower kernel: sd 7:0:2:0: [sdf] tag#3176 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00

Sep 18 00:33:23 Tower kernel: scsi target7:0:2: handle(0x000b), sas_address(0x4433221101000000), phy(1)

Sep 18 00:33:23 Tower kernel: scsi target7:0:2: enclosure logical id(0x500605b009db1330), slot(2)

Sep 18 00:33:27 Tower kernel: sd 7:0:2:0: task abort: SUCCESS scmd(0x00000000f8267ac8)

Sep 18 00:33:27 Tower kernel: sd 7:0:2:0: [sdf] tag#3178 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s

Sep 18 00:33:27 Tower kernel: sd 7:0:2:0: [sdf] tag#3178 Sense Key : 0x2 [current]

Sep 18 00:33:27 Tower kernel: sd 7:0:2:0: [sdf] tag#3178 ASC=0x4 ASCQ=0x0

Sep 18 00:33:27 Tower kernel: sd 7:0:2:0: [sdf] tag#3178 CDB: opcode=0x8a 8a 08 00 00 00 02 00 0a 50 38 00 00 00 08 00 00

Sep 18 00:33:27 Tower kernel: I/O error, dev sdf, sector 8590610488 op 0x1:(WRITE) flags 0x20800 phys_seg 1 prio class 0

Sep 18 00:33:27 Tower kernel: md: disk6 write error, sector=8590610424
Sep 18 00:33:27 Tower emhttpd: read SMART /dev/sdf

Sep 18 00:33:27 Tower emhttpd: read SMART /dev/sdc

Sep 18 00:33:39 Tower emhttpd: read SMART /dev/sdj

Sep 18 00:33:39 Tower emhttpd: read SMART /dev/sdh

Sep 18 00:33:39 Tower emhttpd: read SMART /dev/sdg

Sep 18 00:33:39 Tower emhttpd: read SMART /dev/sdd

Sep 18 00:33:39 Tower emhttpd: read SMART /dev/sdb

Sep 18 00:33:39 Tower emhttpd: read SMART /dev/sdi

Sep 18 01:33:31 Tower emhttpd: spinning down /dev/sdf

Sep 18 01:34:10 Tower emhttpd: spinning down /dev/sdj

Sep 18 01:34:10 Tower emhttpd: spinning down /dev/sdh

Sep 18 01:34:10 Tower emhttpd: spinning down /dev/sdg

Sep 18 01:34:10 Tower emhttpd: spinning down /dev/sdd

Sep 18 01:34:10 Tower emhttpd: spinning down /dev/sdb

Sep 18 01:34:10 Tower emhttpd: spinning down /dev/sdi

Sep 18 02:19:19 Tower emhttpd: read SMART /dev/sdd

Sep 18 02:19:33 Tower emhttpd: read SMART /dev/sdj

Sep 18 02:19:52 Tower emhttpd: read SMART /dev/sdh

Sep 18 02:19:52 Tower emhttpd: read SMART /dev/sdg

Sep 18 02:19:52 Tower emhttpd: read SMART /dev/sdb

Sep 18 02:19:52 Tower emhttpd: read SMART /dev/sdi

Sep 18 03:19:53 Tower emhttpd: spinning down /dev/sdh

Sep 18 03:19:53 Tower emhttpd: spinning down /dev/sdd

Sep 18 03:20:20 Tower emhttpd: spinning down /dev/sdj

Sep 18 03:21:02 Tower emhttpd: spinning down /dev/sdi

Sep 18 03:34:57 Tower emhttpd: spinning down /dev/sdg

Sep 18 04:08:53 Tower emhttpd: spinning down /dev/sdb

Sep 18 04:57:14 Tower emhttpd: read SMART /dev/sdj

Sep 18 04:57:14 Tower emhttpd: read SMART /dev/sdh

Sep 18 04:57:14 Tower emhttpd: read SMART /dev/sdg

Sep 18 04:57:14 Tower emhttpd: read SMART /dev/sdd

Sep 18 04:57:14 Tower emhttpd: read SMART /dev/sdb

Sep 18 04:57:14 Tower emhttpd: read SMART /dev/sdi

Sep 18 06:22:39 Tower emhttpd: spinning down /dev/sdj

Sep 18 06:22:39 Tower emhttpd: spinning down /dev/sdg

Sep 18 06:22:39 Tower emhttpd: spinning down /dev/sdd

Sep 18 06:23:05 Tower emhttpd: spinning down /dev/sdh

Sep 18 06:37:40 Tower emhttpd: spinning down /dev/sdi

Sep 18 06:38:45 Tower emhttpd: spinning down /dev/sdb

Sep 18 09:38:45 Tower emhttpd: spinning down /dev/sdc

Sep 18 11:12:05 Tower emhttpd: read SMART /dev/sdi

Sep 18 11:12:26 Tower emhttpd: read SMART /dev/sdc

Sep 18 12:13:57 Tower emhttpd: spinning down /dev/sdi

Sep 18 12:42:30 Tower root: Fix Common Problems Version 2025.08.07

Sep 18 12:42:31 Tower root: Fix Common Problems: Error: disk6 (ST8000VN004-2M2101_WKD3BKZK) is disabled

Sep 18 12:42:31 Tower root: Fix Common Problems: Error: disk3 (ST8000VN004-2M2101_WKD0NSWM) has read errors

Sep 18 12:42:31 Tower root: Fix Common Problems: Error: disk6 (ST8000VN004-2M2101_WKD3BKZK) has read errors

So my question is, what should be my next steps? Am I safe to turn off the server now that I have provided the server diagnostic file? Ideally I want to power it down so I can check the cable is seated, or try a different cable.

Likely this one is connected to my SAS card but I can try a regular SATA port if not and power back on and see if it will detect. I also do have a spare 8TB replacement drive for just this exact scenario in case a drive fails.

Thanks in advance!

tower-diagnostics-20250918-1242.zip

Looks like I jumped the gun a little on thinking the drive was not detecting at all, as I could clearly still monitor temps and do self-SMART tests.

Steps taken so far.

• STOP array, Power down system. Check cable connection to disabled drive. Power on system.

• Remove disk from array and START array in maintenance mode to "purge" the disabled disk.

• STOP array, add removed disk back into the array again. START array in normal mode to rebuild disk.

Assuming the drive doesn't fail/disable during the rebuild, then I will not need to post again. If the drive does fail the rebuild then I will be putting in my spare 8TB drive and rebuild again on that.