Arbadacarba

I've been having a non Unraid issue that has caused a couple of unclean shutdowns. And I'm trying to let my system do a parity check. But I'm also trying to onboard some system backups through syncthing and with that and a parity check running simultaneously I've had to pause the Parity check to prioritize the backup. But something weird has happened... The Parity tab has stopped updating: But the status bar on the bottom seems to be working. I tried capturing diagnostics but can't get them to collect.

Backed up the drive... had to reboot and the drive failed completely. Swapped it out and I'm back up and running.

Ya, looks like it... So I had to update to flash my BIOS and sure enough it refused to boot back up... It would start off fine and then lose the drive... Of course I ordered a pair of those industrial USB drives a couple of months ago when that forum message first appeared, but I haven't picked them up yet from the address they were shipped too... Now I have to figure out how to swap it again when I get them. Luckily I made a fresh backup of the flash drive as soon as I read your reply.

The usb is plugged into the USB2.0 header on my mainboard... Next time it happens I'll try flipping the main power switch off and on...

I've never seen this before, I restarted my server to make some changes in the BIOS and after failing to find the change I wanted to make got this at boot: The last part that repeated took a LONG time to cycle through and showed no sing of self correcting. In the end I unplugged the UPS and rebooted without issue.

My server has been generally running great through several rebuild over the past 7 years... But over the past year it has developed a funny problem... The USB fails to recognize after a reboot... Not every time but enough to notice... I can unplug it and plug it back in and then it works fine... until the next reboot... I have other USB drives plugged into the mainboard and they seem to stay connected. Is this a failure mode for usb drives? Should I just move over to a different boot method? I have a PCIE drive running as Cache and a pair of SSD's running striped as Config drives for dockers and VM's and such... Is there any REAL benefit to booting from a SSD or PCIE Drive?

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