Background:

I had an array with 1 parity disk (14TB) and several data disks (mix of 12TB, 3TB etc). I ran Parity Sync, it ran for a day and completed with some read errors, and the partity device is disabled. I found this thread about how to re-enable it which basically is re-running Parity Sync (which I did several times).

 

My question: any idea on why is it disabled? How do I ensure parity will be enabled (replacing bad disk / rerunning sync / re-creating array)?

More info:

What I have done:

- Rebuild Parity (several times)

- Rebuild the array with new config (Tools > New Config)

- Read Check (several times).

 

 And the latest Read Check result:

Parity-Sync 2023-06-01, 12:18:11 (Thursday) 14 TB 48 min, 2 sec 4.9 GB/s OK 2784980955

 

 

 

wst-diagnostics-20230601-1651.zip

Edited June 2, 20233 yr by tlk888
Update questions

Jun  1 02:40:16 WST kernel: md: disk1 read error, sector=1157933504
Jun  1 02:40:16 WST kernel: md: disk7 read error, sector=1157932480

You are having read errors on multiple disks, Marvell controllers are not recommended, they tend to drop disks without a reason.

 

 

14 hours ago, JorgeB said:

Jun  1 02:40:16 WST kernel: md: disk1 read error, sector=1157933504
Jun  1 02:40:16 WST kernel: md: disk7 read error, sector=1157932480

You are having read errors on multiple disks, Marvell controllers are not recommended, they tend to drop disks without a reason.

 

 

 

Is there a recommended controller? I'm looking to add something like this : https://www.amazon.com/Original-9211-8i-FreeNAS-unRAID-6Gbps/dp/B082HKNCVD 

That's a good option, more here:

 

On 6/2/2023 at 1:15 AM, JorgeB said:

Jun  1 02:40:16 WST kernel: md: disk1 read error, sector=1157933504
Jun  1 02:40:16 WST kernel: md: disk7 read error, sector=1157932480

You are having read errors on multiple disks, Marvell controllers are not recommended, they tend to drop disks without a reason.

 

 

I re-run it and all drives are green now, parity enabled  Will replace current SATA3 controller with the HBA card .