Stable Releases

When using the Gray theme the dashboard seem to display a weird washout blue background for every card.  I tried to modified it with theme engine but that still doesn't work. (It was working for few week and suddently it just stopped) (Theme Engine was juste a workaround it not the ''issue'') I tried on 3 browser and the issue is still there. Even with private navigation I've cleared my cache Tried with a new install of Unraid Pro on a other server.

Everything the same since upgrade to 7.0.0 , no hardware changes The server becomes unresponsive after a few days, dockers stop responding and can't log into the server interface. Only solution is to hard reset, then it works fine for a few days again. This has happened more than 10 times allready and haven't found a solution. I tried turning off some dockers but the only thing that changes is that it takes a little more time until the server becomes unresponsive again. I wil

I am in the process of removing a drive from a raid1c3 pool. It's currently running with 2 out of 3 drives to be converted to raid1 but every minute it throws a warning saying a disk is missing.   I had to turn off email notifications for the time being to not spam myself with hundreds of these warnings.   Diagnostics will be attached as soon as the  BTRFS operations are completed.  

Things run okay for a week to a couple days, then go to login and everything crashes. SSH into it will allow connection hang after authentication and after a couple minutes of a hang can execute a reboot in command line. WebUI hangs everything on each page load. Docker is completely crashed and so is VMs. on reboot it states vfio-pci-errors had a issue. Attaching a Diag.zip but have to downgrade. Nothing has changed since update. Aside from one container. Memory is known working and memtest86 te

Hello,   when using a Browser's built in autocomplete to visit your server, a simple GET request to https://unraid.example.com/webGui/include/Boot.php should not shut down the server. Since such requests should be always POST requests, I am certain this is a bug and not intended.

Hi there, I noticed on my server today that a single core was stuck at 100%. I assumed it was a scheduled process, but it was still going an hour later. I checked the usage of Dockers, and none of them were using the CPU heavily, so I just assumed it was a stuck process and rebooted. However, after rebooting, and even before starting the array, 2 cores were now stuck at 100% (this has since settled down back to 1 core). So I tried rebooting in Safe Mode, and saw the same thin

Was unable to start array as a result of this error for a cache pool. Had to revert to v6. unraid-diagnostics-20250220_0908.zip

First off, I'd like to say thank you to the team behind unraid. This software has been amazing and I bought pro as soon as I tested it!   Since upgrading to 7.0 I've had problems and cannot access my server, at first, my server/docker would start fine but after a few hours it would crash and I couldn't access anything until a hard shutdown. I saw that it made have to do wigh dhcp so I shut that off, and turned on a static ip to see if that would help (it did not). Now, after re-enablin

Hello, it's been happening to me lately that I let access to the web interface and by ssh for random days, sometimes 2,3,6 days like other colleagues it's happening, here I leave my diagnosis so that please see if you can help me, this happens to me in the version that I have installed so it's not the fault of the version, 7.0. 0, before with the 16... it happened to me and I updated to see if it was solved but it's still the same, I have uninstalled all the plugins that I installed personally a

I have 2 Unraid servers, both running v7.0.0. One is a fileserver (Neo) using both NFS and SMB, the other is an appserver (BusyBee), which uses NFS to mount the shares from Neo. I have been getting the file id changed errors since day one, and have posted on both Facebook and in here, getting no answers. I see no errors in the logs for Neo. The file id changed errors are all from BusyBee. All Docker containers are set to use the Read/Write - Slave options for the remote mounts. I'm attaching dia

At the moment the two default VM network adapters have the following names:   This is really confusing as "virtio" and "virtio-net" are using the same virtual network adapter "virtio-net-pci" (which cost me hours to find out). The only difference is that "virtio-net" disables "vhost-net" access.   My suggestion is to use the real name, but with different notes (and its time for more adapters of course):    

On the V7 UNRaid server share config screen, NFS security setting rule field I put in:   192.168.166.6(rw) 192.168.166.8(rw)     Notice the space between them. After I hit apply, the space is removed and the /etc/exports file has it without a space and there are no exports. See below:   root@UNRaid:~# cat /etc/exports # See exports(5) for a description. # This file contains a list of all directories exported to other computers. # It is used by rpc.nfsd and rpc.mo

We have allways run Unraid with a raid disk setup and did not use the Parity drive. This worked fine for 6.12.x versions. now after the upgrade to v7 I can not start the array. ====== update: i deleted the cache settings and parity checks and then it started working again

SYMTOM: Error IPV4 ADDRESS: NOT SET at console and tower unreachable through network. WHEN: After boot-up, after changing the flash device using the USB creator tool (for Linux, in my case). USE CASE: Using static IP address, outside of router's DHCP range (as before changing flash device). SOLUTION: At console, navigate to /boot/config, edit the network.cfg file with nano, reboot. WHAT TO EDIT: Remove the parts marked red below.   # Generated settings: USE_DHCP="no" IPA

I was on 6.12.10 upgraded to 6.12.11 NFS mounts broke in Windows 10 downgraded back to .10 everything worked, just upgraded to 1.4 everything broke again, now im going back to .10.   Any ideas?? More info here:     

update to 7 went ok. Now, the array will not start. tower-diagnostics-20241030-1018.zip

Hi,   recently i've been having troubles with my server completely locking up and not being accesible. this has been happening for a while - to try and fix i've upgraded to 7.0, changed docker network from macvlan to ipvlan, and forced the os to stay in ram. To get the server running again I have to hard power off the server and for some reason the usb boot drive isnt recognised unless i unplug then replug it. (maybe theres a problem there?)   Heres the syslog fo

When trying to clone a VM, i get the following error:     i checked if it has anything to do with the ":" or "_" in the name, but the error is the same for any VM cloning.  The XML creation works.   is there any obvious thing i am not seeing? Is it because im using a non-standard path? (domains_secondary?)   matthome-diagnostics-20250212-2053.zip

Hi,   I'm managing docker with Portainer (because I prefer compose files) and container updates with watchtower. This works perfectly. I do still use the Unraid interface by specifying net.unraid.docker.icon and net.unraid.docker.webui. Beautiful. If Unraid detects a possible update for a container I get a notification. All good, for all containers. Actually updating containers from Uraid for my containers made with Portainer does not work ending in a "Configuration not found." er

Both my active machines running latest stable give this error in Docker containers. It's makes the GUI of that app completely unusable and it doesn't give me enough clues to know how to fix it. Handbrake and krusader are what I know to be effected but I'd say their a likely lots more. A NodeJS issue seems to be what Google is saying but I lack the knowledge to get much further.   EDIT. Also updating Unraid isn't possible with browsers effected by this. (see recent post)

Hi Lime Tech Team,   I use Unraid in a Mac-only environment with SMB shares formatted in btrfs. From the start I set "Enhanced macOS interoperability" to Yes in the SMB settings. I did not tweak SMB any further manually. The server was running fine until recently. I assume, but am not sure, if my issue is related to the update to version 7.0.0. Since this new version of Unraid contained changes in the macOS interoperability as per the release notes.   My issue: When I copy

I've just upgraded to 7.0.0 and I can't access my Webgui - dockers, VMs, shares etc are all working fine. I just can't get into my Webgui at 192.168.1.1. Any ideas? I've tried searching the forum and I can't find anyone else with the same problem. network.cfg:   # Generated settings: IFNAME[0]="br0" BRNAME[0]="br0" BRSTP[0]="no" BRFD[0]="0" DESCRIPTION[0]="LAN" BRNICS[0]="eth0" PROTOCOL[0]="ipv4" USE_DHCP[0]="no" IPADDR[0]="192.168.1.1" NETMASK[0]="255.255.255.0" GATEWAY[0]="192.1

When play with jellyfin with transcode, the system dies, i have to restart the computer, try multi times with the same issue. When i downgrade to 6, everything works fine   Feb 10 22:40:27 HomeCloud kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks Feb 10 22:40:27 HomeCloud kernel: ACPI: Early table checksum verification disabled Feb 10 22:40:27 HomeCloud kernel: xor: measuring software checksum speed Feb 10 22:4

Not sure where to start....really regret upgrading. Everything has been unstable since November. Freezing and crashes, hard crashes. Can't gracefully shutdown, endless parity checks. Lost a disk because of it. replaced it, rebuilt it, still issues. NginxProxyManager wasn't helping either, starting having issues after upgrade as well. Crash/freezing occurring 2-3 times a week. Hesitant to downgrade. Help me server2-diagnostics-20250210_1527.zip

I recently added a vdev to my 7.0.0 zfs pool. After adding I inspected the pool information to find this.   raidz1-5 being the new vdev fyi. I'm not sure that this presents a real issue long term, but it seems like whatever script creates the new vdev automatically is expecting the array to start at 1 and the one that created the initial array starts at 0. Now I have no 4. Should this change in the future it may break expansion? It seems like its not possible to rename vdevs. Hop