Stable Releases

I use technitium DNS server. This used to have a custom UNRAID container profile, but not any more. So now I install the generic container (as found in Apps with the name "dns-server"). The default configuration does not work as is. I need to edit it with portainer to change a couple of paths and only then it starts.   This is the change I do: /mnt/user/appdata/technitium-dnsserver/config /etc/dns/config /mnt/user/appdata/technitium-dnsserver /etc/dns Both as

Issues with custom IPVLANL3 Docker network after the upgrade. All my dockers run on a custom IPVLANL3 network after the up grade none of the dockers will start and produce this error in the log “failed to create the ipvlan port: device or resource busy”   The custom network is present and all dockers are assigned to it. If I roll back everything works correctly as it always has   root@NAS1:~# docker network ls NETWORK ID     NAME        DRIVER    SCOPE c672

Hi,   In Unraid versions 6.11 (kernel 5.19.17) and 6.12 (6.1.x) on the Gemini Lake CPU architecture, a faulty OpenCL implementation is leading to GPU hangs when Plex attempts hardware-accelerated HDR tone mapping. It's important to note that Plex has verified that the issue is related to Unraid or the kernel's implementation. In contrast, in Unraid version 6.10.3 (kernel 5.15), HW-accelerated HDR tone mapping works without any issues in Plex.    This problem has been acknowle

Hello,   I used to have like 3-4 months uptime or more without problem.   I upgraded the motherboard, ram and added some hard drivers 2 months ago and from there, i had multiples crashed and my system is unstable really often.    I thought everything was behind me before last night I had a crash during the night.   Nov 3 01:50:26 Tower kernel: BUG: unable to handle page fault for address: ffffc9801d1b7a50   Anyone can help me understand the crash

我刚购买的密钥无法使用，提示注册的guid 不匹配，但是实际是一致的

I have a windows 11 VM that I have passed through most cores, a GTX 3060 Ti and a nvme drive. Since the beginning I had many issues with the VM or unraid crashing that I temporarily fixed through various posts about similar issues following stuff as long as it made sense. I didn't have crashing issues for many days even with VFIO. I had a sudden crush so I removed anything VFIO related but later that night (while the VM was practically idle) it froze. Today it froze while in use (the s

I have been having an inexplicable issue where the server hangs and requires a hard reboot to return to normal. This has occurred since upgrading to 6.12.3 (and now 6.12.4).   When I say it's random, I mean it: Sometimes the server has lasted 4+ days after a reboot, sometimes it's become unresponsive within minutes of booting. Sometimes it has crashed while disks are active, sometimes when they are idle. It's crashed with all of these combinations: Dock

Noticing all these errors in the syslog. Possibly related to unraid connect usb stick backup to the unraid servers? Or something else?   Ideas on a postcard..     Oct 29 00:32:22 Moulin-rouge flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Oct 29 00:33:39 Moulin-rouge nginx: 2023/10/29 00:33:39 [error] 15084#15084: *2403 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), c

I had a leading space in my 'Docker vDisk location:', which caused the docker image to be located on root / in a directory called ' ' (space). Since root is memory, it empty on each reboot. It was quite difficult for me to figure out that was the file being written.  It is easy to get into that situation, just stop the docker, add a leading space, and apply and enable docker.  It is difficult to get out of the situation because the GUI will not let me remove the space or change it to a

Hi,   TLDR: My server crashes if i initiate large file transfers with kb to gb sizes. With or without docker enabled. Don't know what to do, any help to diagnose this would be appreciated.   As there was nearly no interaction on my "General Support" post, i'm trying it over here. The previous diagnostics (multiple) are attached to this post:  I've changed docker to ipvlan, but even without docker activated i have these crashes. This also happens since several unraid ver

Precision Tower 5820 Xeon W-2155 32Gig, 10Gig NIC Will not boot past the boot up GUI As an upgrade or plain jane new install

Hi guys, my unraid is 6.12.4 and that is a new server, although I installed on Nov 2022. But I have never run it until rececntly.   I found my server always CPU is alwasy high after running a few days. This issue have occured twice in pass one week.    I only run docker apps besides default system.   I tried to access via web, the system can give me portal.  But I have met http 500 error after I input correct password.    shutdown or reboot command doesn't

Noticed this popping up in the system logs.   I do use a custom share point for docker but not sure if that should affect libvirt?   There's a double // in the log which I can't see that I've entered.   No really running VM's these days so not noticed it.         moulin-rouge-diagnostics-20231024-2149.zip

Hi,   I believe this started after upgrading to 6.12.4. The Stop, Pause, Restart menu items under the Docker tab do not react. The menu functions correctly in 'Dashboard'. Same issue happens both in Chrome and Edge. Upon clicking the menu item changes background to grey, however nothing happens. Screenshot attached.   Any idease? adulis-diagnostics-20231023-1850.zip

Am I confused/mis-understanding something? Am I thinking of a different field?  Or is this a bug? (Actually, even if I’m confused, I feel there IS a bug here.)   THE ISSUE: MINIMUM FREE SPACE for a share unRAID 6.12.3 Drives in share formatted with xfs   HISTORY I used a 3rd party backup program to back up my home PCs.  I have the backup program (Macrium Reflect) write the backup files to a share on my unRAID server.  YEARS AGO, I had the backup progr

BTRFS Cache pool containing 6 drives.  Removed a old slow 500gb drive (ensuring lots of spare space...over 2 TB free in the pool, over the size of the removed 500GB drive) leaving 5. Rebuild started automatically (as expected) has been running faithfully now....for a F-ING MONTH!!!  I know it takes about 4 hours tops to move 500gb of data (on really slow hardware)...why is this taking months to rebalance a small pool???  This has happened with other pools on other machines as well, and one

Hi, Not sure if this is unraid or community apps, but since it's now so closely integrated with a single button install, I'm going to post this here. Please move if needed.   On a new server, I created an "appdatapool" pool: https://imgur.com/8eDRjBk Next, I made the appdata share an exclusive share with just that pool: https://imgur.com/ByPW7Yp My docker is configured to use /mnt/user/appdata as default appdata storage: https://imgur.com/oWTlntH Some

I was running 6.11.5 and upgraded to 6.12. The upgrade went smoothly but none of my VMs could access the internet. I could view the VMs with VNC and access my dockers that have a web GUI from within those VMs, but the VMs themselves cannot connect to the internet or default gateway. My VMs use br0.   I tried downgrading to 6.11.5 and the issue was resolved. I've attached diagnostics from 6.12 before downgrading. tower-diagnostics-20230617-1431.zip   The only thing that s

Hi,   When creating a share with only primary storage set to array, and excluding all disks, instead of creating a share with 0 bytes free, it will not create a share, and it doesn't give an error: https://imgur.com/fAg6AZy I can understand the share is not being created, since there is no disk to create the folder on, but an error message would be nice.   A bigger issue is if the share is already created and disks get excluded. This is my share with all disks inclu

I created a share, then after doing so set all of the avaliable discs to excluded. After this I mapped it as a network drive. The drive showed the total free space of the array, but when I went to write a file to it from windows, I got the error message "there is not enough space on [share name]".   The kind folks on reddit pointed out that I had in fact had all drives excluded, and after including them all this fixed the issue. The SMB system should not show a drive with free space if

Updated from 6.12.3 to 6.12.4 to find that my server would not be reachable via the WebGUI after an array mount. I'm using a set of encrypted volumes and therefore need to start the server manually after each reboot. Originally thought Docker or VM would have been a culprit here, but at this stage, this happens now on a reproducible and constant basis. In syslog, I can see the following:   Oct 1 16:29:12 Tower nginx: 2023/10/01 16:29:12 [alert] 10797#10797: *772 open socket #21 le

I am running an OpenVPN Docker container (ich777/openvpn-client) with network=host and want my unRAID webUI to be accessible via this VPN. I can add the corresponding interface (tun0) to Network Settings -> Interface Extras -> Include listening interfaces but the webUI doesn't bind to the tunnel IP after a restart. I need to delete and readd the entry to get it to work. I guess this happens because the VPN container is still starting when the webUI process binds to the ports.

Hello,   I think I stumbled onto a major bug in 6.12.3. I upgraded tonight (was never on the rc releases so can't speak to that), just like I did any other upgrade.   Upon rebooting, my server had no IP address at all (I did not disable IPv6 in my /boot/config/go file either).    Reverting back to 6.12.2 fixes the issue. If I re-attempt the upgrade, it breaks again, so this is 100% reproducible on my system.   I'm using this NIC (Intel 2.5GbE) `04:00.

Hi all,   I'm not sure if this is thet same as the other bugs posted, because the server isn't hung - the issue only appears to affect the management plane. It's    I'm seeing the following in syslog: Oct 7 08:50:57 server php-fpm[14227]: [WARNING] [pool www] child 25071 exited on signal 9 (SIGKILL) after 42.661800 seconds from start Oct 7 08:50:59 server php-fpm[14227]: [WARNING] [pool www] child 28547 exited on signal 9 (SIGKILL) after 30.913435 seconds from start Oct

Unraid v6.12.4   Tried an undervolt script that made my server crash so had to do a manual reboot.  Had stopped the array because 50% chance it may crash. Anyway on rebooting the server my dockers had all stopped and the docker tab was missing.   Turns out that unraid has reset the custom docker vdisk location.  Not sure what triggered this but it is some kind of bug. It also changed the XFS to BTFS   Looks like it created some kind of symlink to