QNAP NAS NO STANDBY

Discussion about hard drive spin down (standby) feature of NAS.
Post Reply
marc.garcia
Easy as a breeze
Posts: 314
Joined: Sun Aug 09, 2009 3:36 am

Re: QNAP NAS NO STANDBY

Post by marc.garcia »

Thanks for your time again. I'll get back to this thread when I have more information.
marc.garcia
Easy as a breeze
Posts: 314
Joined: Sun Aug 09, 2009 3:36 am

Re: QNAP NAS NO STANDBY

Post by marc.garcia »

Hi again,

my system has become active several times today. I've modified the blkdevMonitor script so it does not try to set the disks to sleep. This way I can capture what is happening and I don't distort the system behavior. I've been away from the network the whole day until tonight. Nobody has physically been able to interact with the NAS.

Again same weird "ps" access to the system, for which I have no explanation... this happens every day around 16:09. This is sooo annoying. I saw this process go off when I disabled all my services and even disconnected the LAN cable.

Code: Select all

2011-11-15_16:07:53
---counter=1919---
2011-11-15_16:08:08
---counter=1920---
2011-11-15_16:08:23
---counter=1921---
2011-11-15_16:08:38
---counter=1922---
2011-11-15_16:08:54
---counter=1923---
2011-11-15_16:09:09
---counter=1924---
2011-11-15_16:09:24
---counter=1925---
2011-11-15_16:09:39
ps(20034): dirtied inode 13507 (passwd) on md9
---counter=1926---
 drive state is:  active/idle
2011-11-15_16:09:57
kjournald(1636): WRITE block 532360 on md9
md9_raid1(1090): WRITE block 1060104 on sda1
md9_raid1(1090): WRITE block 1060104 on sdb1
---counter=1927---
 drive state is:  active/idle
2011-11-15_16:10:15
md9_raid1(1090): WRITE block 1060096 on sda1
md9_raid1(1090): WRITE block 1060096 on sdb1
kjournald(1636): WRITE block 532368 on md9
md9_raid1(1090): WRITE block 1060120 on sda1
md9_raid1(1090): WRITE block 1060120 on sdb1
kjournald(1636): WRITE block 532376 on md9
md9_raid1(1090): WRITE block 1060120 on sda1
md9_raid1(1090): WRITE block 1060120 on sdb1
md9_raid1(1090): WRITE block 1060104 on sda1
md9_raid1(1090): WRITE block 1060104 on sdb1
md9_raid1(1090): WRITE block 1060096 on sda1
md9_raid1(1090): WRITE block 1060096 on sdb1
md9_raid1(1090): WRITE block 1060104 on sda1
md9_raid1(1090): WRITE block 1060104 on sdb1
md9_raid1(1090): WRITE block 1060120 on sda1
md9_raid1(1090): WRITE block 1060120 on sdb1
flush-9:9(20155): WRITE block 524416 on md9
md9_raid1(1090): WRITE block 1060104 on sda1
md9_raid1(1090): WRITE block 1060104 on sdb1
md9_raid1(1090): WRITE block 1060096 on sda1
md9_raid1(1090): WRITE block 1060096 on sdb1
md9_raid1(1090): WRITE block 1060120 on sda1
md9_raid1(1090): WRITE block 1060120 on sdb1
md9_raid1(1090): WRITE block 1060104 on sda1
md9_raid1(1090): WRITE block 1060104 on sdb1
md9_raid1(1090): WRITE block 1060096 on sda1
md9_raid1(1090): WRITE block 1060096 on sdb1
md9_raid1(1090): WRITE block 1060104 on sda1
md9_raid1(1090): WRITE block 1060104 on sdb1
md9_raid1(1090): WRITE block 1060120 on sda1
md9_raid1(1090): WRITE block 1060120 on sdb1
---counter=1928---
 drive state is:  active/idle
2011-11-15_16:10:34
---counter=1929---
 drive state is:  active/idle
2011-11-15_16:10:50
---counter=1930---
 drive state is:  active/idle
2011-11-15_16:11:06
---counter=1931---
 drive state is:  active/idle
2011-11-15_16:11:26
---counter=1932---
 drive state is:  active/idle
2011-11-15_16:11:43
---counter=1933---
 drive state is:  active/idle
2011-11-15_16:11:59
---counter=1934---
 drive state is:  active/idle
2011-11-15_16:12:15
---counter=1935---
 drive state is:  active/idle
2011-11-15_16:12:30
---counter=1936---
 drive state is:  active/idle
2011-11-15_16:12:45
---counter=1937---
 drive state is:  active/idle
2011-11-15_16:13:01
---counter=1938---
 drive state is:  active/idle
2011-11-15_16:13:16
---counter=1939---
 drive state is:  active/idle
2011-11-15_16:13:31
---counter=1940---
 drive state is:  active/idle
2011-11-15_16:13:47
---counter=1941---
 drive state is:  active/idle
2011-11-15_16:14:03
---counter=1942---
 drive state is:  active/idle
2011-11-15_16:14:18
---counter=1943---
 drive state is:  active/idle
2011-11-15_16:14:33
---counter=1944---
 drive state is:  active/idle
2011-11-15_16:14:49
---counter=1945---
 drive state is:  active/idle
2011-11-15_16:15:07
---counter=1946---
 drive state is:  active/idle
2011-11-15_16:15:23
---counter=1947---
 drive state is:  active/idle
2011-11-15_16:15:38
---counter=1948---
 drive state is:  active/idle
2011-11-15_16:15:54
---counter=1949---
 drive state is:  active/idle
2011-11-15_16:16:10
---counter=1950---
 drive state is:  active/idle
2011-11-15_16:16:25
---counter=1951---
 drive state is:  active/idle
2011-11-15_16:16:40
---counter=1952---
 drive state is:  active/idle
2011-11-15_16:16:56
---counter=1953---
 drive state is:  active/idle
2011-11-15_16:17:11
---counter=1954---
 drive state is:  active/idle
2011-11-15_16:17:26
---counter=1955---
 drive state is:  active/idle
2011-11-15_16:17:40
---counter=1956---
 drive state is:  active/idle
2011-11-15_16:17:57
---counter=1957---
 drive state is:  active/idle
2011-11-15_16:18:12
---counter=1958---
 drive state is:  active/idle
2011-11-15_16:18:27
---counter=1959---
 drive state is:  active/idle
2011-11-15_16:18:42
---counter=1960---
 drive state is:  active/idle
2011-11-15_16:18:59
---counter=1961---
 drive state is:  active/idle
2011-11-15_16:19:14
---counter=1962---
 drive state is:  active/idle
2011-11-15_16:19:29
---counter=1963---
 drive state is:  active/idle
2011-11-15_16:19:44
---counter=1964---
 drive state is:  active/idle
2011-11-15_16:20:03
---counter=1965---
 drive state is:  active/idle
2011-11-15_16:20:20
---counter=1966---
 drive state is:  active/idle
2011-11-15_16:20:35
---counter=1967---
 drive state is:  active/idle
2011-11-15_16:20:51
---counter=1968---
 drive state is:  active/idle
2011-11-15_16:21:07
---counter=1969---
 drive state is:  active/idle
2011-11-15_16:21:21
---counter=1970---
 drive state is:  active/idle
2011-11-15_16:21:36
dropbox(21068): READ block 16880 on md2
---counter=1971---
 drive state is:  active/idle
2011-11-15_16:21:52
---counter=1972---
 drive state is:  active/idle
2011-11-15_16:22:08
one system logging in:

Code: Select all

---counter=2918---
 drive state is:  active/idle
2011-11-15_20:31:20
smbd(5228): dirtied inode 50151439 (messages.tdb) on md0
smbd(5228): dirtied inode 50151446 (connections.tdb) on md0
smbd(5228): dirtied inode 50151446 (connections.tdb) on md0
smbd(5228): dirtied inode 13314 (smbpasswd) on md9
qLogEngined(5615): dirtied inode 19923 (conn.log) on md9
qLogEngined(5615): dirtied inode 19934 (conn.log-journal) on md9
smbd(5228): dirtied inode 50151431 (sessionid.tdb) on md0
smbd(5228): dirtied inode 50151431 (sessionid.tdb) on md0
smbd(5228): dirtied inode 50151428 (notify.tdb) on md0
smbd(5228): dirtied inode 50151445 (notify_onelevel.tdb) on md0
qLogEngined(5615): WRITE block 1032200 on md9
md9_raid1(1090): WRITE block 1060104 on sda1
md9_raid1(1090): WRITE block 1060104 on sdb1
md9_raid1(1090): WRITE block 1060096 on sda1
md9_raid1(1090): WRITE block 1060096 on sdb1
md9_raid1(1090): WRITE block 1060136 on sda1
md9_raid1(1090): WRITE block 1060136 on sdb1
qLogEngined(5615): WRITE block 1032208 on md9
qLogEngined(5615): WRITE block 1032216 on md9
qLogEngined(5615): WRITE block 1032224 on md9
qLogEngined(5615): WRITE block 1032232 on md9
qLogEngined(5615): WRITE block 1032240 on md9
qLogEngined(5615): WRITE block 1032248 on md9
qLogEngined(5615): WRITE block 1032256 on md9
md9_raid1(1090): WRITE block 1060136 on sda1
md9_raid1(1090): WRITE block 1060136 on sdb1
kjournald(1636): WRITE block 532648 on md9
kjournald(1636): WRITE block 532656 on md9
kjournald(1636): WRITE block 532664 on md9
kjournald(1636): WRITE block 532672 on md9
kjournald(1636): WRITE block 532680 on md9
kjournald(1636): WRITE block 532688 on md9
kjournald(1636): WRITE block 532696 on md9
md9_raid1(1090): WRITE block 1060120 on sda1
md9_raid1(1090): WRITE block 1060120 on sdb1
kjournald(1636): WRITE block 532704 on md9
md9_raid1(1090): WRITE block 1060120 on sda1
md9_raid1(1090): WRITE block 1060120 on sdb1
kjournald(1636): WRITE block 532712 on md9
md9_raid1(1090): WRITE block 1060120 on sda1
md9_raid1(1090): WRITE block 1060120 on sdb1
qLogEngined(5615): WRITE block 1032200 on md9
qLogEngined(5615): dirtied inode 19923 (conn.log) on md9
qLogEngined(5615): WRITE block 999424 on md9
qLogEngined(5615): WRITE block 999432 on md9
qLogEngined(5615): WRITE block 999456 on md9
qLogEngined(5615): WRITE block 999672 on md9
qLogEngined(5615): WRITE block 1002024 on md9
qLogEngined(5615): WRITE block 1003784 on md9
qLogEngined(5615): WRITE block 1004624 on md9
qLogEngined(5615): WRITE block 1004920 on md9
qLogEngined(5615): WRITE block 1004944 on md9
qLogEngined(5615): WRITE block 1004984 on md9
qLogEngined(5615): WRITE block 1005280 on md9
qLogEngined(5615): WRITE block 1005536 on md9
qLogEngined(5615): WRITE block 1005568 on md9
qLogEngined(5615): WRITE block 1005576 on md9
qLogEngined(5615): WRITE block 1005584 on md9
md9_raid1(1090): WRITE block 1060128 on sda1
md9_raid1(1090): WRITE block 1060128 on sdb1
kjournald(1636): WRITE block 532720 on md9
kjournald(1636): WRITE block 532728 on md9
md9_raid1(1090): WRITE block 1060120 on sda1
md9_raid1(1090): WRITE block 1060120 on sdb1
kjournald(1636): WRITE block 532736 on md9
md9_raid1(1090): WRITE block 1060120 on sda1
md9_raid1(1090): WRITE block 1060120 on sdb1
md9_raid1(1090): WRITE block 1060104 on sda1
md9_raid1(1090): WRITE block 1060104 on sdb1
md9_raid1(1090): WRITE block 1060096 on sda1
md9_raid1(1090): WRITE block 1060096 on sdb1
md9_raid1(1090): WRITE block 1060104 on sda1
md9_raid1(1090): WRITE block 1060104 on sdb1
md9_raid1(1090): WRITE block 1060120 on sda1
md9_raid1(1090): WRITE block 1060120 on sdb1
md9_raid1(1090): WRITE block 1060128 on sda1
md9_raid1(1090): WRITE block 1060128 on sdb1
md9_raid1(1090): WRITE block 1060136 on sda1
md9_raid1(1090): WRITE block 1060136 on sdb1
flush-9:9(5268): WRITE block 524320 on md9
md9_raid1(1090): WRITE block 1060104 on sda1
md9_raid1(1090): WRITE block 1060104 on sdb1
md9_raid1(1090): WRITE block 1060096 on sda1
md9_raid1(1090): WRITE block 1060096 on sdb1
md9_raid1(1090): WRITE block 1060120 on sda1
md9_raid1(1090): WRITE block 1060120 on sdb1
flush-9:0(19505): WRITE block 1605075920 on md0
md0_raid1(1957): WRITE block 1950387200 on sda3
md0_raid1(1957): WRITE block 1950387200 on sdb3
flush-9:0(19505): WRITE block 1605075136 on md0
flush-9:0(19505): WRITE block 1605075912 on md0
flush-9:0(19505): WRITE block 1605075072 on md0
flush-9:0(19505): WRITE block 1605076288 on md0
flush-9:0(19505): WRITE block 1605042240 on md0
flush-9:0(19505): WRITE block 1605042304 on md0
kjournald(1983): WRITE block 974925256 on md0
kjournald(1983): WRITE block 974925264 on md0
kjournald(1983): WRITE block 974925272 on md0
kjournald(1983): WRITE block 974925280 on md0
kjournald(1983): WRITE block 974925288 on md0
kjournald(1983): WRITE block 974925296 on md0
kjournald(1983): WRITE block 974925304 on md0
kjournald(1983): WRITE block 974925312 on md0
kjournald(1983): WRITE block 974925320 on md0
kjournald(1636): WRITE block 532744 on md9
kjournald(1636): WRITE block 532752 on md9
kjournald(1636): WRITE block 532760 on md9
kjournald(1636): WRITE block 532768 on md9
kjournald(1636): WRITE block 532776 on md9
kjournald(1636): WRITE block 532784 on md9
kjournald(1636): WRITE block 532792 on md9
md9_raid1(1090): WRITE block 1060120 on sda1
md9_raid1(1090): WRITE block 1060120 on sdb1
kjournald(1636): WRITE block 532800 on md9
md9_raid1(1090): WRITE block 1060120 on sda1
md9_raid1(1090): WRITE block 1060120 on sdb1
md0_raid1(1957): WRITE block 1950387200 on sda3
md0_raid1(1957): WRITE block 1950387200 on sdb3
md9_raid1(1090): WRITE block 1060104 on sda1
md9_raid1(1090): WRITE block 1060104 on sdb1
md9_raid1(1090): WRITE block 1060096 on sda1
md9_raid1(1090): WRITE block 1060096 on sdb1
md9_raid1(1090): WRITE block 1060104 on sda1
md9_raid1(1090): WRITE block 1060104 on sdb1
md9_raid1(1090): WRITE block 1060120 on sda1
md9_raid1(1090): WRITE block 1060120 on sdb1
---counter=2919---
 drive state is:  active/idle
2011-11-15_20:31:46
flush-9:9(5268): WRITE block 786704 on md9
md9_raid1(1090): WRITE block 1060104 on sda1
md9_raid1(1090): WRITE block 1060104 on sdb1
md9_raid1(1090): WRITE block 1060096 on sda1
md9_raid1(1090): WRITE block 1060096 on sdb1
flush-9:9(5268): WRITE block 786712 on md9
flush-9:9(5268): WRITE block 786720 on md9
flush-9:9(5268): WRITE block 884736 on md9
flush-9:9(5268): WRITE block 0 on md9
flush-9:9(5268): WRITE block 8 on md9
md9_raid1(1090): WRITE block 1060104 on sda1
md9_raid1(1090): WRITE block 1060104 on sdb1
md9_raid1(1090): WRITE block 1060128 on sda1
md9_raid1(1090): WRITE block 1060128 on sdb1
flush-9:0(19505): WRITE block 1604845592 on md0
md0_raid1(1957): WRITE block 1950387200 on sda3
md0_raid1(1957): WRITE block 1950387200 on sdb3
flush-9:0(19505): WRITE block 0 on md0
flush-9:0(19505): WRITE block 384 on md0
flush-9:0(19505): WRITE block 8216 on md0
flush-9:0(19505): WRITE block 180232 on md0
flush-9:0(19505): WRITE block 1604845568 on md0
flush-9:0(19505): WRITE block 1604845584 on md0
md9_raid1(1090): WRITE block 1060104 on sda1
md9_raid1(1090): WRITE block 1060104 on sdb1
md9_raid1(1090): WRITE block 1060096 on sda1
md9_raid1(1090): WRITE block 1060096 on sdb1
md0_raid1(1957): WRITE block 1950387200 on sda3
md0_raid1(1957): WRITE block 1950387200 on sdb3
md9_raid1(1090): WRITE block 1060104 on sda1
md9_raid1(1090): WRITE block 1060104 on sdb1
md9_raid1(1090): WRITE block 1060104 on sda1
md9_raid1(1090): WRITE block 1060104 on sdb1
md9_raid1(1090): WRITE block 1060128 on sda1
md9_raid1(1090): WRITE block 1060128 on sdb1
---counter=2920---
 drive state is:  active/idle
2011-11-15_20:32:07
---counter=2921---
 drive state is:  active/idle
2011-11-15_20:32:23
---counter=2922---
 drive state is:  active/idle
2011-11-15_20:32:38
---counter=2923---
 drive state is:  active/idle
2011-11-15_20:32:55
what the hell is python doing?

Code: Select all

---counter=2990---
 drive state is:  active/idle
2011-11-15_20:50:47
python2.5(13851): dirtied inode 8413692 (log.txt) on md0
python2.5(13851): dirtied inode 8413692 (log.txt) on md0
python2.5(13851): dirtied inode 8413692 (log.txt) on md0
flush-9:0(13854): WRITE block 269821960 on md0
md0_raid1(1957): WRITE block 1950387200 on sda3
md0_raid1(1957): WRITE block 1950387200 on sdb3
kjournald(1983): WRITE block 974925360 on md0
kjournald(1983): WRITE block 974925368 on md0
kjournald(1983): WRITE block 974925376 on md0
md0_raid1(1957): WRITE block 1950387200 on sda3
md0_raid1(1957): WRITE block 1950387200 on sdb3
---counter=2991---
 drive state is:  active/idle
2011-11-15_20:51:04
flush-9:0(13854): WRITE block 269222152 on md0
md0_raid1(1957): WRITE block 1950387200 on sda3
md0_raid1(1957): WRITE block 1950387200 on sdb3
md0_raid1(1957): WRITE block 1950387200 on sda3
md0_raid1(1957): WRITE block 1950387200 on sdb3
---counter=2992---
 drive state is:  active/idle
2011-11-15_20:51:20
---counter=2993---
 drive state is:  active/idle
2011-11-15_20:51:35
python again:

Code: Select all

---counter=2309---
2011-11-15_17:50:24
---counter=2310---
2011-11-15_17:50:39
python2.5(5473): dirtied inode 8413692 (log.txt) on md0
python2.5(5473): dirtied inode 8413692 (log.txt) on md0
python2.5(5473): dirtied inode 8413692 (log.txt) on md0
---counter=2311---
 drive state is:  active/idle
2011-11-15_17:50:56
flush-9:0(5477): WRITE block 269821960 on md0
md0_raid1(1957): WRITE block 1950387200 on sda3
md0_raid1(1957): WRITE block 1950387200 on sdb3
kjournald(1983): WRITE block 974925056 on md0
kjournald(1983): WRITE block 974925064 on md0
kjournald(1983): WRITE block 974925072 on md0
md0_raid1(1957): WRITE block 1950387200 on sda3
md0_raid1(1957): WRITE block 1950387200 on sdb3
---counter=2312---
 drive state is:  active/idle
2011-11-15_17:51:12
flush-9:0(5477): WRITE block 269222152 on md0
md0_raid1(1957): WRITE block 1950387200 on sda3
md0_raid1(1957): WRITE block 1950387200 on sdb3
md0_raid1(1957): WRITE block 1950387200 on sda3
md0_raid1(1957): WRITE block 1950387200 on sdb3
---counter=2313---
 drive state is:  active/idle
2011-11-15_17:51:27
---counter=2314---
 drive state is:  active/idle
2011-11-15_17:51:42
---counter=2315---
python yet again:

Code: Select all

---counter=2309---
2011-11-15_17:50:24
---counter=2310---
2011-11-15_17:50:39
python2.5(5473): dirtied inode 8413692 (log.txt) on md0
python2.5(5473): dirtied inode 8413692 (log.txt) on md0
python2.5(5473): dirtied inode 8413692 (log.txt) on md0
---counter=2311---
 drive state is:  active/idle
2011-11-15_17:50:56
flush-9:0(5477): WRITE block 269821960 on md0
md0_raid1(1957): WRITE block 1950387200 on sda3
md0_raid1(1957): WRITE block 1950387200 on sdb3
kjournald(1983): WRITE block 974925056 on md0
kjournald(1983): WRITE block 974925064 on md0
kjournald(1983): WRITE block 974925072 on md0
md0_raid1(1957): WRITE block 1950387200 on sda3
md0_raid1(1957): WRITE block 1950387200 on sdb3
---counter=2312---
 drive state is:  active/idle
2011-11-15_17:51:12
flush-9:0(5477): WRITE block 269222152 on md0
md0_raid1(1957): WRITE block 1950387200 on sda3
md0_raid1(1957): WRITE block 1950387200 on sdb3
md0_raid1(1957): WRITE block 1950387200 on sda3
md0_raid1(1957): WRITE block 1950387200 on sdb3
---counter=2313---
 drive state is:  active/idle
2011-11-15_17:51:27
---counter=2314---
 drive state is:  active/idle
2011-11-15_17:51:42
---counter=2315---
and again...

Code: Select all

---counter=1621---
2011-11-15_14:50:26
---counter=1622---
2011-11-15_14:50:41
python2.5(19525): dirtied inode 8413692 (log.txt) on md0
python2.5(19525): dirtied inode 8413692 (log.txt) on md0
python2.5(19525): dirtied inode 8413692 (log.txt) on md0
---counter=1623---
 drive state is:  active/idle
2011-11-15_14:50:57
flush-9:0(19527): WRITE block 269821960 on md0
md0_raid1(1957): WRITE block 1950387200 on sda3
md0_raid1(1957): WRITE block 1950387200 on sdb3
kjournald(1983): WRITE block 974925032 on md0
kjournald(1983): WRITE block 974925040 on md0
kjournald(1983): WRITE block 974925048 on md0
md0_raid1(1957): WRITE block 1950387200 on sda3
md0_raid1(1957): WRITE block 1950387200 on sdb3
---counter=1624---
 drive state is:  active/idle
2011-11-15_14:51:13
flush-9:0(19527): WRITE block 269222152 on md0
md0_raid1(1957): WRITE block 1950387200 on sda3
md0_raid1(1957): WRITE block 1950387200 on sdb3
md0_raid1(1957): WRITE block 1950387200 on sda3
md0_raid1(1957): WRITE block 1950387200 on sdb3
---counter=1625---
 drive state is:  active/idle
2011-11-15_14:51:28
---counter=1626---
 drive state is:  active/idle
2011-11-15_14:51:43
---counter=1627---
 drive state is:  active/idle
2011-11-15_14:52:00
---counter=1628---
 drive state is:  active/idle
2011-11-15_14:52:15
---counter=1629---
 drive state is:  active/idle
2011-11-15_14:52:30
---counter=1630---
 drive state is:  active/idle
2011-11-15_14:52:46
---counter=1631---
 drive state is:  active/idle
2011-11-15_14:53:02
and now java:

Code: Select all

2011-11-15_12:38:26
---counter=1113---
2011-11-15_12:38:41
---counter=1114---
 drive state is:  active/idle
2011-11-15_12:38:58
java(5858): READ block 47488 on md2
java(5858): READ block 47496 on md2
java(5858): READ block 47504 on md2
java(5858): READ block 47512 on md2
java(5858): READ block 47520 on md2
java(5858): READ block 47528 on md2
java(5858): READ block 47536 on md2
java(5858): READ block 47544 on md2
---counter=1115---
 drive state is:  active/idle
2011-11-15_12:39:13
---counter=1116---
 drive state is:  active/idle
2011-11-15_12:39:29
---counter=1117---
 drive state is:  active/idle
2011-11-15_12:39:43
---counter=1118---
 drive state is:  active/idle
2011-11-15_12:40:02
---counter=1119---
 drive state is:  active/idle
2011-11-15_12:40:19
---counter=1120---
 drive state is:  active/idle
2011-11-15_12:40:34
---counter=1121---
This looks like one afp conversation:

Code: Select all

2011-11-15_10:17:09
---counter=566---
2011-11-15_10:17:24
---counter=567---
2011-11-15_10:17:39
---counter=568---
2011-11-15_10:17:55
---counter=569---
2011-11-15_10:18:10
---counter=570---
2011-11-15_10:18:25
---counter=571---
2011-11-15_10:18:40
---counter=572---
2011-11-15_10:18:56
---counter=573---
 drive state is:  active/idle
2011-11-15_10:19:11
afpd(17212): dirtied inode 55386114 (__db.002) on md0
afpd(17212): dirtied inode 55386114 (__db.002) on md0
afpd(17212): dirtied inode 55386115 (__db.003) on md0
afpd(17212): dirtied inode 55386115 (__db.003) on md0
afpd(17212): dirtied inode 55386116 (__db.004) on md0
afpd(17212): dirtied inode 55386116 (__db.004) on md0
afpd(17212): dirtied inode 55386113 (__db.001) on md0
afpd(17212): dirtied inode 55386113 (__db.001) on md0
afpd(17212): READ block 24960 on md2
afpd(17212): READ block 24968 on md2
afpd(17212): READ block 24976 on md2
afpd(17212): READ block 24984 on md2
afpd(17212): READ block 24992 on md2
afpd(17212): READ block 25000 on md2
afpd(17212): READ block 25008 on md2
afpd(17212): READ block 25016 on md2
flush-9:0(19865): WRITE block 1772519488 on md0
md0_raid1(1957): WRITE block 1950387200 on sda3
md0_raid1(1957): WRITE block 1950387200 on sdb3
kjournald(1983): WRITE block 974924984 on md0
afpd(17212): READ block 24704 on md2
afpd(17212): READ block 24712 on md2
afpd(17212): READ block 24720 on md2
afpd(17212): READ block 24728 on md2
afpd(17212): READ block 24736 on md2
afpd(17212): READ block 24744 on md2
afpd(17212): READ block 24752 on md2
afpd(17212): READ block 24760 on md2
flush-9:0(19865): WRITE block 1772519504 on md0
kjournald(1983): WRITE block 974924992 on md0
flush-9:0(19865): WRITE block 1772519936 on md0
flush-9:0(19865): WRITE block 1772520592 on md0
flush-9:0(19865): WRITE block 1772520816 on md0
flush-9:0(19865): WRITE block 1772520128 on md0
flush-9:0(19865): WRITE block 1772520200 on md0
flush-9:0(19865): WRITE block 1772520216 on md0
flush-9:0(19865): WRITE block 1772520384 on md0
flush-9:0(19865): WRITE block 1772519424 on md0
afpd(17212): READ block 24768 on md2
afpd(17212): READ block 24776 on md2
afpd(17212): READ block 24784 on md2
afpd(17212): READ block 24792 on md2
afpd(17212): READ block 24800 on md2
afpd(17212): READ block 24808 on md2
afpd(17212): READ block 24816 on md2
afpd(17212): READ block 24824 on md2
kjournald(1983): WRITE block 974925000 on md0
md0_raid1(1957): WRITE block 1950387200 on sda3
md0_raid1(1957): WRITE block 1950387200 on sdb3
---counter=574---
 drive state is:  active/idle
2011-11-15_10:19:29
flush-9:0(19865): WRITE block 1772355600 on md0
md0_raid1(1957): WRITE block 1950387200 on sda3
md0_raid1(1957): WRITE block 1950387200 on sdb3
md0_raid1(1957): WRITE block 1950387200 on sda3
md0_raid1(1957): WRITE block 1950387200 on sdb3
---counter=575---
 drive state is:  active/idle
2011-11-15_10:19:45
---counter=576---
 drive state is:  active/idle
2011-11-15_10:20:04
---counter=577---
 drive state is:  active/idle
2011-11-15_10:20:20
---counter=578---
 drive state is:  active/idle
2011-11-15_10:20:35
---counter=579---
 drive state is:  active/idle
2011-11-15_10:20:51
---counter=580---
 drive state is:  active/idle
2011-11-15_10:21:07
---counter=581---
 drive state is:  active/idle
2011-11-15_10:21:21
---counter=582---
 drive state is:  active/idle
2011-11-15_10:21:36
---counter=583---
 drive state is:  active/idle
2011-11-15_10:21:52
---counter=584---
 drive state is:  active/idle
2011-11-15_10:22:07
---counter=585---
 drive state is:  active/idle
2011-11-15_10:22:22
I'm running python version 2.7 which is required by pyload.

Can anybody help?

Thanks
marc.garcia
Easy as a breeze
Posts: 314
Joined: Sun Aug 09, 2009 3:36 am

Re: QNAP NAS NO STANDBY

Post by marc.garcia »

Can anybody comment on this?

Code: Select all

---counter=4054---
2011-11-21_16:19:16
---counter=4055---
 drive state is:  active/idle
2011-11-21_16:19:32
ps(6450): dirtied inode 13507 (passwd) on md9
kjournald(1638): WRITE block 540184 on md9
md9_raid1(1090): WRITE block 1060104 on sda1
md9_raid1(1090): WRITE block 1060104 on sdb1
---counter=4056---
 drive state is:  active/idle
2011-11-21_16:19:49
md9_raid1(1090): WRITE block 1060096 on sda1
md9_raid1(1090): WRITE block 1060096 on sdb1
kjournald(1638): WRITE block 540192 on md9
md9_raid1(1090): WRITE block 1060120 on sda1
md9_raid1(1090): WRITE block 1060120 on sdb1
kjournald(1638): WRITE block 540200 on md9
md9_raid1(1090): WRITE block 1060120 on sda1
md9_raid1(1090): WRITE block 1060120 on sdb1
md9_raid1(1090): WRITE block 1060104 on sda1
md9_raid1(1090): WRITE block 1060104 on sdb1
md9_raid1(1090): WRITE block 1060096 on sda1
md9_raid1(1090): WRITE block 1060096 on sdb1
md9_raid1(1090): WRITE block 1060104 on sda1
md9_raid1(1090): WRITE block 1060104 on sdb1
md9_raid1(1090): WRITE block 1060120 on sda1
md9_raid1(1090): WRITE block 1060120 on sdb1
flush-9:9(6453): WRITE block 524416 on md9
md9_raid1(1090): WRITE block 1060104 on sda1
md9_raid1(1090): WRITE block 1060104 on sdb1
md9_raid1(1090): WRITE block 1060096 on sda1
md9_raid1(1090): WRITE block 1060096 on sdb1
md9_raid1(1090): WRITE block 1060120 on sda1
md9_raid1(1090): WRITE block 1060120 on sdb1
md9_raid1(1090): WRITE block 1060104 on sda1
md9_raid1(1090): WRITE block 1060104 on sdb1
md9_raid1(1090): WRITE block 1060096 on sda1
md9_raid1(1090): WRITE block 1060096 on sdb1
md9_raid1(1090): WRITE block 1060104 on sda1
md9_raid1(1090): WRITE block 1060104 on sdb1
md9_raid1(1090): WRITE block 1060120 on sda1
md9_raid1(1090): WRITE block 1060120 on sdb1
---counter=4057---
 drive state is:  active/idle
2011-11-21_16:20:07
---counter=4058---
 drive state is:  active/idle
2011-11-21_16:20:24
---counter=4059---
 drive state is:  active/idle
2011-11-21_16:20:40
---counter=4060---
 drive state is:  active/idle
2011-11-21_16:20:56
---counter=4061---
 drive state is:  active/idle
2011-11-21_16:21:11
---counter=4062---
 drive state is:  active/idle
2011-11-21_16:21:28 
what the heck is that ps command doing? it spins my disks up every day around 16:20... I see no point in having ps access that file.

Thanks
tmt
Experience counts
Posts: 1006
Joined: Mon Nov 16, 2009 11:02 am

Re: QNAP NAS NO STANDBY

Post by tmt »

The more interesting question is what is executing ps, but it's perfectly understandable why ps accesses /etc/passwd. It needs to do so because it maps process userids to usernames, which requires a passwd lookup. Note that it "dirties" the inode. It's not in fact writing the file, but the access updates the "last access time", which in turn is synced out to the disk because /mnt/HDA_ROOT (where /etc/config and therefore /etc/passwd reside) isn't mounted with the "noatime" option. I think /etc/passwd is in the buffer cache, and it's the update that spins the disk.

You could perhaps try something like

Code: Select all

 # mount -o remount,noatime /dev/md9 /mnt/HDA_ROOT
#
to see if it makes any difference. But, try to figure out what script is running "ps" at 4:09.
SS-439, Ubuntu Server 12.04.3 LTS, EXT4, RAID10, 4xHitachi 5K1000
TS-112, 4.1.x Beta, EXT4, 1xHitachi 7K1000
marc.garcia
Easy as a breeze
Posts: 314
Joined: Sun Aug 09, 2009 3:36 am

Re: QNAP NAS NO STANDBY

Post by marc.garcia »

tmt wrote:The more interesting question is what is executing ps, but it's perfectly understandable why ps accesses /etc/passwd. It needs to do so because it maps process userids to usernames, which requires a passwd lookup. Note that it "dirties" the inode. It's not in fact writing the file, but the access updates the "last access time", which in turn is synced out to the disk because /mnt/HDA_ROOT (where /etc/config and therefore /etc/passwd reside) isn't mounted with the "noatime" option. I think /etc/passwd is in the buffer cache, and it's the update that spins the disk.

You could perhaps try something like

Code: Select all

 # mount -o remount,noatime /dev/md9 /mnt/HDA_ROOT
#
to see if it makes any difference. But, try to figure out what script is running "ps" at 4:09.
Hi there,

funny thing is that my NAS is currently running no services at all. I've disabled them all because I'm trying to figure out what on earth is keeping it busy... I was requested to disable all the existing services. Now that it is "idle" it should not wake up unless a cronjob is not requesting it to, which is not the case as per my previous crontab.

How can I know which process is making use of "ps"?

Thanks a million in advance! :)
marc.garcia
Easy as a breeze
Posts: 314
Joined: Sun Aug 09, 2009 3:36 am

Re: QNAP NAS NO STANDBY

Post by marc.garcia »

tmt wrote:try to figure out what script is running "ps" at 4:09.
one small detail, if you check the last log I attached, this is the first time I see that process go off at 16:19 instead of 16:09... how weird!!!

I'm scared at what will happen when I start enabling services on the NAS... If you check my previous logs, you can see that python, java, and some others tend to go off often thus waking the system up for no aparent reason :(
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 »

marc.garcia wrote:If you check my previous logs, you can see that python, java, and some others tend to go off often thus waking the system up for no aparent reason :(
Neither Python, Java, or similar are launched on thier own - there must be applications on your NAS making us of the Python, Java, and similar run-time environments.
tmt
Experience counts
Posts: 1006
Joined: Mon Nov 16, 2009 11:02 am

Re: QNAP NAS NO STANDBY

Post by tmt »

... and, why would you be scared that your server runs services? Do you want it to stay asleep or actually do these things? Yes, it's a complicated system and yes it can do things we don't expect or don't want, but in the end I think it'd be best to focus on the task and not the details. If standby is really that important to you, maybe you should consider powering it down and using wake-on-lan or some similar approach.
SS-439, Ubuntu Server 12.04.3 LTS, EXT4, RAID10, 4xHitachi 5K1000
TS-112, 4.1.x Beta, EXT4, 1xHitachi 7K1000
marc.garcia
Easy as a breeze
Posts: 314
Joined: Sun Aug 09, 2009 3:36 am

Re: QNAP NAS NO STANDBY

Post by marc.garcia »

tmt wrote:... and, why would you be scared that your server runs services? Do you want it to stay asleep or actually do these things? Yes, it's a complicated system and yes it can do things we don't expect or don't want, but in the end I think it'd be best to focus on the task and not the details. If standby is really that important to you, maybe you should consider powering it down and using wake-on-lan or some similar approach.
You are totally right but wake on lan takes a considerable amount of time and that puts me off. Thing is, I can't understand why python, java, and other processes have to interact with the disk if no clienst are requesting access... For me standby is an important matter.

I apprecaite your time and your help :)
tmt
Experience counts
Posts: 1006
Joined: Mon Nov 16, 2009 11:02 am

Re: QNAP NAS NO STANDBY

Post by tmt »

Pretty much everything interacts with the disk, for data files, configuration files and system information. Not to mention logging and other administrative functions. Plus, the ARM-based QNAPs have less memory than the Intel-based ones in general, so they may start swapping with many large-footprint programs like Python and Java.
SS-439, Ubuntu Server 12.04.3 LTS, EXT4, RAID10, 4xHitachi 5K1000
TS-112, 4.1.x Beta, EXT4, 1xHitachi 7K1000
Pjotrik
New here
Posts: 4
Joined: Tue Aug 11, 2009 1:54 am

Re: QNAP NAS NO STANDBY

Post by Pjotrik »

Try disabling Instant Messaging Service under notification. It worked for me.
marc.garcia
Easy as a breeze
Posts: 314
Joined: Sun Aug 09, 2009 3:36 am

Re: QNAP NAS NO STANDBY

Post by marc.garcia »

Thanks but I don't have that set up :(
Pjotrik
New here
Posts: 4
Joined: Tue Aug 11, 2009 1:54 am

Re: QNAP NAS NO STANDBY

Post by Pjotrik »

Pitty, it was worth a try. Hope it may helps others.
StarMox
Starting out
Posts: 20
Joined: Fri Mar 25, 2011 12:25 am

Re: QNAP NAS NO STANDBY

Post by StarMox »

Hello to everyone!

I started this thread of frustration and spent lots of dime diagnosing problem of no stand-by. I have been away for a long time now and when I returned one of the things I did was upgrade the firmware on my TS-210 to the version 3.5.2 Build 1126T. One of the biggest surprises came, when I saw my QNAP sleeping again just by mistake. So after a check-up the standby settings work again as they were on 3.3.9 firmware. I will start plugging in all the services and report.

What are your experiences with new firmware? Are issues of no stand-by resolved for most?
byebye
Head8che
New here
Posts: 6
Joined: Thu Feb 03, 2011 3:21 pm

Re: QNAP NAS NO STANDBY

Post by Head8che »

Well the demons conspire...

My QNAP TS-219+ has been running perfectly since I started it over 6 months ago... until recently! I have now noticed it won't go into standby mode!

I have created a blkdevMonitor log and pasted that in below, can anybody decipher it and let me know what service or services are running and stopping me from going into standby mode as before?

Code: Select all

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2012.01.18 16:18:35 =~=~=~=~=~=~=~=~=~=~=~=
login as: admin
admin@192.168.1.20's password: 
c[K[J[0m[~] # cp /share/Public/blkdevMonitor.sh /root
[~] # chmod 766 /root/blkdevMonitor.sh
[~] # /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

/dev/sdb:
 issuing standby command
/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
flush-9:0(31103): WRITE block 1199571200 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
jbd2/md0-8(7471): WRITE block 1200615752 on md0
jbd2/md0-8(7471): WRITE block 973343728 on md0
jbd2/md0-8(7471): WRITE block 973343736 on md0
jbd2/md0-8(7471): WRITE block 973343744 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
flush-9:0(31103): WRITE block 1200615752 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
flush-9:0(31103): WRITE block 270424 on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
---counter=0---
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command

/dev/sdb:
 issuing standby command
/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
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
smbd(31117): dirtied inode 37486599 (locking.tdb) on md0
smbd(31117): dirtied inode 37486599 (locking.tdb) on md0
jbd2/md0-8(7471): WRITE block 1200615752 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
jbd2/md0-8(7471): WRITE block 973343752 on md0
jbd2/md0-8(7471): WRITE block 973343760 on md0
jbd2/md0-8(7471): WRITE block 973343768 on md0
jbd2/md0-8(7471): WRITE block 973343776 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
flush-9:0(31103): WRITE block 1200615752 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
flush-9:0(31103): WRITE block 270424 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
jbd2/md0-8(7471): WRITE block 1200615752 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
jbd2/md0-8(7471): WRITE block 973343784 on md0
jbd2/md0-8(7471): WRITE block 973343792 on md0
jbd2/md0-8(7471): WRITE block 973343800 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
flush-9:0(31103): WRITE block 343933552 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
flush-9:0(31103): WRITE block 1199571200 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
smbd(31117): dirtied inode 37486599 (locking.tdb) on md0
smbd(31117): dirtied inode 37486599 (locking.tdb) on md0
flush-9:0(31103): WRITE block 1200615752 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
jbd2/md0-8(7471): WRITE block 1200615752 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
jbd2/md0-8(7471): WRITE block 973343808 on md0
jbd2/md0-8(7471): WRITE block 973343816 on md0
jbd2/md0-8(7471): WRITE block 973343824 on md0
jbd2/md0-8(7471): WRITE block 973343832 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
flush-9:0(31103): WRITE block 270424 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
smbd(31117): dirtied inode 37486599 (locking.tdb) on md0
smbd(31117): dirtied inode 37486599 (locking.tdb) on md0
flush-9:0(31103): WRITE block 1200615752 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
---counter=1---
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command

/dev/sdb:
 issuing standby command
/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
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
flush-9:0(31103): WRITE block 270424 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
flush-9:0(31103): WRITE block 1199571200 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
jbd2/md0-8(7471): WRITE block 1200615752 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
jbd2/md0-8(7471): WRITE block 973343960 on md0
jbd2/md0-8(7471): WRITE block 973343968 on md0
jbd2/md0-8(7471): WRITE block 973343976 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
flush-9:0(31103): dirtied inode 10748644 (putty.log) on md0
flush-9:0(31103): WRITE block 1200615760 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
smbd(31117): dirtied inode 37486599 (locking.tdb) on md0
smbd(31117): dirtied inode 37486599 (locking.tdb) on md0
jbd2/md0-8(7471): WRITE block 1200615760 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
jbd2/md0-8(7471): WRITE block 973343984 on md0
jbd2/md0-8(7471): WRITE block 973343992 on md0
jbd2/md0-8(7471): WRITE block 973344000 on md0
jbd2/md0-8(7471): WRITE block 973344008 on md0
jbd2/md0-8(7471): WRITE block 973344016 on md0
jbd2/md0-8(7471): WRITE block 973344024 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
flush-9:0(31103): WRITE block 270424 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
jbd2/md0-8(7471): WRITE block 1200615760 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
jbd2/md0-8(7471): WRITE block 973344032 on md0
jbd2/md0-8(7471): WRITE block 973344040 on md0
jbd2/md0-8(7471): WRITE block 973344048 on md0
smbd(31117): dirtied inode 37486599 (locking.tdb) on md0
smbd(31117): dirtied inode 37486599 (locking.tdb) on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
flush-9:0(31103): WRITE block 1199570968 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
flush-9:0(31103): WRITE block 288 on md0
flush-9:0(31103): WRITE block 343933552 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
jbd2/md0-8(7471): WRITE block 1200615760 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
jbd2/md0-8(7471): WRITE block 973344056 on md0
jbd2/md0-8(7471): WRITE block 973344064 on md0
jbd2/md0-8(7471): WRITE block 973344072 on md0
jbd2/md0-8(7471): WRITE block 973344080 on md0
flush-9:0(31103): WRITE block 270424 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
flush-9:0(31103): WRITE block 1200615760 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 37486599 (locking.tdb) on md0
smbd(31117): dirtied inode 37486599 (locking.tdb) on md0
jbd2/md0-8(7471): WRITE block 1200615760 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
flush-9:0(31103): WRITE block 270424 on md0
jbd2/md0-8(7471): WRITE block 973344088 on md0
jbd2/md0-8(7471): WRITE block 973344096 on md0
jbd2/md0-8(7471): WRITE block 973344104 on md0
jbd2/md0-8(7471): WRITE block 973344112 on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
---counter=2---
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command

/dev/sdb:
 issuing standby command
/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
ITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
flush-9:0(31103): WRITE block 1199570968 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
flush-9:0(31103): WRITE block 1199571200 on md0
flush-9:0(31103): WRITE block 288 on md0
flush-9:0(31103): WRITE block 343933552 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
flush-9:0(31103): WRITE block 270424 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
jbd2/md0-8(7471): WRITE block 1200615768 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
jbd2/md0-8(7471): WRITE block 973344280 on md0
jbd2/md0-8(7471): WRITE block 973344288 on md0
jbd2/md0-8(7471): WRITE block 973344296 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
smbd(31117): dirtied inode 37486599 (locking.tdb) on md0
smbd(31117): dirtied inode 37486599 (locking.tdb) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
jbd2/md0-8(7471): WRITE block 1200615768 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
jbd2/md0-8(7471): WRITE block 973344304 on md0
jbd2/md0-8(7471): WRITE block 973344312 on md0
jbd2/md0-8(7471): WRITE block 973344320 on md0
jbd2/md0-8(7471): WRITE block 973344328 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
flush-9:0(31103): WRITE block 1199571200 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
flush-9:0(31103): WRITE block 343933552 on md0
flush-9:0(31103): WRITE block 270424 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 37486599 (locking.tdb) on md0
smbd(31117): dirtied inode 37486599 (locking.tdb) on md0
jbd2/md0-8(7471): WRITE block 1200615768 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
jbd2/md0-8(7471): WRITE block 973344336 on md0
jbd2/md0-8(7471): WRITE block 973344344 on md0
jbd2/md0-8(7471): WRITE block 973344352 on md0
jbd2/md0-8(7471): WRITE block 973344360 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
flush-9:0(31103): WRITE block 270424 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 37486599 (locking.tdb) on md0
smbd(31117): dirtied inode 37486599 (locking.tdb) on md0
smbd(31117): dirtied inode 19985 (smbpasswd) on md9
jbd2/md0-8(7471): WRITE block 1200615768 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
kjournald(900): WRITE block 543040 on md9
md9_raid1(452): WRITE block 1060104 on sda1
md9_raid1(452): WRITE block 1060104 on sdb1
flush-9:0(31103): WRITE block 270424 on md0
jbd2/md0-8(7471): WRITE block 973344368 on md0
jbd2/md0-8(7471): WRITE block 973344376 on md0
jbd2/md0-8(7471): WRITE block 973344384 on md0
---counter=3---
Countdown:
10
9
8
7
6
5
4
3
2
1

/dev/sda:
 issuing standby command

/dev/sdb:
 issuing standby command
/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
1103): WRITE block 1199570968 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
flush-9:0(31103): WRITE block 288 on md0
jbd2/md0-8(7471): WRITE block 1200615776 on md0
jbd2/md0-8(7471): WRITE block 973344528 on md0
jbd2/md0-8(7471): WRITE block 973344536 on md0
jbd2/md0-8(7471): WRITE block 973344544 on md0
smbd(31117): dirtied inode 37486599 (locking.tdb) on md0
smbd(31117): dirtied inode 37486599 (locking.tdb) on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
flush-9:0(31103): WRITE block 1200615776 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
flush-9:0(31103): WRITE block 270424 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
jbd2/md0-8(7471): WRITE block 973344552 on md0
jbd2/md0-8(7471): WRITE block 973344560 on md0
jbd2/md0-8(7471): WRITE block 973344568 on md0
jbd2/md0-8(7471): WRITE block 973344576 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
flush-9:0(31103): WRITE block 1199571200 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
flush-9:0(31103): WRITE block 1200615776 on md0
jbd2/md0-8(7471): WRITE block 973344584 on md0
jbd2/md0-8(7471): WRITE block 973344592 on md0
jbd2/md0-8(7471): WRITE block 973344600 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
smbd(31117): dirtied inode 37486599 (locking.tdb) on md0
smbd(31117): dirtied inode 37486599 (locking.tdb) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
smbd(31117): dirtied inode 10748644 (putty.log) on md0
^[jbd2/md0-8(7471): WRITE block 1200615776 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
jbd2/md0-8(7471): WRITE block 973344608 on md0
jbd2/md0-8(7471): WRITE block 973344616 on md0
jbd2/md0-8(7471): WRITE block 973344624 on md0
jbd2/md0-8(7471): WRITE block 973344632 on md0
flush-9:0(31103): WRITE block 1199571200 on md0
flush-9:0(31103): WRITE block 343933552 on md0
flush-9:0(31103): WRITE block 270424 on md0
md0_raid1(1087): WRITE block 1950387200 on sda3
md0_raid1(1087): WRITE block 1950387200 on sdb3
flush-9:0(31103): WRITE block 1200615776 on md0

etc etc etc....
Qnap TS-219+
Firmware 3.4.0 Build 0212T

Thanks in advance
Nial
Post Reply

Return to “HDD Spin Down (HDD Standby)”