Stable Releases

I have a ZFS pool created via steini84's plugin. I remember I've follow the suggestion to enable the compression as lz4, like:   zfs set compression=lz4 myzpool   And I also remember I've ever confirmed this compression setting not long before. But today after I've imported my ZFS pool, I found the compression is shown as "off", no matter on the webUI or with command zfs get compression myzpool. Then I use the above set compression command again, and later I try get compressi

hi just wanted to x-post from    to put it in the appropriate section, in the hopes of limetech putting priority towards fixing this bug.   I could copy / paste all the messages I wrote from the thread above but it seems needlessly redundant. In summary SMB performance on unraid sucks, is significantly worse than any other implementation by any other provider and all the tests mentioned in that thread can be repeated / are easily verifiable.     SMB to u

Hello,    I am running v6.11.5 on a gen9 HPE dl380 with multiple spinning and ssd drives and 128gb of ecc ram.    In the last month or so I have noticed that I can't check plugins for updates, and community apps are unavailable due to the server not being able to reach git hub. When these issues pop up i see the following error on every page on the web interface    Warning: file_put_contents(): Only -1 of 127 bytes written, possibly out of free disk space in /usr/lo

Meanwhile in reality:     Is it I something doing wrong, or this is a bug form a new version? I didn't receive this alert before and panel didn't show such big memory usage. Only after 6.12.1 upgrade.  

I went from 6.11.5 ro 6.12.0 a few days ago (before the 6.12.1 hit). Now my webui won't start, not remotely nor on localhost. I tried to restore from a backup to a new usb-stick. I also run my router inside a VM on this machine, where i passthrough a NIC.   I'm not sure what is wrong. Any ideas from someone?   from what I can glance, this might be relevant?     changeme-diagnostics-20230622-1618.zip

i have upgradede from 6.12.0 to 6.12.1 and now i cannot re-arrange dockers in the "Docker" tab anymore. no errors in log. 

Built a brand new unRAID setup a month ago on 6.11.5. Rock solid, never had any issues. I upgraded to 6.12 RC over the weekend and had at least 2 instances of the server completely being unresponsive. Until then, 6.11.5 had a runtime of 14 days with no issues.   Within 24 hours of upgrading to 6.12 RC, my server became completely unresponsive. I could not log into the web UI, could not access any shares via macOS Finder and the monitor connected to my server had no input. Weird. I hard

Hello,   After the update I noticed my syslog started filling up extremely fast with several many instances of the bellow message:   Jun 23 12:44:09 Tower01 kernel: pci 0000:05:00.0: device [10ec:b822] error status/mask=00000001/00006000 Jun 23 12:44:09 Tower01 kernel: pci 0000:05:00.0: [ 0] RxErr Jun 23 12:44:09 Tower01 kernel: pcieport 0000:00:1c.2: AER: Multiple Corrected error received: 0000:05:00.0 Jun 23 12:44:09 Tower01 kernel: pci 0000:05:00.0: PCI

The arrows to allow re-ordering docker boot order have disappeared. Some dockers have dependencies and must boot in a specific order.

I updated this morning around 10am EST to 6.12.1   The server is been halting every so often. I can send diagnostic report later when it becomes responsive.   The attached screen to the server has this message:    BUG: Bad rss counter state mm:000000008897cd45 type:HM_ANONPAGES val:1    

Good Afternoon,   I'll have to downgrade (which worked from 12.0), but the share drives will not show up and compute at 0 bytes. When the raid finally comes up, it will still say 0 bytes but on the front everything looks normal. Basically app data and everything else is offline in a sort. I attached the logs also. tower-diagnostics-20230620-1552.zip   Update: I downgraded back to 6.11.5 again from 12.1 and everything works fine. I attached logs for 6.11.5 (which everything is

Sorry for the "light report", but I cannot replicate and provide diagnostics at this time. I have 3 Unraid servers, and I have migrated 2 to 6.12 so far. On both of those migrated servers, I experienced a loss of internet access (LAN works just fine) 3 or 4 mins after the array start; it is hard to diagnose the why because the situation doesn't leave any traces on the logs or diagnostics files as far as I was able to check.   By trial and error, I have come to the conclusion that the c

On my Mac I have this app called AutoMounter. It has an option "Mount using Bonjour". This is how it's been set forever. If I uncheck the option the SMB shares mount successfully. If it's set it gives the error "Bonjour Not Available". I checked the share.cfg file and avahi is enabled. Not sure what happened to avahi in 6.12? unraid-diagnostics-20230621-1029.zip

The DockerSettings.page looks for a running process called dockerd.   <? // Add the Docker JSON client require_once "$docroot/plugins/dynamix.docker.manager/include/DockerClient.php"; $DockerClient = new DockerClient(); $DockerStopped = pgrep('dockerd')===false; function strposX($s, $c, $n=1) { Not only does it determine if Docker is running on Unraid itself, but it also finds the second Docker daemon running in LXC. I would suggest checking if the Docker socket is availa

When creating a ZFS dataset on a zfs-pool, ether with ZFS-Master plugin or terminal, the share that is created sets primary storage to "array" instead of said pool. Its been like this since the first beta/rc with zfs support  as far as I know. Not sure if this is considered a bug or by design as Im sure the "propper" way to create a dataset is from the "share" tab

The Issue: Creating a ZFS formatted cache pool with two disks mirrored was not possible. Following the standard steps of setting up the pool, assigning two disks, and formatting them resulted in the format failing.  The format fails as the disks remain unmounted and Unraid suggests to format them, despite just pressing the format button. This was very consistent - attempt multiple times, preclear the disks and try again, fails. Delete the pool and reset it up, try again, same failure. Restart th

Hey there when i shutdown unraid it does not do a clean shutdown, but waits forever.     Last command issued is: "Starting diagnostics collection..." and stays  there forever (at least i waited 10 minutes until i hard reset the machine).   When i run the diagnostics  through cli the file is created fairly fast after some seconds.

Currently my array is kind of always on and spins up even if manually spun down. When i spin them down it only takes several seconds until they spin up again.   I can not find any reason why they wake up, File Activity plugin does not show anything, grep around with lsof on the terminal does not show anything.   I tested with : - VM Manager disabled - docker container disabled. - smb disabled (no other share system has been enabled) - Most of the

6.12 - Minor annoying thing the dashboard layout changes when logging in via the SSL carted 131i31i4114.myunraid.net address.   Customised layout show with plain ip address or the . local address     Standard layout loads if you use the 10947w47.myunraid.net  

If I revert back to 6.11.5 they are there but not in 6.12 cd1git-unraid-diagnostics-20230615-1314.zip

After update on 6.12 app store and dockerhub version information stopped working. I checked the usual suspects and found out that my server time was stuck at 2002.   I'm using ntp with the pool: pool.ntp.org I disabled ntp and enabled it again, without a change. I rebooted the server without a change. I changed the ntp address to plain ipv4 addresses instead of dns without a change.   [Temporary solution] Only manualy syncing ntp on the command line w

It runs well for a few hours, then randomly, it starts to overload cpu till it finally crashes   Reverting meanwhile to 6.11.5   Testing 6.12.1 and added (i5 11400):   echo "options i915 enable_dc=0" >> /boot/config/modprobe.d/i915.conf   I will post if it keeps crashing or not.   Diagnostics attached diagnostics-20230620-1925.zip

I had Unraid up and running on 6.11.5 with "Intel Corporation Ethernet Connection X553 10 GbE SFP+ (rev 11)" with driver ixgbe. After upgrade to 6.12.0, the SFP+ ports cannot connect. I have reverted to 6.11.5 and the SFP+ ports work there but not in 6.12.0. The diagnostics file is attached. aamarunraid-diagnostics-20230617-2340.zip

Thank you for (hopefully) fixing the issue with reapperaing notifications.   I very much dislike having to go into 3 separate sub-menus to clear my new notifications.   Is there a way to turn off this autoclosing behaviour? i can't see anything within notification settings mentioning it.

I noticed the system has lots of IO-Wait in htop while it was basically idle. Syslog showed the following entry Jun 18 17:00:29 Tower kernel: traps: lsof[29400] general protection fault ip:1529d3557c6e sp:d95a8f1327ed4ec2 error:0 in libc-2.37.so[1529d353f000+169000]