From the Shares tab, you can either create a new share or edit' an existing share. Click the Help icon in the top-right of the Unraid webGui when configuring shares for more information on the settings available. User Shares are implemented by using Linux Fuse file system support. Deleting User Shares. To delete a User Share, just clear the Share name field and click Apply. Only entirely empty User Shares may be deleted. Renaming User Shares. To rename a User share, just click in the Share name field of the share, type it's new name, and then click Apply. Technical notes. If all else fails to remove a share use this command prompt once you have either used SSH or Telnet to connect. Rm -rf /mnt/disk1/Time/ Posted in unRAID on July 14, 2014 by lanky8804. May 03, 2019 This video is the first part of a series taking an in-depth look at Unraid shares. This first one gives a brief introduction then looks at SMB shares and how Windows PCs interact with them.
By default, unRAID has a few pretty big security vulnerabilities which should be addressed immediately after installation.
My take is that unRAID is secure enough to operate within my home network behind a firewall, not exposed to the internet. Adding the steps here will make it more secure to protect against the unlikely, yet unfortunate possibility that someone nefarious gains access to your home network.
Here’s my list of steps taken to secure my unRAID install. If folks have more that I’m missing, I’d love to add them here!
Add password for root
It’s really bad that unRAID doesn’t force you to set a root user password as part of the installation. There’s really no excuse for this type ‘insecure by default’ philosophy when it’s so easy to fix.
So, to fix it yourself, go to the web UI and navigate to Users > Select ‘root’ > Add a Password.
It will take all of 30 seconds to do it.
Create users that aren’t root
It’s always a good idea to do as little as possible as the root account on a Linux system. While you’re on the Users screen, go ahead and make users for yourself and others you want to have access to shares. The only thing these users can do is access shares.
Restrict access to your shares
If you don’t have to expose a share via SMB, don’t! Just turn them off.
If you don’t have to give people write access, make them read only.
I prefer to set my shares that are available via SMB to “Private” for the Security level which gives guests no access, and then set the proper access control for each user in the house. To make the changes, just go through each share under the Shares tab and set your SMB Security Settings and User Access however you see fit.
Disable access to the /flash share
For some crazy reason, the USB drive that hosts the operating system is shared by default as /flash. I don’t remember if the default permissions on it are “Private” or not, but I think it’s a good idea to just not have it shared at all.
This one is trickier to find, however, because it’s not listed under the Shares tab. To find the controls, go to the Main tab, and click on the Flash drive link.
From there, set the Export to “No”.
Disable SMB1
The folks that built the SMB protocol are serious about telling people to stop using the first version for a variety of security reasons. Now, many of those might relate to Windows-only devices, but there’s no reason not to disable it on your Linux box as well.
Go to Settings > SMB (Under Network Services). Under the SMB Extras add the following line text:
Disable Telnet & FTP access
unRAID comes with Telnet and FTP enabled by default. That’s really pretty silly this day and age. If you want to access a command prompt, you should use ssh. If you want to transfer files, use anything but FTP.
The easiest way to disable them both is to leverage the Tips & Tweaks plugin.
- Install the Tips and Tweaks plugin by going to Plugins > Install Plugin and using the following URL:
- After it’s installed, navigate to Settings > Tips and Tweaks (under User Utilities)
- Find the “Disable FTP Server & Telnet” option and select “Yes”
Fix common problems plugin
This one is nice – it’s basically a health check on the unRAID system. It’ll scan logs, look at your current config, and help you find common problems that you may have overlooked.
You can install it by going to Plugins > Install Plugin and using the following URL
You can learn everything you need to know about the Fix Common Problems plugin on it’s forum thread here.
Unraid Midnight Commander
Ransomware protection
I honestly don’t know if this plugin would help in the event of a ransomware attack, but I think the principle is sound and it’s a pretty low hassle way to add some protection. The recent WannaCry ransomware attack highlighted the need for some additional consideration for me.
The general idea is to create a honeypot of files and shared folders that, if modified, immediately trigger unRAID to go into read-only mode (and/or disable access to all shares). If someone tries to encrypt and delete your files, unRAID would simply cut off access. This is particularly useful since these shares can be accessed by all of your users on potentially vulnerable machines… so if one of their machines gets infected with randsomware, and it tries to access your unRAID shares (because those machines likely have the share passwords cached), unRAID can stop the attack from being completely successful.
Ulead video studio 7.0 free software. You can read all about the Randsomware plugin here on it’s forum thread. To install it, I found it easiest to install the Community Applications plugin and search for it and install it from there.
Setup email notifications
This one is important so that you can be notified by the various plugins and unRAID itself about the condition of the server. This isn’t just about security, obviously, but also about the general health of the system.
For example, you’ll be notified about plugin and server updates which are available, hard drives that are too hot, errors that crop up, etc.
You can find the settings under the Settings tab > Notification Settings
Keep your server up to date
unRAID itself and all of the plugins are easy to update – just go to the Plugins tab and click the “Check for Updates” button. Then go through and update each plugin – including the unRAID OS itself.
If you run any Docker containers, unRAID will let you know if they have updates available as well on your dashboard (they’ll be a different color). For any VM you run, make sure to check for updates on them regularly as well.
Further Reading
There’s a good thread on the Lime Technologies forum – Is unRAID really unsecure? I would recommend reading that as well – there are some good pointers there about other basics not covered here, like making sure to keep your system up to date, maintaining good backups, etc.
My take is that unRAID is secure enough to operate within my home network behind a firewall, not exposed to the internet. Adding the steps above make it even more secure to protect against the unlikely, yet unfortunate possibility that someone nefarious gains access to your home network.
There are many reasons to like unRAID, one of them is it’s ability to easily add drives of mismatched size as and when they become available to you. I had followed this principle over the years and ended up with a hodge-podge of drives. As was my want I’ve decided to remove all 6 (yes 6) drives at once from my array and replace them with 2x 3TBs.
This guide will attempt to make the process of removing drives from unRAID a SIMPLE process, something which much of the information around thus far has failed to do. I’ll include screenshots where required, and will always respond to comments below. With that in mind, let’s get cracking!
Identifying the drive(s) to be removed
So I’ll be focusing on only one drive here, but you can easily repeat these steps for as many drives as you want. But first, a disclaimer.
During this process your array will require parity to recalculated at some point, thus leaving your array unprotected for some time (maybe up to 12 hours). Proceed at your OWN RISK!
Before you begin I STRONGLY advise you to take a screenshot of your drive configuration as this will prove a useful reference throughout this guide. The drive I will use during this guide is ‘disk 8’.
Now then, this is where we remove the drives from the array. Using your unRAID web interface go to Utilities > New Config > Check the box and reset your drive config.
What this does is reset the drive list that unRAID uses. If you go back to the main array page now, you’ll see that your drives are ALL unassigned. No data has been lost or deleted at this point, so if you wish you can reassign all drives as they were and restart the array with valid parity.
Ok, next step is to reassign the drives you want to KEEP only. Leave the drives to be removed unassigned, start the array and let the parity resync complete (this can take a while). Optionally, you can do the parity resync at the end – it’s up to you (it’s what I did).
Start the array and it should look something like this now.
Hopefully this make sense, but I’ll recap just incase. We have:
- reset the drive assignments that unRAID uses and created a new config
- added the drives we want to KEEP to a ‘new’ array
- not deleted any data
- *optionally recreated Parity
Mount the removed drive(s)
I’m presuming that the drives you’ve removed have data on them that you want to be kept safe, if so read on.
Log in to telnet, ssh or console (preferred) on your unRAID box. Then using your old array screenshot as a guide find the ‘dev name’ of your disk, for example disk 8, was (sdl).
Now we want to create a mount point for the old drive under /mnt and mount it!
Your drives most likely have only one partition (that’s the number after sdl refers to below) but if you want to check, run fdisk -l. My output is below purely for reference.
You may repeat this as many times as you like so as to mount each old drive, but you’ll need a separate mount point for each to mount them concurrently.
Copying across the data using MC
MC stands for Midnight Commander and is built-in to unRAID. To check that you’ve mounted the right drive to right place, run
The output from this command is very useful and gives you an idea of how much data there is to move. See below:
So now we know that there is 594GB of data on my old drive, I want to transfer the whole lot. Fire up midnight commander with a simple command.
Navigate user the arrows and enter keys to /mnt/olddrive under which will be the directory structure you should recognise from unRAID. I store everything in one folder called /Media so on the left pane highlight the folder you want to move. Then in the right pane navigate to /mnt/user and go back to the left pane.
Then, press F6 (this will move all data, only deleting from old drive upon successful completion), selecting preserve attributes is a personal choice but I like timestamps. Kind of hard to explain like this but hopefully this next screenshot helps…
This process will likely take some time and will vary drastically depending on the amount of data to be transferred. The ‘in progress’ screenshot is below
So to recap this section we have
- mounted the removed drive (referred to as olddrive) to /mnt/olddrive
- checked we’ve mounted the right drive to the right spot with ‘df -h’
- used mc to transfer all the data back to /mnt/user (which is the array).
Finish and tidy up
Once you’ve finished transferring stuff unmount the old drive with umount below. Close mc and cd (change) out of the that directory if it doesn’t work and try again.
Unraid Delete Share Mac
That’s it. Repeat as necessary for each drive and you’re good to go.
It’s not as complex as this guide makes it seem and you’ll really get the hang of it within a couple of go’s! Thanks for reading.
Unraid 6.8 Delete Share
Please let me know if there’s anything I can change in this guide to make it easier – it’s aimed at the beginner…