Squid

diagnostics are always better than a syslog

Edited that post referenced to also say to not delete the go file. My bad -> sorry for the inconvenience. Sometimes around here we assume things and don't properly spell it out for others that might not be as knowledgeable.

Are you using a USB hub or is everything connected to the motherboard. You want the boot device connected to the board, not via a hub

Settings - Schedules - Mover Settings - Enable logs Run mover then post your diagnostics

Post your diagnostics

--restart always if the container crashes will restart the container. If it is continually crashing, it will continually restart with the result you were seeing.

Yes it would be that plugin related. And it's not an issue. It happens during boot up as the plugin isn't considering the fact that when it reinstalls itself the VMs aren't yet enabled

First thing you would want to do is post your diagnostics

Because IOMMU group is including the ethernet adapter and the SMBus controller. You need to try to use one of the ACS override options to try and separate the onboard audio controller out.

Can you still access the system via another computer's browser? Install the GPU-top plugin

Have you tried size 1M instead?

yes Jul 9 16:47:49 NAS mcelog: failed to prefill DIMM database from DMI data A BIOS update might help suppress it if one's available.

First thing to look on import errors is https://forums.unraid.net/topic/57181-docker-faq/?tab=comments#comment-566086

Go to Apps, ensure it's up to date, then clear your cookies again.

Assuming that you've already handled this: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#comment-819173 You definitely want to run a memtest from the Boot Menu (if you're booting via UEFI, you will need to temporarily switch to Legacy mode for Memtest to work or alternatively create a new bootstick via https://www.memtest86.com/ Additionally, if you're going to mix and match memory (which you are), the most stable system is one which Has all matching sticks Has matching sticks installed in pairs (this also has a massive performance boost) If unable to match sticks, then you must ensure the the CL timing is identical between the sticks

Did you shut down the server before copying back and forth the /config folder and then replacing it?

Can you access the server via another system and the IP address?

If the BIOS isn't recognizing them, then zero chance that Unraid will. Looks like you weren't using any add on controllers, so look at cabling, if the controller is disabled in the BIOS etc.

Why do you think it's not binding it.

Then try another flash drive.

No that isolates it from the system. (And dont forget to also remove your manual edits to syslinux.cfg)

Jul 6 23:12:49 Axiom mcelog: failed to prefill DIMM database from DMI data Primarily an informational warning, and safe to ignore. A BIOS update might help though.

Your data is safe, so long as nothing physical happened to the drives. Have you rechecked the boot order in the BIOS yet? Can you manually do the Boot Override (using F12) and then select the flash drive and get the system to boot? Does it at least show the Unraid Boot Menu?

You should be doing the isolation via Tools - System Devices.

Yeah, and I saw the same thing once and had been meaning (and kept forgetting) to bring it to @ich777's attention.