itimpi

I would think even a SATA SSD is likely to be faster than your internet or LAN speed which is likely to be the limiting factor in many cases.
NVME is more likely to be beneficial for items that run locally such as VMs or Docker containers.

The error message is correct because for appdata (for instance) you have:
shareFloor="98100000"
and you do not have that much free space on the 'cache' pool. Change Minimum Free Space for the share to a lower value or make more space free.

That is covered here in the online documentation.

It would start automatically if you restart the array in Normal mode. In Maintenance mode you need to press the Sync button.

I do not think that there is a possibility to bring back the array in a state where recovery of the failed disks is possible. You might want to wait and see if @JorgeB concurs as the best expert on recovering from various combinations of disk failure.

If it is just a case of getting your array back into a usable state with just the contents of the remaining drives then you can use Tools->New Config to do this. In such a case easiest to start with the option to initially retain all assignments. When you then return to the Main tab all drives will be marked with blue icons (I mention this because many people forget to hit the Apply option in the New Config tool and then you do not get the blue icons), and you can remove the drives that have failed. If you now start the array Unraid will recognise the existing data drives and bring them online with their data intact, and will start rebuilding parity based on those drives.

If something ends up in the lost+found folder then that means the repair process could not find the directory entry to give it is original name/location.

Unfortunately sorting out the lost+found folder is a manual process.

There is no standard command that I know of that gives that information about the array in an easily understood format.

However if you install the parity check tuning plugin even if you do not use any of its features it does add the 'parity.check' CLI command that allows you to query the array operation status and start/stop the operation or the whole array amongst other things. I could easily enhance the information provided on status to give everything you mention although the critical stuff is already there.

The current log is always at /var/log/syslog so you can query it using standard linux CLI commands. You can also view it easily via the GUI.

This sounds like an 'automatic' share that has been created because you have a top level folder with that name on one of your drives.

You need to contact support to get any licence related issues sorted.

BTW: if you have a legacy Pro licence this is functionally identical to the new Lifetime licence.

The diagnostics show that all disks are empty which suggests that somehow they were formatted or a global delete was run. You do not have your server exposed to the internet by any chance as there have been occurrences of bad actors doing this in the past.

I would think your best chance of recovering any data is to see if a file recovery program like UFS Explorer on Windows can see anything. That software is not free, but it does have a free trial that would show what (if anything) it could recover.

You should put each rule on a separate line.

The location you have specified for the docker image is set to be "/mnt/cache/appdata/docker-xfs.img“,but you do not have a pool called ‘cache’ so that location is in RAM which is why it does not survive a reboot.

In Unraid v5 if I remember correctly (it was along time ago😀) the Basic licence was a free one allowing up to 3 devices (as opposed to the v6 Basic licence which was paid for and allowed up to 6)? You need a paid-for licence from an old release to avoid having to buy a new one.

I see you have some additions to the config/go file that are not part of standard Unraid. Perhaps one of them is the culprit.

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.

If you are going to combine the Unassigned drives into a single volume this would need to be done before any attempt to share them. Have never tried anything like this myself so cannot give any more detailed advice.

Not at all clear, however, why the drives do not show up remotely if you have mounted them and set the Share option for them at the UD level. If you attach your system’s diagnostics zip file to a new post in this thread we might be able to give feedback on that.

If you explicitly copy to disk1 that is the only place files will go so that explains your symptoms.

That is true if copying internally within Unraid in that you must not mix a disk share and a user share in the same command. However in this case you are copying from an external device to Unraid storage. If using Uranid's built in file manager it will protect you from this issue as it will not allow a combination of source and target that can cause this issue.

What you want to be doing is copying to the 'Mov' user share (which appears at the Linux level as /mnt/user/Mov) as that is a share that spans all drives and pools. That will then obey whatever rules you have set up for that share as to where files should go. The /mnt/user0/Mov path is a variant that only includes array drives having files for the 'Mov' User share omitting any files on pools.

You may want to manually move some files from /mnt/disk/Mov to /mnt/disk2/Mov to free up space on disk1 as Unraid will not automatically move any existing files.

As long as you do not attempt to do anything to them after the Preclear finishes then they should add without Unraid going through a Clear process. When you add a ‘Clear’ disk to a new array slot the array should start without any parity rebuilding required as a clear disk does not affect parity. You then format them after adding to create an empty file system ready to receive files. A common mistake is to format the drives after the Preclear before adding them to the array not realising this destroys the ‘clear’ state.

Having said that there have been reports on some Unraid releases of the Clear state not being correctly recognised - not sure exactly which releases this applies to.

Yes. Normally if you have any options that are not standard with Unraid you need to add them to each of the boot options you want to use.

As you can see lots of .plg files there - one for each plugin installed. If you want to temporarily disable a plugin without completely removing it you can change its .plg file to have a different file extension and then rebooting. Reverse the process to enable it again.

You can end up with files on the wrong drive if using ‘move’ at the Linux level rather than a copy/delete strategy (this also applies to Krusader) to move files between User Shares. If using Unraid’s built-in file manager it will handle this correctly. The easiest thing is to leave the pool as Primary Storage and the array as Secondary Storage and let Mover handle transferring the files to the array.

This was clearly documented in the online docs before the recent reorganisation. I looked and could not find it in the current documentation.

You will not encounter this behaviour if you are moving the files between disk shares rather than User Shares.

If the existing Licence is for Unraid Pro then there is no cost involved to move to the latest Unraid Pro on the latest Unraid release as all legacy licenses are entitled to free updates for life.

The process is covered here in the online documentation.

Looking at the SMART information for this drive:
5 Reallocated_Sector_Ct PO--CK 161 161
196 Reallocated_Event_Count -O--CK 073 073 000 - 127
197 Current_Pending_Sector -O--CK 200 200 000 - 793

Based on these I would think the disk is not in a good state and should not be used in the Unraid array.

It can be worth trying downloading the zip file for the Unraid release and extract all the bz* type files overwriting the ones at the root of the flash drive. It sometimes helps with this sort of issue.