Skip to main content

Why won't TNAS disks hibernate?

Disk hibernation is a core feature of TOS, which helps save energy, reduce noise, minimize disk idle wear, and extend lifespan. When a disk experiences no data read/write and no background tasks within the configured idle time, it will automatically enter a low-power hibernation state. If TNAS disks fail to hibernate automatically, it is not a hardware fault—it is usually caused by interference from background services, applications, system tasks, or external devices. This guide will help you quickly determine the hibernation state and troubleshoot the root cause, even for beginners.

Applicable Models​

All models

I. Important Notes​

  1. New file system initialization delay: A newly created file system must complete its initialization process before the disk can hibernate. The duration depends on the disk capacity: Btrfs file systems require 24–48 hours to complete journaling and Balance operations; ext4 file systems require 12–24 hours for deferred initialization. Copying a large number of files during initialization will extend this time accordingly. For more information on journaling and Balance, visit https://wiki.archlinux.org/index.php/Btrfs
  2. Hibernation indicator light tips: After the disk enters hibernation, the device disk indicator remains steadily lit rather than turning off. Do not misjudge the hibernation state based on the brightness of the indicator light.
  3. How to check hibernation state: Gently touch the TNAS device casing with your hand. If you feel no disk vibration, the disk has successfully entered hibernation mode; if you feel persistent noticeable vibration, it is not hibernating.

II. Troubleshooting Disk Hibernation Issues​

(I) Desktop​

  • Debug mode: When enabled, the system continuously writes debug logs to the disk.
  • Global search: When an indexed folder has been added and file indexing is in progress, the system scans files and writes to the index database.

(II) File Management​

  • Accessing File Management: When browsing file lists, the system needs to read file metadata.
  • File operations: Uploading, downloading, moving, or copying files generates data read/write activity.

(III) Storage Management​

  • Accessing Storage Management: When viewing storage status, the system queries disk health and status information in real time.
  • RAID repair: When a degraded array has a hot spare triggering rebuild, the system performs substantial data sync read/write operations.
  • Memory swapping: When physical memory is insufficient, the system uses swap partitions, causing the disk to perform read/write as virtual memory.

(IV) Access Permissions​

  • Domain: When using TNAS as a domain/LDAP client, authentication and communication with the server generate a small amount of log read/write.

(V) Network Services​

  • File sharing: When SMB, FTP, NFS, Rsync, WebDAV and other services are enabled and files are accessed via these protocols.
  • Remote management: When SSH, Telnet, SNMP and other services are enabled for remote login or status queries.
  • Media indexing: When file indexing is in progress, the system scans files and writes to the index database.

(VI) General Settings​

  • NTP service: When enabled, the system periodically synchronizes with network time servers.
  • Scheduled tasks: When executing timed tasks such as emptying the recycle bin or running custom scripts.

(VII) System Information​

  • Device monitoring: When accessing the "System Information >> Device Monitoring" page, disk status is read in real time.
  • Resource monitoring: When continuous resource monitoring is enabled, the system periodically writes monitoring data to the disk.

(VIII) Client​

  • TNAS PC: When logging in and accessing the device via the TNAS PC client.

(IX) Applications​

  • Sync apps: TerraSync, CloudSync, and similar apps during data synchronization.
  • Backup apps: Centralized Backup, Duple Backup, USB Copy, TFM Backup, and similar apps during backup tasks.
  • Download apps: Transmission, qBittorrent, Aria2, and similar apps during download tasks.
  • Media services: Plex, Emby, DLNA, and similar apps while scanning media libraries.
  • System tools: DNS server, proxy server, mail server, VirtualBox virtual machines, and other persistent background services.
  • Third-party apps: Continuous read/write generated by certain installed apps during operation (e.g., Docker containers, database services).

III. Quick Troubleshooting Steps​

Step 1: Wait for system initialization: After installing a new disk, creating a new storage volume, or copying a large number of files, patiently wait 12–48 hours for system background initialization to complete. Avoid frequent device operations during this period.
Step 2: Remove all external devices: Unplug all USB devices connected to the TNAS, such as USB flash drives and external hard drives, to eliminate external storage interference.
Step 3: Close background third-party apps: Pause or exit persistent background apps such as Docker, download tools, media servers, and CloudSync—these are the most common interference sources.
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 re-enabled later as needed.
Step 5: Verify hibernation by letting it idle: Stop all device operations, wait for the device to reach the preset hibernation timeout, then gently touch the casing to feel for vibration. No vibration means successful hibernation.

IV. Special Emergency Solution​

If you need to use the above services and apps on a daily basis and do not want to disable them but still wish to save energy, you can use the scheduled power-on/off feature as an alternative to disk hibernation: In TOS system settings, configure fixed power-on and power-off time periods. The device will be shut down during idle periods, saving energy while protecting the disks and completely avoiding background process interference.

V. After-Sales Feedback​

If after completing all the above troubleshooting steps the disk still cannot hibernate, submit after-sales feedback directly following the steps below.

  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: [email protected].
  3. The after-sales team will analyze the report promptly and reply with a tailored solution via email.