Stable Releases

Upgrade failed and second attempts will not go through.  My other server worked.       plugin: updating: unRAIDServer.plg plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.8.1-x86_64.zip ... done plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.8.1-x86_64.md5 ... done writing flash device - please wait... Archive: /tmp/unRAIDServer.zip plugin: run failed: /bin/bash retval: 1

after 6.8.1 update fail2ban failed to start:   root@Tower:/custom/fail2ban-0.11.1# /etc/rc.d/rc.fail2ban start Starting fail2ban: ERROR:root:code for hash md5 was not found. Traceback (most recent call last): File "/usr/lib64/python2.7/hashlib.py", line 139, in <module> globals()[__func_name] = __get_hash(__func_name) File "/usr/lib64/python2.7/hashlib.py", line 91, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported h

I have a line in the go file to run a .sh file to set up rsync between unraid servers.  After upgrading to 6.8.0, this stopped working.  I opened a terminal into the source server and tried to run the .sh file by itself.  I get a permission denied message.  There are no related messages in the syslog.  I also logged into the server using putty, logging in as root, and got the same errors. I had to fall back to the previous release (6.7.2) where this is again working fine.   As an

Just woke up to a crashed system, different effect then the last time (See previous post below)   Diagnostics are attached.     Last error in the log was:   Jan 5 06:20:19 Tower shfs: fuse internal error: unable to unhash node: 562319961 Jan 5 06:20:19 Tower shfs: fuse internal error: unable to unhash node: 562319961 Where in previous cases the errors made the total system unavailable now the webinterface is still running but there are no exported shar

In my Unraid box I used to have an SSD cache disk. Some months back I removed the cache disk from cache duty, let it be mounted as just a disk directly on the filesystem. Ostensibly at this point I left cache enabled, just with no disks, mover still appears to be scheduled to run. Everything has been fine with the server for all these months. Then a week back I upgraded to 6.8.0 and it started randomly crashing ~an hour after booting, completely unresponsive over the network. I didn't even reall

Unraid version: 6.8.0 stable   Bug replication: 1- Create a user, user1 2- Create a second user, user2 3- In unraid webGUI, Users-->user1, or Users-->user2, user access for domains and system folders is set to "No access" 4- In unraid webGUI, Users-->user1, change user access for domains and system folders to read/write and apply: settings are correctly saved and service restarted 5- In unraid webGUI, go back to Users 6- Enter user1 7- Change

Important: please upgrade to the latest available stable release first, and if the bug/defect still exists please continue...   In the Summary: field, please put the exact version of unRAID OS you are running inside brackets.  For example: [6.2.1] <your topic>   In Detailed Description please include as much information as possible in your report, including HOW TO REPRODUCE.   Please visit Tools/Diagnostics and attach the diagnostics.zip file to your post.

I'm doing nothing   tower-diagnostics-20200106-2253.zip tower-syslog-20200106-1449.zip

When "Primary vDisk Location:" is set Manually to a vdisk image it is preserved in the XML file but it is not preserved in the Form view after leaving the VM and checking into Edit again. Then it is always showing "Auto" and the autopath wich is not the one used by the VM. The manually set and used path is correctly shown in the XML form though.   This is confusing.

Hi all,   Finally decided to transition my MacOS Devices from AFP to SMB connections and I'm noticing randomly disappearing folders after they've been connected for awhile (usually about 6-12 hrs the folders start to disappear). It tends to happen more on shares with larger file counts, but it's basically making SMB unusable for my use case where I'm serving media files via Plex (on a Mac, not docker).    I'm going to try to disable SMB Cache enumeration, but that shouldn't a

I recently exchanged one of my cache disks from a Samsung EVO 850 500GB to a nvme 1TB Samsung EVO 860. The first issue I noticed was that none of the docker containers worked as it seems that the docker.img file became read only while doing the initial replace (You probably understand better what happened from the log). Should the mounting of docker.img maybe wait until device replacement is finished? Anyway, that is not the main issue I wanted to report, and it was fixed by stopping and st

I ran the update from the GUI, got a "run failed" message and then I clicked done. The entire GUI then switched to a white theme, my dockers tab disappeared and I no longer had access to community apps. I figured a restart would resolve the issue; it did not.   I am no longer able to boot UnRaid, boot stops at: ret_from_fork+0x35/0x40 --- [ end trace a12f838edfbe4353 ]--- Been trying to get this to work for hours. Any help would be great, thanks in advance!

I decided to just look through the entire diagnostics file to check if it really is anonymous.    It is not: if the "mover" logging is enabled, it will write the entire move with path and filename into the syslog and the diagnostic does NOT anonymize this data.    Quoted from the diagnostic page:   Yes, it says it will backup the syslog - but I expected it to run through an anonymize filter first.   This is a serious security flaw for the users, not good

Hey, I have weird issues when I copy files over my SMB shares. Often one or more cores stuck at 100% and the file transfer will stop for a while and will go on for 5-10 seconds until it happens again. I also attached my diagnostics, maybe you can help me.   My hardware is a Ryzen 2700X paired with a X570 Gigabyte Ultra at the latest BIOS version F11. nas-diagnostics-20200102-0224.zip

See the attached screenshot. My Dashboard is showing fan speed instead of motherboard temp.  

All currently supported versions of FreeBSD (11, 12,12.1) do not detect any emulated network interface. I discovered this after upgrading from FreeBSD 11.2 to 11.3. Rolling back restores network interface.    I have reproduced the issue by downloading the installer ISO for 11.2, 11.3, 12, 12.1, and creating new VMs. ONLY the 11.2 installer is able to detect a network interface.   Q35-3.1 SATA primary vdisk e1000-82545em   I believe something in unRAID need

Last upgraded to 6.8.0 on 12/22/2019.     I can edit the settings on installed (stopped) VM Ubuntu 18.04 and 19.04, works correctly. I can install and run VM Ubuntu 19.10 successfully.   However trying to edit settings on (stopped) Ubuntu 19.10 causes the Unraid GUI to spin forever (buttons stay greyed out, spinner spins forever). After this, the Ubuntu 19.10 VM will not boot, it is stuck at grub screen with no bootable image found.   "Remove VM &

This has been bothering me for a while now....when you create a new container or edit an existing container with a custom network, when trying to add a port mapping, the field 'Container Port' is gone. You'll have to switch to 'Bridge', add the port, switch back to your custom network. Is it a bug or some strange feature?

When changing SMB User Access rights through the menu:  SETTINGS/Users for any SMB Users all the other SMB Users Access rights will be reset to "No Access" and only the last one that was changed will remain as intended. The error could quite easily be reproduced.   However if you go throught the SHARES menu and click on any of the particular User SHARES and type in the access Rights for the Users for that particular SHARE it seem to keep all the other USER Access rights.  

If you use any custom theme, or simply rename a stock theme, ui elements get broken on the syslinux configuration page.   This is easily reproducible with the following: cp /usr/local/emhttp/plugins/dynamix/styles/default-white.css /usr/local/emhttp/plugins/dynamix/styles/default-test.css cp /usr/local/emhttp/plugins/dynamix/styles/dynamix-white.css /usr/local/emhttp/plugins/dynamix/styles/dynamix-test.css   Select "Test" theme from Display Settings. Navigate to you

I upgraded a server running 6.4.2 to 6.8.0. I did a manual upgrade copying all files except for the config folder. There server boots and works fine except for the web UI. When i login in all I get is the top banner stating the version and up time. The gray bar below is empty and there is nothing else on the page. Chrome has asked me multiple times to translate the page?!

After several days of finally figuring out how to install VMs in 6.8 last night (separate thread), all of the VM's which were running fine last night now throw the following error:   noVNC encountered an error:   SyntaxError: import not found: supportsImageMetadata http://192.168.0.250/plugins/dynamix.vm.manager/novnc/core/display.js:11:9 noVNC   Diagnostics attached.   tower-diagnostics-20191217-0643.zip

Im losing one container after another on auto updates. I just found out about it today.   /usr/bin/docker: links are only supported for user-defined networks. See '/usr/bin/docker run --help'. The command failed.   I don't want to generate a network for  a mysql machine where all the container accessing this machine are in the same network and also do not really like the cli way of adding custom networks. This is why i liked the linking.   Is there another w

Updated to Unraid 6.8.0 and when I tried to log in root didn't recognize my password. I tried to reset password via removing drive, looking for config/shadow config/smbpasswd and deleting it. Shadow config folder didn't exist but I found smbpasswd in the config directory and removed it. But when I try to log in with just root and no password it is saying I can't leave that field empty.