Stable Releases

Hello,   I am hoping there is a way to get around this issue with open permissions.  This appears to be the default on UnRaid.   Please see this post.     I would view this as a very large security hole.   This may not be an issue for the average user, but it should be stated for any user that expects security for files on UnRaid.   If I am incorrect on anything, please let me know.  I have tested and reproduced this behavior on UnRaid stab

I'm not 100% sure if this was introduced in 6.6.5 or 6.6.6 but I'm leaning towards 6.6.6 as I don't remember seeing it previously.  

Hi, i have the problem that the host and guest complete lockup/crash when I try to install win10 and/or install gpu driver. Since the host (unraid) doenst respond (no network, ssh, webgui, freezed screen vm) I can't pull any diagnostics. The bios I used to use in the vm and I removed the header with HxD (spaceinvaderone method). https://www.techpowerup.com/vgabios/151132/zotac-gtx760-2048-131028   All other system info and so should be in the diagnostics zip or ?

Hello, I have a problem that restart my server every 5/6 hours on average. Would you tell me what it is.   Thank you

I have had this issue come up before, but could never pull diagnostics. This time I had syslog open, and was able to copy the full log from it before being disconnected from the server. Dec 2 14:00:02 TheiaHD kernel: BUG: Bad page map in process php7 pte:800000067dff6067 pmd:4f0c94067 Dec 2 14:00:02 TheiaHD kernel: page:ffffea0019f7fd80 count:2 mapcount:-1 mapping:ffff88014f47c370 index:0xce0a Dec 2 14:00:02 TheiaHD kernel: flags: 0xaffff0000000038(uptodate|dirty|lru) Dec 2 14:00:02 TheiaHD

Issue detailed in general support forum here.  After upgrading to unraid 6.6.0 my server would periodically lose all network connectivity. Reboot would make it come back online or awhile, but then it would fail again.  Diagnostics attached that were taken during the failure. Downgraded to 6.5.3 and all is working normally.    Let me know what other information you need.     ungeo-diagnostics-20180925-1829(1).zip

Hey Guys,   Have upgraded to 6.6.0 recently and ever since I've been getting kernel panics around every 12 hours or so, as expected requires a hard reset to get it back up and going again.   Doesn't seem hardware related as it was running fine on the previous stable version.   Diagnostics attached   Thanks! tower-diagnostics-20180926-1022.zip

I'm posting here even though this might be something for @dlandon and the Unassigned devices plugin.  I'm pretty sure though it's 6.6.6 related as the problem only started when I upgraded.   I have had 2 HDDs connected via USB as UDs for about 3 months with no problems at all, but yesterday after upgrading from 6.6.3 to 6.6.6 the devices disappeared from the GUI view on the Main tab, and only after power cycling a few times was I able to get them to reappear - however I couldn't get th

Love the black theme.  There are a few pages though that use the old theme if black is selected:   - docker update progress - plugin update progress   Not a problem, just pointing out

So over the last couple of days I have had a couple of total freezes of Unraid. The server becomes completely unresponsive. Shares, webgui or SSH are not accessible. I haven't found a way to reproduce it but my guess is that it must be connected to some background activities (like parity check or mover) but I cannot confirm this as it does not happen all the time. And of course I cannot exclude hardware errors.   - The first time it was booted in default mode (no GUI) and the cursor ke

The system had gone into undefined state. It was accessible via GUI but docker was down and /var/log/syslog showed number of error when I tried to simply reboot the system (either via GUI or manually via reboot command from console). I have attached a snippet of error output.   Not sure if this is a hardware issue that has developed or simply an OS bug.    Had a few instances where docker images would not start (rubbing is SSD cache) and had to reboot the box to clear this st

Show Unraid port assignments in the Docker allocations to prevent Docker ports being assigned to Unraid ports.  Server type Dockers tend to want to use ports 80, 443, 8080, and 8443 that are potentially being used by Unraid.  This causes Dockers to fail because of improper port assignments.   An alternative approach would be to not allow any ports to be assigned to those potentially used by Unraid.  i.e. reserve those ports (80, 443, 8080, and 8443) to be used for Unraid exclusively.

Log message seems to have a line feed causing a blank line in the syslog: Dec 6 05:15:38 MediaServer kernel: mdcmd (167): set md_write_method 0 Dec 6 05:15:38 MediaServer kernel:   Not a big issue, but adds empty lines to the log.  Also change the message to 'set turbo write enable/disable' rather than 'set md_write_method 0/1'?  

To replicate:   Size browser so there is no horizontal scrollbar. Resize so there is a horizontal scrollbar. Scroll right.   Banner area at top does not cover entire canvas on the right.

verified on safari and Firefox   clicking log shows       plugins tab: update check shows:   and further on that tab, I can't click any plugin icon to access options for that plugin (I thought I was able to access them there)   System information popup is working.   OS update check:     and further, it doesn't know what it is or who made it:       feedback popup displays correct

The link in unRAID Docker template Edit mode Help for "Privileged" option has a broken link due to changes in documentation pages on docker.com    

The built-in new permissions, not Docker Safe New Perms, but the standard one, doesn't work any longer in 6.6.5

The vars page has some php warnings:

Since my old defect report was marked as deprecated after the forum change I am reposting it here. The defect does still exist. The linked thread has details of exactly what permissions are being applied when using these settings and connecting to a share from OS X.

Don't know if this is a bug or a limitation, but even if it's not a bug maybe something can be done to make it better, this happened to a user recently in this thread and I was able to reproduce it.   How to reproduce: -start with a 3 device cache pool -unassign cache1 -re-arrange pool, e.g., re-assign cache3 to cache1 slot, up to here all is working fine -change cache slots to 2, now Unraid will indicate cache1 is new and result in an unmountable and damaged cache

Just a minor cosmetic bug when having loads of CPU cores: As you can see, anything past 18c/36t is a bit loopy.

This is more a question than a bug report, since v6.6 and during scripted rsync backups, Unraid is on the receiving end, log gets spammed with these warnings:   Oct 2 14:46:00 Tower1 sshd[14336]: SSH: Server;Ltype: Version;Remote: 192.168.1.27-42621;Protocol: 2.0;Client: OpenSSH_7.5 FreeBSD-20170903 Oct 2 14:46:00 Tower1 sshd[14336]: SSH: Server;Ltype: Kex;Remote: 192.168.1.27-42621;Enc: [email protected];MAC: <implicit>;Comp: none [preauth] Oct 2 14:46:00 Tower1 ss

It is quite possible to create a share with a name which is incompatible with FAT32 naming limitations.  When this happens everything works correctly (assuming that the name is also SMB compliant) except that shcmd will spam the log with errors, and no adjustment of the share's .cfg will be possible.   Similarily, shares differing only by their case (test, Test, TEST) are all perfectly valid (assuming of course that they are not exported over SMB -> which there is no requirement to

Description: After changing network routers the IP address of my Unraid server changed (from 192.168.178.3 to 192.168.1.3). Afterwards I kept getting this error whenever trying to start either docker (mariadb, nextcloud): rc.docker: mariadb: Error response from daemon: driver failed programming external connectivity on endpoint mariadb (6944c8378ca4adc184f9dc65b050ad6d22253c8925c2f8f0096b848c8bb949e6): Error starting userland proxy: listen tcp 192.168.178.3:3306: bind: cannot assig

Good day all   After using Unraid for a few months now we were very happy with 6.5.3 and installed the newer version onto our second 45drives (28 storage, 2 parity and 15 cache) 8TB WD Red Pro+ drives   the first server after figuring out that unraid wanted a specific usb to be used to retain anything after a reboot works like a charm 300mbs+ to shares on it. However with 6.6.5 on the second machine i get max 20mbs and a failure to use Veeam backup and replication as sho