Distinguished

I am also having this issue, still on 6.9.2. I thought my server memory modules were going bad, happy to see this is not just me...

Similarly, I'm running an Xeon E5-2648Lv2 on a Supermicro X9SRH-7F board and no matter what NVIDIA Unraid build I try, it will kernel panic with my Quadro P400 inserted. Also, it will kernel panic MOST times (90%+) on any build when the card is not even inserted. My processor has the VT-d instruction set and by all other metrics it looks like the Unraid Nvidia builds should work, but they won't. I always get one of two kernel panics after unpacking initramfs.

I swapped power and sata cables and moved the Parity 1 drive to a different SAS port, started a new config, and was able to build full parity without issue. Everything appears to be running fine. Thanks everyone!

I did see that in the logs but didn't think much of it since I've been seeing a lot of that lately. Thanks for the suggestion, I'll give it a shot.

Logs attached here. Thanks for the speedy reply. unRAID is still doing a parity check which is presumably borked. redacted-diagnostics-20180418-1452.zip

I'm new to unRAID but have read documentation and am continually scratching my head about this issue. Just bought a pro license yesterday but am very concerned about what's been happening. So, this all started when I started a parity check one evening and woke up the next morning to my Parity 1 drive moved to "Unassigned Devices", but still also listed as a spun-up Parity drive but reading 22 trillion read and write errors. This drive has 32 days of uptime and is brand new, and given the information at the time I thought this meant my 2nd Parity drive was bad given its already questionable SMART status, so I decided to order a new drive and replace it. I stopped everything, powered off, checked connections, powered on, and found that my unRAID flash drive had become corrupted and/or the filesystem was totally wrecked. I replaced this with a brand new flash drive, was able to recover my config and copy it over, and boot back into unRAID to find that 2 DATA drives were now labeled as "missing", and did not show up in terminal using lshw -c disk. Parity 1 was also unassigned, but was visible so I reassigned it. I powered off again, checked connections again, and rebooted to find one data disk to still not work. Easy enough to deal with, I thought, since that one data disk didn't have any data on it. I replaced that data disk, and now I'm back to pretty much the same scenario from the start: I am doing a parity rebuild/check with a NEW 2nd Parity drive, and a NEW data drive, and the rebuild/check has run all day until now without issue, but as it approached 1.91TB in the parity check (which it should be stopping at since the data drives in my array all have a writable volume of 1.81TB) , Parity 1 suddenly listed 22 trillion read and write errors again, now shows no SMART temperature, and is listed when you drill down as a SPUN DOWN drive. Mind you, this parity check is still RUNNING as we speak, and reports no issues, and the system logs show absolutely nothing. It's completely silent. I've checked all drives for SMART status, checked my drive configuration, and am completely at a loss. Something is really messed up and I don't know what it is. This is running on a pre-owned but well-conditioned SuperMicro X9SRH-7F and E5-2630Lv1 with 96GB of Samsung ECC DDR3-1066MHz RDIMMs. This problem seems to keep occurring at a particular point, and is not intermittent which leads me to believe it's not a hardware issue. See photos for more info on how my array is situated and the current status.