QNAP NAS NO STANDBY

Discussion about hard drive spin down (standby) feature of NAS.
Post Reply
StarMox
Starting out
Posts: 20
Joined: Fri Mar 25, 2011 12:25 am

QNAP NAS NO STANDBY

Post by StarMox »

I Have QNAP NAS TS-210, firmware 3.4.4.

qnap never goes to sleep (standby), no downloads, no processes, no server, no samba, no access. On firmware 3.3.9 top green light went out and disks were not spinning (during the night or days when nobody was using it), now the NAS works ALL the time and disks are ALWAYS SPINNING (nights, days,....).

Please help,
thanx
StarMOx
TonyPh12345
Been there, done that
Posts: 738
Joined: Tue Jul 13, 2010 11:53 pm

Re: QNAP NAS NO STANDBY

Post by TonyPh12345 »

StarMox
Starting out
Posts: 20
Joined: Fri Mar 25, 2011 12:25 am

Re: QNAP NAS NO STANDBY

Post by StarMox »

thanks,
after a long time here is the diagnostic report from blkdevMonitor:

Code: Select all

[/] # /root/blkdevMonitor.sh     
---blkdevMonitor---
Countdown:
10
9
8
7
6
5
4
3
2
1
Turn on block_dump
Clean old dmesg
Start...

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
 drive state is:  active/idle
[58165.020000] nmbd(27372): dirtied inode 1414 (wins.dat.27372) on md0
[58165.020000] nmbd(27372): dirtied inode 1413 (?) on md0
[58170.910000] flush-9:0(1290): WRITE block 108195264 on md0
[58170.910000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58170.910000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58171.000000] jbd2/md0-8(1279): WRITE block 973403032 on md0
[58177.100000] md0_raid1(1246): WRITE block 1950387200 on sda3
[58177.100000] md0_raid1(1246): WRITE block 1950387200 on sdb3
[58179.090000] jbd2/md0-8(1279): WRITE block 973403040 on md0
[58179.090000] jbd2/md0-8(1279): WRITE block 973403048 on md0
[58179.090000] jbd2/md0-8(1279): WRITE block 973403056 on md0
[58179.090000] jbd2/md0-8(1279): WRITE block 973403064 on md0
[58179.090000] jbd2/md0-8(1279): WRITE block 973403072 on md0
[58179.090000] jbd2/md0-8(1279): WRITE block 973403080 on md0
[58179.090000] jbd2/md0-8(1279): WRITE block 973403088 on md0
[58179.090000] jbd2/md0-8(1279): WRITE block 973403096 on md0
[58179.090000] jbd2/md0-8(1279): WRITE block 973403104 on md0
[58179.100000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58179.100000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58179.100000] md0_raid1(1246): WRITE block 1950387264 on sda3
[58179.100000] md0_raid1(1246): WRITE block 1950387264 on sdb3
[58180.340000] jbd2/md0-8(1279): WRITE block 973403112 on md0
[58180.600000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58180.600000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58180.610000] md0_raid1(1246): WRITE block 1950387200 on sda3
[58180.610000] md0_raid1(1246): WRITE block 1950387200 on sdb3
---counter=1---
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
 drive state is:  active/idle
[58211.020000] jbd2/md0-8(1279): WRITE block 973403256 on md0
[58211.020000] jbd2/md0-8(1279): WRITE block 973403264 on md0
[58211.020000] jbd2/md0-8(1279): WRITE block 973403272 on md0
[58211.020000] jbd2/md0-8(1279): WRITE block 973403280 on md0
[58211.020000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58211.020000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58211.020000] md0_raid1(1246): WRITE block 1950387264 on sda3
[58211.020000] md0_raid1(1246): WRITE block 1950387264 on sdb3
[58211.040000] jbd2/md0-8(1279): WRITE block 973403288 on md0
[58211.270000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58211.270000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58211.280000] md0_raid1(1246): WRITE block 1950387200 on sda3
[58211.280000] md0_raid1(1246): WRITE block 1950387200 on sdb3
[58212.290000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58212.290000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58213.290000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58213.290000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58213.290000] md0_raid1(1246): WRITE block 1950387264 on sda3
[58213.290000] md0_raid1(1246): WRITE block 1950387264 on sdb3
[58216.180000] flush-9:0(1290): WRITE block 0 on md0
[58216.180000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58216.180000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58216.190000] md0_raid1(1246): WRITE block 1950387200 on sda3
[58216.190000] md0_raid1(1246): WRITE block 1950387200 on sdb3
[58216.200000] flush-9:0(1290): WRITE block 8 on md0
[58216.200000] flush-9:0(1290): WRITE block 32 on md0
[58216.200000] flush-9:0(1290): WRITE block 8328 on md0
[58216.200000] flush-9:0(1290): WRITE block 8464 on md0
[58216.200000] flush-9:0(1290): WRITE block 9160 on md0
[58216.200000] flush-9:0(1290): WRITE block 74104 on md0
[58216.200000] flush-9:0(1290): WRITE block 77848 on md0
[58216.200000] flush-9:0(1290): WRITE block 104857696 on md0
[58216.210000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58216.210000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58216.420000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58216.420000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58216.430000] md0_raid1(1246): WRITE block 1950387200 on sda3
[58216.430000] md0_raid1(1246): WRITE block 1950387200 on sdb3
[58217.440000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58217.440000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58218.440000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58218.440000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58225.180000] nmbd(31182): dirtied inode 1413 (wins.dat.31182) on md0
[58225.180000] nmbd(31182): dirtied inode 1414 (?) on md0
[58230.200000] flush-9:0(1290): WRITE block 108195288 on md0
[58230.200000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58230.200000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58231.000000] jbd2/md0-8(1279): WRITE block 973403296 on md0
[58232.090000] md0_raid1(1246): WRITE block 1950387200 on sda3
[58232.090000] md0_raid1(1246): WRITE block 1950387200 on sdb3
[58233.250000] jbd2/md0-8(1279): WRITE block 973403304 on md0
[58233.250000] jbd2/md0-8(1279): WRITE block 973403312 on md0
[58233.250000] jbd2/md0-8(1279): WRITE block 973403320 on md0
[58233.250000] jbd2/md0-8(1279): WRITE block 973403328 on md0
[58233.250000] jbd2/md0-8(1279): WRITE block 973403336 on md0
[58233.250000] jbd2/md0-8(1279): WRITE block 973403344 on md0
[58233.250000] jbd2/md0-8(1279): WRITE block 973403352 on md0
[58233.250000] jbd2/md0-8(1279): WRITE block 973403360 on md0
[58233.250000] jbd2/md0-8(1279): WRITE block 973403368 on md0
[58233.250000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58233.250000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58233.250000] md0_raid1(1246): WRITE block 1950387264 on sda3
[58233.250000] md0_raid1(1246): WRITE block 1950387264 on sdb3
[58233.270000] jbd2/md0-8(1279): WRITE block 973403376 on md0
[58233.530000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58233.530000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58233.540000] md0_raid1(1246): WRITE block 1950387200 on sda3
[58233.540000] md0_raid1(1246): WRITE block 1950387200 on sdb3
[58234.550000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58234.550000] md0_raid1(1246): WRITE block 1950387208 on sdb3
---counter=2---
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
[58310.270000] md9_raid1(461): WRITE block 1060120 on sda1
[58310.270000] md9_raid1(461): WRITE block 1060120 on sdb1
[58310.470000] flush-9:0(1290): WRITE block 108195320 on md0
[58310.470000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58310.470000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58310.490000] md0_raid1(1246): WRITE block 1950387200 on sda3
[58310.490000] md0_raid1(1246): WRITE block 1950387200 on sdb3
[58310.510000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58310.510000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58310.720000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58310.720000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58310.740000] md0_raid1(1246): WRITE block 1950387200 on sda3
[58310.740000] md0_raid1(1246): WRITE block 1950387200 on sdb3
[58311.000000] jbd2/md0-8(1279): WRITE block 973403648 on md0
[58311.000000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58311.000000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58311.010000] md0_raid1(1246): WRITE block 1950387200 on sda3
[58311.010000] md0_raid1(1246): WRITE block 1950387200 on sdb3
[58311.010000] jbd2/md0-8(1279): WRITE block 973403656 on md0
[58311.010000] jbd2/md0-8(1279): WRITE block 973403664 on md0
[58311.010000] jbd2/md0-8(1279): WRITE block 973403672 on md0
[58311.010000] jbd2/md0-8(1279): WRITE block 973403680 on md0
[58311.010000] jbd2/md0-8(1279): WRITE block 973403688 on md0
[58311.010000] jbd2/md0-8(1279): WRITE block 973403696 on md0
[58311.010000] jbd2/md0-8(1279): WRITE block 973403704 on md0
[58311.010000] jbd2/md0-8(1279): WRITE block 973403712 on md0
[58311.010000] jbd2/md0-8(1279): WRITE block 973403720 on md0
[58311.010000] md0_raid1(1246): WRITE block 1950387264 on sda3
[58311.010000] md0_raid1(1246): WRITE block 1950387264 on sdb3
[58311.020000] jbd2/md0-8(1279): WRITE block 973403728 on md0
[58311.260000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58311.260000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58311.270000] md0_raid1(1246): WRITE block 1950387200 on sda3
[58311.270000] md0_raid1(1246): WRITE block 1950387200 on sdb3
[58312.280000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58312.280000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58313.290000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58313.290000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58313.290000] md0_raid1(1246): WRITE block 1950387264 on sda3
[58313.290000] md0_raid1(1246): WRITE block 1950387264 on sdb3
[58313.900000] flush-9:9(6057): WRITE block 0 on md9
[58313.900000] md9_raid1(461): WRITE block 1060104 on sda1
[58313.900000] md9_raid1(461): WRITE block 1060104 on sdb1
[58313.920000] md9_raid1(461): WRITE block 1060096 on sda1
[58313.920000] md9_raid1(461): WRITE block 1060096 on sdb1
[58313.930000] flush-9:9(6057): WRITE block 8 on md9
[58313.930000] flush-9:9(6057): WRITE block 272 on md9
[58313.930000] flush-9:9(6057): WRITE block 280 on md9
[58313.930000] flush-9:9(6057): WRITE block 288 on md9
[58313.930000] flush-9:9(6057): WRITE block 304 on md9
[58313.930000] flush-9:9(6057): WRITE block 3608 on md9
[58313.940000] md9_raid1(461): WRITE block 1060104 on sda1
[58313.940000] md9_raid1(461): WRITE block 1060104 on sdb1
[58314.150000] md9_raid1(461): WRITE block 1060104 on sda1
[58314.150000] md9_raid1(461): WRITE block 1060104 on sdb1
[58314.160000] md9_raid1(461): WRITE block 1060096 on sda1
[58314.160000] md9_raid1(461): WRITE block 1060096 on sdb1
[58315.160000] md9_raid1(461): WRITE block 1060104 on sda1
[58315.160000] md9_raid1(461): WRITE block 1060104 on sdb1
[58316.500000] flush-9:0(1290): WRITE block 0 on md0
[58316.500000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58316.500000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58316.520000] md0_raid1(1246): WRITE block 1950387200 on sda3
[58316.520000] md0_raid1(1246): WRITE block 1950387200 on sdb3
[58316.530000] flush-9:0(1290): WRITE block 8 on md0
[58316.530000] flush-9:0(1290): WRITE block 32 on md0
[58316.530000] flush-9:0(1290): WRITE block 8328 on md0
[58316.530000] flush-9:0(1290): WRITE block 8464 on md0
[58316.530000] flush-9:0(1290): WRITE block 9160 on md0
[58316.530000] flush-9:0(1290): WRITE block 74104 on md0
[58316.530000] flush-9:0(1290): WRITE block 77848 on md0
[58316.530000] flush-9:0(1290): WRITE block 104857696 on md0
[58316.540000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58316.540000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58316.750000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58316.750000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58316.770000] md0_raid1(1246): WRITE block 1950387200 on sda3
[58316.770000] md0_raid1(1246): WRITE block 1950387200 on sdb3
[58316.930000] md9_raid1(461): WRITE block 1060104 on sda1
[58316.930000] md9_raid1(461): WRITE block 1060104 on sdb1
[58317.780000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58317.780000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58318.800000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58318.800000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58325.440000] nmbd(6451): dirtied inode 1414 (wins.dat.6451) on md0
[58325.440000] nmbd(6451): dirtied inode 1413 (?) on md0
---counter=3---
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
 drive state is:  active/idle
[58396.310000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58396.310000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58398.040000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58398.040000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58398.040000] md0_raid1(1246): WRITE block 1950387264 on sda3
[58398.040000] md0_raid1(1246): WRITE block 1950387264 on sdb3
[58400.200000] flush-9:0(1290): WRITE block 0 on md0
[58400.200000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58400.200000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58400.210000] md0_raid1(1246): WRITE block 1950387200 on sda3
[58400.210000] md0_raid1(1246): WRITE block 1950387200 on sdb3
[58400.220000] flush-9:0(1290): WRITE block 8 on md0
[58400.220000] flush-9:0(1290): WRITE block 32 on md0
[58400.220000] flush-9:0(1290): WRITE block 8328 on md0
[58400.220000] flush-9:0(1290): WRITE block 8464 on md0
[58400.220000] flush-9:0(1290): WRITE block 9160 on md0
[58400.220000] flush-9:0(1290): WRITE block 74104 on md0
[58400.220000] flush-9:0(1290): WRITE block 77848 on md0
[58400.220000] flush-9:0(1290): WRITE block 104857696 on md0
[58400.230000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58400.230000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58400.450000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58400.450000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58400.470000] md0_raid1(1246): WRITE block 1950387200 on sda3
[58400.470000] md0_raid1(1246): WRITE block 1950387200 on sdb3
[58401.480000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58401.480000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58403.100000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58403.100000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58409.700000] nmbd(14025): dirtied inode 1414 (wins.dat.14025) on md0
[58409.700000] nmbd(14025): dirtied inode 1413 (?) on md0
[58415.000000] jbd2/md0-8(1279): WRITE block 108195360 on md0
[58415.000000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58415.000000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58415.020000] md0_raid1(1246): WRITE block 1950387200 on sda3
[58415.020000] md0_raid1(1246): WRITE block 1950387200 on sdb3
[58415.030000] jbd2/md0-8(1279): WRITE block 973404088 on md0
[58415.030000] jbd2/md0-8(1279): WRITE block 973404096 on md0
[58415.030000] jbd2/md0-8(1279): WRITE block 973404104 on md0
[58415.030000] jbd2/md0-8(1279): WRITE block 973404112 on md0
[58415.030000] jbd2/md0-8(1279): WRITE block 973404120 on md0
[58415.030000] jbd2/md0-8(1279): WRITE block 973404128 on md0
[58415.030000] jbd2/md0-8(1279): WRITE block 973404136 on md0
[58415.030000] jbd2/md0-8(1279): WRITE block 973404144 on md0
[58415.030000] jbd2/md0-8(1279): WRITE block 973404152 on md0
[58415.030000] jbd2/md0-8(1279): WRITE block 973404160 on md0
[58415.030000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58415.030000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58415.030000] md0_raid1(1246): WRITE block 1950387264 on sda3
[58415.030000] md0_raid1(1246): WRITE block 1950387264 on sdb3
[58415.050000] jbd2/md0-8(1279): WRITE block 973404168 on md0
[58415.310000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58415.310000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58415.330000] md0_raid1(1246): WRITE block 1950387200 on sda3
[58415.330000] md0_raid1(1246): WRITE block 1950387200 on sdb3
[58416.340000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58416.340000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58418.220000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58418.220000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58418.220000] md0_raid1(1246): WRITE block 1950387264 on sda3
[58418.220000] md0_raid1(1246): WRITE block 1950387264 on sdb3
[58420.220000] flush-9:0(1290): WRITE block 0 on md0
[58420.220000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58420.220000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58420.220000] md0_raid1(1246): WRITE block 1950387200 on sda3
[58420.220000] md0_raid1(1246): WRITE block 1950387200 on sdb3
[58420.230000] flush-9:0(1290): WRITE block 8 on md0
[58420.230000] flush-9:0(1290): WRITE block 32 on md0
[58420.230000] flush-9:0(1290): WRITE block 8328 on md0
[58420.230000] flush-9:0(1290): WRITE block 8464 on md0
[58420.230000] flush-9:0(1290): WRITE block 9160 on md0
[58420.230000] flush-9:0(1290): WRITE block 74104 on md0
[58420.230000] flush-9:0(1290): WRITE block 77848 on md0
[58420.230000] flush-9:0(1290): WRITE block 104857696 on md0
[58420.240000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58420.240000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58420.450000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58420.450000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58420.470000] md0_raid1(1246): WRITE block 1950387200 on sda3
[58420.470000] md0_raid1(1246): WRITE block 1950387200 on sdb3
---counter=4---
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
[58489.960000] nmbd(20719): dirtied inode 1414 (wins.dat.20719) on md0
[58489.960000] nmbd(20719): dirtied inode 1414 (wins.dat.20719) on md0
[58489.960000] nmbd(20719): dirtied inode 1413 (?) on md0
[58495.000000] jbd2/md0-8(1279): WRITE block 108195392 on md0
[58495.000000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58495.000000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58495.010000] md0_raid1(1246): WRITE block 1950387200 on sda3
[58495.010000] md0_raid1(1246): WRITE block 1950387200 on sdb3
[58495.020000] jbd2/md0-8(1279): WRITE block 973404440 on md0
[58495.020000] jbd2/md0-8(1279): WRITE block 973404448 on md0
[58495.020000] jbd2/md0-8(1279): WRITE block 973404456 on md0
[58495.020000] jbd2/md0-8(1279): WRITE block 973404464 on md0
[58495.020000] jbd2/md0-8(1279): WRITE block 973404472 on md0
[58495.020000] jbd2/md0-8(1279): WRITE block 973404480 on md0
[58495.020000] jbd2/md0-8(1279): WRITE block 973404488 on md0
[58495.020000] jbd2/md0-8(1279): WRITE block 973404496 on md0
[58495.020000] jbd2/md0-8(1279): WRITE block 973404504 on md0
[58495.020000] jbd2/md0-8(1279): WRITE block 973404512 on md0
[58495.020000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58495.020000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58495.020000] md0_raid1(1246): WRITE block 1950387264 on sda3
[58495.020000] md0_raid1(1246): WRITE block 1950387264 on sdb3
[58495.050000] jbd2/md0-8(1279): WRITE block 973404520 on md0
[58495.300000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58495.300000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58495.310000] md0_raid1(1246): WRITE block 1950387200 on sda3
[58495.310000] md0_raid1(1246): WRITE block 1950387200 on sdb3
[58496.320000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58496.320000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58497.320000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58497.320000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58497.320000] md0_raid1(1246): WRITE block 1950387264 on sda3
[58497.320000] md0_raid1(1246): WRITE block 1950387264 on sdb3
[58500.300000] flush-9:0(1290): WRITE block 0 on md0
[58500.300000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58500.300000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58500.310000] md0_raid1(1246): WRITE block 1950387200 on sda3
[58500.310000] md0_raid1(1246): WRITE block 1950387200 on sdb3
[58500.320000] flush-9:0(1290): WRITE block 8 on md0
[58500.320000] flush-9:0(1290): WRITE block 32 on md0
[58500.320000] flush-9:0(1290): WRITE block 8328 on md0
[58500.320000] flush-9:0(1290): WRITE block 8464 on md0
[58500.320000] flush-9:0(1290): WRITE block 9160 on md0
[58500.320000] flush-9:0(1290): WRITE block 74104 on md0
[58500.320000] flush-9:0(1290): WRITE block 77848 on md0
[58500.320000] flush-9:0(1290): WRITE block 104857696 on md0
[58500.330000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58500.330000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58500.540000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58500.540000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58500.560000] md0_raid1(1246): WRITE block 1950387200 on sda3
[58500.560000] md0_raid1(1246): WRITE block 1950387200 on sdb3
[58501.560000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58501.560000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58502.560000] md0_raid1(1246): WRITE block 1950387208 on sda3
[58502.560000] md0_raid1(1246): WRITE block 1950387208 on sdb3
[58510.000000] nmbd(21586): dirtied inode 1413 (wins.dat.21586) on md0
[58510.000000] nmbd(21586): dirtied inode 1414 (?) on md0
---counter=5---
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
again qnap is ts-210

thanks for the help
StarMox
User avatar
schumaku
Guru
Posts: 43579
Joined: Mon Jan 21, 2008 4:41 pm
Location: Kloten (Zurich), Switzerland -- Skype: schumaku
Contact:

Re: QNAP NAS NO STANDBY

Post by schumaku »

Enabled WINS in Microsot Networking on the NAS - either without really knowning when it's required (rare situations only) or in the attempt to make the NAS discoverable by it's name ie. \\NASname ?
StarMox
Starting out
Posts: 20
Joined: Fri Mar 25, 2011 12:25 am

Re: QNAP NAS NO STANDBY

Post by StarMox »

disabled microsoft networking alltogeather

still no standby; ill post another diagnostic.

bye
StarMox
StarMox
Starting out
Posts: 20
Joined: Fri Mar 25, 2011 12:25 am

Re: QNAP NAS NO STANDBY

Post by StarMox »

on disabling windows networking, qnap went to standby when blkdevMonitor was run

but only when blkdevMonitor was run. Upon standing, no access, no serveces running, no comp. connected qnap ts-210 will NOT go to sleep mode (disks will not spin down)

help
StarMox
TonyPh12345
Been there, done that
Posts: 738
Joined: Tue Jul 13, 2010 11:53 pm

Re: QNAP NAS NO STANDBY

Post by TonyPh12345 »

Of course it will go to sleep when you run blkdevMonitor. That's what that script does. It forces the drives to idle, and then watches to see what wakes them up.

You need to run blkdevMonitor for as long as it takes to find out what's waking the drives up.
StarMox
Starting out
Posts: 20
Joined: Fri Mar 25, 2011 12:25 am

Re: QNAP NAS NO STANDBY

Post by StarMox »

ok here is the second diagnostic, went to standby immediately and was woken up after a couple of minutes

blkdevMonitor script was run twice in a row

Code: Select all

[/] # root/blkdevMonitor.sh 
killall: dd: no process killed
---blkdevMonitor---
Countdown:
10
9
8
7
6
5
4
3
2
1
Turn on block_dump
Clean old dmesg
Start...

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
 drive state is:  active/idle
[92535.270000] curl(10779): dirtied inode 35 (ds.db-journal) on md9
[92541.000000] kjournald(1062): WRITE block 543424 on md9
[92541.000000] md9_raid1(461): WRITE block 1060104 on sda1
[92541.000000] md9_raid1(461): WRITE block 1060104 on sdb1
[92547.930000] md9_raid1(461): WRITE block 1060096 on sda1
[92547.930000] md9_raid1(461): WRITE block 1060096 on sdb1
[92549.840000] kjournald(1062): WRITE block 543432 on md9
[92549.840000] kjournald(1062): WRITE block 543440 on md9
[92549.840000] kjournald(1062): WRITE block 543448 on md9
[92549.840000] kjournald(1062): WRITE block 543456 on md9
[92549.840000] kjournald(1062): WRITE block 543464 on md9
[92549.840000] kjournald(1062): WRITE block 543472 on md9
[92549.840000] kjournald(1062): WRITE block 543480 on md9
[92549.840000] md9_raid1(461): WRITE block 1060120 on sda1
[92549.840000] md9_raid1(461): WRITE block 1060120 on sdb1
[92551.120000] kjournald(1062): WRITE block 543488 on md9
[92551.120000] md9_raid1(461): WRITE block 1060104 on sda1
[92551.120000] md9_raid1(461): WRITE block 1060104 on sdb1
[92551.140000] md9_raid1(461): WRITE block 1060120 on sda1
[92551.140000] md9_raid1(461): WRITE block 1060120 on sdb1
[92551.360000] md9_raid1(461): WRITE block 1060104 on sda1
[92551.360000] md9_raid1(461): WRITE block 1060104 on sdb1
[92551.360000] md9_raid1(461): WRITE block 1060096 on sda1
[92551.360000] md9_raid1(461): WRITE block 1060096 on sdb1
---counter=8---
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
^C
[/] # root/blkdevMonitor.sh 
killall: dd: no process killed
---blkdevMonitor---
Countdown:
10
9
8
7
6
5
4
3
2
1
Turn on block_dump
Clean old dmesg
Start...

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
 drive state is:  active/idle
[92840.780000] curl(22698): dirtied inode 35 (ds.db-journal) on md9
[92846.000000] kjournald(1062): WRITE block 543496 on md9
[92846.000000] md9_raid1(461): WRITE block 1060104 on sda1
[92846.000000] md9_raid1(461): WRITE block 1060104 on sdb1
[92852.930000] md9_raid1(461): WRITE block 1060096 on sda1
[92852.930000] md9_raid1(461): WRITE block 1060096 on sdb1
[92854.850000] kjournald(1062): WRITE block 543504 on md9
[92854.860000] kjournald(1062): WRITE block 543512 on md9
[92854.860000] kjournald(1062): WRITE block 543520 on md9
[92854.860000] kjournald(1062): WRITE block 543528 on md9
[92854.860000] kjournald(1062): WRITE block 543536 on md9
[92854.860000] kjournald(1062): WRITE block 543544 on md9
[92854.860000] kjournald(1062): WRITE block 543552 on md9
[92854.860000] md9_raid1(461): WRITE block 1060120 on sda1
[92854.860000] md9_raid1(461): WRITE block 1060120 on sdb1
[92856.160000] kjournald(1062): WRITE block 543560 on md9
[92856.160000] md9_raid1(461): WRITE block 1060120 on sda1
[92856.160000] md9_raid1(461): WRITE block 1060120 on sdb1
[92856.380000] md9_raid1(461): WRITE block 1060104 on sda1
[92856.380000] md9_raid1(461): WRITE block 1060104 on sdb1
[92856.380000] md9_raid1(461): WRITE block 1060096 on sda1
[92856.380000] md9_raid1(461): WRITE block 1060096 on sdb1
---counter=11---
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
---counter=12---
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command
 setting standby immediately.

/dev/sdb:
 issuing standby command
 setting standby immediately.
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
thanks
hope ww can diagnose

bye
StarMOx
TonyPh12345
Been there, done that
Posts: 738
Joined: Tue Jul 13, 2010 11:53 pm

Re: QNAP NAS NO STANDBY

Post by TonyPh12345 »

Well, I can tell you WHAT it is.. : Curl.

But I don't know what process on your QNAP is using it...
User avatar
AliceBToklas
Know my way around
Posts: 166
Joined: Sun May 22, 2011 7:07 pm
Location: North Carolina, US

Re: QNAP NAS NO STANDBY

Post by AliceBToklas »

Can you tell us more about your configuration? Things like UPnP, Syslog, UPS, etc.. You mentioned 'no downloads, no processes, no server, no samba, no access' but there is obviously something running and/or accessing the system. Is it the local master browser? Anything? Double check to be certain. Admittedly I'm grasping and understand these things can be frustrating to diagnose.

For my part, it took me a couple of hours before I realized the obvious - the syslog server was writing to the disk. Duh.
StarMox
Starting out
Posts: 20
Joined: Fri Mar 25, 2011 12:25 am

Re: QNAP NAS NO STANDBY

Post by StarMox »

on TS-210, 3.5.0
system services: AFP, NFS, web file manager, iTunes server, download station, that is it. UPnP is disabled. No UPS present. (would like to start a web server though ...)

syslog server is a great idea but not using it.

maybe:
system event log shows a recording every 10 seconds or so:
2011-09-16 06:06:23 System 127.0.0.1 localhost [Security] Access Violation from 93.103.144.117 with TCP (port=51413)
2011-09-16 06:04:45 System 127.0.0.1 localhost [Security] Access Violation from 86.61.20.38 with TCP (port=51413)

Interesting, under firmware 3.3.9 qnap showed around 2% CPU usage when idling. Under 3.5.0 it is around 7-10%.
top:

PID USER STATUS RSS PPID %CPU %MEM COMMAND
28512 admin Z 0 2470 7.5 0.0 manaRequest.cgi
28510 admin Z 0 2470 6.6 0.0 sysRequest.cgi
28509 admin R 904 28434 4.7 0.3 top
3396 admin S 5360 1 2.8 2.0 btd
4578 admin S 11M 1 0.9 4.4 transmission-da
2470 admin S 3332 1 0.9 1.3 _thttpd_
28501 admin Z 0 2470 0.9 0.0 manaRequest.cgi
28513 admin Z 0 1 0.9 0.0 _thttpd_
3876 admin S 2676 1 0.0 1.0 hd_util
4243 admin S 2648 1 0.0 1.0 qLogEngined
680 admin S 2580 1 0.0 1.0 bcclient
1300 admin S 2564 1 0.0 1.0 hotswap
1305 admin S 2556 1 0.0 0.9 qsmartd
2908 admin S 2540 1 0.0 0.9 hwmond
2873 admin S 2540 1 0.0 0.9 gpiod
4886 admin S 2516 1 0.0 0.9 upnpcd
4321 admin S 2460 1 0.0 0.9 afpd
4419 admin S 2460 1 0.0 0.9 Qthttpd
2833 admin S 2456 1 0.0 0.9 picd

manarequest, sysrequest? 7.5 % ?

thanks in advance!
StarMox
Last edited by StarMox on Fri Sep 16, 2011 4:44 pm, edited 1 time in total.
User avatar
schumaku
Guru
Posts: 43579
Joined: Mon Jan 21, 2008 4:41 pm
Location: Kloten (Zurich), Switzerland -- Skype: schumaku
Contact:

Re: QNAP NAS NO STANDBY

Post by schumaku »

So plenty of reasons, why your NAS HDD are waked up, citing from your post:
StarMox wrote:...download station, that is it.
No, there is more...
StarMox wrote:(would like to start a web server though ...)
...with the NAS configured for a defined list of hostss or subnets? This is why you see the Access Violations below..
StarMox wrote: syslog server is a great idea. my system event log ...
...which is not the syslog server
StarMox wrote:... shows a recording every 10 seconds or so:
2011-09-16 06:06:23 System 127.0.0.1 localhost [Security] Access Violation from 93.103.144.117 with TCP (port=51413)
2011-09-16 06:04:45 System 127.0.0.1 localhost [Security] Access Violation from 86.61.20.38 with TCP (port=51413)
Again, when limiting the access to the NAS to a certain subnetwork, TCP/IP range, or TCP/IP addresses, all other attempts are logged...
StarMox wrote:Interesting, under firmware 3.3.9 qnap showed around 2% CPU usage when idling. Under 3.5.0 it is around 7-10%.
Well, anything you show above is not really idling...a really idling NAS is <0.1% CPU
StarMox wrote: 3396 admin S 5360 1 2.8 2.0 btd
4578 admin S 11M 1 0.9 4.4 transmission-da
So beyond the Download Station, also Transmission is active...paired with a useless "high" security setting when running download services, limiting access to a defined addresses and networks, this is triggering the access violations above.
StarMox wrote:manarequest, sysrequest? 7.5 % ?
Most likely triggered by Web UI activities, still ongoing ACL changes after access right modifications, security logging, ...
StarMox
Starting out
Posts: 20
Joined: Fri Mar 25, 2011 12:25 am

Re: QNAP NAS NO STANDBY

Post by StarMox »

Schumaku, thanks for help ...

p.s.
-download station is enabled but with no active downloads
-WOULD like to start a web server (no need for now)
-not using syslog server
-yes logging other attempts (nas is set for specific local users)
-I only ment ”idling" in parenthesis just for comparison
-transmission was installed (QPKG) and is DISABLED (for a long time)
-yes *request.cgi is web UI -thanks

Interesting is that NAS was sleeping normally under previous firmware and with the same settings (nothing major was changed, maybe win. networking disabled) cannot sleep under 3.4 and now on 3.5 firmware (and latter is really good adding lots!)

So can I gather from your post that plenty of reasons now exist and not much can be done?
thanks in advance
StarMox
User avatar
schumaku
Guru
Posts: 43579
Joined: Mon Jan 21, 2008 4:41 pm
Location: Kloten (Zurich), Switzerland -- Skype: schumaku
Contact:

Re: QNAP NAS NO STANDBY

Post by schumaku »

StarMox wrote:-download station is enabled but with no active downloads
Often misunderstood - incoming connection attempts will be there, regardless - as soon as the port(s) is/are open/forwarded.
StarMox wrote:-WOULD like to start a web server (no need for now)
Can't be combined (just like ie. download station or transmission) with the "trusted only" network connections (misleadingly named "high security"). Evey connection from other sources will be blocked/rejected [what is obvious not in the sense of BT, an ftp or Web server - agree?] and the security action is logged - of course to the HDD, which has to spin-up to write the audit record.
StarMox wrote:-transmission was installed (QPKG) and is DISABLED (for a long time)
Aparently not - see the transmission-da process.
StarMox wrote:So can I gather from your post that plenty of reasons now exist and not much can be done?
Any connection attempt to the btd (in attempt to grab some bricks formerly shares) or transmission (for bricks formerly shared, or for DHT look-up access) does likley lead to a disk access - and therefore a HDD spin-up.

As soon as you are going to serve a Web site, an ftp server - depends on how fast you are populating it (intentional by submitting the URL to the search engines, or unintentional) to the search engines, as well as all the other crawlers that are around seeking for web sites served (for good and bad reasons like probing), the disk will barely spin-down.

Actually, I'm not 100% convinced, the current Download Station code does correctly remove no longer served parts from the BT trackers. As well, the common dynamic change of IP addresses in the end-user Internet connection are does leave everything listed - to the IP address previously assigned ...
StarMox
Starting out
Posts: 20
Joined: Fri Mar 25, 2011 12:25 am

Re: QNAP NAS NO STANDBY

Post by StarMox »

thanks for explanations and suggestions for the future...

-transmission uninstalled (was disabled before)
-download station disabled
-"high" security removed (system log is now empty)

Still no standby.
StarMox

p.s. worked with everything above in 3.3.9
Post Reply

Return to “HDD Spin Down (HDD Standby)”