Stable Releases

I tried to fix this odd issue for about an hour earlier with no success.  Unraid is setting CPU pinning for containers even after I remove these definitions.  I've tried ensuring that there's nothing set under "Settings > CPU Pinning" for any docker containers, removing a container/image and recreating from a template that doesn't contain the `--cpuset-cpus` param (NOTE: there needs to be an inline code option here, not just code block), rebooting, etc.     For example, I'll start o

Hi all Since updating to 6.6.1 from 6.5.4 my docker page on UnRaid always shows updates available for all containers. Pressing update all does not remove the message. Attached is my diagnotics.   Thanks tower-diagnostics-20181005-0924.zip

Hello, I need help with my system. I'm running on version 6.5.0 and it does not update to 6.6.1 and also will not let me install any plugins or remove those that are already installed.       I would be very grateful for the help.   tw-nas-diagnostics-20181004-1052.zip

I followed the in browser "Update Now" link to upgrade to version 6.6.1 from 6.5.3, and my server never came back up. I run my server headless, so when I went to go check on it I found it was stuck in a restart loop. I moved my server to a location where I could hook a monitor/keyboard to it, and found that every time it reached the automatic start splash screen for Unraid it would show “bzimage…ok”, and then “bzroot…ok” and then it crashes and restarts.   When I changed the option to

Hi. I using GitLab-CE docker for all my company projects with these extra parameters: <ExtraParams>--env GITLAB_OMNIBUS_CONFIG="external_url 'https://subdomain.domain.duckdns.org/'; nginx['listen_port'] = 9080; nginx['listen_https'] = false"</ExtraParams> according to this post: https://forums.unraid.net/topic/48653-support-gitlab-ce/?page=3&tab=comments#comment-605797   In version 6.5.3 everything works fine but in version 6.6.0 and 6.6.1 I have an err

Hello I have been having mover issues on one Unraid server (my dual Xeon E5's)...all my shares are set to use High Water and leave min 1GB free space. its bays are populated with 4x 1TB drives (2.5") for data and 2x 1TB for Parity i was messing around with use cache settings last night when i was tired (first mistake i know) and woke up to see that it had filled my dual 500GB SSD's up with data from the Array (and meant for the array)   i fixed my use cache settings and started runn

I have noticed if a share has SMB (Private) and NFS (public) (possibly other configs) being accessed around the same time the user/ folder permissions break (forcing a reboot to restore) this was happening to me on constantly on 6.6 RC 4 and up. I ultimately went back to 6.5.3 where this issue doesn't happen and tried again with mention of an NFS fix in 6.6.1 the setup I had to cause this was two unraid systems know as Sif (unraid plus) and Thor unraid pro and the system this was happening on

I was wondering why a bunch of my dockers were failing. Any of them that used BR0, bridge 0 have stopped working. There's no option that I could find in Settings-Networking or Settings - Docker to enable the bridge mode again to allow a Docker to have it's own "host" IP again.   I tried to change the networking to Bridge 0 and there's no option so therefore I have to revert for now. (Really nice interface though)   I also had to toggle the settings off and on to revert back t

See attached. With multiple cores at high usage, the indicator bar overruns its real estate.  

I upgraded to 6.6.0 when it came out and within 30 minutes my drives started throwing read errors. I rolled back and discovered the issues were still there, but i did have a faulty power supply it seems.   I've replaced my Power Supply and everything is stable again. I tried upgrading to 6.6.1 again and within 30 minutes read errors. I have rolled back to 6.5.3 till its fixed but something seems to have changed with the mpt2sas driver. Looking for LSI and 6.6.0 i've

Bug Description: docker is unaccessible when losing Internet connectivity    How to reproduce: turn off Internet, try to access docker containers over network.   Expected results: works the same with and without Internet connectivity   Actual results: unable to access running containers over mapped ports   Other information: https://forums.unraid.net/topic/69749-dockerdashboard-tab-unresponsive-docker-containers-are-unreachable/   Hi,  

Hello,   I just updated to unRaid 6.6.1 from unRaid 6.4.x.  In 6.4 every time I restarted unRaid it started up saying it had an IP address 192.168.xxx.xxx, however no computers on the network could see it.  I would then have to do `ifconfig eth0 down` and `ifconfig eth0 up` to restart my 10GB network connection and all was fine until the next restart. With 6.6 this is worse though.  Now I have to do that on restart, but also every couple of hours.  This is an issue since my DNS is

Hi,   there seems to be a bug when using "wait" values for docker containers and then rearranging the order of the docker containers. This won't update the list order. So the start order of the docker containers stays the same as before.   these are my settings in the webUI     and this is the start order of the containers   Sep 28 18:32:08 unMARV rc.docker: EmbyServer: started succesfully! Sep 28 18:32:08 unMARV rc.docker: EmbyServer: wait 5

When trying to start a Win10 VM, I was getting the following error.   Editing the VM did not present the device in question.     Saving and relaunching did not remove the orphan item and the error persisted. I had to manually remove the following block from the XML in order to launch the VM.     If it is not supposed to remove the orphan USB device, I recommend listing items in the XML but not attached to allow them to remain or be removed i

Fresh Install of Unraid 6.6.0 in a system System Config :    Issue : Created a share named media and set security to private. Unable to see controls for changing share permissions. This was observed in version 6.6.0 as well as 6.6.1. See below for screenshots.   SMB Configuration :    tower-diagnostics-20180928-2338.zip

Rebooted the system and the web Gui and all docker services failed to start. Logs attached.   I can access the system through putty, but I can't figure out how to get to the services. The man page doesn't list anything useful and the command 'service' doesn't exist. tower-diagnostics-20180928-0757.zip

I don't know if this is and AMD x399 Zenith board bug or Unraid so posting this to to verify. Was using my machine and got this below. I force stopped the VM and it killed unraid completely. 100% unresponsive so had to hard reset. This isn't the exact one it got but its very similar. It was the only thing logged in the syslog before it occured. Sep 26 15:08:57 Tower kernel: iommu ivhd2: AMD-Vi: Event logged [ Sep 26 15:08:57 Tower kernel: iommu ivhd2: INVALID_DEVICE_REQUEST device=00:00.0 pa

Docker CPU usage is showing over 100% on the bar.

Two NICs from the "Asrock Z370 Professional Gaming i7" motherbaord are listed with the same MAC address. (Behaviour identical between 6.5.3 and 6.6.0-rc2)   This is the after the FIRST boot with a fresh install:     After rebooting eth0 is displayed as eth111, MAC address conflict is persistent:     ruler-diagnostics-20180912-0401.zip   EDIT: 3 hours later, the MAC address property field of eth0/eth111 is now a Yes/No dropdown menu

This is truly just an annoyance and not causing any problems but when I goto to updates and choose next, I'm shown 6.6.0-rc4.  I'm using 6.6.0 so going back to rc4 would be the prior, not the next release (at least I think it is)🙂   I only notice this when I'm checking to see if there is any new update out that I should look at.   Thanks for all your hard work!! Scott

I have my unRaid setup running under ESXi 6 with 8 virtual cores and 16 GB ram.  This worked fine with all prior versions, including 6.5.3, but with 6.6.0 the boot gets stuck on "x86: Booting SMP configuration:"   When this happened, I first moved back to 6.5.3 and unRaid booted as expected.  Then I re-downloaded the 6.6.0 update and tried booting again.  It failed at the same spot.  Lastly, I tried changing the number of cores in ESXi from 8 (4 virtual sockets with 2 cores per socket)

Having an ongoing issue since upgrading to 6.6.0 where the webgui disappears like in the screenshot. The top 'menu' bar is still there but there is no other content, the box where the data should be is just white, I have to physically restart the server to get it to return, this is only possible by actually being at the server so makes it impossible to do any work on it. (in the screenshot I have blanked out safari and the server name but nothing else)     Plugins I have runn

Hello twice in two days now one of my server has nginx (webgui) crashing   i can recover it via cli with" /etc/rc.d/rc.nginx restart then: /etc/rc.d/rc.php-fpm restart but it keeps happening...known bug? here is the logs once it happens (this was happening in RC3 and 4 as well and was posted)   in this latest instance i wasn't able to restart the gui and had to reboot...on a reboot its now performing a parity check   diagnostics are from well after

just looking at remote SMB/NFS mounting and see the Search for Servers box is so big it does fit on the window

Upgraded from 6.5.3 to 6.6 stable version. Everything looks good and was running as expected until I attempted to start my Windows 10 vm with GPU passthrough (GTX1080) Threadripper 1950x cpu PCIe override downstream/multifunction vfio-pci with appropriate details enabled at startup   Working smooth in 6.5.3 and previous versions Now with exact same settings in 6.6 the VM fails to start with log codes stating GPU stuck in D3 state.   Reverted to 6.5.3 and c