[[6.5.3] - HDD temperatures not correctly updated]

There can be a delay before the GUI is updated.   What do you have under Settings->Disk Settings->Tunable (poll_attributes) ?    The default value of 1800 means that the disks are only polled every 30 minutes.  You may want a much smaller value - something like 300 (5 minutes) is what I use.

[Unraid OS version 6.6.0-rc2 available]

Upgrade from rc1 appears to have gone through without issue.  

 

Well timed as I was just about to report the issue with dockers not updating!

[[6.5.3] Mover appears to be non-atomic and loses writes]

8 hours ago, testdasi said:

Wow, does this mean the mover is not to be trusted until the bug is fixed? ?

This is one of those issues that while genuine is very hard to reproduce in practice.   The timing window for hitting this error will be very narrow so probably not an issue for most people in typical usage..    Definitely will not be an issue if running mover at its default of early morning when nobody is likely to be using the server.

[[6.5.3] unRaid trying to move a file of 107GB from cache to a disk with 106GB free]

It is not a bug in unRAID but the way it is designed to work.   The problem is that once the free space disk drops below the value then unRAID stops copying new files to the drive.    

 

i think you are probably going to have to manually copy these very large files directly to the target disk (which bypasses the Minimum Free Space setting) or you are going to have to add a lot more disk space.

[[6.5.3] unRaid trying to move a file of 107GB from cache to a disk with 106GB free]

What value do you have for Minimum Free Space?    It needs to be larger than the file you are trying to copy.  That is the only way you will get mover to select the correct disk.   The problem is that is not mover that selects the disk (and can thus take into account the file size) but the underlying unRAID disk handler.

[[6.5.3] unRaid trying to move a file of 107GB from cache to a disk with 106GB free]

Unfortunately that is not how unRAID currently works.     If non of your disks have enough free space for the file then you have a problem as unRAID will never split a file across disks.

[[6.5.3] unRaid trying to move a file of 107GB from cache to a disk with 106GB free]

You need to have the Minimum Free Space value for the share to be larger than the largest file you will be copying.    That stops a disk with less than that amount of free space from being selected as the target by mover.

[[6.5.0] Upgrade to 6.5.1]

I would it is time to update the minimum requirement for unRAID v6 to be 2GB?

[CPU load not displayed]

@digitalfixerIf you are running any sort of adblocker, have you made sure that the unRAID server has been whitelisted?    Adblockers are notorious for interfering with the correct functioning of the unRAID GUI.