Parity Disk in Error State

[Uplinkpro]

So recently after cleaning out my server I booted it up and noticed one of my parity disks had a big red X,  I stopped the array tested the drive and it seems ok but any time I try to bring it back online I get this error that its been stopped. Is the drive bad? I checked the plugs into my drive cages all seem fine.

 

tower-diagnostics-20220424-1203.zip tower-smart-20220424-0956.zip

[Frank1940]

It looks like the PARITY disk is MIA in your second Diagnostics file.  (I did not check your first Diagnostic file.)    Open up the case and carefully make sure that all of the SATA connections (both power and data)  are secure seated.  Then double check again all of them again before buttoning things back up.  (It is not uncommon for a SATA connector to come loose or even totally unseated whenever they are disturbed in any fashion!)

Edited April 24, 2022 by Frank1940

[Uplinkpro]

51 minutes ago, Frank1940 said:

It looks like the PARITY disk is MIA in your second Diagnostics file.  (I did not check your first Diagnostic file.)    Open up the case and carefully make sure that all of the SATA connections (both power and data)  are secure seated.  Then double check again all of them again before buttoning things back up.  (It is not uncommon for a SATA connector to come loose or even totally unseated whenever they are disturbed in any fashion!)

Its in unassigned devices at the moment as i have tried to remove it and add it back with no luck.

[Frank1940]

2 hours ago, Uplinkpro said:

Its in unassigned devices at the moment as i have tried to remove it and add it back with no luck.

@dlandon, I would hope you might be able to help here...

[dlandon]

3 hours ago, Frank1940 said:

@dlandon, I would hope you might be able to help here...

Looks like a disk/controller/cable issue:

Apr 24 00:10:02 Tower kernel: blk_update_request: I/O error, dev sdg, sector 72 op 0x0:(READ) flags 0x80700 phys_seg 6 prio class 0
Apr 24 00:11:01 Tower kernel: sd 13:0:2:0: [sdg] tag#917 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Apr 24 00:11:01 Tower kernel: sd 13:0:2:0: [sdg] tag#917 Sense Key : 0xb [current] 
Apr 24 00:11:01 Tower kernel: sd 13:0:2:0: [sdg] tag#917 ASC=0x4b ASCQ=0x3 
Apr 24 00:11:01 Tower kernel: sd 13:0:2:0: [sdg] tag#917 CDB: opcode=0x28 28 00 91 87 ff 8f 00 00 15 00

 

[Uplinkpro]

14 hours ago, dlandon said:

Looks like a disk/controller/cable issue:

Apr 24 00:10:02 Tower kernel: blk_update_request: I/O error, dev sdg, sector 72 op 0x0:(READ) flags 0x80700 phys_seg 6 prio class 0
Apr 24 00:11:01 Tower kernel: sd 13:0:2:0: [sdg] tag#917 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s
Apr 24 00:11:01 Tower kernel: sd 13:0:2:0: [sdg] tag#917 Sense Key : 0xb [current] 
Apr 24 00:11:01 Tower kernel: sd 13:0:2:0: [sdg] tag#917 ASC=0x4b ASCQ=0x3 
Apr 24 00:11:01 Tower kernel: sd 13:0:2:0: [sdg] tag#917 CDB: opcode=0x28 28 00 91 87 ff 8f 00 00 15 00

 

I moved the drive to another area of my backplane with the same error happening so i guess its a dead drive?