itimpi

You can also try rewriting the bz* type files as described here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page.

You need to run without -n and adding -L

How are they connected? If via USB then it is possible the serial numbers are not being passed through correctly. Some USB enclosures pass them through while others do not.

You seem to have the same drive assigned to disk1 and parity2. Not quite sure how you got yourself into that position. Have you tried setting parity2 to not assigned and then starting the array.

No 14TB drives are showing up in the SMART reports suggesting they are no longer online. The fact that UD has one showing with the same serial but a different ID suggests that drive dropped offline and then reconnected. You probably need to shutdown the server; check power and SATA cabling to both of them; and then reboot to see if either of them is now showing up as expected. Posting new diagnostics at that point might be a good idea.

This is one of those things that seem to be highly variable. Some seem to to get failure in months, while others get many years - 10 years being reported. What does seem to help is getting USB2 drives (I suspect because they typically run cooler than USB3 ones) if you can find them nowadays. Also ones with metal casings can help with heat dissipation. Having said that I have some nano form factor ones that I have been using for years and they are too small to have much cooling. Sounds as if you definitely want to get an automated backup of the flash drive in place going forward. The two standard ways of achieving this are: via the appdata backup plugin which includes an options for the flash drive as part of scheduled backups. Via Unraid connect which supports automated backups to the cloud (on Limetech servers). There is still the manual backup method of clicking on the boot drive on the Main tab and selecting the backup option from there.

This is not an issue if the USB enclosure passes the drive serial numbers through to Unraid as that is the way that Unraid identifies drives, not by the order in which they initialise.

You could simply rename the folder under the appdata share and edit the container settings accordingly. There should be no need to copy the folder in that case. You can use the Dynamix File Manager to do the rename.

Rebuilding a drive will not clear an unmountable status. The procedure for this is covered here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page.

The problem with using encryption is that if you end up with file system level corruption then encryption can compromise recovery processes so it then becomes critical that you have a good (and tested) backup strategy in place.

No, it is always based on the number of folders in the files path.

You can use something like UFS Explorer on Windows to do this.

The User Scripts plugin can be used to initiate the scripts on a selected schedule for devices permanently available. Alternatively the Unassigned Devices plugin allows you trigger a script when a particular drive is plugged in. The content of the script will depend on exactly you want to copy and to where.

I would think so to clear out the old syslog (held in RAM and restarted after each boot). Not sure it will clear the problem though.

You get the zip file via Tools->Diagnostics FYI: You will often see certain phrases in forum posts (such as the word diagnostics) underlined that are a link to the relevant instructions in the online documentation.