JahzyB

This worked!

I can try and come back with what happens.

I'm sure it was one of the data drives and not parity. I took a snapshot of the array as it was before. I also just tried a different data drive from my previous configuration and the same thing is happening.

That's how it looks with the array started or stopped. Not sure how I'd recreate the issue since it is ongoing and is the same as when the array is stopped. I started the array and am attaching diagnostics.

Here you go! Appreciate any help you can give.

I replaced every drive in my array and was planning on using unassigned devices to move the data back to the new drives in the array. When I plug an old drive in to attempt to move data on to the new drives in the array it only shows the size and the filesystem just shows a dash. When I attempt xfs_repair I get this: Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... and that just goes on forever. I'm not sure what to do and would appreciate any help. No partitions show and I'm unable to mount the disk.

Why don't I have enable multicore par2 as a setting? Repairing and verifying are going incredibly slowly on my system. Processor is a Ryzen 1700x.