QNAP NAS NO STANDBY

[AlexKe]

Hi StarMox

To identify the HDD standby issue, please also check if the following services are running.

 UPnP function on NAS
 NTP server
 BT download
 AD service
 QNAP Finder (close finder)
 Share folder mapping (SAMBA /AFP)
 Web Server
 Twonky Media server

FAQ
http://www.qnap.com/faq_detail.asp?faq_id=525

[danibas]

Can anyone please help me by analyzing the Putty output about the -not- hard-disk spinning down om my QNap TS 119? Thanks in advance!

Code: Select all

...
/dev/sda:
 issuing standby command
 setting standby immediately.
/dev/sdb: No such device or address
/dev/sdc: No such device or address
/dev/sdd: No such device or address
/dev/sde: No such device or address
qLogEngined(3832): WRITE block 393408 on md9
qLogEngined(3832): WRITE block 393416 on md9
qLogEngined(3832): WRITE block 393424 on md9
qLogEngined(3832): WRITE block 393440 on md9
md9_raid1(413): WRITE block 1060104 on sda1
md9_raid1(413): WRITE block 1060112 on sda1
kjournald(1002): WRITE block 30488 on md9
kjournald(1002): WRITE block 30496 on md9
kjournald(1002): WRITE block 30504 on md9
kjournald(1002): WRITE block 30512 on md9
kjournald(1002): WRITE block 30520 on md9
kjournald(1002): WRITE block 30528 on md9
kjournald(1002): WRITE block 30536 on md9
kjournald(1002): WRITE block 30544 on md9
kjournald(1002): WRITE block 30552 on md9
md9_raid1(413): WRITE block 1060104 on sda1
kjournald(1002): WRITE block 30560 on md9
md9_raid1(413): WRITE block 1060104 on sda1
kjournald(1002): WRITE block 30568 on md9
md9_raid1(413): WRITE block 1060104 on sda1
qLogEngined(3832): WRITE block 393336 on md9
qLogEngined(3832): WRITE block 425984 on md9
qLogEngined(3832): WRITE block 425992 on md9
qLogEngined(3832): WRITE block 426016 on md9
qLogEngined(3832): WRITE block 426024 on md9
qLogEngined(3832): WRITE block 426032 on md9
qLogEngined(3832): WRITE block 426040 on md9
qLogEngined(3832): WRITE block 426056 on md9
qLogEngined(3832): WRITE block 426064 on md9
qLogEngined(3832): WRITE block 426104 on md9
qLogEngined(3832): WRITE block 426112 on md9
qLogEngined(3832): WRITE block 429184 on md9
qLogEngined(3832): WRITE block 430592 on md9
qLogEngined(3832): WRITE block 431520 on md9
qLogEngined(3832): WRITE block 431680 on md9
qLogEngined(3832): WRITE block 431784 on md9
qLogEngined(3832): WRITE block 432688 on md9
qLogEngined(3832): WRITE block 433112 on md9
qLogEngined(3832): WRITE block 433208 on md9
qLogEngined(3832): WRITE block 433216 on md9
qLogEngined(3832): WRITE block 433256 on md9
qLogEngined(3832): WRITE block 433264 on md9
qLogEngined(3832): WRITE block 433280 on md9
qLogEngined(3832): WRITE block 433288 on md9
kjournald(1002): WRITE block 30576 on md9
kjournald(1002): WRITE block 30584 on md9
md9_raid1(413): WRITE block 1060104 on sda1
kjournald(1002): WRITE block 30592 on md9
md9_raid1(413): WRITE block 1060104 on sda1
md9_raid1(413): WRITE block 1060104 on sda1
md9_raid1(413): WRITE block 1060096 on sda1
flush-8:0(525): WRITE block 869400456 on sda3
flush-8:0(525): WRITE block 869400464 on sda3
flush-8:0(525): WRITE block 869400472 on sda3
flush-8:0(525): WRITE block 869381984 on sda3
flush-8:0(525): WRITE block 869401592 on sda3
flush-8:0(525): WRITE block 869405984 on sda3
flush-8:0(525): WRITE block 869406040 on sda3
kjournald(1305): WRITE block 869318728 on sda3
kjournald(1305): WRITE block 28968 on sda3
kjournald(1305): WRITE block 28976 on sda3
kjournald(1305): WRITE block 28984 on sda3
kjournald(1305): WRITE block 28992 on sda3
kjournald(1305): WRITE block 29000 on sda3
kjournald(1305): WRITE block 29008 on sda3
kjournald(1305): WRITE block 29016 on sda3
kjournald(1305): WRITE block 29024 on sda3
kjournald(1305): WRITE block 29032 on sda3
kjournald(1305): WRITE block 29040 on sda3
kjournald(1305): WRITE block 29048 on sda3
md9_raid1(413): WRITE block 1060104 on sda1
md9_raid1(413): WRITE block 1060104 on sda1
md9_raid1(413): WRITE block 1060112 on sda1
flush-9:9(20798): WRITE block 524304 on md9
md9_raid1(413): WRITE block 1060104 on sda1
md9_raid1(413): WRITE block 1060096 on sda1
md9_raid1(413): WRITE block 1060120 on sda1
md9_raid1(413): WRITE block 1060104 on sda1
md9_raid1(413): WRITE block 1060096 on sda1
md9_raid1(413): WRITE block 1060104 on sda1
md9_raid1(413): WRITE block 1060120 on sda1
kjournald(1002): WRITE block 30600 on md9
md9_raid1(413): WRITE block 1060104 on sda1
md9_raid1(413): WRITE block 1060096 on sda1
kjournald(1002): WRITE block 30608 on md9
kjournald(1002): WRITE block 30616 on md9
kjournald(1002): WRITE block 30624 on md9
kjournald(1002): WRITE block 30632 on md9
kjournald(1002): WRITE block 30640 on md9
kjournald(1002): WRITE block 30648 on md9
kjournald(1002): WRITE block 30656 on md9
md9_raid1(413): WRITE block 1060104 on sda1
kjournald(1002): WRITE block 30664 on md9
md9_raid1(413): WRITE block 1060104 on sda1
md9_raid1(413): WRITE block 1060104 on sda1
md9_raid1(413): WRITE block 1060096 on sda1
md9_raid1(413): WRITE block 1060104 on sda1
flush-8:0(525): WRITE block 869269536 on sda3
flush-8:0(525): WRITE block 869392944 on sda3
flush-8:0(525): WRITE block 0 on sda3
flush-8:0(525): WRITE block 208 on sda3
flush-8:0(525): WRITE block 238551056 on sda3
flush-8:0(525): WRITE block 454033648 on sda3
flush-8:0(525): WRITE block 869269504 on sda3
flush-8:0(525): WRITE block 869269512 on sda3
flush-8:0(525): WRITE block 869269520 on sda3
md9_raid1(413): WRITE block 1060104 on sda1
smbd(29083): dirtied inode 54329348 (connections.tdb) on sda3
smbd(29083): dirtied inode 54329348 (connections.tdb) on sda3
flush-9:9(20798): WRITE block 0 on md9
md9_raid1(413): WRITE block 1060104 on sda1
md9_raid1(413): WRITE block 1060096 on sda1
flush-9:9(20798): WRITE block 8 on md9
flush-9:9(20798): WRITE block 262416 on md9
flush-9:9(20798): WRITE block 262424 on md9
flush-9:9(20798): WRITE block 262432 on md9
flush-9:9(20798): WRITE block 327680 on md9
md9_raid1(413): WRITE block 1060104 on sda1
md9_raid1(413): WRITE block 1060112 on sda1
md9_raid1(413): WRITE block 1060104 on sda1
md9_raid1(413): WRITE block 1060096 on sda1
md9_raid1(413): WRITE block 1060104 on sda1
md9_raid1(413): WRITE block 1060104 on sda1
md9_raid1(413): WRITE block 1060112 on sda1
flush-8:0(525): WRITE block 869400464 on sda3
flush-8:0(525): WRITE block 869400472 on sda3
flush-8:0(525): WRITE block 869381984 on sda3
kjournald(1305): WRITE block 29056 on sda3
kjournald(1305): WRITE block 29064 on sda3
kjournald(1305): WRITE block 29072 on sda3
nmbd(18867): dirtied inode 54329365 (wins.dat.18867) on sda3
nmbd(18867): dirtied inode 54329425 (?) on sda3
---counter=4---
Countdown:
10
9
8
7
6
5
4
3
2
1

[schumaku]

Code: Select all

smbd(29083): dirtied inode 54329348 (connections.tdb) on sda3
smbd(29083): dirtied inode 54329348 (connections.tdb) on sda3

a) Any Windows resp. Microsoft Networking Clients keeping the connetivity up (ie. a recently update WD media player)?

Code: Select all

nmbd(18867): dirtied inode 54329365 (wins.dat.18867) on sda3
nmbd(18867): dirtied inode 54329425 (?) on sda3

b) Why is WINS activated in the Microsfto Networking Services?

[No Expert]

I have exactly the same problem on my TS-110.
There are a lot of users with this issue as well, see here: http://forum.qnap.com/viewtopic.php?f=50&t=41291

Also, this person has exactly the same issue, so I'm not alone:
http://forum.qnap.com/viewtopic.php?f=5 ... 42#p226592

I used version 3.3.9 for months and that did allow disks to spindown and the LEDs did not flash.
I made the mistake of upgrading to 3.5 and now both the yellow and green LEDs are on 24/7.

I tried downgrading back to 3.3.9 but it will not accept it, the error message is: "Update failed. Please check the firmware version."
To be honest, I was quite happy with 3.3.9 but I cannot even go back to the old version now.

To be clear: there was no configuration change before upgrading to 3.5.

Can anyone from Qnap please help?

EDIT: I managed to resolve this (hopefully permanently) by doing a clean,manual installation of the firmware as described here:
http://forum.qnap.com/viewtopic.php?p=213779
http://forum.qnap.com/viewtopic.php?t=9737

[MightyAtom]

I have the same problem. Ironically the NAS was only upgraded to 3.5 when a QNAP rep accessed it in an abortive attempt to get XDove working. (don't even get me started with that)

My blkdevMonitor results are :

/dev/sda:
issuing standby command

/dev/sdb:
issuing standby command

/dev/sdc:
issuing standby command

/dev/sdd:
issuing standby command
/dev/sde: No such device or address
drive state is: active/idle
jbd2/md0-8(2260): WRITE block 3901205104 on md0
md0_raid10(2224): WRITE block 3903891200 on sda3
md0_raid10(2224): WRITE block 3903891200 on sdd3
md0_raid10(2224): WRITE block 3903891200 on sdc3
md0_raid10(2224): WRITE block 3903891200 on sdb3
jbd2/md0-8(2260): WRITE block 3901205112 on md0
jbd2/md0-8(2260): WRITE block 3901205120 on md0
jbd2/md0-8(2260): WRITE block 3901205128 on md0
jbd2/md0-8(2260): WRITE block 3901205136 on md0
jbd2/md0-8(2260): WRITE block 3901205144 on md0
jbd2/md0-8(2260): WRITE block 3901205152 on md0


Can anyone advise what this means?

thks


jbd2/md0-8(2260): WRITE block 3901205160 on md0

[TonyPh12345]

... it means you didn't run the script long enough to get the culprit. You need to see a "dirtied inode" message, which isn't shown above.

[Federico]

Before the last firmware, I had 300 connection all day long, now is over 900. Download Station is always enable but not active (up/down)Torrent, everything is clear from the list (removed).

No Standby since 4.3.x

No
 UPnP function on NAS
 NTP server
 AD service
 QNAP Finder (close finder)
 Share folder mapping (SAMBA /AFP)
 Web Server
 Twonky Media server

and I just disabled BT download and I still have over 500+ connections... (router with DD-WRT)

[schumaku]

Just woth no listener on the NAS, no new sessions can be enabled.

As long as the DS is up, new sessions can be establisehd - no matter if there are active seeds available. Other BT clients will connect looing for data, as well the DHT activities will be there. This does all lead to new sessions.

[No Expert]

I just tried the latest firmware, TS-110_3.5.1_Build1002, and the problem is still there, i.e. constant flashing of the LAN LED.
There is only one solution: downgrade to version TS-110_3.3.9_Build0120 which solves the problem... no more flashing.

So the solution is NOT to upgrade to the newest firmware as it appears to be buggy (at least for me).

I hope someone from Qnap is reading these posts.

[xavierh]

See if any of your samba shares have guest access enabled.... That did the trick for me.and all my devices go on standby for me. You can see on my signature the services that I have enabled on them


Sent from my iPad using Tapatalk

[MightyAtom]

My current opinion of this NAS box is that it is in breach of the goods and services act or whatever exists here in Australia.

It is sold as having a standby mode in which you see much lower power consumption and of course increased disk life.

In reality you have to turn off practically every single element of functionality - including it has been suggested, some shortcuts I have put on the PC desktops to help the family quickly find the right folders.

Seriously? What a crock.

A standby mode that means you have to disable all of the functionality of the system is not a standby mode.

I don't know why the QNAP feels it has to keep drives spinning just to retain some kind of polled presence on the network. It seems to me the coding of the standby functionality does not serve it's purpose. Wishing I had bought something else at the moment to be honest

rgds

[schumaku]

In reality you have to turn off practically every single element of functionality

Can't follow you. Have more than one QNAP NAS (actually on v3.5.1) with almost all services enabled - except of surveillance. We have a bunch of almost alwaqys-on Windows XP/Vista/7 and OS X systems (ancient and Lion), PS3, muliple DMP, iOS and Android devices...all-in-all about 160 devices with IP addresses on the net, dedicated ports forwarded for the download station. However ftp, ssh, Web server, or the admin Web UI are not accessible from the Internet. For secure home and SOHO data access we're using different VPN technologies, implemented on a security appliance; for the Web services I prefer my own server(s) on a dedicated housing site with multiple 1 GbE connections: All NAS do spin-down when it's feasible. In fact, some do spin-down where we don't want this to happen - as it's not configured accordignly.

It is sold as having a standby mode in which you see much lower power consumption and of course increased disk life.

Not sure if frequent spin-down and more critical the spin-up does expand the expected disk life time. Observation: We still manage som older systems - some run on SCSI HDD older than ten years now. Interesting enough, the always on devices create much less issues than the drives we have on stock for service and replacement purpoes.

[MightyAtom]

Hi Schumaku

First point re having to turn stuff off. I have in the past seen info advising many things stop the HD spin-down - for example drive mappings or running Twonky etc. On raising my current situation with QNAP - having run the blkdevmonitor script and providing the log - I was asked to provide a prtscr of the system services disable and then told to disable all of the services listed. I have avoided mapping shares to drive letters and got around that issue - I thought - by putting a shortcut on the PC desktops so that users (wife and children) can get to relevant directories quickly. I have been told by QNAP that even these shortcuts cause the mapping problem although i find that hard to believe.

So if you say in your case that all NAS do spin-down when it's feasible then 1) how have you achieved that 2) what does "feasible" mean?

In our case 2 or 3 PCs access the NAS.The PCs are off at night. In the morning the NAS will still be sat there with green lights all on and what seems to be a noisier fan than it used to be. I may be imaginging things but it seems to have got noisier since 3.5 was installed and I'm pretty sure spin down worked before that as well.

The only new thing on the network is a netgear WNCE2001 which spoofs wireless connectivety for a Topfield box I have. That is very often always on but it connects to the network not the NAS as such

Second point - I take your point. On the other hand the PCs get turned on an off everday with no ill effect so far. On the power and perhaps heat side of things it is defintely beneficial for the box to go into standby. (a bit power conscious right now as we just had solar put in)

Very interested in any other comments you or others have on this

thanks

[schumaku]

So if you say in your case that all NAS do spin-down when it's feasible then 1) how have you achieved that 2) what does "feasible" mean?

1) How? Have activated HDD standby.
2) Feasible means there are not many services exposed to the Internet (Web UI, Web Server, ftp server) which will almost certainly be queried, scanned, tested - and sometimes really used - much more frequent than the HDD spin-down can be ever active.

This #2 is also the reason you can't blame QNAP for wrong advertisiement. Compare your door bell system: In general it's idle and not making noise. When somebody is pushing the button, the door bel will ring. Would you blame the door bell manufacturer, too?

After the successful mapping, having a share mapped and create a shortcut alone from _normal_ clients like WIndows/OS X/generic Linux systems does not lead to ongoing activities keeping the disks busy. But then - having Windows Explorer or OS X Finder open on the share can cause activities. Refreshing, short WLAN disconnects and re-connects, ...

Of course, disabling services can be useful in a systematic search - but are certainly not aimed to be _the_ solution.

Thee can be many activities keeping the HD turning, or triggering a spin-up again: Process (aoplication) activities, netwsork services that can be triggered from the LAN or from the Internet, scheduled jobs, application and system activities on clcieents accessing the NAS. Trouble is that we have a large number of potential factors making it simply impossible to provide generic advise - beyond the pure forced HDD spin-down, and then monitoring the activities wetting the cache (read or write) - requiring the disks to spin-up again.

While some Twony versions were known to prohibit the HDD from spin-down due to some ongoing disk activities in the past, the newer Twonky 6 (available as QPKG) are fine. Of course, you must ensure the Twonky logging is turend off - othewiese simple DLNA activities will cause logging....as it's written to the disks...figure.

There are some network appliances (ie. digital media players), which are known to continously test the network for new servers, new shares, or constantly check if the shaes are still around. Some do (or did) this even when the device is in standby mode.

Please follow the HDD spin-down test procedures, and post results and observations into the appropriate and dedicated HDD spin-down forum here.

Hope tis gives some ideas, what can keep the disks spun-up.

[lmoseley]

All of the answers that have been given, about how one internal process or another is keeping the drives spinning, are garbage. If there is no external input, the processes should not be messing with the drive. If they are, it is a programming error. The solution is not to turn off all of the features of the QNAP box, thus removing all of its functionality... the solution is to find and fix the programming errors.

In my case, I unplugged the network cable from the back of the QNAP (thus removing any possibility of any external event keeping the drives spinning). Alter letting the QNAP sit unplugged from the network overnight, the drives are STILL SPINNING: programming error.

Has anyone "official" from QNAP made any comment about this matter? Are they looking for solutions? Or are we expected to live with the internal processes having a circle jerk with the drives forever?