itimpi

You could put the 2x3TB into a ZFS raidz1 pool for maximum speed and the 2x8TB drives into the main array without a parity drive. The 2x8TB could alternatively be put into single device pools of their own. Perhaps a bit more detail of your intended Use Case would help pin down the best option?

Not sure this is at all obvious as I have never heard of this happening before so will be interested if the root cause is pinned down. It might be worth posting your system's diagnostics to see if we can see anything unusual in your configuration./setup.

Have you tried enabling it under Settings->Management Access.

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 should post your system's diagnostics zip file in your next post in this thread to get more informed feedback. It is always a good idea to post this if your question might involve us seeing how you have things set up or to look at recent logs. 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 a crash. 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.

Read errors can be caused by factors external to the drive itself so I would suggest that you run the Extended SMART test on the drive. If that fails then the drive needs replacing, but if it succeeds you might instead want to look at cabling/power to the drive.

If you are going to use macvlan then you have to disable bridging on eth0 to avoid system instability.

You could also try rewriting the system files on the flash drive as described here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI.

You do not want to ignore this as it is known to cause system's to be unstable. Strongly recommended you take one of the recommended actions - switch to ipvlan docker networking or if continuing to use macvlan turn off bridging on eth0. This tends to indicate either problems with the flash drive or with the USB port to which it is attached.

looks like your server might be using macvlan networking? If so to avoid stability problems you need to either switch to using ipvlan docker networking or disable bridging on eth0

Not sure. Might be worth waiting to see if @JorgeB had an ideas.

The syslog in the diagnostics is full of errors relating to the cache drive which is probably why the docker service is not starting. I would suggest starting by running check filesystem on that pool.

yes

Do you mean something different to the current Unraid Connect feature?

The files are there - if you can work out by examining them what their correct filename should be. in practice many people find it easier to restore from backups.

From a functional point of view current Pro licences are equivalent to the new Lifetime licence.

For the time being you need to revert. Any ‘hot fix’ would get a higher patch number (e.g. 6.12.10).

An unexpected reboot is nearly always hardware related. Nothing in the logs that I can see indicating a software reason for the reboot.

I would expect you to now have a lost+found folder on the drive with files/folders with cryptic numeric names. These are ones for which the repair process could not find the directory entry giving the correct name and would need sorting out manually. The Linux ‘file’ command can be useful if doing this by at least telling you the content type of any file.

If the Caddy passes through to Unraid the drive serial number then it will work fine with Unassigned Devices. It is easy using UD to set a script to run when the drive is inserted that could then do the backup.

that is a quirk of the way Unraid UserShares interact with the underlying Linux system and is mentioned in the User Shares part of the online documentation. If you had instead used Dynamix Fiile Manager to do this you would have gotten the expected result as that implements ‘move’ using a copy/delete strategy.

Have you rebooted yet? That should be the first step. I would recommend posting a copy of your diagnostics after doing that to see if we can spot anything.

You must never forward the Unraid GUI directly as you will almost certainly get hacked.. You should only do it either via Unraid Connect or using the built-in WireGuard VPN server.

The report does not look good - I would expect there to be quite a lot that ends up in the lost+found folder with cryptic names. and needs manually sorting out What is the state of your backups? Makes me wonder if parity is good and it might be better to try and get that drive emulated and then repair the emulated drive? Any thoughts @JorgeB

Good chance rebooting will clear that as the location is in RAM, but you should post your diagnostics to let us give more informed feedback. Is you sever exposed to the internet? Unraid is not hardened enough to be directly exposed to the internet.