How to Reduce UGREEN NAS Power Consumption
Hard drive sleep provides the most practical power reduction when your UGREEN NAS must remain available but its mechanical drives have long idle periods.
Scheduled shutdown saves more when nobody needs the NAS, its applications, or its backup tasks during predictable hours.
Start With the Power State That Fits Your NAS
The right strategy depends on what your NAS does when nobody is actively opening files.
| How you use the NAS | Best starting point | Main limitation |
|---|---|---|
| Backups, remote access, Plex, Docker, virtual machines, Home Assistant, surveillance, or iSCSI run continuously | Keep the NAS on and test Hard Drive Sleep | Background disk activity may prevent the drives from sleeping |
| The NAS is used only during predictable daytime hours | Schedule automatic startup and shutdown | Overnight backups, applications, and remote access will be unavailable |
| The NAS is used occasionally as an archive | Shut it down between sessions | Automatic backups cannot run while it is off |
| Drives enter sleep but wake repeatedly | Identify the task causing the wake-up | A short sleep timeout may save little power |
| The NAS uses only SSD storage | Reduce background workloads or schedule shutdown | Hard Drive Sleep does not apply to SSDs |
Hard Drive Sleep leaves UGOS Pro and the NAS itself running. Only eligible mechanical drives enter a lower-power state. Any application or client that needs data from those drives will wake them.
A scheduled shutdown turns off the entire NAS. It saves more power, but it also stops every backup, container, media server, synchronization task, and remote-access service.
Enable Hard Drive Sleep in UGOS Pro
Hard Drive Sleep works best when the NAS must remain online but its HDDs have long periods without reads or writes.
In UGOS Pro, open:
Control Panel > Hardware & Power > Power > Hard drive sleep
Then configure the setting:- Select all eligible drives or choose specific drives.
- Set the automatic sleep period.
- Choose the wake-up strategy.
- Enable the hard-drive sleeping log.
- Apply the settings.
If your NAS is used in bursts with long gaps between them, 20 minutes is a reasonable initial test. It is not the right interval for every workload. If the log shows that drives repeatedly sleep and wake, lengthen the interval or leave them active during your busy hours.
UGOS Pro provides two wake-up strategies:
- Sign-in: The selected drives wake when a user signs in.
- On-demand: The drives remain asleep until a request requires access to their data.
On-demand wake-up can preserve longer sleep periods, but the first file request will take longer while the drives spin up. That delay is normal.
Hard Drive Sleep Does Not Apply to SSDs
Internal SSDs do not use the Hard Drive Sleep control because they have no mechanical platters to stop.
An all-SSD NAS can still reduce power use by stopping unnecessary applications or shutting down during genuine off-hours. Adding an SSD cache to an HDD-based NAS does not guarantee lower power use. The SSD consumes power, and background tasks may continue waking the HDD pool.
Do not add SSD cache solely as an energy-saving measure.
External USB Drive Sleep
UGOS Pro also provides sleep controls for supported external USB drives. Whether an external drive sleeps successfully also depends on the USB enclosure and its controller.
External USB sleep uses similar drive-selection, timeout, and wake-up controls, but it does not provide the same sleep log available for internal HDDs. If an external drive remains active, test the setting with the enclosure manufacturer’s supplied cable and check whether that enclosure supports drive sleep commands.
Find the Task That Keeps Waking the Drives
Enabling Hard Drive Sleep does not stop applications from accessing the storage pool. A scheduled task that reads or writes one small file can wake the drives and restart the idle timer.
Start with the hard-drive sleep log. Compare every wake-up time with backup, synchronization, indexing, download, and application schedules.
| What you observe | Likely cause | What to check |
|---|---|---|
| Drives wake at the same time each day | Scheduled backup, synchronization, scan, or maintenance task | Compare the sleep log with scheduled jobs |
| Drives stopped sleeping after an application was installed | A container or virtual machine is writing logs, databases, or application data to the HDD pool | Stop the application temporarily and test again |
| Drives wake even when nobody is opening files | Photo indexing, media-library scanning, downloads, monitoring, or client-side indexing | Disable one task at a time and review the next wake-up |
| Plex or Jellyfin is idle but the drives still wake | Library scans, metadata updates, thumbnail generation, or application logs | Review the application schedule and data-folder location |
| Drives connected to an iSCSI LUN never sleep | The initiator maintains a persistent block-storage session | Pause or disconnect the iSCSI connection before expecting hibernation |
| An external USB drive never sleeps | Its enclosure may not pass or support the sleep command | Test the enclosure separately and review its power behavior |
| Drives alternate between sleeping and waking throughout the day | The timeout is too short for the workload | Lengthen the idle period or disable sleep during active hours |
Other computers can also trigger access. Thumbnail generation, antivirus scanning, search indexing, and monitoring software may read a mapped network folder without someone deliberately opening a file.
Scheduled S.M.A.R.T. tests, data-consistency checks, and other storage maintenance can also wake the drives. These tasks protect the storage pool and should not be disabled merely to obtain a lower power reading. Schedule them during a defined maintenance window instead.
Moving Application Data to SSD Storage
On a model that supports M.2 storage pools, moving suitable container databases, logs, or application data away from the HDD pool may allow the mechanical drives to remain asleep longer.
This is a workload decision, not a guaranteed power-saving method. The SSD and application continue to consume electricity, and applications may still access media or other files stored on the HDD pool.
Use Scheduled Shutdown During True Off-Hours
If nobody needs the NAS overnight or during another predictable period, scheduled shutdown provides a clearer saving than repeatedly waking and sleeping the drives.
In UGOS Pro, open:
Control Panel > Hardware & Power > Power > Scheduled startup and shutdown
To create a schedule:
- Add a new scheduled action.
- Select Shutdown.
- Choose every day, weekdays, weekends, or custom dates.
- Set the shutdown time.
- Add a corresponding Boot schedule if the NAS should start automatically.
- Click Apply.
Before enabling the schedule, confirm that the NAS is not expected to perform any of these jobs while it is off:
- Computer or phone backup
- NAS-to-cloud backup
- File synchronization
- Remote file access
- Plex, Jellyfin, or another media service
- Docker containers or virtual machines
- Home Assistant or another smart-home service
- Surveillance recording
- Downloads
- iSCSI storage for another computer or server
Set the startup time early enough for UGOS Pro, storage pools, and applications to become available before the first user or scheduled job needs them.
Do not use a basic smart plug to cut power to a running NAS. An abrupt loss of power can interrupt writes and leave the storage pool in an inconsistent state. UGOS Pro’s scheduled shutdown closes services and storage cleanly.
A UPS remains valuable even when the NAS uses a shutdown schedule. It protects the system from unexpected outages and gives UGOS Pro time to complete a controlled shutdown. See our guide to protecting a NAS from power outages for the correct role of battery backup.
Remove Workloads That Run Without a Purpose
Once sleep and shutdown settings are correct, review what the NAS is doing during supposedly idle periods.
Stop Unused Applications
Shut down Docker containers and virtual machines that no longer serve a purpose. Even an application with little CPU activity can write logs, update a database, or check files often enough to keep the storage pool awake.
Do not stop a service solely because it appears inactive in the dashboard. First confirm that it is not responsible for backups, authentication, remote access, monitoring, or another required function.
Give Recurring Jobs a Maintenance Window
Scattering backup, indexing, synchronization, and scanning jobs throughout the night leaves no uninterrupted idle period.
Place recurring tasks within a deliberate maintenance window where practical. For example, a backup can run first, followed by media indexing and then a scheduled drive-health test. Once the work finishes, the drives have a longer opportunity to sleep.
This does not make the jobs themselves use less energy. The saving comes from creating a longer period in which the drives remain asleep or the entire NAS can shut down.
Safely Disconnect Unused External Devices
USB hard drives and other bus-powered devices can draw power whenever they remain connected.
Use UGOS Pro to eject an external storage device before disconnecting it. Never unplug a drive during a transfer, backup, or filesystem operation.
Keep Cooling Efficient
Blocked vents, accumulated dust, and a hot enclosed cabinet can make the fan work harder. Keep the intake and exhaust clear, leave space behind the NAS, and follow the UGREEN NAS maintenance checklist.
The goal is safe airflow, not the lowest possible fan speed. Do not restrict ventilation or modify the enclosure to save a small amount of fan power.
Consider Drive Count When Planning Future Capacity
Each installed HDD adds its own idle and active power draw. Fewer high-capacity drives can therefore consume less power than a larger number of smaller drives.
That does not justify rebuilding a healthy storage pool solely to save a few watts. Bay count, usable capacity, fault tolerance, rebuild risk, noise, and independent backup are more important. Apply drive consolidation when planning a future expansion or replacement, and choose compatible NAS drives for the workload.
Do not choose a RAID level primarily for power savings.
Conclusion
The useful result is not the lowest possible wattage. It is lower measured consumption without sacrificing the availability, backup, and data-protection jobs the NAS was purchased to perform.
