itimpi

Can’t see anything obvious to explain the behaviour. Could there be existing files that are growing in size after initial creation? Existing files are always amended/changed on their current disk and will not get moved if doing so breaks the Minimum Free Space setting.

You are likely to get more informed feedback if you attach your system's diagnostics zip file to your next post in this thread. It is always a good idea to do this to allow us to see the current state of your system and so we can see logs.

This is almost always hardware related with the two most likely culprits being insufficient power or the CPU overheating. 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.

Note that you will only be able to balance to the Single profile after you have removed the second drive. You cannot remove ANY drive from a multi-drive pool in Single profile without breaking the file system.

This must be something that was added a long time ago. Unmenu is not compatible with any recent Unraid releases. As was motioned removing it (i.e. reverting to stock version) of the config/go file is the answer.

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.

I am guessing that the share anonymized as m---a is the one you expect to be moved? However that is set up incorrectly for this as it only has primary storage set. Mover ignores shares that only have primary storage set. For that share to be moved you would need Primary Storage: cache, Secondary storage: array; Mover direction cache->array. The another share that is not completely as you would expect is the 'system' one that has some files on disk1. For those files to be moved to the cache pool to improve performance you need to run Mover with both the Docker and VM services disabled as they keep files open on that share which stops them being moved. The share anonymised as 's----g' is set to be written only to cache but has files on disk3. Again this is configured incorrectly to get its files moved to the cache. In this case you would need Primary Storage: cache, Secondary storage: array, mover direction array->cache. Once you have all the files for a share you want only on the cache pool you can then (optionally) remove the secondary storage option as you no longer need to get Mover involved for those shares. Doing that would allow such share to run as 'Exclusive' shares (as long as you have enabled this under Settings->Global Share settings) which can improve performance for such shares by eliminating the Fuse overhead that is otherwise involved for User Shares.

You are likely to get better informed feedback if you attach your system’s diagnostics (with everything in the one zip file) to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog. Also mention the name of a share(s) that you think the system should be moving to the array.

Unraid does NOT support hot swap/hot plug. Perhaps you are thinking of the Unassigned Devices plugin that DOES support this for drives it manages.

Your steps 1-3 look correct. I suggest you post your system's diagnostics zip file with them taken just after attempting these steps your next post in this thread. It is always a good idea to do this to allow us to see the current state of your system and so we can see logs

If you want to remove the main array then make sure the number of slots is set to 0. If that is not your issue then post your system's diagnostics zip file so we can see your setup.

According to those diagnostics the array has not yet been started, so it is not surprising no shares are showing up.

That is just ‘listening’ for syslog messages from elsewhere and will not capture anything. As mentioned in the syslog server link you either need to enable the “Mirror syslog to flash” option, or put your server’s IP address into the Remote Syslog server field.

To emphasise the point it is perfectly OK to run with parity2 as the only parity drive. Trying to move the current parity drive to be the parity1 drive will force parity to be rebuilt (as they are not interchangeable) and your array would be unprotected until the rebuild completed.

Yes, but I would not expect Unraid to ever support that configuration via the GUI so you will have to keep your script without a way to 'tidy' up.

No. If it does not complete in a few minutes after reaching that stage it is never going to complete and you need to force a shutdown by holding down the power switch.

You can get the sort of issue you have if the casing of the .cfg file on the flash drive is different to the casing of the top level folder for the share on your drives.

That would cause problems! I suspect that whatever you were doing should have been done using the User Scripts plugin with the relevant script set to run at first array start?

Nerd tools is incompatible with Unraid 7.

Performance of ZFS formatted drives in the main array is known to be slow (performance in pools is fine).

Make sure Fast Boot is not enabled in your BIOS settings.

You are likely to get more informed feedback if you attach your system's diagnostics zip file to your next post in this thread. It is always a good idea to do this to allow us to see the current state of your system and so we can see logs.

I think you will only be able to do what you want if different media types are in their own share. You are asking for behaviour to be specified for an individual folder within a share which is not something that Unraid Supports.

Any previous release should be in the ‘previous’ folder on the flash drive. Restoring these files to the root of the flash drive will then revert to that release. It is recommended that you always make a backup of your flash drive before attempting an update to make reverting very easy This backup can be easily done by clicking on the boot device on the Main tab and selecting the Backup option. Why are you trying to upgrade to 6.11.3 in the first place? The last release in the 6.x.x versions was 6.12.15 and the current stable release is 7.1.4.

The syslog in the diagnostics is the RAM copy and only shows what happened since the reboot. It could be worth enabling the syslog server to get a log that survives a reboot so we can see what happened prior to the reboot. The mirror to flash option is the easiest to set up, but if you are worried about excessive wear on the flash drive you can put your server’s address into the Remote Server field.