Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Miminserver log prevents disk spinning down
17-06-2017, 08:49 (This post was last modified: 17-06-2017 08:50 by Rudi64.)
Post: #1
Miminserver log prevents disk spinning down
Bought this week a second hand Qnap HS-210 and a brand new WD Red 3T
HDD.
Instal with the latest Qnapfirmware, and as i just gonna to use it from streaming music i have just Miminserver and java enabled.
But as soon as i enable miminserver the HDD refuses to go at standby and keeps spinning..set at 30m or 5min makes no difference.
Opend putty, run blkdevMonitor and watching a lot of activity from
miminserver writing a log to the public share..almost constantly.
I removed the pad to the public share at properties with miminwatch and everything fine now and the hdd spins down now.
Possible bug?
Its a short log but it keeps on going..


Code:
[~] # 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 ===============
Find all posts by this user
Quote this message in a reply
18-06-2017, 05:14
Post: #2
RE: Miminserver log prevents disk spinning down
This problem is normally caused by having the wrong logging level set for MinimServer. The logging level should be set to Info to ensure that the HDD can enter standby. You can use MinimWatch to show the log window and check this setting.

What exactly do you mean by "I removed the pad to the public share at properties with miminwatch"? This might be the same as what I have said above but I am not sure about this from the words that you used.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)