itimpi

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.

If you did tis before the rebuild completed then the rebuild would be started again from the beginning.

The end of both logs finishes with errors along the lines of: Apr 22 08:33:48 Tower kernel: ata14.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 Apr 22 08:33:48 Tower kernel: ata14.00: irq_stat 0x40000001 Apr 22 08:33:48 Tower kernel: ata14.00: cmd a0/01:00:00:00:01/00:00:00:00:00/a0 tag 7 dma 16640 in Apr 22 08:33:48 Tower kernel: opcode=0x12 12 01 80 00 ff 00res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x3 (HSM violation) Apr 22 08:33:48 Tower kernel: ata14: hard resetting link Normally we would think these were power/sata cabling related but the fact it has occurred at the same point twice suggest it may really be a drive problem if ata14 is the new drive.

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. I strong;y suspect that you have something incorrectly configured. It seems unlikely that mover will report files ‘exists’ when it does not so I suspect that you do not have things set up correctly to get the behaviour you want.

You may find this section of the 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 useful in understanding what is happening and what actions to take.

Have you tried clicking on the orange icon for the drive on the Dashboard to see what error it is? If it is a CRC error then if you. Lick on the Acknowledge option Unraid will only notify you again if it increases. CRC errors are connection related rather than a disk problem and would be triggering retries. They never reset to 0. Occasional CRC errors is not really something to worry about but if you get lots of them you should look into the power and SATA cabling to the drive as the most likely culprits.