(SOLVED) Array has many errors after adding new drives, issue happens around 75% of parity check (SOLVED)

[ksculland]

Back story:

I just upgraded my parity drives from 3tb to 4tb
Then added the 2 old parity 3 tb drives as data drive to the array.

 

Since then I have not been able to pass a parity check.

 

Greatly appreciate any suggestions

 

 

unraid-diagnostics-20200314-0940.zip

[JorgeB]

Problem with the onboard SATA controller:

Mar 14 02:52:18 Unraid kernel: ahci 0000:01:00.1: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x0000100000000000 flags=0x0010]
Mar 14 02:52:18 Unraid kernel: ahci 0000:01:00.1: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x0000100000000880 flags=0x0010]
Mar 14 02:52:18 Unraid kernel: ahci 0000:01:00.1: Event logged [IO_PAGE_FAULT domain=0x0000 address=0x0000100000000d80 flags=0x0010]

 

Seen it several times before on the forums with AMD boards, disabling IOMMU might help.

[ksculland]

Ok, weird that it would be an issue only now aftyer all this time.
I also have many VMs on this system. 
Are you suggesting I temperately disable the IOMMU to get my new hard drive configuration to pass the 1st parity check, then turn back on?
Or are you suggesting I turn it off permanently and not run VMs?

[JorgeB]

8 minutes ago, ksculland said:

Are you suggesting I temperately disable the IOMMU to get my new hard drive configuration to pass the 1st parity check, then turn back on?

You could try that to at least get the array stable.

 

8 minutes ago, ksculland said:

Or are you suggesting I turn it off permanently and not run VMs?

If you need VM hardware pass-trough and those errors keep happening, and like mentioned it's not that unusual with AMD boards, you might need a new board, bios update/newer kernel might also help, also note that I believe that on at least one case the user was still having issues even with IOMMU disable.

[ksculland]

Bios looks up to date ver 1.3
newer kernel??? not sure how to check this.

[JorgeB]

5 minutes ago, ksculland said:

newer kernel??? not sure how to check this.

Newer kernel would come with a newer Unraid release, e.g. you could try v6.9-beta1 which comes with kernel 5.5

[ksculland]

Issue Solved!!!

The issue seemed to be with the amd on board sata controller, as only the drives connector to it would have errors during the parity check which didn't happen before and I have had this system since 2018 ish.  I did try unplugging the connectors and putting new ones in. Same issue.

The parity issue only started happening after I was on UnRaid 6.8.3 so I restored the old version 6.8.2

 

Went to tools => new config

 

carefully ensured all drives where in the correct slots (serial numbers and disk slot number) and was able to add each back to the array one at a time, with ZERO erros !


Steps I followed for new config as I wanted to remove the two new data drive and add each drive back one at a time.
https://wiki.unraid.net/index.php/Shrink_array

1. Make sure that the drive or drives you are removing have been removed from any inclusions or exclusions for all shares, including in the global share settings. Shares should be changed from the default of "All" to "Include". This include list should contain only the drives that will be retained.
2. Make sure you have a copy of your array assignments, especially the parity drive. You may need this list if the "Retain current configuration" option doesn't work correctly
3. Stop the array (if it is started)
4. Go to Tools then New Config
5. Click on the Retain current configuration box (says None at first), click on the box for All, then click on close
6. Click on the box for Yes I want to do this, then click Apply then Done
7. Return to the Main page, and check all assignments. If any are missing, correct them. Unassign the drive(s) you are removing. Double check all of the assignments, especially the parity drive(s)!
8. Do not click the check box for Parity is already valid; make sure it is NOT checked; parity is not valid now and won't be until the parity build completes
9. Start the array; system is usable now, but it will take a long time rebuilding parity
   
   Attached Image for things now working!!!