Stable Releases

This is a very low priority issue, but one I've noticed in the last week or so (probably since upgrading to 6.12.9, but I don't recall when I first saw it).   The CPU graph on the Dashboard of the GUI always "drips" to zero at the left edge of the graph as the line runs off the edge of the graph. I've captured this GIF to show it: You can see how it "drips" down the left hand edge of the graph.   Again, this is a very minor, low-priority issue, but one that is, hopefull

Hi I've been having issues with my servers. I have two almost identical servers. The only difference is the motherboard and ram. Both have very similar issues with Kernels. I'm not running any dockers and I've ran Ram tests 2 times with no issues. I've swapped out the usb thumb drives. Swapped out the power supply, ram, cooler, motherboard. I've had times where the server will stay up for hours, but it randomly will become unresponsive and I have to manually reboot the server.     

Hello. After renaming the name of the script in the section where user scripts are located, the file is not renamed and the original name remains. Do you can fix it, please?

I already commented this in one of the Unraid 6.8.X or 6.9.X update topics after the main dashboard has been completely changed, but it was never fixed.   Bug: Clicking on "Disk X" or any other of the clickable icons does randomly nothing.   The reason is that Unraid is reloading most of the content through the "devices" API every second:   And if you click on an icon while the content is reloading, the click does nothing (race condition).   How

Not sure i'm doing it right, but this morning my NAS crashed. Rebooting, i had a new errror message   vm (CT1000T500SSD8_240145FB304E) has file system errors ()   In fix common problems i have :     So that may be the cause of the crash. In any case, i cannot see my SSD as mounted.....       nas-diagnostics-20240423-1052.zip

Never seen this before.  I have 3 servers, most running Unraid since 6.9 or so.  All have multiple interfaces with some interfaces having VLANs.  Each runs macvlan, with bridging off on all interfaces.  I assign the appropriate subinterface and a static IP for each container.  Two have stayed pretty current on 6.12.x and went from 6.12.6 to 6.12.8 just fine.    One 11th gen Intel has stayed on 6.11.5 because 6.12 was causing instability.  I decided to bite the bullet and try 6.12.8 and

The server crashes and becomes unreachable after a couple of hours, up to now I cannot find out what could be the problem any help is appreciated.unraidserver-diagnostics-20240330_0932.zip

Crashes every couple of days since update. Was stable before, but on pretty old version, 6.9.2 and the UI was getting a little sluggish, so I tried updating to see if that would help, it did and is more responsive, but crashes every so often. Haven't pinpointed yet a catalyst. Console show no signal, but it's powered on, have to hard power cycle or reset button. Boots up no issues as far as I can tell. server-diagnostics-20240419_1350.zip

Hi all,   I have container that use network from other container using --net parameter (network type is set to none):   for some reason in Docker tab I can see random IP and ports maping for this container, sometimes after reboot this value is correct and empty:  

I just upgraded to unraid 6.12.10 from 6.11.5.  Server comes up OK.  But as soon as I begin using the Windows 10 VM, the entire server freezess, not just the VM.  I have to do a hard reboot to access the unraid server again.   When I went to downgrade back to 6.11.5, unraid requested I submit a report here.  I have attached the diagnostics file.  This server is older hardware.  I am semi-technical, so please keep that in mind as you respond.  Thanks.   This also happened when

System version: 6.12.6   urd-diagnostics-20240417-2146.zip

Unraid 6.12.10: I cannot install windows 11 VM,because the vnc window halt after system reboot during the install process. tower-diagnostics-20240417-1102.zip

I upgraded from 6.12.6 and the gui becomes unresponsive after ~ an hour.   I hard rebooted (console also was unresponsive) into safe mode with gui, no plugins. Ran for half a day and became slow/unresponsive again.  I did make the suggested network config change (forget what it was for 6.12.10). Diagnostics attached.  USB has worked fine since installation in early 2020. But wondering if it could be USB related? At this point, i'm thinking of reverting to my prior versio

Apr 6 12:30:13 Ugreen kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks Apr 6 12:30:13 Ugreen kernel: ACPI: Early table checksum verification disabled Apr 6 12:30:13 Ugreen kernel: xor: measuring software checksum speed Apr 6 12:30:13 Ugreen kernel: floppy0: no floppy controllers found Apr 6 12:30:25 Ugreen mcelog: failed to prefill DIMM database from DMI data Apr 6 12:30:47 Ugreen root: Error response from daemon: networ

经查，loop2是nvme(zfs)的docker。图像

netheril-diagnostics-20240413_1419.zip

Sorry for ChatGPT   Dear Unraid Forum,   Following up to this post in the German community, I am writing to report a recurring issue with my server that started after transitioning to a new Unraid build, utilizing solely used hardware. The server experiences frequent crashes, rendering it inaccessible along with its applications. After some troubleshooting, I suspect the problem might be related to a Docker container or similar, as the server remained stable with plugins, arr

My share "appdata" used my "cache" pool as an exclusive share. Now I wanted to replace the SSD of the "cache" pool against a bigger one. So I changed (without stopping the array) the "appdata" share configuration from:   to:   After that I started the mover and several hours later my nextcloud was broken (could not access relevant files). This was solved by rebooting the server.   I assume that inside of the nextcloud container the mount to the exclusive

I've recreated this issue twice as I expand my primary array, previously in 6.12.8, now in 6.12.10:   Purchase new disk(s), slot into backplane Drives are recognized under Unassigned Drives Start Preclear on some/all drives, wait for drives to complete Preclear. Optional: Purchase and add more new disks to backplane Once Preclear is complete, stop array to add drives Add drives, start array, this succeeds as expected Tick the "Yes, Format" a

Hello,   I have a kernel panic every day, this is only happening after upgrade to 6.12.8. At first looks like it was around same time but i can not be sure 100%, so i disable some custom script for backing up some folder to google drive, also change the backup pluging to 2 hours late since was running at the same time as the lates log line that i see before i wake up next day. these kernel panic are around 3am (CEST).     the only thing that i did try yet is to downgrade.

When running a docker scrub, the progress is never updated. Refreshing the page updates the progress.   ( cache scrub updates progress every 1 second )

Please see pre-questions： also see ZAP implementation limits filename length, causing operational errors. In view of this situation, I recommend using the normalization=formC setting when creating pool and dataset from webgui. Hope to get a reply to discuss this issue

[6.12.10]   Settings > UPS Settings > click the 'Online Manual' link on the right hand side of the page.   -------------------------------------- An error has been encountered in accessing this page. 1. Server: apcupsd.org 2. URL path: /manual/manual.html 3. Error notes: NONE 4. Error type: 404 5. Request method: GET 6. Request query string: NONE 7. Time: 2024-04-09 07:45:44 UTC (1712648744) --------------------------------------   I

Don't know if this has been reported before, but the diagnostics package saved contains VPN passwords if the server is currently running a docker container using a VPN. That would create an issue for anyone that has posted their diagnostics to the forum   (note that I've masked the user and pass here)   \_ /usr/bin/openvpn --reneg-sec 0 --mute-replay-warnings --auth-nocache --setenv VPN_PROV pia --setenv VPN_CLIENT openvpn --setenv DEBUG false --setenv VPN_DEVICE_TYPE tun0 --se

Hello,   I've been struggling with my other issue below, but maybe found a specific bug/fix for it. Therefor this new issue because it might not even fix the other one.   It seems like line 166 in rc.d/rc.docker is not entirely correct. "[[ -n $NETWORK ]] && nsenter -n -t $PID ip -4 route add $NETWORK via $THISIP dev br0 2>/dev/null" translates to nsenter -n -t 9439 ip -4 route add 10.253.0.0 via 192.168.0.231 dev br0   If I understand it correctly