Stable Releases

unraid 6.12.6 Mar  7 07:56:48 unRAID kernel: ------------[ cut here ]------------ Mar  7 07:56:48 unRAID kernel: WARNING: CPU: 0 PID: 27381 at net/netfilter/nf_nat_core.c:594 nf_nat_setup_info+0x8c/0x7d1 [nf_nat] Mar  7 07:56:48 unRAID kernel: Modules linked in: macvlan xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle ip6table_nat iptable_mangle vhost_net tun vhost vhost_iotlb tap veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_a

So I just updated for 6.12.6 to 6.12.8, and now when I run or resume a parity check the GUI locks up especially the Dashboard Tab. If I am on any other tab then they work, but if I click the Dashboard tab then it does not populate, if I then click on main (Or any other tab), it take like 2 mins for that tab to populate, but once it populates I can click on any tab without issue (Except the Dashboard Tab)   If I stop the parity check or pause the parity check, and wait 5 mins then all t

My server was rebooted unexpectedly, as I found I had to log in and start the array this morning.  I suspect this may have something to do with the Appdata Backup plugin as well, which I have scheduled to do updates every Monday morning, and this was the first time that scheduled job would have triggered since I updated my OS to Unraid 6.12.8.  I also see from the Appdata Backup logs that it tried (and failed) to backup/update the docker images.   I'm not able to delete containers with

Today I accidentally removed a drive from it's bay while my server was running (turns out that bay's power light doesn't work, oops).   Wouldn't have been a big deal, except when I reinserted it, it was detected as a separate device (/dev/sdq instead of /dev/sdj).   I went to stop the array to fix this, but the stop array button in the GUI is broken now. This is logged when I click "proceed" to stop the array: Mar 4 16:33:51 Global-Dynamics nginx: 2024/03/04 16:33:51 [err

As usual, I was greeted this morning with some container updates. Rather than update all automatically, I checked to see if any were in use, containers like postgres, apps that you don't want shutdown if someone is working with it.   I updated NPM, Vaultwarden and PHPMyAdmin, one by one as needed. Once I go to the less important containers, I clicked the Update All button.   That process went and tried to update containers I already updated. It tried to DL the images, realize

It looks like the "Update All" button caches the Docker state at page load and uses that cache to determine which containers need to be updated. It should actually be fetching the current configuration at the moment you press the button.   This results in: Containers being "updated" when they're already up to date, causing service interruption related bug report from March 2023 Deleted containers being recreated   How to recreate: W

I made the mistake of upgrading while not being physically near my server from 6.11.4(I think it was .4)->6.12.4 a couple months ago, and since then I have been experiencing random system hang/crashing. It starts with me being notified by my UptimeKuma my websites crashed, and when I navigate to the Unraid GUI, it never resolves and then says page timed out. I check my KVM and the console is still booted up awaiting a CLI login input. When I tell the KVM to send a short power button

After upgrade, starting the vm shows a strange behavior on Unraid dashboard of pegging all cores/threads assigned to it.  Vm is not accessible via rdp and the plex server that starts automatically in windows vm is not accessible from any plex clients.  The vm is set up to use gpu passthrough. Downgrading results in the vm running normally. tower-diagnostics-20240217_0716.zip

Hi, Last week, I updated my server to the latest version, but it's been crashing randomly ever since. Last night, I tried disabling most of the containers and only kept a few running, but the server still crashed."   I enabled SysLog server setting and attached syslog file from the USB drive. Also, I attached diagnostics file from 2/19. This server has been running smoothly for the last five years until the latest upgrade. I updated all plugins and installed Docker patch

good morning, I have an old computer, I would like to upgrade from the current 6.9.2 to the latest one, but after the upgrade, the array does not start, after a couple of attempts, everything reboots. Do I have any hope or do I change hardware? thanks   Model: Custom M/B: Intel Corporation DQ77MK Version AAG39642-500 - s/n: BTMK308004RB BIOS: Intel Corp. Version MKQ7710H.86A.0074.2018.1025.1727. Dated: 10/25/2018 CPU: Intel® Core™ i5-3550 CPU @ 3.30GHz HVM: Enabled

Recently, I have been dealing with very high RAM usage on my Unraid server, without a clear cause to pin it down to. When all my docker containers and VMs are running, I'm getting as high as 28 out of 32 GBs of RAM. After shutting down all containers and VMs and disabling both docker and VM support in settings, the system still reports 20GB used:   root@home-server:~# free -h total used free shared buff/cache available Mem: 30Gi 20Gi

Webui was inaccessible (Fixed with two commands: nginx -s start & /etc/rc.d/rc.php-fpm restart) All my dockers were removed, it says no docker installed. Community App store was not working said socket could not be created. antoniii-diagnostics-20240228_0610.zip

Basically the title.   I added a L2ARC cache to my ZFS-disk in the array (zpool add [pool name] cache [disk identifier])   Upon restarting the array, the disk goes unmountable.   Removing the cache disk fixes the issue (zpool remove [pool name] [device name])

I'm having this same issue and tried posting in this thread, but couldn't, so figured I'd post in a separate bug report thread since I don't see one posted for this issue:   I upgraded to 6.12.8 and the Web UI became almost unusable with how slow it was. After finding the above thread, I was able to confirm I was in the same boat with special characters in both the Description and Model fields for my server. After emptying those fields out, the Web UI became snappy and operated normal

Hey there,   basically 6.12.4 is the last version where I can reach C10 with my I5 13500. All versions above only allow C2. Nothing changed only the upgrade of Unraid. Is this issue known?

After restarting the machine, if Docker is not started, everything will be stable. However, when I started Docker, my Weiui crashed. This issue not only occurred in version 6.12.8, but also in version 6.12.6. The sensitive operations I have carried out are as follows: Enable automatic acquisition of IPv6 Updated all plugins Using the NerdTools plugin One of my hard drives is 100% full, and the remaining data is currently stored on the disk.   taor-unraid-diagnostics-20240221-23

Description: Upon upgrading my home NAS from Unraid 6.12.6 to Unraid 6.12.8, my server lost all network connectivity, and I was unable to ping the network interface.  Rebooting into safe mode didn't resolve the issue. I also upgraded the linux kernel back to 6.7.3 (latest stable from thor), which I was using to provide proper support to the Intel GPU in the server.  That did not resolve the issue either. Digging further, I discovered that the ethernet interfaces weren't being bond

Today at 16:23, a scheduled disk scan in Sonarr reported that over 850 episodes of TV shows had disappeared from my system without warning.   There are no log entries at that time that would indicate anything had gone wrong. Feb 25 16:05:50 Global-Dynamics sshd[24685]: Accepted publickey for root from 192.168.0.2 port 51256 ssh2: ED25519 SHA256:5b6Ebu2l2lANTclMchJAJk4XviWfjlgDJt7ngCuXszc Feb 25 16:05:50 Global-Dynamics sshd[24685]: Received disconnect from 192.168.0.2 port 512

One of the recent updates to Unraid updated the kernel version, causing this error to appear (more on that in a second).   I am running a Intel 12600k, utilizing Quicksync for hardware encoding within Jellyfin. Up until recently, this was working fine for transcoding 4k down to any other resolution. With a recent update to Unraid, this is now broken. See this jellyfin github conversation for more information on the details of the issue, as well as the likely cause.   I am cur

Can we have a way to update USB sticks without having to use the stick for the temp download storage?   Something's changed about the update process. Currently on 6.12.6 & attempting to go to 6.12.8   There's a .git folder on the usb stick that is 1.25GB.   Unraid runs in ram I have 128GB... why is the update being saving to my USB stick? Then processed.       My stick is an industrial 2GB stick..   Also it says 512MB usb stick is o

Hello, My array was fine this morning and I came back tonight and the parity drive now shows as stopped:     Trying to spin it up doesn't do anything (the icon remains as is). The server logs only show this:   Feb 21 18:52:15 Tower emhttpd: spinning down /dev/sda Feb 21 18:52:22 Tower emhttpd: spinning up /dev/sda Feb 21 18:52:29 Tower emhttpd: read SMART /dev/sda Feb 21 19:12:33 Tower emhttpd: spinning down /dev/sda Feb 21 19:12:35 Tower emhttpd: spinning up /d

I'm getting out of memory crashes with 6.12.8 and had the same issue on 6.12.7-rc2. Unfortunately I haven't had time to dig deeper until now.   Syslog isn't reporting anything interesting but I've attached the diagnostics.   I think the issue is being caused by the web ui. I managed to get a couple of screenshots from htop just before the system crashed. m33-nas-01-diagnostics-20240221-1244.zip

After upgrade my main zfs SSD pool does not start automatically. However using pool import – a in console does work correctly. I checked unraid still has correct device names against those listed against the functioning pool pool list -a and that part of it is correct. I'm trying a downgrade to see if it comes right but just noting this here in case anyone else comes across it.skywalker-diagnostics-20240222_2054.zip

Hi, new user here. I've been using Unraid trial for a week, I've setup everything I need as in disks and docker containers, paths, everything. Everything was working good. Yesterday I bought a Basic license and updated from 6.12.6 to 6.12.8.   I noticed that all of my containers are "gone" and the docker settings are reset.   Re-enabling docker and setting the correct paths for the vDisk and appdata restored everything, but I was still nervous for a bit, because I spent a cou

Hello, I upgraded to 6.10.3 from 6.9.2 and lost reverse proxy access to my shinobi docker.  Other reverse proxies (Nextcloud and Emby) work fine.  Shinobi uses a custom IP in a vlan.  I restored 6.9.2 and it works fine.   thanks, tower-diagnostics-20220921-1712.zip