Stable Releases

I've noticed this issue since 6.9 RC1. The issue was not present in 6.8x   When I reboot the server, the docker containers that have network set to br0 will not auto start. If I try to manually start the affected docker containers, I will get an error "Execution error no such container."   Any applications that have network settings to "host" or "bridge" auto start without issue. The only way I can get the docker containers that have network set to br0 to start, is to go

For reference, 6.9 rc2, admittedly on different server

This issue is still happening as per rc2.   I have installed doron's SAS plugin to standardise on the approach rather than using my own sdspin and versions of smartctl.   Connecting a USB flash drive causes the parity drive(in my case) to spin up. But the ball stays grey and Unraid thinks it is spin spun down but it isn't. sdf is the parity drive, and sdl is the new usb stick plugged in.   All other drives stay spun down.   In UA dev2 gets missed out for s

The NVIDIA plugin broke after the installation of 6.9.1.   I can't reinstall it either.

After a couple of days of mucking about I was able to update 6.8.3 to 6.9. Pretty proud of myself :-)   I am now running 6.9 although without my 10GB card functioning. I am running on a bond with my 10GB in it together with two 1GB connections.   My network speeds are at 1GB level so I safely assume that my 10GB is not active, this is also logical because with -only- that 10GB in use as connection there was no connection at all.   For details on this issue see:

Yes, I save my credentials in my browser. I know that makes me an evil, non-security-minded person. I don't even put passwords on the VNC interface of my VMs. Let's move on. When I'm reconfiguring VMs since updating to the 6.8.x versions of unraid, Chrome's password manager thinks that the VNC Password field is the same field as the main login page password field, and tries to fill in the password. I often don't notice it and end up having to re-edit the VM again because I've started it but

The upgrade from 6.8.3 60 6.9 failed in my case.   The update itself succeeded, reboot worked but the system did not become active on the network. No GUI, no share, no telnet.   - I was able to IPMI into the system and get on console; - The system could ping its own IP address from console but not the default gateway. GUI mode also did not work from console; "page not found"; - Network setup appeared good, correct default gateway and such (ROUTE -N) - The port

Hi, I just updated to 6.9.0 and get a "Boot error" message. I did not want to update, I got the feeling something like this would happen. This is what I've tried so far: Tried to reboot and didn't work. Access the boot menu and tried UEFI, it does nothing and comes back to the boot menu From the boot menu tried USB and get the "Boot error" message   What do I do now?    

Hi,   This error is in my log every second, I don't believe it was there but didn't look at logs to much before updating to UnRAID v6.9.   ErrorWarningSystemArrayLogin Mar 8 11:12:25 Tower emhttpd: error: get_key_info, 579: Invalid argument (22): get_message: /boot/config/BTRS.key (-3) Mar 8 11:12:26 Tower emhttpd: error: get_key_info, 579: Invalid argument (22): get_message: /boot/config/BTRS.key (-3) Mar 8 11:12:27 Tower emhttpd: error: get_key_info, 579: Invali

Hi, after upgradfe from 6.8.3 to 6.9.0 shfs cpu usage is very high, at level of 70-80%. Server is doing very little. How to fix shfs problem, cpu is very hot for these reason? nas-diagnostics-20210307-1020.zip

Hello, Since upgrading to the newest Unraid version I cannot enable Desired MTU / Jumbo Frames 9000 at all. My network on my Unraid server completely brakes even though all my network devices support and work with Jumbo Frames. I have to delete the network config file and revert all my network settings back to default (Desired MTU 1500) in order for my Unraid to reconnect. My network also has Bonding mode 802.3ad (4) enabled.   I stated noticing this issue when I redid my netwo

I'm not sure what's up with 6.9.0, but I have to suspect the update has a driver issue with my RAID controller as all the drives connected to it are suddenly missing. I had to rollback to 6.8.3 to restore my UnRAID server. When I installed 6.9.0, I rebooted and shutdown multiple times, but could not restore the missing drives.  Installed RAID Controller: SUPERMICRO AOC-SAS2LP-MV8 PCI-Express x4 Low Profile SAS RAID Controller I've attached my diagnostics file and would appreciat

After update to 6.9.0, unRaid states all drives have returned to normal utilization after update, even though they're full.   Once all messages were cleared (1 for each drive) a view of the main page shows the correct usages and color (red) of each drive. However, the dashboard displays the correct usage, but the indicators are all in green. This has happened on both my production and backup boxes.         Main Page                                 Dashboard       

after update from 6.8 to 6.9 there is no button "CHECK FOR UPDATES" on plugins-page. (available updates are shown anyway)   on my second rig I updated from 6.9 RC2 to 6.9. Here the button is visible:    

Updated from 6.8.3 to 6.9 and now the webui will not load even locally on the machine. Docker and VM's are working.   any ideas how to roll back via ssh?    

I had [homes] Samba working without issues for several years, (could access \\server\homes, \\server\username)   Now I found that shares stopped working and server writes this message all the time when trying to access these shares: `[homes] share not available for user %s because it was not found or created at session setup time` (https://github.com/samba-team/samba/blob/master/source3/smbd/smb2_tcon.c line 265)   For me it seems like when session is establish

Please have a look at the two screenshots. They show the editor windows of two existing VMs.   The Broadcom devices are marked gray (unavailable) if they are in use.   The USB devices stay available even if in use.   IMHO, the USB devices must be marked gray (unavailable) as well if they are in use.  

As soon as I upgraded to 6.9.0 stable release and restarted my server, the docker Plex would not automatically start.  When I tried to manually start it, a large error window opened stating "Execution Error, Bad Parameter".     This is from my log file:   Setting ini file to /usr/lib/plexmediaserver/Resources/comskip.ini as per commandline Using /usr/lib/plexmediaserver/Resources/comskip.ini for initiation values. Auto selecting the PID. Commercials were found. Plex C

I ran 6.8.3 with never any problem for over a year.   After the upgrade to 6.9.0 that went very smoothly it ran for at least a day without issues.   For the past two nights the system was online but sometime overnight when I come back in the morning I return to a system that is either "powered off" (no sound or anything) or the screen become black, no reaction on keyboard presses and can ping but no responses on the network by http, telnet or ssh    I left a monitor

Thanks for your great job! After upgrading,  I am unable to use the Plugins tab in the web UI. Plugin itself is running, and all the plugins did autostart and are working fine. Attached the System Log and diagnostics.   Mar 2 21:43:01 Abee-EZ300 nginx: 2021/03/02 21:43:01 [error] 6179#6179: *1925 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.88.36, server: , request: "GET /plugins/dynamix.plugin.manager/include/Show

I have this week upgraded from 6.8.3 to 6.9. I have been running 6.83 without any issues forever. As soon as I upgraded to 6.9 I have gotten USB flash errors as soon as I am copying files to the Shares. The whole system hangs up for a few min. The the UI is coming back but it does not read from the USB key and the cache drive is also not detected. I have already replaced my USB key today with a brand new one, but the same happened atower-diagnostics-20210305-1908.zipfterwards. I am not sure what

I add a new bug report because this is a little bit different.   Here Unraid is running within VMs. Funny thing: Two identical VMs, one spins down, the other does not spin down. Both VMs are nearly bare, just two dockers (MakeMKV, MKVToolNix), four plugins (Community Applications, Unassigned Devices, User Scripts, Nerd Tools) are all that is running.   All disks of the two VMs are attached to two LSI 9300-8e HBAs. Backplanes are identical.   VM #1 (TowerVM01): Spins

Hey,    Just wanted to throw this out there in case anyone else runs into it.  Have 2 servers updated one to 6.9.0 everything seemed fine so I updated my primary server as well.  Then noticed I could not access shares either via SMB or dolphin docker.  Also when attempting to reboot/shutdown it just failed and never actually went offline.     Did a bit of research and figured I would look at my go file and see if anything seemed off.  Only stuff in the go file was for server

Write errors across multiple disks since updating to 6.9 Appeared for the first time during the night after installation (see below, logs included in that post)   Then today new errors on another disk leading to the device being disabled by UNRAID. Both disks are ST8000VN004, through Broadcom / LSI SAS2008. Forced to reverse back to 6.8.3 and rebuild array. NB : had no issues at all with disk spin up or down