Find out which process prevents the hard drives from spindown: Difference between revisions

From QNAPedia
Jump to navigation Jump to search
No edit summary
No edit summary
Line 2: Line 2:


#Harddisk(s) do spin down after the configured timeout, but show unwanted regular wake ups, without being accessed from clients
#Harddisk(s) do spin down after the configured timeout, but show unwanted regular wake ups, without being accessed from clients
#Harddisk(s) wont spin down at all
#Harddisk(s) won't spin down at all




Line 21: Line 21:
#Copy the program to the Public folder of the NAS
#Copy the program to the Public folder of the NAS
#Login to the NAS by ssh port 22 with admin username/password. If you don’t know which ssh client should be used, you can try putty on the following link:<br/>[http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html]
#Login to the NAS by ssh port 22 with admin username/password. If you don’t know which ssh client should be used, you can try putty on the following link:<br/>[http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html]
#After login, copy the blkdevMonitor.sh script to root folder by the following command:
#After login, copy the blkdevMonitor.sh script to root folder by the following command:<br/>
#:<pre>cp /share/Public/blkdevMonitor.sh /root</pre>
<pre>cp /share/Public/blkdevMonitor.sh /root</pre>


#Change the file to be executable by the following command:
#Change the file to be executable by the following command:<br/>
#:<pre>chmod 766 /root/blkdevMonitor.sh</pre>
<pre>chmod +x /root/blkdevMonitor.sh</pre>


#Run the program by the following command:
#Run the program by the following command:<br/>
#:<pre>/root/blkdevMonitor.sh</pre>
<pre>/root/blkdevMonitor.sh</pre>


#Wait for a few minutes(depend on your spindown time settings) to see if any process is accessing the HDD (WRITE block or READ block) or not. Send us the result for us to check which process wake the HDD.
#Wait for a few minutes(depend on your spindown time settings) to see if any process is accessing the HDD (WRITE block or READ block) or not. Send us the result for us to check which process wake the HDD.


Instructions in PDF and a sample of result can be found on one of the links:
*[ftp://csdread:csdread@ftp.qnap.com/NAS/spindown/How%20to%20know%20which%20process%20prevents%20the%20NAS%20HDD%20from%20spindown.pdf ftp://csdread:csdread@ftp.qnap.com/NAS/spindown/How%20to%20know%20which%20process%20prevents%20the%20NAS%20HDD%20from%20spindown.pdf]
*[http://us1.qnap.com/Storage/tsd/spindown/spindown_detection_instruction.zip http://us1.qnap.com/Storage/tsd/spindown/spindown_detection_instruction.zip]
[[Category:HDD Spin Down (HDD Standby)]]
[[Category:HDD Spin Down (HDD Standby)]]

Revision as of 13:06, 18 November 2015

Aspects of harddisk spindown problems

  1. Harddisk(s) do spin down after the configured timeout, but show unwanted regular wake ups, without being accessed from clients
  2. Harddisk(s) won't spin down at all


Find processes causing regular wake ups of hard drives

Manually check QNAP configuration:

  • Several QNAP services (Twonky, Music Station, etc.) can enable regular cleaning jobs that wake up hard disks from spindown. Check the configuration of these services, if they are activated
  • Automatically synchronizing QNAPs NAS time with an internet timeserver can wake hard drives
  • Having the QNAP NAS obtain IP address(es) automatically using DHCP can wake hard drives several times a day. Using fixed IP addresses can prevent unwanted spin ups
    (careful when changing the network configuration, improper network reconfiguration can prevent further access to the NAS)


Find processes preventing hard drives from spindown

  1. Download the diagnostic program from one of the following links:
  2. Copy the program to the Public folder of the NAS
  3. Login to the NAS by ssh port 22 with admin username/password. If you don’t know which ssh client should be used, you can try putty on the following link:
    http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
  4. After login, copy the blkdevMonitor.sh script to root folder by the following command:
cp /share/Public/blkdevMonitor.sh /root
  1. Change the file to be executable by the following command:
chmod +x /root/blkdevMonitor.sh
  1. Run the program by the following command:
/root/blkdevMonitor.sh
  1. Wait for a few minutes(depend on your spindown time settings) to see if any process is accessing the HDD (WRITE block or READ block) or not. Send us the result for us to check which process wake the HDD.