Skip to main content

Why won't TNAS disks hibernate?

Disk hibernation is one of the core functions of TOS, which can save energy and reduce noise, as well as reduce disk idling wear and extend service life. When the disk has no data reading or writing and no background tasks running within the set idle time, it will automatically enter a low-power hibernation state. The failure of TNAS disks to hibernate automatically is not a hardware failure, but is mostly caused by background services, applications, system tasks, or external device interference. This guide will help you quickly determine the hibernation state and troubleshoot the root cause of the problem, even for beginners.

Applicable models​

All models

I. Important notes

  1. New file system initialization delay: A newly created file system needs to complete the initialization process, during which the disk cannot hibernate. The specific duration depends on the disk capacity: the Btrfs file system takes 24-48 hours to complete log and balance operations; the ext4 file system takes 12-24 hours to complete delayed initialization. If a large number of files are copied during initialization, the time taken will be extended accordingly. If you need more information about logs and balance, please visit https://wiki.archlinux.org/index.php/Btrfs
  2. Hibernation indicator light: After the disk enters the hibernation state, the device disk indicator light will remain solid on, not off. Do not misjudge the hibernation state by the light or darkness of the indicator light.
  3. Hibernation state judgment method: Touch the body of the TNAS device with your hand. If you cannot feel the vibration of the disk running, it means the disk has successfully entered hibernation mode; if there is continuous obvious vibration, it is in a non-hibernating state.

II. Troubleshooting the causes of hibernation failure

(I) Desktop​

  • Debug mode: Once enabled, the system needs to continuously write debug logs, occupying disk read and write.
  • Global search: If index folders have been added, accessing them will automatically update the index files.
  • Security advisor: During scanning, various system services will be detected, waking up the disk.

(II) File management​

  • Accessing file management: The system needs to read file-related information during access.
  • Performing various file operations: Uploading, downloading, moving, or copying files will trigger disk operation.

(III) Storage management​

  • Accessing storage management: Real-time query of disk status information is required during access.
  • The volume is in a degraded, crashed, or abnormal repair state, and the system continues background self-checking, making it impossible to trigger hibernation.
  • No volume has been created on the device, and the disk is continuously in a standby running state.
  • External USB devices: The reading and writing of USB storage devices or the system identification process will indirectly wake up the disk.
  • Memory usage overload triggers disk virtual memory swapping (insufficient RAM capacity, disk temporarily acts as cache).

(IV) Access permissions​

  • Domain: TNAS communicates continuously with the server when running as a domain/LDAP client.

(V) Network services​

  • Enable IPv6: Device network broadcast behavior will wake up the disk from hibernation.
  • File sharing services: After enabling SMB, FTP, NFS, Rsync, or WebDAV, broadcast packets and device detection in the local area network will wake up the disk.
  • Windows Media Player network sharing service is enabled in the local area network, triggering continuous response from the disk.
  • Remote management services: After enabling SSH, Telnet, or SNMP, network requests need to be continuously monitored.
  • Enable VPN: Background network processes run continuously.
  • Enable media indexing: The system background continuously updates index files.
  • Remote access services: Enabling DDNS domain name resolution or TNAS.online remote access continuously synchronizes data.

(VI) General settings​

  • Enable NTP service: Regularly synchronize with the network time server.
  • Custom scheduled tasks: Tasks such as emptying the recycle bin or scheduled scripts.

(VII) System information​

  • Access "System Information >> Device Monitoring": Needs to obtain disk operation data in real time.
  • Enable continuous resource monitoring: The disk needs to continuously write monitoring data to the disk.

(VIII) Clients​

  • TNAS PC: Searching for devices or accessing devices remotely.

(IX) Applications​

  • Cloud synchronization applications: CloudSync and other cloud disk synchronization tools continuously synchronize data in the background.
  • Download applications: Transmission, qBittorrent, Aria2, and other tools have background processes running continuously even when there are no download tasks.
  • Media service applications: Plex Media Server, Emby Media Server, and DLNA services continuously scan files and respond to playback requests.
  • System utility applications: DNS server, proxy server, mail server, and VirtualBox virtual machine run constantly in the background.
  • Various third-party applications: Some installed applications will continuously read and write to the disk (such as Docker containers, database services).

III. Quick Troubleshooting Steps

Step 1: Wait for system initialization: After a new disk, a new storage volume, or a large number of files have been copied, wait patiently for 12-48 hours to complete the system background initialization. Avoid frequent operation of the device during this period.
Step 2: Remove all external devices: Unplug all USB devices connected to the TNAS, such as USB flash drives and mobile disks, to eliminate interference from external storage.
Step 3: Close background third-party applications: Pause or exit permanent background applications such as Docker, download tools, media servers, and CloudSync. These are the most common interferences.
Step 4: Disable non-essential system services: Temporarily disable non-core services such as IPv6, VPN, DDNS, and NTP, keeping only basic file sharing functions. These can be reopened as needed later.
Step 5: Static verification of hibernation: Stop all device operations, wait for the device to reach the preset hibernation duration, and touch the body to feel for vibration. No vibration means successful hibernation.

IV. Special emergency solution

If you need to use the above services and applications daily and do not want to close them but want to achieve energy saving, you can use the scheduled power on/off function to replace disk hibernation: In the TOS system settings, configure fixed power-on and power-off time periods. Turning off the device directly during non-use periods saves energy and protects the disk, completely avoiding background process interference issues.

V. After-sales feedback

If the disk still cannot hibernate after troubleshooting according to the above steps, please submit after-sales feedback directly according to the following process.

  1. Open the TOS desktop, go to Technical Support >> Problem Feedback, and generate a system diagnostic report.
  2. Send the report to the official after-sales email: support@terra-master.com .
  3. The after-sales team will analyze the report as soon as possible and reply with an exclusive solution via email.