WalkerJ

The 1.6 version has a couple of issues. Missing closing quotation marks on lines 95 an 101 prevent it from running, and "preogram_dir" is misspelled on line 49 which makes that check fail silently. The version number returned from -V was incorrect, also. Here's an updated file with those issues fixed. unRAIDFindDuplicates v1.7.zip

I just tried installing it for the first time and am getting the same error. I tried several different UI options with the same result. Edit... the Fooocus UI works, but some of the others do not.

Fix Common Problems is saying "Realtek R8125 NIC found" and suggesting that I install this plugin. When I check Tools->System Devices, my built-in NIC reports as "Realtek Semiconductor Co., Ltd. Killer E3000 2.5GbE Controller (rev 06)". System drivers says that I have "r8169 - RealTek RTL-8169 Gigabit Ethernet driver" in use, but no mention of 8125. Is this a false positive with Fix Common Problems? I have some flaky issues with browsing shares occasionally, long delays to load the folders and files, but I'm not sure it's related to the network card. The server has an i7-13700k with 64GB RAM, so CPU/RAM should not be an issue.

I had a Zerotier container running. I disabled both it and the built-in Wireguard VPN and the container still fails to start with the same error: "possible DNS issues, exiting..." There must be something different about how the Deluge container starts the VPN vs how the QBT one does because the QBT one works fine, but the VPN setup in init.sh is identical for both. I am not enough of a Docker expert to investigate much further myself.

This container stopped working for me after upgrading to 6.12, also, and I was already bridge networking. The symptom is the VPN can't connect because of "possible DNS issues". That could be because it just can't connect to anything due to a networking issue. I had been running 6.12 RC5 for a while, and I don't think I had any issues then. It only broke after upgrading to 6.12 final. I tried two different VPN providers with the same result. The binhex-qbittorrentvpn container works fine, though.

After upgrading, the "Minimum free space" for all of my shares was set to 51.2%, both those that are assigned to a cache pool and those that are not. The pop-up help for this field says: Which suggests that the value should be a size, not a percentage. Does the help text need to be changed? What is the behavior of this setting for shares with no "secondary storage" configured? That's not clear from the release notes or help text. Why did it default to something like 51.2%? If I understand the function correctly, that is not a sensible value for the system to choose automatically.

My VM's have been randomly crashing. I've done dozens of tests for two weeks and there is no evidence of hardware being to blame. Is there something in libvirt.img that could cause something like this? Should I rebuild my Unraid USB? Here are some details: After lots of troubleshooting I've found that Prime95 will crash any of the VM's instantly when running the small or smallest FFT torture test. It crashes the second I click the start button and the temp never goes above 45 C. It only crashes the VM and doesn't affect Unraid. Booting the server with Windows instead of Unraid and running the same tests directly on the server rather than from a VM doesn't cause a crash, and in fact it spikes the temp to 100 C (which is the default thermal throttle temp for a 13700k, and Intel says is an OK temp for that CPU) and continues to run completely stable in spite of the temp. (The VM's were crashing randomly before. I started testing with Prime95 because it can cause them to crash on demand.) I've tried everything else possible with the hardware, BIOS settings, and Unraid and VM settings. I've set the Tjmax in BIOS to 65C to prevent the CPU from going higher than that, and set max power draw to 235w, and it still crashes. There's no correlation between the temp/power and crashing. The problem is also 100% not RAM related. I've tried different RAM, one stick or two, and lowering the RAM speed to half of stock. The VM's still crash in all scenarios. I replaced the power supply with a brand new Seasonic 850w, which is more than double what the system really needs. If the problem were the CPU or motherboard (or any of the hardware) it would crash running the torture tests locally rather than through a VM because it's using more cores than I had allocated to the VM, and the temp goes much higher. There's nothing helpful in any of the logs. Here's my original post...

That was the issue. I used their config builder to create a new config file and it worked with the latest image. I left in the line "comp-lzo adaptive" and it seems to work, in spite of an earlier post saying that the comp-lzo line had to be removed.

Removing the "compress" line causes errors and the VPN never connects. I rolled back to 4.4.5-1-01 for now until this gets sorted out.

It's crashing with both Windows and Linux guests (Ubuntu & Clear Linux). Some are old, others I just created from scratch. I don't think it's the guest, but I'm not sure where to go next. I tried undervolting the CPU and setting a CPU power limit, but it didn't change anything. I also ran Memtest and there were no errors. I also tried limiting a VM to only 2 cores, and enabled hugepages. Update... I tried restoring a libvirt backup and moving the VM IMG to a different disk (from cache to array) - same result. I also tried running Prime95 instead of the app I usually use in these VM's. It crashed just the same with Prime95, so it's not something specifically to the apps I'm using in the VM. Update 2.... I updated Unraid to 6.12.0-rc2 and get the same result.

I tried this and it got rid of the split log messages in the log, but the VM's still crashed.

All of my VM's just started crashing today. AFAIK nothing has changed with the VM or Unraid. The rest of Unraid and multiple Docker containers are unaffected. I tried a VM I haven't started for months (so it's on a much older version of Windows 10) and it crashed the same way. One of them is using a RAW image, the other Qcow2. Hardware is i7 13700k with 64GB RAM. I have tried searching the forums and Google, and rebooted the Unraid server. I tried updating VirtIO drivers, expanding the Vdisk to make sure it's not out of space, and disabled Windows Defender. I also changed which CPU's were assigned so that only the P-cores were assigned to the VM, but it didn't make a difference. It seems to be OK as long as I just boot it and leave it idle. As soon as I run something that uses the CPU, it crashes. In particular I am running an old Java 8 based application that I use for my business. I doubt the particular app or Java is the root cause because this app is ancient and hasn't changed since 2017. I've been running this app on VM's on Unraid for years and it has run flawlessly until today, and on this server for about 6 months. I just created a new VM from scratch using a freshly downloaded Windows 10 ISO. I didn't install any Windows updates and only install the aforementioned Java app. It crashed the same way as soon as I tried to run the Java program. I'm not trying to pass through GPU or sound. All of my VM's are vanilla Windows 10 installs. The last thing in the VM log when it crashed is the following, then a register dump. I don't think the spice-server bug is the issue because I've seen it on VM's that didn't crash. Syslog, VM log, and VM XML are attached. I tried running the same Java app on a Linux VM and it froze but didn't crash to the point of doing a register dump. I could still connect with VNC, but everything was frozen and there was no CPU usage according to Unraid. char device redirected to /dev/pts/1 (label charserial0) qxl_send_events: spice-server bug: guest stopped, ignoring error: kvm run failed Invalid argument voyager-syslog-20230407-2319.zip UnraidVMlog.txt UnraidVM.xml

There are no lines with 'comp-lzo' in the config file. There is a line that says 'compress'. Is that related?

I am getting this error also, and the container can't connect to the VPN/internet.

I've been having to restart the API every couple of days to resolve this. Restarting it fixes the issue immediately but it eventually returns. It started for me the same day OP posted this thread. I'm on 6.11.5.