New HDD Failed already?

[PsyCl0ne]

Hey everyone, just got 3 18TB HDDs, Completed preclear, without issue. While migrating from my smaller 4TB drives onto the new drives using unbalance one of the drives disabled itself. I have completed a long SMART test that came back clean so I am not sure what is going on. Attached are logs from the diagnostics page as well as the SMART log from the drive itself.

 

Second question to go along with this, if the drive has actually shit the bed, can I use unbalance again to move the data off the drive back onto the 4TB drives or what is the best way to go about this? I have a new 18TB drive on its way but it will be another ~4 days at least.

tower-smart-20231103-1459.zip tower-diagnostics-20231103-1456.zip

[JorgeB]

It's not logged as a disk problem and SMART looks fine, problem happened on spin up, and some Seagate drives have known issues with spin ups with LSI HBAs, so it could be that.

[PsyCl0ne]

15 hours ago, JorgeB said:

It's not logged as a disk problem and SMART looks fine, problem happened on spin up, and some Seagate drives have known issues with spin ups with LSI HBAs, so it could be that.

 

Hey thank you for looking into the logs. What is the next best step? Reboot the server? Still swap the drive out?

 

Am I able to still pull the data from this drive?

[JorgeB]

I would rebuild and disable spin down to see if that helps.

[PsyCl0ne]

9 hours ago, JorgeB said:

I would rebuild and disable spin down to see if that helps.

JorgeB, apologies your help has been appreciated but while I understand what you have advised I am not sure of the steps to take.

 

I know that normally with a failed drive if I take it out and then put in a new drive, I can rebuild the array. How would it work in this situation? Do I force the system to start a rebuild or do I take the drive out and start the rebuild? Would the array rebuild onto the 4 TB drives that are still in shape?

 

Attached are screenshots of how my "Main" tab is looking for the drives and array options.

 

A side note when I clicked on the little icon next to the drive it pulled up Logs? and I have the following showing in it for the drive that is disabled
 

Nov  1 05:30:04 Tower  emhttpd: spinning down /dev/sdo
Nov  1 06:00:01 Tower  emhttpd: read SMART /dev/sdo
Nov  1 07:30:04 Tower  emhttpd: spinning down /dev/sdo
Nov  1 08:00:01 Tower  emhttpd: read SMART /dev/sdo
Nov  1 08:30:23 Tower  emhttpd: spinning down /dev/sdo
Nov  1 09:00:01 Tower  emhttpd: read SMART /dev/sdo
Nov  1 10:30:03 Tower  emhttpd: spinning down /dev/sdo
Nov  1 11:00:16 Tower kernel: sd 8:0:1:0: [sdo] tag#2775 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2798 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=19s
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2798 Sense Key : 0x2 [current] 
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2798 ASC=0x4 ASCQ=0x0 
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2798 CDB: opcode=0x88 88 00 00 00 00 06 33 f5 63 d0 00 00 04 00 00 00
Nov  1 11:00:20 Tower kernel: I/O error, dev sdo, sector 26641523664 op 0x0:(READ) flags 0x0 phys_seg 128 prio class 0
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2799 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=19s
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2799 Sense Key : 0x2 [current] 
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2799 ASC=0x4 ASCQ=0x0 
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2799 CDB: opcode=0x88 88 00 00 00 00 06 33 f5 5b d0 00 00 04 00 00 00
Nov  1 11:00:20 Tower kernel: I/O error, dev sdo, sector 26641521616 op 0x0:(READ) flags 0x0 phys_seg 128 prio class 0
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2800 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=19s
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2800 Sense Key : 0x2 [current] 
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2800 ASC=0x4 ASCQ=0x0 
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2800 CDB: opcode=0x88 88 00 00 00 00 06 33 f5 5f d0 00 00 04 00 00 00
Nov  1 11:00:20 Tower kernel: I/O error, dev sdo, sector 26641522640 op 0x0:(READ) flags 0x0 phys_seg 128 prio class 0
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2801 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=19s
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2801 Sense Key : 0x2 [current] 
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2801 ASC=0x4 ASCQ=0x0 
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2801 CDB: opcode=0x88 88 00 00 00 00 06 33 f5 4f d0 00 00 04 00 00 00
Nov  1 11:00:20 Tower kernel: I/O error, dev sdo, sector 26641518544 op 0x0:(READ) flags 0x0 phys_seg 128 prio class 0
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2802 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=19s
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2802 Sense Key : 0x2 [current] 
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2802 ASC=0x4 ASCQ=0x0 
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2802 CDB: opcode=0x88 88 00 00 00 00 06 33 f5 53 d0 00 00 04 00 00 00
Nov  1 11:00:20 Tower kernel: I/O error, dev sdo, sector 26641519568 op 0x0:(READ) flags 0x0 phys_seg 128 prio class 0
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2803 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=19s
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2803 Sense Key : 0x2 [current] 
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2803 ASC=0x4 ASCQ=0x0 
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2803 CDB: opcode=0x88 88 00 00 00 00 06 33 f5 57 d0 00 00 04 00 00 00
Nov  1 11:00:20 Tower kernel: I/O error, dev sdo, sector 26641520592 op 0x0:(READ) flags 0x0 phys_seg 128 prio class 0
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2804 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2804 Sense Key : 0x2 [current] 
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2804 ASC=0x4 ASCQ=0x0 
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2804 CDB: opcode=0x88 88 00 00 00 00 06 33 f5 67 d0 00 00 04 00 00 00
Nov  1 11:00:20 Tower kernel: I/O error, dev sdo, sector 26641524688 op 0x0:(READ) flags 0x4000 phys_seg 128 prio class 0
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2815 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2815 Sense Key : 0x2 [current] 
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2815 ASC=0x4 ASCQ=0x0 
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2815 CDB: opcode=0x88 88 00 00 00 00 06 33 f5 6b d0 00 00 04 00 00 00
Nov  1 11:00:20 Tower kernel: I/O error, dev sdo, sector 26641525712 op 0x0:(READ) flags 0x0 phys_seg 128 prio class 0
Nov  1 11:00:20 Tower  emhttpd: read SMART /dev/sdo
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2761 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2761 Sense Key : 0x2 [current] 
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2761 ASC=0x4 ASCQ=0x0 
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2761 CDB: opcode=0x8a 8a 00 00 00 00 06 33 f5 63 d0 00 00 04 00 00 00
Nov  1 11:00:20 Tower kernel: I/O error, dev sdo, sector 26641523664 op 0x1:(WRITE) flags 0x4000 phys_seg 128 prio class 0
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2765 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2765 Sense Key : 0x2 [current] 
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2765 ASC=0x4 ASCQ=0x0 
Nov  1 11:00:20 Tower kernel: sd 8:0:1:0: [sdo] tag#2765 CDB: opcode=0x8a 8a 00 00 00 00 06 33 f5 67 d0 00 00 04 00 00 00
Nov  1 11:00:20 Tower kernel: I/O error, dev sdo, sector 26641524688 op 0x1:(WRITE) flags 0x4000 phys_seg 128 prio class 0
Nov  1 11:30:23 Tower  emhttpd: spinning down /dev/sdo
Nov  2 10:24:06 Tower  emhttpd: read SMART /dev/sdo
Nov  2 10:27:07 Tower  emhttpd: shcmd (6623718): echo 128 > /sys/block/sdo/queue/nr_requests

 

Edited November 5, 2023 by PsyCl0ne

[JorgeB]

13 hours ago, PsyCl0ne said:

How would it work in this situation?

Make sure the emulated disk is mounting and contents look correct then:

https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself

 

[PsyCl0ne]

On 11/6/2023 at 3:05 AM, JorgeB said:

Make sure the emulated disk is mounting and contents look correct then:

https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself

 

 

@JorgeB Thank you, honestly you're a godsend. Thank you for your help once again.