After reboot, 1 parity disk disabled, 1 data disk disabled/emulated.

[artgineer]

Hello,

 

My unraid server was mostly unresponsive so I rebooted it.

After the first reboot all disks went offline. I reseated the HBA and unplugged/plugged all SATA cables and power cables.

Now my first parity drive is disabled, and my data disk #3 is also disabled/emulated.

 

I tried using onboard sata ports and different cables, no differences.

 

My second parity drive is online but it has SMART issues and was scheduled to be replaced very soon, I'd rather fix this before it fails.

 

Before I break something I'd like this community's advice.

 

Thanks,

 

 

tower-diagnostics-20240612-1728.zip

Edited June 12 by artgineer

[JorgeB]

Once a disk gest disabled it must be rebuilt, post new diags after array start, to see if the emulated disk is mounting.

[artgineer]

Sadly the array does not start, I only get this in a loop:

 

Jun 14 07:15:35 Tower kernel: ata8.00: error: { UNC }
Jun 14 07:15:35 Tower kernel: ata8.00: configured for UDMA/133
Jun 14 07:15:35 Tower kernel: sd 8:0:0:0: [sde] tag#15 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Jun 14 07:15:35 Tower kernel: sd 8:0:0:0: [sde] tag#15 Sense Key : 0x3 [current]
Jun 14 07:15:35 Tower kernel: sd 8:0:0:0: [sde] tag#15 ASC=0x11 ASCQ=0x4
Jun 14 07:15:35 Tower kernel: sd 8:0:0:0: [sde] tag#15 CDB: opcode=0x88 88 00 00 00 00 01 97 8e 9b 00 00 00 00 20 00 00
Jun 14 07:15:35 Tower kernel: I/O error, dev sde, sector 6837672704 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 2
Jun 14 07:15:35 Tower kernel: md: disk29 read error, sector=6837672640
Jun 14 07:15:35 Tower kernel: md: disk29 read error, sector=6837672648
Jun 14 07:15:35 Tower kernel: md: disk29 read error, sector=6837672656
Jun 14 07:15:35 Tower kernel: md: disk29 read error, sector=6837672664
Jun 14 07:15:35 Tower kernel: ata8: EH complete
Jun 14 07:15:39 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x10000 SErr 0x0 action 0x0
Jun 14 07:15:39 Tower kernel: ata8.00: irq_stat 0x40000000
Jun 14 07:15:39 Tower kernel: ata8.00: failed command: READ FPDMA QUEUED
Jun 14 07:15:39 Tower kernel: ata8.00: cmd 60/20:80:00:9b:8e/00:00:97:01:00/40 tag 16 ncq dma 16384 in
Jun 14 07:15:39 Tower kernel:         res 41/40:20:00:9b:8e/00:00:97:01:00/00 Emask 0x409 (media error) <F>
Jun 14 07:15:39 Tower kernel: ata8.00: status: { DRDY ERR }
Jun 14 07:15:39 Tower kernel: ata8.00: error: { UNC }
Jun 14 07:15:39 Tower kernel: ata8.00: configured for UDMA/133
Jun 14 07:15:39 Tower kernel: sd 8:0:0:0: [sde] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s
Jun 14 07:15:39 Tower kernel: sd 8:0:0:0: [sde] tag#16 Sense Key : 0x3 [current]
Jun 14 07:15:39 Tower kernel: sd 8:0:0:0: [sde] tag#16 ASC=0x11 ASCQ=0x4
Jun 14 07:15:39 Tower kernel: sd 8:0:0:0: [sde] tag#16 CDB: opcode=0x88 88 00 00 00 00 01 97 8e 9b 00 00 00 00 20 00 00
Jun 14 07:15:39 Tower kernel: I/O error, dev sde, sector 6837672704 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 2
Jun 14 07:15:39 Tower kernel: md: disk29 read error, sector=6837672640
Jun 14 07:15:39 Tower kernel: md: disk29 read error, sector=6837672648
Jun 14 07:15:39 Tower kernel: md: disk29 read error, sector=6837672656
Jun 14 07:15:39 Tower kernel: md: disk29 read error, sector=6837672664
Jun 14 07:15:39 Tower kernel: ata8: EH complete

[JorgeB]

Looks like parity2 is failing, post new diags.

[artgineer]

Here's the latest diag.

 

Thank you for your help btw.

tower-diagnostics-20240614-1114.zip

[JorgeB]

SMART doesn't look good, run an extended SMART test to confirm.

 

 

[artgineer]

Does not look good.

tower-smart-20240614-1313.zip

[JorgeB]

Yeah, that disk needs to be replaced, so you cannot rebuild disk3, but disk3 and parity look, so most likely they got disabled due to a power/connection error, I would try the following:

 

-Tools -> New Config -> Retain current configuration: All -> Apply
-Check all assignments are correct, unassign parity2 since that one is bad

-Check "parity is already valid" next to array start button and start the array

 

Disk3 should hopefully mount, if it does run a correcting parity check, if it doesn't, post new diags.

[artgineer]

I did like you said and the array is started, Disk3 mounted correctly.

 

Parity check has been started and it will probably take about a day, will update after.

 

Once again thank you so much for your help!

[artgineer]

Weirdly enough, both my parity drives were toast.

 

The WD one disappears every time I stop the array, it passes extended smart in Unraid but not on a computer. It's still under warranty so I'm not gonna spend much more time on it.

I just put two brand new disks in there.

 

Thank you for your help!