My son accidentally hit the power bar and shutdown my UNRAID server. When I started it up again, my Disk 5 was showing as unassigned. I tried to add it, but the status stayed at "unassigned"... and a red x showed next to Disk 5 with the message device is missing (disabled).

 

I spent a couple hours trying to troubleshoot... but haven't had any luck.

 

I believe it's related to these error messages from the log files:

Jan 11 08:48:03 Tower kernel: ata2.00: failed to enable Sense Data Reporting, Emask 0x1
Jan 11 08:48:03 Tower kernel: ata2.00: configured for UDMA/133 (device error ignored)
Jan 11 08:48:03 Tower kernel: sd 3:0:0:0: [sdd] tag#8 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Jan 11 08:48:03 Tower kernel: sd 3:0:0:0: [sdd] tag#8 Sense Key : 0x5 [current]
Jan 11 08:48:03 Tower kernel: sd 3:0:0:0: [sdd] tag#8 ASC=0x21 ASCQ=0x4
Jan 11 08:48:03 Tower kernel: sd 3:0:0:0: [sdd] tag#8 CDB: opcode=0x88 88 00 00 00 00 06 5d df ff 80 00 00 00 08 00 00
Jan 11 08:48:03 Tower kernel: blk_update_request: I/O error, dev sdd, sector 27344764800 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 11 08:48:03 Tower kernel: Buffer I/O error on dev sdd, logical block 3418095600, async page read
Jan 11 08:48:03 Tower kernel: ata2: EH complete
Jan 11 08:48:03 Tower kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 11 08:48:03 Tower kernel: ata2.00: irq_stat 0x40000001
Jan 11 08:48:03 Tower kernel: ata2.00: failed command: READ DMA EXT
Jan 11 08:48:03 Tower kernel: ata2.00: cmd 25/00:08:80:ff:df/00:00:5d:06:00/e0 tag 2 dma 4096 in
Jan 11 08:48:03 Tower kernel:         res 51/04:08:80:ff:df/00:00:5d:06:00/40 Emask 0x1 (device error)
Jan 11 08:48:03 Tower kernel: ata2.00: status: { DRDY ERR }
Jan 11 08:48:03 Tower kernel: ata2.00: error: { ABRT }

 

If anyone has any suggestions, I'd greatly appreciate it. Only 1 month into the UNRAID world, so I'm pretty green. Diagnostics are attached.

 

Thanks in advance!

tower-diagnostics-20220111-0941.zip

There is an Unassigned disk in those diagnostics, 9MHKJYLK. SMART report not working for it though. Is that supposed to be disk5?

 

In any case, check connections, both ends, SATA and power, including splitters.

1 minute ago, trurl said:

There is an Unassigned disk in those diagnostics, 9MHKJYLK. SMART report not working for it though. Is that supposed to be disk5?

 

In any case, check connections, both ends, SATA and power, including splitters.

That's right... that unassigned disk is supposed to be disk5.

 

Thanks, I'll check the connections later this morning.

It looks like you have been getting messages about drives resetting ever since the system was booted on 7th Jan.   I did not spot anything obviously wrong in the SMART reports for the drives, so these issues may well be related to the power/SATA connections to the drives.

 

I would suggest that you shutdown the server, carefully check all the power and SATA cabling is well seated, and then power up the server to and get new diagnostics.

 

 

3 hours ago, itimpi said:

It looks like you have been getting messages about drives resetting ever since the system was booted on 7th Jan.   I did not spot anything obviously wrong in the SMART reports for the drives, so these issues may well be related to the power/SATA connections to the drives.

 

I would suggest that you shutdown the server, carefully check all the power and SATA cabling is well seated, and then power up the server to and get new diagnostics.

 

 

Appreciate the help. I checked all power/SATA connections and I'm now able to select Disk 5 as part of the array devices.

 

I booted up the array and now it's doing a parity sync / Data-Rebuild. Is that normal? New diagnostics just exported are attached too.

 

Appreciate all the help. I'm really digging UNRAID.

 

tower-diagnostics-20220111-1326.zip

Edited January 11, 20224 yr by surfNL
Fixing uploaded zip file. Fixing typo "not" --> "now"

Diagnostics are no longer showing the continual resets which is a good sign  

2 hours ago, surfNL said:

I booted up the array and now it's doing a parity sync / Data-Rebuild. Is that normal?

Yes

46 minutes ago, Frank1940 said:

Yes

Thanks, Frank. (And everyone else too)