No spindown anymore..

Discussion about hard drive spin down (standby) feature of NAS.
Post Reply
Rudi64
New here
Posts: 7
Joined: Tue Apr 15, 2014 1:18 am

No spindown anymore..

Post by Rudi64 »

I have bought a nice second hand HS-210 with a brand new WD RED 3T HDD.
Install it with the latest firmware, and as i just want to to use it for streaming my music
disabling most of the app and stations , just have Minimserver and java running.
Had set the standby to 5min everything was fine, but when setting the standby to 30min
it refused to spin down after that time. Reverting back to 5min, no spin down anymore...
I'm sure i have everything disabled, even Qcloud..
When back and forth to a old firmware HS-210_20160823-4.2.2, but no cure..
Any toughts, solutions :?: :?:
User avatar
dolbyman
Guru
Posts: 35024
Joined: Sat Feb 12, 2011 2:11 am
Location: Vancouver BC , Canada

Re: No spindown anymore..

Post by dolbyman »

follow this guide and post the results
https://wiki.qnap.com/wiki/Hard_drives_spindown_issues
Rudi64
New here
Posts: 7
Joined: Tue Apr 15, 2014 1:18 am

Re: No spindown anymore..

Post by Rudi64 »

dolbyman wrote:follow this guide and post the results
https://wiki.qnap.com/wiki/Hard_drives_spindown_issues
Will do ..
Forgot also to mentioned that even with the disks spinning the LCC
increases..
User avatar
dolbyman
Guru
Posts: 35024
Joined: Sat Feb 12, 2011 2:11 am
Location: Vancouver BC , Canada

Re: No spindown anymore..

Post by dolbyman »

disk or disks ?
Rudi64
New here
Posts: 7
Joined: Tue Apr 15, 2014 1:18 am

Re: No spindown anymore..

Post by Rudi64 »

dolbyman wrote:disk or disks ?
sorry, typo..just one disk
User avatar
dolbyman
Guru
Posts: 35024
Joined: Sat Feb 12, 2011 2:11 am
Location: Vancouver BC , Canada

Re: No spindown anymore..

Post by dolbyman »

risky business, you should think about another and RAID1
Rudi64
New here
Posts: 7
Joined: Tue Apr 15, 2014 1:18 am

Re: No spindown anymore..

Post by Rudi64 »

dolbyman wrote:risky business, you should think about another and RAID1
Yeah i know..but still have 2 backups outside the nas.
Logs running, and quite a lot of activity..
Rudi64
New here
Posts: 7
Joined: Tue Apr 15, 2014 1:18 am

Re: No spindown anymore..

Post by Rudi64 »

Here we go..

Code: Select all

[~] # cp /share/Public/blkdevMonitor_20151225.sh /root
[~] # chmod 766 /root/blkdevMonitor_20151225.sh
[~] # /root/blkdevMonitor_20151225.sh
===== Welcome to use blkdevMonitor_v2 on Fri Jun 16 17:57:38 CEST 2017 =====
Stop klogd.sh daemon... Done
Turn off/on VM block_dump & Clean dmesg
Countdown: 3 2 1
Start...
============= 0/100 test, Fri Jun 16 17:58:18 CEST 2017 ===============
<7>[ 1070.681642] java(9067): dirtied inode 128581636 (minimserver.log) on sda3
<7>[ 1070.681671] java(9067): dirtied inode 128581636 (minimserver.log) on sda3
<7>[ 1070.881594] java(9067): dirtied inode 128581636 (minimserver.log) on sda3
<4>[ 1075.680976] flush-8:0(1903): WRITE block 2843032 on sda (8 sectors)
<4>[ 1075.687297] flush-8:0(1903): WRITE block 2843040 on sda (8 sectors)
<4>[ 1076.021304] jbd2/sda3-8(2171): WRITE block 2930026776 on sda (8 sectors)
<4>[ 1076.028050] jbd2/sda3-8(2171): WRITE block 2930026784 on sda (8 sectors)
<4>[ 1076.034819] jbd2/sda3-8(2171): WRITE block 2930026792 on sda (8 sectors)
<4>[ 1076.041560] jbd2/sda3-8(2171): WRITE block 2930026800 on sda (8 sectors)
<4>[ 1076.048293] jbd2/sda3-8(2171): WRITE block 2930026808 on sda (8 sectors)
<4>[ 1076.085908] jbd2/sda3-8(2171): WRITE block 2930026816 on sda (8 sectors)
<4>[ 1081.131958] flush-8:0(1903): WRITE block 2120592 on sda (8 sectors)
<4>[ 1081.138270] flush-8:0(1903): WRITE block 2128800 on sda (8 sectors)
<4>[ 1081.144599] flush-8:0(1903): WRITE block 4116733064 on sda (8 sectors)
<4>[ 1081.151176] flush-8:0(1903): WRITE block 4116994960 on sda (8 sectors)

============= 1/100 test, Fri Jun 16 18:01:25 CEST 2017 ===============
<4>[ 1173.374458] nmbd(10004): READ block 346408 on md13 (24 sectors)
<4>[ 1173.380460] nmbd(10004): READ block 346488 on md13 (8 sectors)
<4>[ 1173.406074] nmbd(10004): READ block 346440 on md13 (8 sectors)
<4>[ 1173.411983] nmbd(10004): READ block 346512 on md13 (8 sectors)
<4>[ 1173.374458] nmbd(10004): READ block 346408 on md13 (24 sectors)
<4>[ 1173.380460] nmbd(10004): READ block 346488 on md13 (8 sectors)
<4>[ 1173.406074] nmbd(10004): READ block 346440 on md13 (8 sectors)
<4>[ 1173.411983] nmbd(10004): READ block 346512 on md13 (8 sectors)

============= 2/100 test, Fri Jun 16 18:02:54 CEST 2017 ===============
<7>[ 1253.381530] java(9067): dirtied inode 128581636 (minimserver.log) on sda3
<7>[ 1253.381560] java(9067): dirtied inode 128581636 (minimserver.log) on sda3
<4>[ 1258.380978] flush-8:0(1903): WRITE block 2843040 on sda (8 sectors)
<4>[ 1259.021012] jbd2/sda3-8(2171): WRITE block 2930026824 on sda (8 sectors)
<4>[ 1259.027753] jbd2/sda3-8(2171): WRITE block 2930026832 on sda (8 sectors)
<4>[ 1259.035504] jbd2/sda3-8(2171): WRITE block 2930026840 on sda (8 sectors)
<4>[ 1264.100961] flush-8:0(1903): WRITE block 4116733064 on sda (8 sectors)

============= 3/100 test, Fri Jun 16 18:04:23 CEST 2017 ===============
<7>[ 1547.051532] java(9067): dirtied inode 128581636 (minimserver.log) on sda3
<7>[ 1547.051558] java(9067): dirtied inode 128581636 (minimserver.log) on sda3
<4>[ 1552.050965] flush-8:0(1903): WRITE block 2843040 on sda (8 sectors)
<4>[ 1553.021015] jbd2/sda3-8(2171): WRITE block 2930026848 on sda (8 sectors)
<4>[ 1553.027764] jbd2/sda3-8(2171): WRITE block 2930026856 on sda (8 sectors)
<4>[ 1553.035489] jbd2/sda3-8(2171): WRITE block 2930026864 on sda (8 sectors)
<4>[ 1558.100962] flush-8:0(1903): WRITE block 4116733064 on sda (8 sectors)

============= 4/100 test, Fri Jun 16 18:09:16 CEST 2017 ===============
<7>[ 1960.251565] java(9067): dirtied inode 128581636 (minimserver.log) on sda3
<7>[ 1960.251595] java(9067): dirtied inode 128581636 (minimserver.log) on sda3
<4>[ 1965.252067] flush-8:0(1903): WRITE block 2843040 on sda (8 sectors)
<4>[ 1966.021010] jbd2/sda3-8(2171): WRITE block 2930026872 on sda (8 sectors)
<4>[ 1966.027760] jbd2/sda3-8(2171): WRITE block 2930026880 on sda (8 sectors)
<4>[ 1966.035494] jbd2/sda3-8(2171): WRITE block 2930026888 on sda (8 sectors)
<4>[ 1971.130970] flush-8:0(1903): WRITE block 4116733064 on sda (8 sectors)

============= 5/100 test, Fri Jun 16 18:16:10 CEST 2017 ===============
User avatar
dolbyman
Guru
Posts: 35024
Joined: Sat Feb 12, 2011 2:11 am
Location: Vancouver BC , Canada

Re: No spindown anymore..

Post by dolbyman »

looks like the minimserver.log has a lot of activity
Rudi64
New here
Posts: 7
Joined: Tue Apr 15, 2014 1:18 am

Re: No spindown anymore..

Post by Rudi64 »

dolbyman wrote:looks like the minimserver.log has a lot of activity
Yep..
I removed the path that miminserver writes to for the logfile and for about
20 min dead quiet..fingers crossed!
Rudi64
New here
Posts: 7
Joined: Tue Apr 15, 2014 1:18 am

Re: No spindown anymore..

Post by Rudi64 »

And touchdown.. :DD finally reaches standby.
Seems miminserver writes a lot to a log file on the public share.
Removed the path solves it...
Thanks for the support,dolbyman 8)
User avatar
dolbyman
Guru
Posts: 35024
Joined: Sat Feb 12, 2011 2:11 am
Location: Vancouver BC , Canada

Re: No spindown anymore..

Post by dolbyman »

glad it was solved
kimm
New here
Posts: 6
Joined: Wed Oct 31, 2007 1:14 am

Re: No spindown anymore..

Post by kimm »

Hi Rudi64
How/where did you remove the path ...
cagnulein
New here
Posts: 3
Joined: Wed Dec 11, 2019 5:20 pm

Re: No spindown anymore..

Post by cagnulein »

dolbyman wrote: Fri Jun 16, 2017 11:07 pm follow this guide and post the results
https://wiki.qnap.com/wiki/Hard_drives_spindown_issues
i think that the bash script is missing in the wiki. Could you please reupload it?
Thanks
cagnulein
New here
Posts: 3
Joined: Wed Dec 11, 2019 5:20 pm

Re: No spindown anymore..

Post by cagnulein »

I think this is the script https://paste.ubuntuusers.de/416392/
Post Reply

Return to “HDD Spin Down (HDD Standby)”