Download https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.6.7-x86_64.zip
Open it up, and extract all of the bz* files (bzfirmware, bzimage, bzmodules, bzroot, bzroot-gui) in the root of the zip to the root of the flash drive
Reboot
FWIW, instead of entering in the command that might scare people off, you can also get the info via Tools - System Devices. And also via the various ACS override options, you can also potentially separate devices that are natively in a single IOMMU group to their own.
May or may not be related, but you need to run File system checks on the cache drive
Jul 07 03:08:44 shoebox kernel: XFS (sdg1): Metadata corruption detected at xfs_dinode_verify+0xa5/0x52d [xfs], inode 0x40a71b6a dinode
Jul 07 03:08:44 shoebox kernel: XFS (sdg1): Unmount and run xfs_repair
FYI for anyone else (since its a seemingly minor problem) is that you would not have been able to install or update any plugin while it was in that state.
Because it's not a .cfg file
But, is that a standard file that is executed by unRaid itself when stopping the array? If so, then I've missed the memo there.
Just a forewarning, not all hardware is compatible with passthrough, and even if the manufacturer says that it is (ie: includes IOMMU in the BIOS, it does not mean that it actually works correctly)
In your case, you are attempting to use passthrough on a motherboard that was first sold at least 8 years ago. First suggestion is to check for updates to the BIOS (it is dated 2011)
I'm thinking that if you're pointing everything to it that it's what's interfering. I don't use piHole, so can't really offer up any suggestions though.