Leaderboard

To upgrade: If you are running any 6.4 or later release, click 'Check for Updates' on the Tools/Update OS page. If you are running a pre-6.4 release, click 'Check for Updates' on the Plugins page. If the above doesn't work, navigate to Plugins/Install Plugin, select/copy/paste this plugin URL and click Install: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer.plg Refer also to @ljm42 excellent 6.4 Update Notes which are helpful especially if you are upgrading from a pre-6.4 release. BIOS: Especially if using Virtual Machines, we highly recommend keeping your motherboard bios up-to-date. Bugs: If you discover a bug or other issue in this release, please open a Stable Releases Bug Report. Version 6.6.2 2018-10-13 Base distro: cairo: version 1.15.14 fontconfig: version 2.13.1 freetype: version 2.9.1 glibc: version 2.28 glibc-solibs: version 2.28 harfbuzz: version 1.9.0 jansson: removed libdrm: version 2.4.94 librsvg: version 2.44.6 libvirt: version 4.8.0 libXinerama: version 1.1.4 libXxf86misc: version 1.0.4 mesa: version 18.2.1 pango: version 1.42.4 p11-kit: version 0.23.14 samba: version 4.8.6 xterm: version 337 xf86-video-ast: version 1.1.5 [revert] xf86-video-mga: version 1.6.5 [revert] xf86-video-vesa: version 2.3.4 [revert] xorg-server: version 1.19.6 [revert] Linux kernel: version 4.18.14 OOT Intel 10gbps netowrk drivers: ixgbe-5.5.1, ixgbevf-4.5.1 Management: blacklist DRM_AST Aspeed video driver emhttp: added instrumentation to FUSE/shfs update smartmontools drivedb and hwdata/{pci.ids,usb.ids,oui.txt,manuf.txt} webgui: Revert docker run Security webgui: Updated button styling webgui: Added new setting "Font size" webgui: Styling update: height & width scaling webgui: Docker: fixed autostart order not updated when "wait" values are present webgui: Docker: added "container size" calculation webgui: on Tools/Vars set PHP_AUTH_PW to asterisks webgiu: Change anonymized email address webgiu: Add global CPU core pinning for containers webgiu: fixed: VM CPU mode not properly updated

The is no rule about when you should move from single parity to dual parity. It depends of your Risk Tolerance. This thread will provide you with a good approximation of the risks involved and some factors that you may not have even thought about: https://forums.unraid.net/topic/50504-dual-or-single-parity-its-your-choice/

I had quite some problems with my speed and Cinebench score of my Ryzen 1700. The first step is to use the plugin "TipsAndTweaks" to change the "CPU Scaling Guvenor" to "On Demand". In my case it was set to "Power Save" as default. This moved my from about 550 to 1170 in CineBench. A noticeable change. Looking at the at terminal with the following command, it was wasy to see that my Ryzen 1700 just wouldn't boost properly when using Cinebench: To fix this Download zenstates from https://github.com/r4m0n/ZenStates-Linux/blob/master/zenstates.py Save the script in a share under the name zenstates.py (I chose /mnt/user/appdata) Use NerdPack to install python (Needed for executing the python script) I used the UserScripts plugin to set up this script. Running every time that my array starts. I got the script from @david279 (He also made an Excel sheel to calculate the value to enter for difference zenstate entries https://docs.google.com/spreadsheets/d/1icKFa0COFFpIKmkXOXVUrTt7mnMqdYYLbtRiedat5zs/edit?usp=drivesdk) I only apply for P0 as that is the only state I'm interested in. The rest is up to CPU to downclock itself After all of these changes, CineBench score jumped from 550 to 1420. So I'd said everything worked out just fine I hope this can help somebody else with the same or similar problems.

Hello - Upgraded to unRAID 6.6 last week and, since then, I can't backup to my NAS anymore. The connection to the NAS is via SSH and I'm using Duplicati. I'm also unable to download files via SFTP using FileZilla - this worked perfectly and without issue before I upgraded to 6.6. Now any attempt to reauthenticate fails (FileZille does this before very file transfer). Wondering - was there change under the covers to the way SSH works that might've caused this? Thanks

Looks like a default / reserved share created by Samba

Your device doesn't use those drivers you quoted. It uses the i40e driver. Current OOB version from intel is 2.4.10 No idea if it compiles with latest kernel's yet... Intel seems to be dragging there feet.

Just crashed again on me with same results - updating to 6.6.2 and will upload diags when it happens again. FYI, what seems like a surefire way of killing the nfsserver and then the shfs (and making everything remount on /mnt/user0) is mounting one of the NFS exports as /home for a linux VM, especially with lots of little NFS I/O calls and NFS locks for Firefox, etc. It gradually slows down more and more, until finally nfsd on unraid just croaks.

After all of the issues I've had, it would appear that PIA went ahead and cancelled my account, which was the reason that I couldn't get the docker to work properly... After some time spent with PIA support, they finally refunded my purchase, and I decided to go with another vpn provider... I have since re-configured all the docker containers to the new vpn provider, and they work perfectly! My thanks to Binhex and everyone else who helped me with this problem!

Current max is 28 with a Pro license. Incorrect, Unraid supports dual parity since v6.2

drop the comma Rule: 10.0.0.100(sec=sys,rw) 10.0.0.101(sec=sys,rw)

Upgrade to v6.6.2 and see if it makes a difference.

Put old drive back in and replace parity with new drive. Go to Tools - New Config. Retain ALL then make the necessary assignments changes. Don't check the parity is valid box and start the array to build parity.

Are you trying to access the server from a Windows 10 machine? If so, did it recently install any major updates? Lots of problems lately with users not being able to access the server via Windows Explorer>Networks by server name due to SMBv1 being disabled and other issues with Windows 10 networking. It's solvable but the solution is not always the same for everyone. You might want to consider giving your server a static IP address and setting the array to auto start on reboot in case you have issues in the future. Of course, you may have reasons not to do either if that is your preference.

It would be nice if the built in /etc/rc.d/rc.M and the UI event system was modified to support persistent groups and hosts.

Probably. But you can automate it either through the "go" file or via the user scripts plugin. Not much other choice at the moment.

So I'm having issues where Time Machine backup is dirt slow even though unraid and Mac are connected to router on 1 Gbps. Mac Activity Monitor shows the machine is barely doing anything even though it has all that speed available. Over 24 hours to backup 2/3 of my 200 GB. I setup the AFP share with TimeMachine and only using that share for TimeMachine One thing Apple told me is that for NAS Time Machine setup, has to be SMB and AFP is no longer supported for this purpose (https://support.apple.com/en-us/HT202784). I noticed that SMB Time Machine is not available in the Unraid config. Anyone know how I can better configure the share or perhaps I saw a docker container that could run a Time Machine server in a container? Would appreciate any ideas here so backing up my Mac doesn't take 2-3 days even sitting idle on 1 Gbps connection. Thanks

Unraid must boot off of the licensed USB stick, but it runs in RAM to keep the USB stick healthy. Only config changes and the like are saved back to the USB to preserve the state for subsequent bootup. So, the thing that sticks out most to me IS your USB flash drive. 3.1 spec drives may be problematic, you will have to see whether you have issues as the root cause of the 3.0/3.1 problems is illusive. USB 2.0 are MUCH preferred, typically less heat / wear, and the lower speed doesn't really change anything because Unraid runs in RAM. Your next issue could be the PCIe HBA, I don't know of ANY 4 port cards that work well. Either 2 port Asmedia chipset cards or 8 port LSI chipset cards work well, Marvell based controllers can be very problematic. Your post is unclear about VM access, headless or local console, so hard to comment on that.

I upgraded to 6.6 and 6.6.1 - since upgrading I had all sorts of issues. I have since rolled back to 6.5.3 but am listing the issues I've experienced. I'd love to get some feedback from those that know better than me (i.e. everyone) as the issues seem strange/bad enough to be worth mentioning. 1. Fuse crashing and taking NFS shares offline. I'm aware this is a known issue caused by an incompatible or problematic kernel version, but I'm very frustrated that this wasn't caught during testing. For a free or open source product I could understand or be a bit more relaxed about it, but this is a paid/commercial product. Shares going offline (which is mentioned in the forums since 2014) is unacceptable. I don't use CIFS and changing to that is not an option for me. 2. Unable to SFTP transfer any file bigger than around 32KB. The file transfer begins and then just stops. This means my workstation backups fail, since I'm doing that via SFTP. 3. Not long after, SSH stopped working altogether. 'root' login via SSH just said access denied. GUI login works fine so I know my credentials are correct. Upon checking the unRAID box with physical keyboard, I found /etc/ssh/sshd_config to be completely empty/zero bytes. There was a file called /etc/ssh/ssh_config but that's not the correct file for SSH configuration. Now that I'm on 6.5.3 again I can see the contents of /etc/ssh/sshd_config and it's got stuff in it. Empty/zero bytes is obviously not the way things are supposed to be. 4. Some parts of the configuration disappeared. My NTP configuration reverted to factory defaults and the unRAID system identification reverted to 'Tower' with no description. Both are things I had altered via the GUI. It's worth mentioning that unRAID 6.5.3 was rock solid before the upgrade - I don't know how or why but the 6.6 upgrade is exactly when these issues started occurring. None of the above issues have occurred, not even once, since rolling back to 6.5.3 (which I did by reimaging the flash drive and starting my config from scratch).

Thanks for this - given me a lot to look into and think about.

Some TRIM performs like zeroing - so a RAID machine can recompute the parity as if the data was zeroed (which means all disks needs to be online or the original contents needs to be read before TRIM is sent). But the parity drive can never make use of TRIM, since it doesn't have a file system with unused portions to TRIM. This means that a RAID should be designed in a way where TRIM isn't needed for it to work well. So the way to use SSD in a RAID is to have overprovisioning. Either enterprise disks that is delivered with a significantly large, hidden, amount of overprovisioning. Or high-end customer drives that can be configured so parts of the user space of the drive is reserved for overprovisioning. But note that large HDD (especially helium-filled models) are quite efficient when used for a home media server, since you can often manage with a single disk spinning. So best is a tiered solution where data files and audio is stored on SSD and movies and TV-series are stored on big HDD. This is what I am currently doing. So mirrored SSD for often used data. Mirrored 2.5" HDD for next tier of data. And then multi-disk RAID with dual-parity for bulk storage. And backup to drives that are allowed to spin down between each backup run, with new data "rolling" over multiple drives so backup drives doesn't need to spin up every night.

Samsung announced this week mass production of consumer level 4TB SSDs. Whilst the prices aren't known yet (to me at least), it got me thinking again about a supported version of unRaid running on SSDs. I'd quite happily shift over to something running quieter, faster, smaller and more efficient at some point. Does anybody know the latest on Lime Tech officially supporting/recommending SSDs in the array? Or does the TRIM rule it out completely?

SSH into the server or use the console and type: mover stop