itimpi

Yes. Unraid has to update each drive to say it has been successfully unmounted.

It looks like many of your shares have a Minimum Free Space of 97GB set and none of your array drives have this much free so mover will not be able to do anything. Reducing this to a smaller value might be a temporary solution, but it sounds like you need to add more disk space to the array.

To get mover to do what you want you need:
Primary storage=cache
Secondary storage=array
Mover direction = cache->array

If a share only has primary storage and no secondary storage then mover ignores it.

Yes.

The number of parity drives does not affect performance (once you have even 1), nor does the number of data drives.

Yes within the limit of 28 data drives.

Support for multiple 'Unraid' type arrays is a roadmap item although we have no idea of the likely timescale for this support actually being released as it has been on the roadmap for quite some time. When that support arrives it will probably be treated as just another 'pool' type.

You can have multiple pools using either BTRFS or ZFS file systems. so that is another way of utilising extra drives.

Note that 'caching' is technically a function associated with User Shares and reference a pool of any name (i.e it does not need to be called 'cache'). Its purpose is to act a staging post for writes to the array to improve perceived performance.

You might also want a pool to host docker containers and/or VMs with maximum performance. This can optionally be the same pool that you used for 'caching' but that is up to how you configure thins.

Not a simple answer as it can depend on what the client wants 😊. By default Unraid supports connections using SMB 2 or higher. It will also support SMB 1 if you enable NetBios support.

This.

That allows the "TV Shows" and "movies" folders to exist on multiple drives, but not any folders created within them.

The process is as easy as that.

On Unraid 7 you only need to install the Unassigned Devices plugin to handle mounting the drive in the dock. Dynamix File manager to handle the copying is now built in, although you are free to use other copying tools if you prefer.

You can use the New Config tool for that as long as you are only interested in the data on the 'good' drives. The tool is covered here in the online documentation.

No. Mover ignores any share that does not have secondary storage set.

You need Primary storage=cache; secondary storage=array; and mover direction=cache->array to get mover to move files from cache to array.

Do the shares (folders) show up if you look directly at the drives from the Main page rather than going via the Shares page?

It could be worth running a check filesystem on you drives as file system level corruption has been known to cause this type of issue. In particular the diagnostics suggest that disk7 has file system level corruption that needs fixing.

Yes.

You would need to temporarily disconnect the 7th drive until the array has been started, although after the array is started you can add in additional drives that are being handled by Unassigned Devices. This would apply any time you reboot the system.

Yes you could do this. You could then use the any file copying program you like to move (or better use copy) the data across to the other drive - if you do not have a preference then the Dynamix File Manager built into Unraid 7 might be the easiest. Note that while doing this your data is unprotected as you have no parity.

Once all the data is on the 12TB drive you can use the New Config tool to put the 14TB drive as parity and the 12TB drive as disk1. When you start the array after doing this parity will be built to get your array back to a protected state.

Yes. Legacy licences are valid for all Unraid releases.

A point to note is that no plugins from the earlier version are compatible with v7 but as you will be starting afresh that should be no issue.



Strongly suggest you back up the contents of both flash drives before trying anything. They are in standard Windows compatible FAT32 format so this is easy to do. Failing that at least backup the license (.key) file first as that is what ties the licence to the GUID of a particular flash drive. Nowadays that is the ‘config’ folder on the flash drive - not sure if that was the case with 4.7 or if that allowed it in the top level of the flash drive.

You can then use the USB Creator tool to put 7.1.4 release on one of the flash drives and after doing that put the licence file for that flash dtive from your backups into the ‘config’ folder. When you boot that it will show as a licenced copy.

Not sure how big the flash drives you were using are? It is possible they may be a little small for current Unraid, but if so you can use the online licence transfer process to move a licence to a larger drive.

Mover will ignore shares that do not have secondary storage set.

To get shares moved from cache to array you need Primary Storage=Cache, Secondary Storage=Array, Mover Direction Cache->array.

If that doe not solve you problems then post your system's diagnostics zip file giving the names of some shares that you expect to be moved.

the order of the drives will not matter if you only have parity1 as long as you did not restrict shares to particular drives under your share settings.

If that is the case you can use Tools->New Config and select the option to keep current assignments and click Apply.

On returning to the Main tab add the additional drives. Click the Parity is Valid checkbox (ignore the warning about parity being overwritten as it does not take into account the checkbox) and then start the array. You should find all drives mount fine with their data intact. If you have parity2 you should not click the checkbox as its calculation uses disk number as one of its parameters so you need to rebuild parity from scratch.

I would recommend you now run a parity check to confirm parity really was valid.

The syslog in the diagnostics is the RAM version that starts afresh every time the system is booted. You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to the problem. The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field and log to a share instead.

The configuration details when you install a container are stored on the flash drive. It sounds as if you installed this container after the backup so there are no saved settings for it which is why you got the message. To fix it you would need to reinstall it using the previous settings if you can remember them.

You need to run a check filesystem on disk9 as there is file system corruption for it being reported in the syslog.

I suspect that this is the cause of your trouble if radarr is trying to use a linux level move command to transfer files to the 'media' share which is by-passing the Unraid Share level and leaving the file on the cache in a 'media' folder. As I said the easiest workaround is to simply to set the share up as I described so that Unraid thinks the file is being cached and mover will later transfer the files to the array.

The licence is tied to the USB stick that is used to boot Unraid - not to the hardware it is running on.

Individual files are never spanned across drives in the Main array so there is no duplication of files.. What you are seeing is the fact that Unraid combines the top level folders on each drive to give the combined view as the User Share.

You should copy from the User Share level if you want all files in a share - that way you do not need to know which disk (or pool) the individual files ended up on.

'user' is the the standard User Share combining files across both the main array and any pools. user0 is the subset that is only on the array so you should normally avoid using this. user0 has also been deprecated as it might disappear in a future Unraid release.

Note that /mnt/user/appdata includes /mnt/cache/appdata as it is a merge of the ‘appdata’ folder on any array drive or pool.

Those errors are typical of connection issues due to cabling and/or power.

When you have a pool then all the details of pool size, etc are listed against the first device.

If you click on the pool name then you can see some more detail on the resulting screen.

Since your steps invalidate parity anyway, then you seem to have some unneeded steps and quickest would be to
stop server,
remove old drives
put in new drives
Start server
Use Tools->New Config - probably easiest at this point to select the Keep All Assignments option
Assign drives as you want them to end up (both parity and data drives) and remove drives no longer present
Start server to build parity based on the new drive set.