Dr_Cox1911

Been a while since I updated my Unraid, I was still running `6.11.5` and just updated to `6.12.3`. Reboot took ages and now as it's back up I started the array and Unraid immediately started a parity check. Has this happened to someone else too? Normal behavior? Or should I check anything?

Baffled by this and never thought that something like this could happen with Unraid. I'm not talking about the corruption itself, Unraid can't do anything about it, but the fact that this can happen "silently" where the user doesn't get a notification/warning leaves a really bitter taste. Hope that Limetech addresses this ASAP, it's really their selling point with Data.

Greetings, I'm running a Debian Linux VM and use it for web browsing. The performance of my VM is really bad, I can barely use it to browse the web. My Hardware I've got a Ryzen 5 2600 with 16GB RAM, where I assigned 8GB RAM and the CPU-Cores 4, 5, 10, 11 to it. I'm connection from a different Linux host using Remmina via RDP. The rendering of Web pages takes ages and if I start scrolling I have a couple of seconds no feedback after the site rapidly jumps in the scroll direction. Is there anything I can optimize to get better performance out of the VM? Right now it's not really usable. If there is any info missing I'm more than happy to provide it.

I know how to get the diagnostics when the GUI is available, but in the case described above I only had direct access on the machine it self. Is there a built-in command to generate the diagnostics zip through console? Just asking when this happens again so that I can provide the zip accordingly. I will run with the cables switched for now to see if that was indeed the problem. Or do you guys have a different strategy in mind?

Sorry, don't know how to back the diagnostics up with the console. I just switched the network cables between my PC and the Unraid server and now the server is accessible again. The only strange part: my PC works fine with the cable that had problems on the server. I changed nothing else on the setup (so my PC is now using the same cable and is on the same switch port that the server used to have and vice versa). I can provide diagnostics now, but I guess they won't be of any help as now everything is working fine (for now?)?

Greetings all, I come to you in dire need again. My Unraid server was running fine for ~200 days and suddenly today as I wake it up with WOL I can't reach the WebUI. I started to ping the IP but I get "Destination Host Unreachable", so I plugged in a monitor but got no output. I did a hard reboot and now I have output. I booted into normal Unraid and logged in as root. My eth0 still has the proper IP address that got assigned to it, so that's not the problem. I then did a clean reboot from the root-login and booted up the safe mode. In safe mode I still get the same problem (WebUI down, ping "Destination Host Unreachable"). I then started to look through the "syslog" and found a bunch of lines regarding eth0 and one instantly caught my eye: "device eth0 entered promiscuous mode" Before this line there are statements that eth0 is active and live, after that line I get: These are repeated a couple of times and the syslog ends with this. Any tips on what I should do next? I did not install anything new the last time the server was accessible.

For client backups to my Unraid server I would really like to use BorgBackup. In order for BorBackup to work there needs to run a server instance, so it would be really nice if someone could make a Docker container for BorgBackup.

Jukebox (playing the sound locally on the machine where airsonic is running) doesn't work for me. If I configure the jukebox player and start a song I get this error in the log: Error in jukebox: java.lang.IllegalArgumentException: No line matching interface SourceDataLine supporting format PCM_SIGNED 44100.0 Hz, 16bit, stereo, 4 bytes/frame, big-endian is supported