i have bought a zimacube a few weeks ago and am so happy with the built quality, support and great community.
i installed 2 nvme’s (where i install my docker database using migration setting) and 6 hdds in raid5 that i use only for storage (user database).
the hdds never go to sleep even though there is no resource that is actively using them to my knowlwdge.
i tried disabling all dockers but the issue persists.
there is also no insight on what process might be accessing them and preventing them to go to standby which i set up for 20m.
this is a major issue of the os and needs to be solved asap.
is there a way to find out what might be accessing the drives preventing them to sleep?
currently i am thinking of ditching zimaos for unraid (which i used in the past and has a great hdd sleep function) for this exact reason.
Hello t1ll1s, thank you very much for your feedback. We attach great importance to your feedback and that of other users. We have also made a series of optimizations discussed above in the upcoming version v1.3.2. It is currently under intensive testing and will be released soon. The optimizations to be covered will be:
Simplify the health check logic
a. Unenabled hard disks are only checked once at startup
b. Enabled hard disks are checked every 1 hour (not in standby status)
Disk data cache refresh interval optimization
a. Optimized to trigger only after a disk change is found
No longer try to obtain disk information of standby disks
a. Previously, some users reported that standby disks do not display information, so try to obtain information of standby disks
b. Including but not limited to power-on time, temperature, etc. (some brands of hard disks have no cache, which will cause the hard disk to wake up)
In addition, considering the possibility of unknown application read and write access, we will also provide troubleshooting guidance for querying which services are accessing the disk.
You can check which process is accessing it by for pid in $(fuser -m <device_path> 2>/dev/null); do ps -p $pid -o comm=; done | uniq, <device_path> is the corresponding disk path, such as /dev/sda or /media/SDD-Storage.
You can check whether you can enter the hibernation state normally by trying to shut down some system services.
a. systemctl stop zimaos-local-storage (but it should be noted that after shutting down, some functions in the settings interface and Files application will be unavailable)
b. systemctl stop icewhale-files
If it still cannot be located, it may be caused by some kernel services.
