Stable Releases

I don`t know what problems happend after I update to 6.12.3.The snapshot and diagnostics file is below.Thanks! update:After a while the server crashed.   unraid-diagnostics-20230829-1044.zip

Hi, my server has been acting strange for months, freezing at random when there is any greater write activity. I haven't been able to narrow this down to the SSDs until now. The wear leveling count for both drives is 1 (1% life remaining), and the LBAs written equal almost 5x the rated TBW for a Samsung 860 EVO! One of the drives even had a CRC error count of 6. How come there is no notification about this state? I'm receiving notifications about parity checks just fine. This is either a huge bu

Originally posted on r/unraid but realized this is a better place.   I stumbled on this today. Maybe someone here has seen this before? I found a way to get files stranded on a cache pool.   My setup: 2 cache pools: One is named `app_data_cache` and it has a single share, `appdata` that has cache set to Prefer and assigned to the `app_data_cache` pool. One is named `cache` and has a share named `Backups` and has cache set to Yes and assigned to the `cache` pool.  

I suddenly have the problem that i can not access the VM pages on my unraid server anymore. Neither the VM page nor the VM settings page are accessible.   the logs state  Aug 26 03:09:30 Server nginx: 2023/08/26 03:09:30 [error] 7827#7827: *298579 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.10.100.31, server: , request: "GET /Main HTTP/1.1", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock",

Description: The diagnostics zip files created using the "Anonymize Diagnostics" option in the UI still contain the public facing IPv6 address, which can be used to roughly geolocate users or gather lists of unraid hosts on the internet, scan them to find exposed services and so on.   In the dhcplog.txt is a line like "eth0: adding address 2a02:9...." and " Registering new address record for ..." in the syslog.txt. Since with ipv6 there is no nat and instead all addresses are dire

I am unable to mount my ZFS pool, starting the array in Maintenance mode work. Running in safemode sometimes work. My system has been less stable since upgrading to 6.12.x, but has improved since I changed docker to use ipvlan. Things were running well until yesterday, the system took a hard crash and have been unable to mount the ZFS shares since.   The diagnostic tool did not grab my entire log file, so I manually added it to the zip.   Jul  7 02:07:24 MCP emhttpd: mounting

In previous versions of UNRAID the /usr and part of the /lib folder were a part of the root filesystem / and in the process were never unmounted because the root filesystem / persisted in RAM throughout the shutdown sequence in /etc/rc.d/rc.6. This also meant that all the binaries in /usr/sbin and /usr/local/sbin were available to the services until the system halted entirely, ensuring - for example - plugins could also run their respective shutdown sequences gracefully by utilizing their binari

Hello team. Minor issue but figured I would post. Sure there is a fix. The Dashboard tab "Unassigned devices" list has not updated.  I changed the name of an unassigned device and it is correct on the Main tab. I do not believe I have rebooted the server since the rename either. Attaching a screen capture of each tab showing "dev 1" and "D3-S4510" which is what I renamed it to. I set the device name a couple days ago. Grabbed a copy of the diag file as well.  

Happened 3 times over 2 weeks following upgrade to 6.12.3.  Previously ran with 6months uptime before upgrading Symptoms : I have a Docker instance running PiHole.  The first indication is the DNS entries stop resolving as this Docker container crashes. If I'm quick I can get onto the WebUI and see 1 x CPU core at 100% (Intel® Xeon® CPU E3-1226 v3 @ 3.30GHz - 4 cores) As soon as I try to stop the array etc the rest of the cores follow until the server becomes unresponsive

Unraid needs updated btrfs progs for v6.2.2+   root@redacted:~# btrfs version btrfs-progs v6.2.1 root@redacted:~# btrfs dev stats /mnt/cache [/dev/sdg1].write_io_errs 0 [/dev/sdg1].read_io_errs 0 [/dev/sdg1].flush_io_errs 0 [/dev/sdg1].corruption_errs 4 [/dev/sdg1].generation_errs 0 [/dev/sdf1].write_io_errs 0 [/dev/sdf1].read_io_errs 0 [/dev/sdf1].flush_io_errs 0 [/dev/sdf1].corruption_errs 4 [/dev/sdf1].generation_errs 0 root@redacted:~# btrfs dev stats -T /mnt/

looking at logs, i see smbd core'd a few days ago (it then auto recovered). i never noticed anything on my side. just noting logs here in case others have seen   Aug 19 20:30:27 husky smbd[15075]: [2023/08/19 20:30:27.828234, 0] ../../source3/smbd/close.c:1397(close_directory) Aug 19 20:30:27 husky smbd[15075]: close_directory: Could not get share mode lock for TV/Foundation 2021 Aug 19 20:30:27 husky smbd[15075]: [2023/08/19 20:30:27.828285, 0] ../../source3/smbd/fd_handle.c:39(fd_h

When publishing a docker container's ports from a bridge network, the syntax 192.168.2.10:8443 can be used instead of 8443 if you want the port published only by a specific IP address on the server. This works as expected. However, the Docker GUI will incorrectly list Unraid's IP address on the port mappings list, regardless of what IP address is actually use by the container.   The above in only a minor GUI reporting issue, everything works as expected despite the incorrect mapping in

Windows 10 w/ Firefox 114.0.1   The notifications menu dropdown causes horz scrollbar, and you can see is slightly misaligned    

I am running Unraid 6.12.3 with a Windows 10 VM. I have qBittorrent running on the VM for downloads. It's been running fine for a while and just recently I started getting errors on my downloads stating it couldn't write because the disk was out of space. I had 1.76TB free on the array. The issue ended up being the allocation method for the shares. I Had it using "Fill-up" which up until recently was working fine by filling up one drive and moving to the next but this week it stopped doing that

Hi, Server just stopped working,.. i guess eth0 stoped working. I wasn't able to ping the Server anymore or login via Gui. Same from the Server directly, i was able to login with an attached Screen and Keyboard. Same here.. not able to Ping.    Here is the Syslog and Diganostics for you. let me know if i can provide anything else ?   best regards  syslog.txt stevenas-diagnostics-20230816-0952.zip

upgrade to 6.12.3, then can cann't startup, cann't open webgui, no nginx process,no docker process....... what should i do ?     Jul 17 11:11:13 Tower rpc.statd[3499]: Version 2.6.2 starting Jul 17 11:11:13 Tower rpc.statd[3501]: Version 2.6.2 starting Jul 17 11:11:13 Tower sm-notify[3502]: Version 2.6.2 starting Jul 17 11:11:13 Tower sm-notify[3500]: Version 2.6.2 starting Jul 17 11:11:13 Tower sm-notify[3500]: Already notifying clients; Exiting! Jul 17 11:11:13 Tower rpc.statd[349

As this post points that    The docker script will use $IPV6(2409:xxxx:xxxx:5ee0::4b8/128) to get $SUBNET6(2409:xxxx:xxxx:5ee0::/64) via ip -6 route show dev $NETWORK $IPV6|awk '{print $1;exit}' It will case $SUBNET6 be null, and $GATEWAY6 always be 1 —— So that it leads to br0: ipv6 is disabled in docker network inspect.    

Premise: - I am using Tailscale to access my Unraid server (UI, SMB, SSH, everything) - I have no access to real hardware. I am in a different country. - I have upgraded to 6.12. - After reboot I lost access to my Unraid server. I don't know how to get access back.   Description:   After I went to Unraid UI, I saw that there is a new version and I decided to upgrade as I am doing often. After server reboot I could not access my server anymore.  

UGREEN USB Network Adapter appears in System Devices but not in Network Settings to configure. I did see it show up in Network Settings in 6.11.5 but after upgrading it disappeared. Thank you. Amazon link Chip link UGREEN link   How to reproduce: 1. Plug in adapter in USB port 2. Start Unraid server 3. Adapter appears in System Devices but not Network Settings lucifer-diagnostics-20230704-2354.zip

I suggest moving the words "Cache" and "Array" and keeping the arrows pointing in the same direction "->"   Current design:   Suggested design:

Using Chrome: Version 115.0.5790.172 (Official Build) (64-bit) Edge: Version 115.0.1901.200 (Official build) (64-bit) Checked Win 7, Chrome Version 115.0.1901.200 (Official build) (64-bit), works as expected. Left is Chrome Desktop, right is Android (BlueStacks)   tnas-diagnostics-20230810-2253.zip

I switched from an onboard 10g aquantia nic that was failing to a Mellanox ConnectX-3 card yesterday.  The Aqua nice was ethernet to SFP+, the ConnectX card is SFP+ to SFP+.  The ConnectX card is in ethernet mode and fully updated.  It works, unraid sees it, and it can connect to my other servers on the network.  The issue is myunraid wont connect, Wiregaurd wont connect, and I deleted the SSL cert from the management access section and tried to reprovision it, but it fails to reprovision.

I posted this in general support and didn't get any response can someone assist please?   "Your server has detected hardware errors. You should install mcelog via the NerdPack plugin, post your diagnostics and ask for assistance on the Unraid forums. The output of mcelog (if installed) has been logged" tower-diagnostics-20230802-0912 (1).zip

I'm attempting to migrate my encrypted btrfs formatted cache pool to an encrypted zfs formatted pool, but it fails when I attempt to format the drives after starting the array. It will format an unencrypted pool just fine but if I attempt to format either an encrypted btrfs or zfs pool it fails, reporting that the pool is unmountable. I am attempting this with a 4MB keyfile. unraid-diagnostics-20230805-1711.zip

I can't figure out what's using avahi-daemon but it just eats up all RAM until the process is killed.   Any ideas how to fix this? I'm on 6.11.5 since 6.12 just locks up my system and is unuseable   CPU: 0 PID: 10324 Comm: avahi-daemon Tainted: P O 5.19.17-Unraid #2 Call Trace:   kernel: out_of_memory+0x3e8/0x41a kernel: Out of memory: Killed process 10324 (avahi-daemon) total-vm:62465396kB, anon-rss:62460352kB, file-rss:4kB, shmem-rss:2868kB, UID:61 pgtables:1