itimpi

The SMART test failing is never a good sign as it runs completely internally to the drive. The only external factor that springs to mind that could cause this is power issues. If the drive cannot past the Extended (let alone the short) SMART test then we would normally think that it needs replacing.

Do you have macvlan enabled for docker networking? If so you need to make sure bridging is disabled on eth0 to avoid potential system instability.

You are likely to get better informed feedback if you attach your system’s diagnostics 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.

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.

You want Secure Boot to be disabled. You do not need it just because you are using UEFI boot and Unraid does not support it anyway. I would think you could also enable Legacy USB support and CSM support. This would give you the option of alternatively booting in legacy mode (but does not stop UEFI boot). Not sure if it helps in any other way.

Which method did you use? Going via the contact support form seems to work reliably but other routes are less reliable for some reason. If you did not get the automated acknowledgement then the request almost certainly did not get through. If necessary/easier you can do a manual upgrade to 6.12.10 by following the procedure documented here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI.

You can do a manual upgrade to the current 6.12.10 release by following the procedure documented here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom. The Unraid OS->Manual section covers most aspects of the current Unraid release. Having done that the purchase option should now work. If you still encounter problems you will need to contact support as they handle all licencing issues.

It is always possible that disk7 is not really dead as the fact it is disabled simply means a write to it failed. This can be caused by external factors such as cabling or power. It is not showing up in the SMART information in the diagnostics so at the very least it is currently offline. Have you taken any action to confirm it is dead? @JorgeB mentioned using ddrescue with the parity drive. It might also be possible to do it with the disabled drive as an alternative way of recovering its data. I have succeeded in the past with ddrescue on drives that would fail their smart TESTS. Regardless I would keep both of those drives intact until one of the approaches has worked to maximise recovery chances.

The top level is the Share name (which maps onto a folder at the disk level). Each additional folder in the files path adds another potential level. Looking at your examples you would need '2' to keep all of Breaking Bad on the same drive or '3' if you are happy for each season to potentially be on a different drive. Your second example has an extra folder in the path so not sure what you want to keep together there?

That is the location from within Unraid (/boot is where the flash drive is mounted). If you have the Dynamix File Manager plugin installed then it has built-in capability to view/edit such files which might be the easiest way to do it.

They should not be, and often cause problems. Your initial results suggest at that point you might be getting a 10Gb link in one direction and something like 2.5Gb in the other.