Leaderboard

Well, you want one of us to go through all of the updates and pick out the ones that are important to you? Come on, give us a break. Everything in these updates is important to the various different users of Unraid for different reasons! Some are security updates. Some are updates to Samba, some address hardware issues, driver issues, incompatibilities, and some are new drivers for the latest hardware. It is easy enough to roll back if you find some issue or you can request assistance to solving the problem. But understand that waiting until some future version in the distance future may give you a lot of upgrade problems because of the small adjustments and tweaks that were detailed out as each update came out. You will have to make your own decision about about when to move up to a new version but I can assure you that keeping in the current major release version will give you the fewest problems over the long haul! (Plus, unlike other software, all updates are FREE!!!)

NerdPack is fairly benign and doesn't include any packages that are present in unRAID. It's the DevPack that's the problem. I put it out there on request as a repository for compiling on a dev unRAID system not for daily use. It uses just installpkg. Going forword I think I'll strip out all the packages inherent to unRAID, include only the headers and add - headers tag to them. Something may not compile right but it won't hose the system. Basically all that is needed is the headers you guys strip out to save space for the preinstalled unRAID packages.

Unassigned Devices Plugin Unassigned Devices (UD) includes a lot of functionality and has become a bit complex. Please read the first and second post. You will find answers to most of your questions. Note: You will need to install the Unassigned Devices Plus (UD+) plugin to enable HFS+ and APFS (Apple file formats) and exFAT (flash larger than 64MB) disk mounting, and to enable 'Destructive Mode' for formatting of some UD supported disk formats. UD and UD+ are available in Community Applications (CA). Hover your mouse over any active area on the UD page and a tool tip will show you what clicking that area does. UD supports all Unraid native disk formats. You will need to install the 'Unassigned Devices Plus' plugin to mount HFS+, APFS and exFAT file formats. UD has a destructive mode that allows deleting disk partitions and formatting disks. If Destructive Mode is not turned on in the UD Settings, you WILL NOT be able to format a disk. Go the the Settings page and scroll to the bottom to see the UD settings. To format a disk: Destructive Mode must be enabled. You will need to install the 'Unassigned Devices Plus' plugin to enable Destructive Mode. UD Plus will install the 'parted' package needed for formatting and deleting partitions. Disk must have all partitions removed. Unmount the disk, click on the '+' icon next to the serial number, and click on all red-X to delete partitions. You can also click on the red-X next to the disk serial number to delete all partitions. A precelared disk will have a partition without a file system and will show a grayed 'Mount' button. You can assign this disk directly to the array and Unraid will see the disk as 'pre-cleared' and will not clear it again. If you want to format the disk for use in UD, you need to first click on the red-X on the preclear status line to remove the preclear stats and then remove all partitions by clicking on the red-X icon next to the serial number and then you'll be able to format the disk. There are different operations in various active areas (especially the disk serial number) based on whether or not the disk drive is mounted. If the disk is not mounted, click on the '+' icon by the serial number, click on the partition name, you will get a pop-up dialog to change the mount point name. This will now become the mount point and the share name when the disk is shared. In order to share any UD device, sharing needs to be enabled in the UD Settings and the switch turned on to share the particular device. SSD disks formatted with xfs, btrfs, or ext4 will be mounted with 'discard' if the "Mount SSDs with 'discard' option?" is set to "Yes". This includes encrypted disks. Reiserfs does not support discard. This enables TRIM on SSD devices. If you have the trim plugin installed, it is recommended to not mount SSD disks with discard. Disks formatted XFS or BTRFS will be partitioned compatible with the array disks and can be installed in the array without a re-format. SSD devices are now partitioned with a 1MiB offset as of Unraid 6.9 Beta 25 and cannot be installed as a cache or pool device on earlier versions. Because of security issues with samba, the mounting of remote SMB shares with CIFS has become more complicated. The default protocol is now SMB3 and not SMB1; the default security is now ntlmv2 and not ntlm. UD will try to mount SMB shares with SMB3, then SMB2, and then SMB1 to try to get the mount to use the most secure protocol it supports and the ntlmv2 protocol. If you have an older server that only supports SMB v1, you need to update that server so it will support SMB v2 or v3. SMB v1 is being phased out and will probably eventually be removed from samba. You will not be able to mount a remote SMB share using SMBv1 if NetBIOS is disabled in Unraid. It is recommended to disable NetBIOS on Unraid servers. Note: UD disks add to the total disks allowed by the Unraid license you have purchased except for a Pro license. See here for details. Unassigned Devices allows you to mount and share disk drives that are not managed as part of the array. Some users are mounting a drive specifically for Dockers and/or VMs rather than having them on a cache or array drive. You can also mount a UNC share on another system (SMB or NFS) and have it show in the Unraid shares when browsing the Unraid shares with Windows. This is called Remote Share Mount. The UNC path is mounted locally and shared as a \\Tower share that can be accessed by SMB or NFS. Access to Unassigned Devices shares defaults to Public with everyone having read/write access. User access can be enabled in the Unassigned Devices Settings. Access can be enabled by user for read/write, read only, or no access to Unassigned Devices shares. Installing the plugin You can install the plugin from the Community Applications (Apps tab); Remote Mounted Shares You can remote mount SMB and NFS shares. SMB shares are accessed through \\Tower\share. There are several special cases of remote mounting SMB shares. Windows. You have to provide user login credentials to be able to show the shares with the 'Load Shares' button. Even if the shares are not password protected, Windows insists on login credentials. Domains. You can remote mount shares on a domain by specifying a domain. It is preferred to use the server name and not the IP address. Let UD search for the servers and then make a selection, then load shares and make a selection. This is much less error prone than manually entering the information. Unless you use a static IP address on the server, it can change making the remote mount fail. Note: With NetBIOS disabled on a remote server or computer on your LAN, UD may only be able to look up the server and show its IP address because the name cannot be resolved. It is recommended that you type in the name of your other server or computer instead of using the IP address. UD will make an adjustment so the name can be resolved when mounting the remote share. UD also keeps the IP current if it is changed by a DHCP server. When a USB device is plugged in or mounted an event is initiated to run a user defined script. This is useful for backing up files from the server initiated by plugging in the USB device or copying pictures from a camera to the array. Scripts are created unique for each device. You can also setup one script to run whenever any device is plugged in or mounted. Mount Points and Shares There seems to be a lot of confusion over a mount point vs. a share. The mount point is where the device is mounted locally on Unraid. A share makes the mount point available in Windows at '\\Tower' as a browseable folder. When disk devices and ISO Mounts are mounted, they are mounted at /mnt/disks/. They are not a part of the Unraid array and are not mounted at /mnt/disk/ which is for Unraid disk drives. As an example, you have a device named 'MyDisk'. When it is mounted, it is accessed locally at /mnt/disks/MyDisk. If you want to use 'MyDisk' in a Docker Container or VM, you would refer to it by '/mnt/disks/MyDisk'. It is not automatically shared at '\\Tower\MyDisk' unless you enable sharing the device. To share 'MyDrisk', you would turn on the 'Share' switch for the drive and 'MyDisk' would be shared at '\\Tower\MyDisk'. The share 'MyDisk' is not accessed at /mnt/user/MyDisk' because it is not an Unraid user share. When remote shares are mounted, they are mounted at /mnt/remotes/. They are not a part of the Unraid array and are not mounted at /mnt/disk/ which is for Unraid disk drives. As an example, you have a share named 'MyShare'. When it is mounted, it is accessed locally at /mnt/remotes/MyShare. If you want to use 'MyShare' in a Docker Container or VM, you would refer to it by '/mnt/remotes/MyShare'. It is not automatically shared at '\\Tower\MyDisk' unless you enable sharing the device. To share 'MyShare', you would turn on the 'Share' switch for the remote share and 'MyShare' would be shared at '\\Tower\MyShare'. The share 'MyShare is not accessed at /mnt/user/MyShare' because it is not an Unraid user share. If you are using the legacy mapping of remote shares at /mnt/disks/ for your Docker Containers or VMs, and it is not practical to remap them in your Docker Containers or VMs, you can set a legacy mapping option in UD Settings that will put symlinks in /mnt/disks/ to the remote shares in mnt/remotes/. When you map to the /mnt/disks/MyShare be sure to have a trailing '/' on the mapping so the symlink will be treated as a directory and not a file. Mount points and shares are two separate things. Partitions and Formatting If you turn on the destructive mode in the Unassigned Devices Settings, you will be able to delete partitions and format disks. It is defaulted off as a safety measure. Scripts Here is an example script that will back up a Pictures share to a USB drive when plugged in. The USB drive is unmounted once the script completes so you just plug in the drive, wait for it to be completed, and then unplug the drive. The beeps in the script will make speaker sounds if you have a speaker to let you know when the drive is plugged in, when the backup has started, and when the backup has finished and the drive unmounted. The nice thing about this script is that all you have to do is plugin the drive and wait for it to finish. You will also be notified when it is done if you have turned on Unraid notifications. Set the drive to auto mount. Set the script to run in the background. If you mount and unmount the drive from the Unassigned Devices gui, the drive will mount and unmount but the script will not run because it has detected the 'OWNER' as 'user' and will skip the backup. #!/bin/bash PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin ## Available variables: # ACTION - if mounting, ADD; if unmounting, UNMOUNT; if unmounted, REMOVE; if error, ERROR_MOUNT, ERROR_UNMOUNT # DEVICE - partition device, e.g. /dev/sda1 # UD_DEVICE - unassigned devX designation # SERIAL - disk serial number # LABEL - partition label # LUKS - if the device is encrypted, this is the partition device, e.g. /dev/sda1 # FSTYPE - partition filesystem # MOUNTPOINT - where the partition is mounted # OWNER - "udev" if executed by UDEV, otherwise "user" # PROG_NAME - program name of this script # LOGFILE - log file for this script case $ACTION in 'ADD' ) # # Beep that the device is plugged in. # beep -l 200 -f 600 -n -l 200 -f 800 sleep 2 if mountpoint -q $MOUNTPOINT; then if [ $OWNER = "udev" ] then beep -l 100 -f 2000 -n -l 150 -f 3000 beep -l 100 -f 2000 -n -l 150 -f 3000 logger Started -t$PROG_NAME echo "Started: `date`" > $LOGFILE logger Pictures share -t$PROG_NAME rsync -a -v /mnt/user/Pictures $MOUNTPOINT/ 2>&1 >> $LOGFILE logger Syncing -t$PROG_NAME sync -f $MOUNTPOINT beep -l 100 -f 2000 -n -l 150 -f 3000 beep -l 100 -f 2000 -n -l 150 -f 3000 beep -r 5 -l 100 -f 2000 logger Unmounting PicturesBackup -t$PROG_NAME /usr/local/sbin/rc.unassigned umount $DEVICE echo "Completed: `date`" >> $LOGFILE logger Pictures Backup drive can be removed -t$PROG_NAME /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Server Backup" -d "Pictures Backup completed" -i "normal" fi else logger Pictures Backup Drive Not Mounted -t$PROG_NAME fi ;; 'REMOVE' ) # # Beep that the device is unmounted. # beep -l 200 -f 800 -n -l 200 -f 600 ;; 'ERROR_MOUNT' ) /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Server Backup" -d "Could not mount Pictures Backup" -i "normal" ;; 'ERROR_UNMOUNT' ) /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Server Backup" -d "Could not unmount Pictures Backup" -i "normal" ;; esac Here is a nice UD script for importing photos from a camera/memory card into the array: Photo Script Thanks to ljm42. Cron Task A better way of running cron scripts is the 'User Scripts' plugin. You can set up a script to run at a particular time to perform disk operations. It is best to leave the device mounted so the script can access the drive. This is a simple way to set up a cron task to run a script to copy files to a backup. This method is a little cumbersome, but does work well. You will need to set up your drive to auto mount and it has to be left mounted. You can use the default script or the following one if you want beeps when the drive is mounted and unmounted. Set the drive to auto mount. he drive has to stay mounted for the script to work. Set the script to run in the background. #!/bin/bash PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin ## Available variables: # ACTION - if mounting, ADD; if unmounting, UNMOUNT; if unmounted, REMOVE; if error, ERROR_MOUNT, ERROR_UNMOUNT # DEVICE - partition device, e.g. /dev/sda1 # UD_DEVICE - unassigned devX designation # SERIAL - disk serial number # LABEL - partition label # LUKS - if the device is encrypted, this is the partition device, e.g. /dev/sda1 # FSTYPE - partition filesystem # MOUNTPOINT - where the partition is mounted # OWNER - "udev" if executed by UDEV, otherwise "user" # PROG_NAME - program name of this script # LOGFILE - log file for this script case $ACTION in 'ADD' ) # # Beep that the device is plugged in. # beep -l 200 -f 600 -n -l 200 -f 800 ;; 'REMOVE' ) # # Beep that the device is unmounted. # beep -l 200 -f 800 -n -l 200 -f 600 ;; esac Now set up a cron file in the /flash/config/plugins/dynamix/ directory. Name the file 'custom.cron' (or a name of your own choosing.cron) with the following contents. This will set up a cron task to run at 4:30 AM every day. It runs a script in the /boot/custom/ directory called DailyBackup. # Custom cron scripts: 30 4 * * * /boot/custom/DailyBackup &> /dev/null Sample Daily Backup script #!/bin/bash # # Perform daily backup. # MOUNTPOINT=/mnt/disks/DailyBackup PROG_NAME=DailyBackup logger Started -t$PROG_NAME if mountpoint -q $MOUNTPOINT; then logger Pictures share -t$PROG_NAME rsync -a -v /mnt/user/Pictures $MOUNTPOINT/ 2>&1 logger Completed -t$PROG_NAME /usr/local/emhttp/webGui/scripts/notify -e "Unraid Server Notice" -s "Server Backup" -d "Daily Backup completed" -i "normal" else logger Daily Backup Drive Not Mounted -t$PROG_NAME fi After you have copied your cron file to the dynamix directory you will have to load the cron file manually one time to get it started. Unraid will manage the cron file after that and insert it into the crontab for you. Use the following command to load the cron file the first time. /usr/local/sbin/update_cron Encrypted Dsks You can format a xfs or btrfs encrypted disk with UD that is compatible with the array. The disk is created with the array password/passphrase. You must have at least one encrypted disk in the array. Unraid 6.8 and greater only. You can format an encrypted disk for use outside the array without having an encrypted array. The disk password is entered when the disk is formatted. You need to set the disk password in UD settings so the disk will mount. Unraid 6.8 and greater only. A disk encrypted with a different password than the array can be mounted with a disk password set in the UD settings. A different password can be set for each disk. Pooling Disks You can create multiple pools with UD, with some limitations, details here. Starting with Unraid 6.9, there is a 'Pool' feature that should be used for pooling disks. Click on the 'Help' button on the main menu bar of Unraid to get some additional help. If you hover your mouse over an active area on the gui, you will see tool tips that will help you understand the operation of the active area. Verify you have the latest version installed and check the syslog for information if you are having any issues. Many questions can be answered by reading this post and checking the syslog. Root Share You can create a root share in UD and collect all your shares in /mnt/user/ into one named root share. The root share is then accessible at /Tower/rootshare. There are some advantages and disadvantages to this approach: You control the root share permissions in UD Security settings. You may increase your risk of a malware attack by having all your shares accessible on one root share. Use secure passowrds! Addon Mount Folder UD adds the folder '/mnt/addons' where you can mount anything you need mounted. A protected mount is added to '/mnt/addons' so a misconfigured app cannot fill the rootfs and crash the system. FCP will ignore this mount folder so you won't see any warnings. If you mount something at '/mnt/addons' before UD is installed, you will see a reboot message over the banner. If this is the case, you need to delay your mount until after UD installs. Mount Button Indicators Disks In order to point out to users normal operation and situations that may prevent UD from operating on a disk device properly, the 'Mount' button will show some greyed out text that indicates status on the disk. If the text shows with the not symbol, the disk is in an error conndition. 'MOUNT' or 'UNMOUNT' - when the 'Mount' button shows either of these grayed out, the 'Disable Mount Button' switch is on. This situation lets UD do auto mount and unmount, but operator actions are not permitted. Theere are occasions when these indicators are grayed out because of disk drive issues. 'PASSED' - This indicates the 'Passed Through' switch is set. This is used to tell UD that a VM or Docker Container is using the disk and for UD to not manage the disk in any way. 'PRECLEAR' - The UD Preclear or binhex Preclear Docker is preclearing the disk. 'POOL' - This is used to indicate that a disk is part of a BTRFS pool. 'PARTITION' - This will show when a disk is detected that has a file system but no partition. UD cannot mount a disk in this situation. If it is a disk introduced to UD that you want to use in UD, you can clear the disk and reformat it for use with UD. 'ARRAY' - This indicates that a disk has not been detected by Unraid as an Unassigned Device and UD thinks the disk is a part of the array. This generally happens when an array disk drops from the array. 'UDEV' - UD has detected that the disk format reported by udev does not match the format as reported by lsblk. This can sometimes be rectified by clicking on the double arrows on the UD UI to refresh the udev data in UD. 'REBOOT' - This shows when UD has detected a disk was probably removed before being unmounted and then re-installed. The best way to clear this up is to reboot. If this happens because of several disks having the same mount point, unmount the disk with this mount point and change mount points on all disks to be unique. Remote Shares 'MOUNT' or 'UNMOUNT' - when the 'Mount' button shows either of these grayed out, the remote sever is off-line. When these indicators are grayed out on an ISO mount, the iso file is not available.

OS: unRAID 6.4.0-rc10b Pro License CPU: Intel Xeon E3-1240 v3 $152 used eBay Motherboard: SUPERMICRO MBD-X10SLL-F uATX Server Motherboard LGA 1150 $109 used eBay RAM (24GB): Crucial 16GB ECC (2 x 8GB) and HYNIX 8GB (4GB x 2) UNBUFFERED ECC SERVER 240-Pin DDR3 SDRAM 1600 (PC3L 12800E) $176 from old build & $41 used eBay Case: Silverstone Case Storage Series CS380 $125 Drive Cage(s): Ultra Quadruple 4 X 2.5″ to 5.25″ SATA SSD Hot Swap Drive Bay Enclosure $20 Power Supply: Corsair SF600 $109 + Cable Mod extension cables $30 SATA Expansion Card: LSI LOGIC SAS 9207-8i Storage Controller LSI00301 $65 new eBay Cables: 2 x Monoprice 0.5m 30AWG Internal Mini SAS 36pin (SFF-8087) Male w/ Latch to SATA 7pin Female (x4) Forward Breakout Cable $9/ea Fans: 2 x Noctua NF-F12 120mm PWM $20/ea 2 x ENERMAX T.B. Silence UCTB12P 120mm PWM $15/ea UPS: Tripp Lite 1200VA Smart UPS Battery Back Up, 700W Rack-Mount, AVR, 2U (SMART1200LCD) $177 Parity Drive: 2 x 4TB Toshiba MD04ACA400 Data Drives: 2 x 4TB Western Digital WD40EZRX, 4TB Seagate ST4000DM000, 4TB Seagate ST4000VN008, 2 TB Western Digital WD20EZRX Cache Drive: 2 x Corsair Force 120GB SSD $70/ea Total Array Capacity: 18TB Total cost w/o drives or UPS= $915 Primary Use: Media Storage and backup Power Consumption: will update when done This isn't really a new build but a consolidation and upgrade. I'm combining my main server and my backup server with a few new parts. My 2nd ASRock C2750-D4I was starting have problems with sensors missing in the BIOS and IPMI e.g. 3v, 5v, 12v and MB temp. So I plan to RMA then sell it. Then use the Supermicro board. Since the SM is a uATX, I needed a new case. I also needed a SATA card and a new processor since the G3220 wouldn't be adequate. Idle Power: 41 watts

I don't believe that any testing / reconfiguring of the UI is done against IE / Edge. Everything is tested against Chrome / Firefox / Brave / Safari

It has already been updated. However this plugin was meant to be used on a dev system for compiling packages for unRAID. unRAID is a mix of Slackware current and I cannot always keep up with every package change or incompatibility. I don't scour through every release thread either. I do try to compare unRAID releases against this repo. So unless someone posts in this thread about a problem with a package in this repo, I may not know. So moving forward I'm going to strip out every inherent unRAID package in this plugin and only include the headers for those packages.

Cache dirs has (or had?) an issue where it doesn't start up after a reboot. Go to its settings and toggle the enable function. Because the system looks for the file(s) on disk 1. If it doesn't find it, it goes to disk 2 etc...

Limetech makes announcements in their blog

From your last screenshot, scroll down to see the "storage" folder.

Log is full of weird stuff I've never seen before, like: Oct 23 00:55:01 Server kernel: 8d 42 Oct 23 00:55:01 Server kernel: 0f 1f Oct 23 00:55:01 Server kernel: ff 4c Oct 23 00:55:01 Server kernel: 84 00 Oct 23 00:55:01 Server kernel: 8d 74 Oct 23 00:55:01 Server kernel: 00 00 Oct 23 00:55:01 Server kernel: c3 08 Oct 23 00:55:01 Server kernel: 00 00 Try booting in safe mode, if that fails try booting with a clean flash drive, trial or redo yours.

From your original screenshot it looks like the files on your flash have been encrypted by ransomware, which means you have at least one system on your network infected by the ransomware software. Before getting your unRaid back up you need to find what systems are infected by the ransomware and fix them, if you have not already. Be aware that when you do get your unRaid system back up, it is quite possible you will find all the files on it encrypted by the ransomware if the system infected by the ransomware had write access to your shares.

When upgrading to 6.6.x, the upgrade process automatically creates a "previous" folder on the flash drive and copies the necessary files there to facilitate a roll back, if desired. If you want to roll back, you just go to Tools-->Update OS-->Restore.

Hi , it will persist, but if you do an update of settings from plugin it will over write this. Skickat från min iPhone med Tapatalk

Good read: https://www.servethehome.com/investigating-implausible-bloomberg-supermicro-stories/

Anyone figure this out? AFP is dreadfully slow to backup even over a 1 Gbps on Mac and 10.14 seems to have made it worse. Over 24 hours to backup 2/3 of my 200 GB of data on the Mac. Apple's documents says they only support SMB over the network for Time Machine. https://support.apple.com/en-us/HT202784#nas Would love to get rid of AFP once and for all... anyone know how to make this work? ***EDIT*** May have found a way to cheat: https://www.makeuseof.com/tag/turn-nas-windows-share-time-machine-backup/ I created a sparsebundle image and put it up in the SMB share then mounted the disk in Mac and forced TimeMachine to use it with a simple sudo command. Granted I have to make sure the share is mounted and the volume name doesn't change to get it to back up, I'll have to see if it's any faster. Just started a fresh backup and off we go... ***UPDATE 2*** About 30 minutes in and already 21 GB backed up. It's estimating 4 hours left... much MUCH less than the 24+ hours it would have taken using the AFP share. ***UPDATE 3*** This method may only be effective for a desktop that never sleeps. My laptop as soon as I close the lid drops the connection to the remote disk which causes macOS to force an fsck on the sparsebundle image the next time it's mounted. This isn't really feasible. Hoping we get real support in unraid!

It's supported if used with AFP (Apple's own network filesystem). Since AFP will be deprecated, we are discussing the usage of SMB as successor of AFP. Aye, it was via SMB that I was referring to. If support is a ways out, I'll go with AFP or hack up something in the meantime, but if it's around the corner I'll just be patient and back up the machines locally. :]

It's supported if used with AFP (Apple's own network filesystem). Since AFP will be deprecated, we are discussing the usage of SMB as successor of AFP.

Doesn't it already? There is at least one container available on the apps tab which is not hosted on dockerHub. Can't you use the extra parameters / post parameters already available in the GUI *Should* be nothing you can do via the cli in running a container that you can't manage to get into a template and then have unRaid be able to manage it. Unless you also have to build it.

The problem with direct writes (for /me/) is that it causes disks to spin up a lot. In the evening during the TV season I'll get 2-5+ episodes a night, spinning up the drives in a staggered way for each one is pointless when I can cache them and then move them at once. For the Movies share, it would make sense to do that as those tend to be larger and less frequent additions. ie: it is a balance, usage management combined with cache size :).

my few cents; I have used a 750 EVO but the NAND is not durable. Currently I use a CRUCIAL MX500 1TB and it seems excellent price/performance ratio wise (paid ~260 USD). it tends to overheat (probably my bad -airflow since its stuck on the backside of the board against a tower wall) It also feels a bit slower than a Samsung Pro. I´d stick with Samsungs PRO line either SATA or if you need the speed NVMe via PCIe. The PRO line has a higher TBW spec but costs a bit more than the EVO. About size - totally up to you - I had the 750 EVO with 500 and it got too small quickly with all the VMs on it.

Nice...those submitting copyright your work and license it.

When are we going to be seeing some more limetech / unRaid gear? Badges were available a while ago, and I would think that they flew off the shelves. Myself, I've been off and on bugging jonp to get my hands on one of the Limetech beer steins to no avail... I'm sure that mugs / beer steins / t-shirts would have a high markup, and would move fast enough to make them worthwhile. Something reflecting the esoteric nature of this forum...

Hi John, let me explain. If you read through the forum about Time Machine and UNRAID the usual recommendation is not to spread an individual TM backup over multiple disks. Easiest way is to use a disk share instead of a User share. You can put different TM backups on different disks though. As I explained, this defeats the advantages of UNRAID to store a TM backup of a Mac with one or more big hard drives. Because TM backups keep a history of changes, it is recommended that the TM volume should be at least 1.5 times bigger than the size of all hard disk attached to your Mac. And because TM has no functionality to spread a TM backup over more than one hard disk, you need a virtual hard disk like a RAID, JBOD made from individual hard disks or easier and more flexible a User share on an UNRAID, if the total disk space you want to backup exceeds the biggest hard disk you can buy currently. Second recommendation is not to use a cache disk. Usually that is not an issue as TM backups can run slowly in the background. But if you set up a big UNRAID to backup a couple of Macs, things can become a bit slow without a cache disk. So if you follow the "official" recommendation you have to use only a single disk and no cache disk for TM backups, which in fact makes UNRAID less appropriate for TM backups than traditional RAID solutions. You can do it my way and use a User share spread over multiple/all disk and use a cache disk. And as long as you use method high-water it seemed to work. But I wouldn't call this a proven and solid solution. The fact that my first test with method fill-up failed, implies, that there is a risk, that a TM backup gets corrupted, if any hard disk, that is involved in the backup process fills up. That could be a disk in the User share or the cache disk. Frankly I don't understand, why this is an issue, because TM backups on network volumes are store as Sparse Bundles and those are just a collection of bands. And that is probably, why you were confused: I call it only partially working, because there are some potential issues you can run into, that lead to a corrupted TM backup. And that is the last thing you want to see on your backup. I have the impression, that if the developers would investigate into the issues that sparse bundles might have with multi-disk user shares or the cache disk, find the reason for this and iron it out, UNRAID would be the ideal server for TM backups and I would recommend it to anyone as the first choice. Currently using it the way I do is more like an experiment and not recommended for the average user.

Can you get to the command line in unRAID? You don't have to know a lot about Linux to do what you want to do. There is a GUI-like file manager called Midnight Commander you can run by typing mc.