So I was playing with some power management wires (which I should not have been doing while the array was on). Nothing was being written, and drives were spun down, but I heard one spin up as unpledged power.

 

I'm sure I've messed things up by trying to read the forms and not know exactly what I was doing using New Config and started the array which started to rebuild the parity drive with the drive not in place.

 

It won't let me assign the drive back to its original assignment (not in drop down)

 

it listed in unassigned

 

 

I guess in short how can I bring the drive back on and rebuild the parity?

 

 

here some of the drive log:
Jul 21 14:08:01 NAS kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jul 21 14:08:01 NAS kernel: ata5.00: irq_stat 0x40000001
Jul 21 14:08:01 NAS kernel: ata5.00: failed command: READ DMA EXT
Jul 21 14:08:01 NAS kernel: ata5.00: cmd 25/00:08:80:ff:df/00:00:5d:06:00/e0 tag 24 dma 4096 in
Jul 21 14:08:01 NAS kernel: ata5.00: status: { DRDY SENSE ERR }
Jul 21 14:08:01 NAS kernel: ata5.00: error: { UNC }
Jul 21 14:08:01 NAS kernel: ata5.00: supports DRM functions and may not be fully accessible
Jul 21 14:08:01 NAS kernel: ata5.00: Read log 0x13 page 0x00 failed, Emask 0x1
Jul 21 14:08:01 NAS kernel: ata5.00: Read log 0x12 page 0x00 failed, Emask 0x1
Jul 21 14:08:01 NAS kernel: ata5.00: supports DRM functions and may not be fully accessible
Jul 21 14:08:01 NAS kernel: ata5.00: Read log 0x13 page 0x00 failed, Emask 0x1
Jul 21 14:08:01 NAS kernel: ata5.00: Read log 0x12 page 0x00 failed, Emask 0x1
Jul 21 14:08:01 NAS kernel: ata5.00: configured for UDMA/133
Jul 21 14:08:01 NAS kernel: sd 5:0:0:0: [sdf] tag#24 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Jul 21 14:08:01 NAS kernel: sd 5:0:0:0: [sdf] tag#24 Sense Key : 0x3 [current] 
Jul 21 14:08:01 NAS kernel: sd 5:0:0:0: [sdf] tag#24 ASC=0x11 ASCQ=0x4 
Jul 21 14:08:01 NAS kernel: sd 5:0:0:0: [sdf] tag#24 CDB: opcode=0x88 88 00 00 00 00 06 5d df ff 80 00 00 00 08 00 00
Jul 21 14:08:01 NAS kernel: I/O error, dev sdf, sector 27344764800 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
Jul 21 14:08:01 NAS kernel: Buffer I/O error on dev sdf, logical block 3418095600, async page read
Jul 21 14:08:01 NAS kernel: ata5: EH complete

 

Edited July 22, 20241 yr by nathan909

Please post the diagnostics.

Hope this helps?!

nas-diagnostics-20240721-1729.zip

5 hours ago, JorgeB said:

Please post the diagnostics.

FYI, this drive was spun down, so I'm confident nothing was being written to it. It was FULL, with about 14tb of only media movies & tv shows.

I would like to put it back online and rebuild the parity.

 

Thanks again

Nathan

SMART for disk2 doesn't look, swap cables with a different disk and post new diags.

Here ya go

 

nas-diagnostics-20240722-0849.zip

That disk is no good, unfortunately, and since parity is not valid, that means there will probably be some data loss.

On 7/22/2024 at 9:33 AM, JorgeB said:

That disk is no good, unfortunately, and since parity is not valid, that means there will probably be some data loss.

 

OK, if that's the case. Unfortunately, I have no one to blame but myself.

 

I also sent you a cup of coffee, I appreciate you helping out

Edited July 24, 20241 yr by nathan909

On 7/22/2024 at 9:33 AM, JorgeB said:

That disk is no good, unfortunately, and since parity is not valid, that means there will probably be some data loss.

How do I remove this disk so it doesn't show that it's part of an array? 

On 7/22/2024 at 9:33 AM, JorgeB said:

That disk is no good, unfortunately, and since parity is not valid, that means there will probably be some data loss.

 

As soon as I put a new drive in place of it on the array, the old (sdf) drive became accessible:

 

is they anything i can do to add it back or copy the files off it?

You can try to clone it with ddrescue

18 minutes ago, JorgeB said:

You can try to clone it with ddrescue

Sorry for my ignorance Jorge, but is the drive bad or is there something preventing it from being attached to the array or readable from unassigned devices?

 

I couldn't get drive attributes until a replace drive on array, and when I stop the array, it shows "array" likes it wants to be attached to an array

It look like it's bad to me, it's back now but there's not even a mount option with UD.

I have definitely had drives in the past that stopped being recognised under Unraid, but then running ddresue (under Windows) was able to clone a drive despite not being able to not even get a SMART report from it so this is definitely something to consider trying.