Parity device disabled

[EduAid]

Hello

 

I have recently build a storage server and just when i was putting on my data into the server one of the drive showed it is disabled.

for that reason since there was no data in my server i thought of rebuilding it from scratch.

which i did yesterday and replaced the drive which failed with the parity one 

but now also same problem.

hdd is a new wd gold hard disk 

please suggest how to proceed 

 

[ChatNoir]

7 minutes ago, EduAid said:

please suggest how to proceed 

Hello, your diagnostics might provide a clue as to why the drive is disabled.

Preferably before rebooting, go to Tools / Diagnostics and attach the zip file in your next post.

[EduAid]

hello

have attached the Diagnostic report

jarvis-diagnostics-20210624-1129.zip

[howyoulikethat]

I had the exact same problem a few days ago. Parity disabled. My logs show this a bunch (eventually followed by read & write errors):

Jun 22 15:53:38 Tower kernel: ata14.00: exception Emask 0x0 SAct 0x6018000 SErr 0x0 action 0x6 frozen
Jun 22 15:53:38 Tower kernel: ata14.00: failed command: READ FPDMA QUEUED
Jun 22 15:53:38 Tower kernel: ata14.00: cmd 60/00:78:58:a7:d2/01:00:03:01:00/40 tag 15 ncq dma 131072 in
Jun 22 15:53:38 Tower kernel:         res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Jun 22 15:53:38 Tower kernel: ata14.00: status: { DRDY }

 

I just compared to yours, and we have the same (or similar) error, I think? 

Jun 23 17:08:51 Jarvis kernel: ata7.00: exception Emask 0x10 SAct 0x7e000003 SErr 0x10000 action 0xe frozen
Jun 23 17:08:51 Jarvis kernel: ata7.00: irq_stat 0x80400000, PHY RDY changed
Jun 23 17:08:51 Jarvis kernel: ata7: SError: { PHYRdyChg }
Jun 23 17:08:51 Jarvis kernel: ata7.00: failed command: WRITE FPDMA QUEUED
Jun 23 17:08:51 Jarvis kernel: ata7.00: cmd 61/40:00:60:2a:ef/05:00:9b:01:00/40 tag 0 ncq dma 688128 out
Jun 23 17:08:51 Jarvis kernel:         res 50/02:01:01:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Jun 23 17:08:51 Jarvis kernel: ata7.00: status: { DRDY }

 

Don't ask me what it means or how to fix it. Mine was on Disk4. I started a 2 day long parity check (12TB). I'll see if that helps. Maybe a reboot. Rebuild the drive? 

Yours looks to be on Disk0, which I'm assuming is your parity.

[itimpi]

According to the diagnostics the parity disk was disabled because it dropped offline  As a result there is no SMART information for the drive so we can check that for the drives health.

 

Most of the time this sort of issue is a problem with the power or SATA cabling to the drive.   I would suggest powering off; checking (or changing) the cabling to the drive; powering back on; and then getting new diagnostics so we can see the SMART information for the drive.

[EduAid]

43 minutes ago, howyoulikethat said:

I had the exact same problem a few days ago. Parity disabled. My logs show this a bunch (eventually followed by read & write errors):

Jun 22 15:53:38 Tower kernel: ata14.00: exception Emask 0x0 SAct 0x6018000 SErr 0x0 action 0x6 frozen
Jun 22 15:53:38 Tower kernel: ata14.00: failed command: READ FPDMA QUEUED
Jun 22 15:53:38 Tower kernel: ata14.00: cmd 60/00:78:58:a7:d2/01:00:03:01:00/40 tag 15 ncq dma 131072 in
Jun 22 15:53:38 Tower kernel:         res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Jun 22 15:53:38 Tower kernel: ata14.00: status: { DRDY }

 

I just compared to yours, and we have the same (or similar) error, I think? 

Jun 23 17:08:51 Jarvis kernel: ata7.00: exception Emask 0x10 SAct 0x7e000003 SErr 0x10000 action 0xe frozen
Jun 23 17:08:51 Jarvis kernel: ata7.00: irq_stat 0x80400000, PHY RDY changed
Jun 23 17:08:51 Jarvis kernel: ata7: SError: { PHYRdyChg }
Jun 23 17:08:51 Jarvis kernel: ata7.00: failed command: WRITE FPDMA QUEUED
Jun 23 17:08:51 Jarvis kernel: ata7.00: cmd 61/40:00:60:2a:ef/05:00:9b:01:00/40 tag 0 ncq dma 688128 out
Jun 23 17:08:51 Jarvis kernel:         res 50/02:01:01:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Jun 23 17:08:51 Jarvis kernel: ata7.00: status: { DRDY }

 

Don't ask me what it means or how to fix it. Mine was on Disk4. I started a 2 day long parity check (12TB). I'll see if that helps. Maybe a reboot. Rebuild the drive? 

Yours looks to be on Disk0, which I'm assuming is your parity.

Yes I do think it might be because of power issue such as molex cable or sata cable or may be in worst case the power supply .
but in my case powersupply is a brand new one so is molex cable but i have attached all the hdd to one molex cable and will retry with another sata cable must not be a problem lets see . will update if it resolves the issue 

 

Currently i m moving my data so it will take time for  me to apply the fix 

 

[trurl]

5 hours ago, howyoulikethat said:

started a 2 day long parity check (12TB). I'll see if that helps. Maybe a reboot. Rebuild the drive? 

Parity check will not help. Unless you have dual parity it will only do a read check. Parity check won't fix a disabled data disk. Just wasting your time while your array is unprotected.

 

You should start your own thread with your Diagnostics 

[EduAid]

hello 

have reboot the entire system and also swapped the sata cable and molex cable and after that also it showed the same

have attached the diagnostics report please look into it 

jarvis-diagnostics-20210624-1630.zip

[itimpi]

Would not expect the view to change after a reboot.    The updated diagnostics suggest the disk itself is fine.   Hopefully you have fixed any cabling issues.

 

To clear the disabled state the parity has to be rebuilt.   You can follow the process given here in the online documentation accessible via the ‘Manual’ link at the bottom of the Unraid GUI.

[EduAid]

Thanks it worked parity is rebuilding itself and hope after 16 hours it will resolve itself. 

will update after its done

 

[EduAid]

while rebuilding the parity i got another disk error can suggest if i have to change it or have some troubleshooting to do.

jarvis-smart-20210624-2215.zip

[JorgeB]

Disk2 is failing, copy whatever you can manually or using ddrescue and then rebuild parity with a new disk.

[howyoulikethat]

On 6/24/2021 at 6:30 AM, trurl said:

Parity check will not help. Unless you have dual parity it will only do a read check. Parity check won't fix a disabled data disk. Just wasting your time while your array is unprotected.

 

You should start your own thread with your Diagnostics 

 

Thanks! I do have dual parity. Both were disabled and one of the array drives was the one with read/write errors, but it was not disabled. It was just doing a read-check like you said, and I didn't realize that. I troubleshooted as suggested: swapped some cables and rebooted, the array drive reconnected, then I emptied, restarted the array, and reassigned the parity drives. It's doing a parity rebuild now. Hopefully we'll be back in business in... 2 days and 3 hours.

[EduAid]

Yes Friend it helps mine is working fine wait for the parity check it will resume .

[itimpi]

2 hours ago, howyoulikethat said:

 

Thanks! I do have dual parity. Both were disabled and one of the array drives was the one with read/write errors, but it was not disabled. It was just doing a read-check like you said, and I didn't realize that. I troubleshooted as suggested: swapped some cables and rebooted, the array drive reconnected, then I emptied, restarted the array, and reassigned the parity drives. It's doing a parity rebuild now. Hopefully we'll be back in business in... 2 days and 3 hours.

That screenshot is showing a lot of errors  was it taken before you started the parity rebuild as if not then you still have a problem to solve.

[howyoulikethat]

Yeah, you can't do parity rebuild when they're disabled (red Xs). It started a read-check and obv every sector was a no go on disk4. But what was weird was it still had a green dot and said normal operational/active. I didn't know what was going on. It apparently just had a wonky cable connection develop. Everything seems to be working now. 

 

[itimpi]

This last screenshot looks like what I would expect to see with a parity rebuild that is proceeding satisfactorily  

[EduAid]

Hello the disk again failed 

and it shows 1872 errors donot know why and how.

jarvis-diagnostics-20210626-1051.zip

[JorgeB]

1 hour ago, EduAid said:

Hello the disk again failed 

Parity dropped offline, you're using a controller with SATA port multipliers that is known to drop disks, if you need an ad-don controller see here, but since you have so few disks why are you not using the Intel onboard ports (except for the SSD)?

 

Jun 25 01:50:24 Jarvis kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jun 25 01:50:24 Jarvis kernel: ata1: SATA link down (SStatus 0 SControl 300)
Jun 25 01:50:24 Jarvis kernel: ata4: SATA link down (SStatus 4 SControl 300)
Jun 25 01:50:24 Jarvis kernel: ata2: SATA link down (SStatus 4 SControl 300)
Jun 25 01:50:24 Jarvis kernel: ata3: SATA link down (SStatus 0 SControl 300)
Jun 25 01:50:24 Jarvis kernel: ata6: SATA link down (SStatus 4 SControl 300)

 

[EduAid]

https://www.electrobot.co.in/product/2562?gclid=CjwKCAjwoNuGBhA8EiwAFxomA8ihmtf4qytLzsE9ItkgW8EO6_0AFHjHalxgziPED2LB_qFWBnuG-xoCFssQAvD_BwE

 

i m using this card please advice me if i have to change it or it will work

[JorgeB]

8 minutes ago, EduAid said:

please advice me if i have to change it or it will work

I already did, it won't work correctly with Unraid.

[EduAid]

The only reasonable card and cable i found a=on amazon in INDIA are give below 

Cable : https://www.amazon.in/gp/product/B013G4ESWC/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1

Card :- https://www.amazon.in/gp/product/B002RL8I7M/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1

 

Please suggest if they work 

and also if this card will support Western Digital Red 4TB NAS Hard Disk Drives

[JorgeB]

14 minutes ago, EduAid said:

Please suggest if they work 

Should work, make sure HBA is in IT mode.

[EduAid]

Please suggest me how to verify it , or how change it ot it mode

[JorgeB]