Dela7460

I got this resolved.
The original power supply was still good; but since  I already got a new one I went ahead and swapped it.
The old power supply had a odd auto reset failure switch rather than a fuse and I just didn't want to mess with it.
 
The real problem came out to be board tension. At the bottom of the board I had a USB adaptor that plugged into the motherboard.
This adaptor sat at the very bottom of the board and held my Flash stick for Unraid. The metal housing of the adapter was making contact with the bottom of the case.
Which was fine; but it was causing the board to be under tension. 
 
For some reason a motherboard support peg (stand off) between the ram and the  SATA plugs was not exactly aligned and  was a bit cocked eyed and the bolt holding down the board to it was not the right size and was causing the board to be off kilter. This was causing a short some how.
 
Switching out the stand off and bolt and reseating everything seemed to have helped.
I still have the USB adapter pugged into the same place but I plan on changing it to one that doesn't touch the case when plugged in their.
 
Over all the sever got a good cleaning and I tossed in a 970TI that was laying around.
 
I do have 2 more sticks of ram I want to toss in it but it seems that every time I do the server freezes a week later.
I've done extended prime 95 test for over a week on each stick and can't find any faults.
 
Without fail each time those addition sticks are in the slots the server freezes with in a week.
Other wise it go's without issue for years. 
 
Even if I swap out the current sticks with the new ones it still eventually freezes.
 
Yes same brand, same everything on the ram. Way to late to RMA them. 
Board ram max is 128g  I currently have 32g in it and wanted to upgrade that to 64g.
Ram is mainly used for my VM's.
Back in the day when I ran a Ark server that thing would gobble it up.
Now I hardly run any VM's so no real reason to add the ram other than I already paid for it and its just sitting their.

I reseated the drive and It came back to life. I'm backing up all the data now.
And ordering two Nvme drives to raid them together as a new cache drive.
 
My VM's are the only thing I'm concerned about; it seems that every few months I'm having to deal with some issue regarding my VM's

So it looks like all my troubles were caused by a bad brand new NVMe drive I got from Amazon.
creating a pool of cache drives with it caused all kinds of madness to happen.
Probably why it was saying it was read only and in other places it would save device 2 was missing.
 
I would recommend people stay away from fanxiang branded drives yes they are super cheap but seem to be total crap.
 
Waiting on Parity to finish to restore docker and vm's
Thankfully I did have backups of all that.

Solved the issue.
Had to turn on the following options in BIOS
IOMMU - enabled
SR-IOV - enabled
 
In addition there are some values that have to be set to enabled putting them on AUTO seems to have no effect. Unfortunately I forgot what those were.
But if you have the option of Enable use that rather than AUTO
 
Everything looks stable and is running smoothly; there is still a peeked  thread when someone joins but only for about 5 seconds then back  down to 2-6%

Ok, I'm up and running just like I wanted too.
I had to open terminal and rebuild the partition tables on each drive.
 
Open Terminal
parted /dev/sd?                 sd? = the drive your targetting like sdh or sdg
select /dev/sd?                  make sure drive is selected
mklabel gpt                        y  = to confirm
 
That made the drives available for preclear.
 
One other note,
In order to have drives slots show up under the new pool you need to change the pool size of your main array so instead of 22 -> 12
This allowed me add the 2 new/old drives to the newly created pool.