itimpi

The fact that drives are doing a parity sync should be irrelevant. You do not mention what type of SMART error it is and since you did not post your system's diagnostics (which includes amongst other things SMART reports for your drives) we cannot look for ourselves to see if there appears to be genuine problem.

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.

No - you DO get all Unraid features (including VMs and Docker) and keep your lifetime update status. All releases of Unraid are functionally equal, and the web site should make this clearer.

You have this in your syslog: Apr 23 09:32:36 Tower root: Fix Common Problems: Error: Macvlan and Bridging found so it appears you are using macvlan for docker networking. If using macvlan then for stability you need to disable bridging on eth0. The alternative is to use ipvlan for docker networking.

You could try installing the nVidia Drivers plugin. Whether it supports that card or not I have no idea.

Did you get an automated acknowledgement of your request?

Do you have any drives showing as unmountable as if you have any files on those drives will not currently be available? 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.

That is what most people seem to use for pools although it is not mandated.

Except that Limetech has already explicitly said that they intend a Lifetime subscription to remain valid forever and they do not intend to do that behavior of a 'new' version' that you then have to pay for. Unraid 7 and Unraid 8 were given as examples of free upgrades for lifetime licences in the various podcasts on this subject.

Yes that drive will be kept spinning any time docker is running. Most people tend to put the docker.img file onto a pool (cache) by configuring the 'system' share appropriately. This stops keeping the array drive spinning and also improves performance.

Looks like you might be falling foul of the behaviour described in the Caution in this section of the online documentation accessible via the Manual link at the bottom of the Unraid GUI. Not sure there is much that can be done about it as it is a quirk of the way Linux handles move operations. If you can configure the docker container to use Copy/Delete instead of 'move' then you would get the result you expected. The alternative is to set that share to have the 'downloads' pool as its primary storage.

You will have to contact support as they are the only ones who can handle licence issues.

Yes, but it is unreasonable to expect a small company like Limetech to continue to support obsolete versions of their software forever i think the Limetech policy is significantly more generous than I have seen offered on many other products..

It is not quite that simple. You get any security updates that are available for the release you are on at the end of the years paid update period. What you do not get is security updates that are only available in future releases. As an example Limetech says that if when your update support period expires you are on 7.0.x then you get all updates for the 7.0.x releases even though you have not taken out another years of updates support. While Limetech is working on and releasing the next release beyond your current one (i.e. 7.1.x releases) then they will (if possible apply patches to the 7.0.x releases. Once they start releasing the second release beyond yours (i.e. the 7.2.x releases) then the 7.0.x releases will no longer get any more updates. At any point you can decide to take out another year of update support and then you the update to the release current at that time, and after another year the same principle as outlined above applies (which could be you being on a later release than you started the year on).

With high-water allocation then the relative size of disks can become relevant as the high-water cutover points are based on the largest drive but your screenshot does not show the sizes so we cannot see if the behaviour is what should be expected.