MylesDB

Hey so I've managed to get the array all up and working now. 

So as for the crashing when stopping the array, this issue was two-pronged. A.) I had XFS errors on disk2, so I fixed it with:
 
xfs_repair /dev/md2p1
B.) I was seeing opcode errors. I'm using Ryzen 1st Gen CPU architecture. In the process of trying to get the new HBA working I reset bios, and thus it reset settings relating to C-states and idle power. So I changed those to the apropos settings. 

As for fixing it all I did the following:

When replacing my disk with parity, I actually viewed the syslog to see what UnRaid was doing to create the GPT partitions:

Screenshot from GPU using capture card.. (not sure if gui syslog would have been running to see)


 
Once I fixed my crashing issue I proceeded to:
 
1.) Start the array in maintenance mode. 
2.) Run the following commands (x denoting the appropriate disk):
 
sg_disk -Z /dev/sdx  
sg_disk -o -a 8 -n 1:32K:0 /dev/sdx
3.) Stopped the array and then started it in normal mode.

The drive mounted and I did it with the rest of my data drives, one by one - just to be safe. 

For my 2TB disk in my array, UnRaid said the disk was smaller than the original disk.. so I'm assuming the partition I wrote to it is not what UnRaid would usually use for a 2TB disk. But to get around this I just created a new config, preserving disk assignments. I then started the array and it mounted successfully, albeit it's not using what UnRaid would have intended for its partition, however, I'm assuming it's not a big deal.

As you can see below all disks are mounted successfully. 

I have some lost+found directories within the disk I mounted in R/W so that's on me. All the other disks are fine. 


 
I hope the following may be useful for anyone who finds themselves in a similar situation and doesn't wish to replace each disk through parity. 

Lastly, thanks Jorge for the support, it's been very much appreciate.