This 20TB hard drive is a Western Digital model, while the others are all 4TB drives. All 4TB drives can enter sleep mode normally. Previously, on version 6.12, this 20TB drive also could spin down. However, after upgrading to version 7.01, this 20TB drive can no longer enter sleep mode.‌  

docker & VMS were turn off. 

Installed "File Activity" but no programs are detected accessing it‌。

On the main interface, only this hard drive's read/write activity indicator is blinking.

 

strange is when ‌manually putting all HDD into sleep mode‌ causes only this 20T drive to wake up when a particular Docker container is activated, despite no explicit association between the container and the drive‌r. Other disks remain in sleep state during this process‌.

 

Please post the diagnostics.

17 hours ago, JorgeB said:

Please post the diagnostics.

this is my diagnostics,thank you.

hua-unraid-diagnostics-20250407-1843.zip

Appdata, system and domains shares exist on disk6, so if docker or VM services are running, it may never spin down, those shares so typically exist on a pool, or at least a single array disk.

15 hours ago, JorgeB said:

Appdata, system and domains shares exist on disk6, so if docker or VM services are running, it may never spin down, those shares so typically exist on a pool, or at least a single array disk.

 

I've already taken all these into consideration and completely removed disk6 from the storage pool. After shutting down all Docker containers and VMs, the issue still persists.‌

You don't have parity?

 

Disk1 is an SSD. SSDs in the array cannot be trimmed. And can only be written at parity speed (I guess not currently relevant if you have no parity). SSDs normally would be used in pools instead of the array.

 

8 minutes ago, shanehua said:

completely removed disk6 from the storage pool. After shutting down all Docker containers and VMs, the issue still persists.‌

Was disk6 not the disk you were concerned with? In what way does the issue persist without disk6?

 

Post new diagnostics.

10 minutes ago, shanehua said:

shutting down all Docker containers and VMs, the issue still persists.‌

shutting down all individual containers and all individual VMs does not shut down Docker and VM services. These are in Settings - Docker and Settings - VM Manager.

16 hours ago, JorgeB said:

if docker or VM services are running

 

10 hours ago, trurl said:

You don't have parity?

 

Disk1 is an SSD. SSDs in the array cannot be trimmed. And can only be written at parity speed (I guess not currently relevant if you have no parity). SSDs normally would be used in pools instead of the array.

 

Was disk6 not the disk you were concerned with? In what way does the issue persist without disk6?

 

Post new diagnostics.

 

This time I confirmed that disk6 was excluded from the storage pool‌, and both Docker services and virtual machine functionalities were disabled‌（Disabled the Docker and virtual machine features in the settings menu.).  disk6 can spinning down,but i setting docker functionalities enable. disk6 turn on immediate.

Strange, I've already excluded DISK6 from the storage pool, and there are no files or Docker-related content on DISK6. The read/write values are gradually increasing

this is my new diagnostics,thank you. 

 

hua-unraid-diagnostics-20250408-2157.zip

Edited April 8, 20251 yr by shanehua

42 minutes ago, shanehua said:

I've already excluded DISK6 from the storage pool

I don't really understand what exactly you mean by this.

 

And still this:

On 4/7/2025 at 7:10 AM, JorgeB said:

Appdata, system and domains shares exist on disk6

appdata                           shareUseCache="no"      # Share exists on disk1, disk6
domains                           shareUseCache="no"      # Share exists on disk1, disk6
system                            shareUseCache="no"      # Share exists on disk1, disk6

You can see this yourself by browsing into disk6 with Dynamix File Manager.

17 hours ago, trurl said:

I don't really understand what exactly you mean by this.

 

And still this:

appdata                           shareUseCache="no"      # Share exists on disk1, disk6
domains                           shareUseCache="no"      # Share exists on disk1, disk6
system                            shareUseCache="no"      # Share exists on disk1, disk6

You can see this yourself by browsing into disk6 with Dynamix File Manager.

this is my share setting,appdata;domains,system,excluded DISK6,

That won't help now, since the disk already has files, you would need to move then first.

Also, there is never any good reason to set BOTH Include and Exclude.

 

Include already excludes all disks not listed for inclusion.

 

Exclude already includes all disks not listed for exclusion.

 

Use one or the other.

4 hours ago, JorgeB said:

you would need to move then first.

Nothing can move open files.

 

Disable Docker and VM Manager in Settings.

 

Set appdata, domains, and system shares to Primary:nvme; Secondary;array; Mover action:array->nvme

 

Run mover, wait for it to complete, post new diagnostics.