Arbadacarba

Everything back online and ran parity check... No issues... Not sure what the initial cause really was

I ended up deleteing the VFIO file entirely and starting fresh... Worked

Further, if you are keeping the system in your office, I'd recommend Coolercontrol (Docker) to let you adjust cooling and sound.

You might also consider running two of the SSD's striped with regular backups to the aforementioned 12TB. That would be excellent for your active editing. Not that I know much about editing, but that'e what I've done for my VMs

So, having looked I just have to hit save and ... Nope, hadn't noticed the "ACKNOWLEDGE ALL PCI CHANGES" button... Totally obvious if you expected to see that button... The message could say to look for that? Thank you

I've been playing, replacing some components and reconfiguring others... But I've clearly messed something up. I have two VMs that autostart at startup: One that uses the Network card (Upgraded) to run the router, and another to run home assistant. Once I log in I can just start the two VMs and they seem to be working fine. I also have a gaming VM that uses a Dedicated SSD, a USB card, and Video card. But it gets launched as needed (Sure wish I could let the server use that Video card when the Gaming machine isn't in use.) I guess I could completely wipe out the vfio-bind and rebuild, but if there error is coming from the config of a virtual machine that might not fix it. Thanks jupiter-diagnostics-20260609-0825.zip

Maybe leave it off and run a parity check?

Good point, is there a test I can run other than just going about my business for a week?

So I replaced a couple of drives with new 26TB drives, and am encountering a problem I've never seen before... I'm getting the occasional read error... But I'm not seeing anything in SMART reports. I had to move massive quantities of small files around in order to remove the old drives and install the new ones, so now I'm moving files back around to balance the drives out a bit. I'm not even certain these are happening on the new drives, I think I've had a few on each, and have had one on the cache drive which I know is 6 months old or so. I did upgrade to 7.3 but I'm pretty sure the first one happened before the upgrade. Any thoughts? jupiter-diagnostics-20260527-1446.zip

Is it just me? or is anyone else finding that making changes to the docker with Edit does NOT result in a modification to the configuration.py file? I feel like if I had done everything right the first time, it would have worked off the bat. Instead I had to use VI to edit the file inside the docker console until I got it right.

It may also be windows being weird with credentials... (assuming you are using windows on the laptop) Take a look at the credential manager and manually add an entry for the different addresses that you use... I've run into that on a few systems, and found adding a credential for both the numbered address and the dns name helps.

Common Script: gged in. What am I doing wrong that it won't let me put anything in here? I've seen that the black theme might be an issue but I can't seem to make it whatever it wants to see. My goal is to make in run a script from user scripts when a drive is plu

OK, Tried a reboot and got a bigger version of the image above... I wonder? Pulled the USB Drive I had plugged in... and System is back... Dangit... that is an unraid thumb drive that I created for something...

What on earth just happened: I'm playing with the idea of using a AV in a Docker to scan external drives (Thumb Drives) that are of questionable provenance... I have at least one that I suspect may have some kind of virus that transferred from a Windows machine that I pulled some data from. I installed the ClamAV docker and was about to see if I could point it at the unassigned drives folder to scan anything I mount in there... Then I tried mounting a drive and got a failure to mount... OK, lets try another one... Neither of these are suspect, I was really just trying to get the mount location right for the Docker I was configuring... All of a sudden I get this: and my fans spin up as my array goes offline... WTH? Anyone have any thoughts before I reboot my server? jupiter-diagnostics-20260421-1429.zip

Looking through that I'm impressed at how I think the scripts work... but at the same time I might not be able to take advantage of it since it doesn't have all the features that I need... So we can create scripts - Bash or PHP etc. That depending on the folder they are located in, can run when the referenced VM makes transition to Start, or Stop... but there is no provision to call a script when it is paused? Hmm. so I pause the VM when the AMP input switches to t different source so that wehn it gets switched back it comes up faster... So the script would not run in that case and my cooling system would continue to act as if the temps were remaining the same. What about the network hooks? Could a script be triggered when the VM loses connection? It mentions being unplugged, and when I pause the VM it vanishes from my network... Thanks