Hard drives spindown issues - Revision history

Admin at 03:04, 18 February 2016

2016-02-18T03:04:42Z

Admin at 03:03, 18 February 2016

2016-02-18T03:03:33Z

Admin at 03:02, 18 February 2016

2016-02-18T03:02:43Z

Admin: Created page with "= Aspects of harddisk spindown problems
= #Harddisk(s) do spin down after the configured timeout, but show unwanted regular wake ups, without being accessed from clients..."

2015-06-18T07:33:51Z

Created page with "= Aspects of harddisk spindown problems = #Harddisk(s) do spin down after the configured timeout, but show unwanted regular wake ups, without being accessed from clients..."

New page

= Aspects of harddisk spindown problems =

#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 

 

= 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 =

#Download the diagnostic program from one of the following links:
#:*ftp://csdread:csdread@ftp.qnap.com/NAS/spindown/blkdevMonitor.sh
#:*http://eu1.qnap.com/Storage/tsd/spindown/blkdevMonitor.zip
#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:
#:*http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
#After login, copy the blkdevMonitor.sh script to root folder by the following command:
#:<pre>cp /share/Public/blkdevMonitor.sh /root</pre>
#Change the file to be executable by the following command:
#:<pre>chmod 766 /root/blkdevMonitor.sh</pre>
#Run the program by the following command:
#:<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.

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
*http://us1.qnap.com/Storage/tsd/spindown/spindown_detection_instruction.zip

 

[[Category:HDD_Spin_Down_(HDD_Standby)]]

@@ Line 25: / Line 25: @@
+<ol start="2">
-#Copy the program to the Public folder of the NAS
+<li>Copy the program to the Public folder of the NAS</li>
-#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:
+<li>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:
-#:
+:</li>
 *[http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html]
-<ol start="3">
+<ol start="4">
 <li>After login, copy the blkdevMonitor.sh script to root folder by the following command:
 :<pre>cp /share/Public/blkdevMonitor_20151225.sh /root</pre>
 </li>
 </ol>
-<ol start="4">
+<ol start="5">
 <li>Change the file to be executable by the following command:
 :<pre>chmod 766 /root/blkdevMonitor_20151225.sh</pre>
 </li>
 </ol>
-<ol start="5">
+<ol start="6">
 <li>Run the program by the following command:
 :<pre>/root/blkdevMonitor_20151225.sh</pre>
 </li>
 </ol>
-<ol start="6">
+<ol start="7">
 <li>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.</li>
 </ol>
 [[Category:HDD Spin Down (HDD Standby)]]

@@ Line 20: / Line 20: @@
 #Download the diagnostic program from the following links:
-<span style="line-height: 1.6;">https://drive.google.com/file/d/0B8u8qWRYVhv0S1ozWFRjazFEX1E/view?usp=sharing</span>
+<span style="line-height: 1.6;">[https://drive.google.com/file/d/0B8u8qWRYVhv0S1ozWFRjazFEX1E/view?usp=sharing https://drive.google.com/file/d/0B8u8qWRYVhv0S1ozWFRjazFEX1E/view?usp=sharing]</span>
+:
@@ Line 28: / Line 29: @@
 #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 http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html]
-#After login, copy the blkdevMonitor.sh script to root folder by the following command:
+<ol start="3">
-#:<pre>cp /share/Public/blkdevMonitor_20151225.sh /root</pre>
+<li>After login, copy the blkdevMonitor.sh script to root folder by the following command:
 :<pre>cp /share/Public/blkdevMonitor_20151225.sh /root</pre>
-#Change the file to be executable by the following command:
+</li>
-#:<pre>chmod 766 /root/blkdevMonitor_20151225.sh</pre>
+</ol>
+<ol start="4">
-#Run the program by the following command:
+<li>Change the file to be executable by the following command:
-#:<pre>/root/blkdevMonitor_20151225.sh</pre>
+:<pre>chmod 766 /root/blkdevMonitor_20151225.sh</pre>
+</li>
-#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.
+</ol>
+<ol start="5">
+<li>Run the program by the following command:
 [[Category:HDD Spin Down (HDD Standby)]]

@@ Line 1: / Line 1: @@
-= Aspects of harddisk spindown problems<br>  =
+= Aspects of harddisk spindown problems =
-#Harddisk(s) do spin down after the configured timeout, but show unwanted regular wake ups, without being accessed from clients<br>
+#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<br>
+#Harddisk(s) wont spin down at all
-Manually check QNAP&nbsp;configuration:
+= Find processes causing regular wake ups of hard drives =
-*Several QNAP&nbsp;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
+Manually check QNAP&nbsp;configuration:
-<br>
+*Several QNAP&nbsp;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
-Instructions in PDF and a sample of result can be found on one of the links:
+= Find processes preventing hard drives from spindown =
-*ftp://csdread:csdread@ftp.qnap.com/NAS/spindown/How%20to%20know%20which%20process%20prevents%20the%20NAS%20HDD%20from%20spindown.pdf
+#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.
-[[Category:HDD_Spin_Down_(HDD_Standby)]]
+[[Category:HDD Spin Down (HDD Standby)]]

Hard drives spindown issues - Revision history

Admin at 03:04, 18 February 2016

Admin at 03:03, 18 February 2016

Admin at 03:02, 18 February 2016

Admin: Created page with "= Aspects of harddisk spindown problems = #Harddisk(s) do spin down after the configured timeout, but show unwanted regular wake ups, without being accessed from clients..."

Admin: Created page with "= Aspects of harddisk spindown problems
= #Harddisk(s) do spin down after the configured timeout, but show unwanted regular wake ups, without being accessed from clients..."