QNAP NAS Community Forum

by **bigkid** » Sat Jun 23, 2012 9:30 am

Hi all.

Been slowly working through my network dealing with the variety of devices/servers etc that spin up the drives on my NAS. My home network has 3 x Windows 7 PCs and an A-300 PopcornHour NMT. The NMT was a constant source of spinning up the drives until I changed the NAS from a samba share to NFS and disabled Master browser on the NAS. Currently, one of the Windows PCs now seems to be waking the NAS. Everytime the PC is turned on, or reconnected to the network after being disconnected, the NAS drives almost immediately spin up.

I do not have the NAS mapped as a drive on the PC - which used to cause problems. I now access the NAS files from a link to the NAS name or IP on my desktop. I have disabled Network Discovery on the PC without any change. And the Node is 'Hybrid'.

I have also followed the instructions from QNAP Support and disabled: UPnP/Twonkymedia function on NAS; NTP server; BT download; Microsoft Networking -> AD service, WINS server, Domain Master; Share folder mapping; DMZ or port forwarding on the router/firewall; and QNAP Finder, Quick Install Wizard, NetBak Replication. I don't have any add-on programs and the NAS is not set up NAS as a DHCP client.

To troubleshoot I have tried blkdevMonitor.sh following the instructions but just can't get it to work, using either putty or WINSCP. Each time i get the following error when I run the script.

"-sh: /root/blkdevMonitor.sh: /bin/shM: bad interpreter: No such file or directory"

I am afraid I am a novice at such things and have no clue what is going on. When I attempted to download the script, it asked for an FTP user id and password. I don't have them, so, assuming it was just text, I copied it into notepad and saved it as blkdevMonitor.sh. Is this correct?

It was also suggested that I changed the 'rights to 777' on another forum, which I did, without any success.

Appreciate any advice as to how to get this script to work, or on what my PC might be doing to spin up the NAS drives.

Now, not sure if it is relevant, but I don't recall having this problem before the most recent firmware upgrade - but, the NMT was also causing spin-ups so it is hard to know.

Regards,

Allan

by **bigkid** » Sat Jun 23, 2012 1:03 pm

Hmmmm. Just turned on system connection logging on the NAS and apparently my PC is attempting to login via a SAMBA connection to the NAS every 20 minutes or so, and failing. Appreciate any advice on what might be doing this. No other PCs on the network are showing up in the log.

Regards,

Allan

edit......noticed this issue is dealt with, but possibly not resolved here: viewtopic.php?f=55&t=8895&start=15

Would still appreciate any response helping out with the blkdevMonitor.

a

by **schumaku** » Sat Jun 23, 2012 9:16 pm

Cconfigure same username/password pairs on the Windows system and the NAS, plus configure the access rights accordingly.

HDD can't spin-down when there are systems on the network continously discoveing the network environment (Windows Vosta or 7 doesn't so..!) or ie. Explorer is always trying to access with invalid usernames and passwords.

All my NAS where HDD spin-down is feasible remain with HDD spined-down over boot of any Winndow Vista or 7 system - and this situation remains so as long a the NAS shaes are not accessed.

BAck to your "-sh: /root/blkdevMonitor.sh: /bin/shM: bad interpreter: No such file or directory" message...

Something went wrong with downloading and saving the script. The message is typical if there is an invaild character - this could be an M or a contorol-M character - at the end of every line, ie.

#!/bin/shM
...

I'll suggest to do use a direct download to the NAS, to avoid any corrruption by non-Unix-text-file capable editors, ie on Windows:

1. Download the script direct to a share, ie.

[~] # cd /share/Public
[/share/Public] # wget http://us1.qnap.com/Storage/tsd/spindown/blkdevMonitor.zip
--2012-06-23 15:06:45-- http://us1.qnap.com/Storage/tsd/spindown/blkdevMonitor.zip
...
Saving to: `blkdevMonitor.zip'
...
2012-06-23 15:06:45 (45.2 MB/s) - `blkdevMonitor.zip' saved [1426/1426]

2. Extract the shell script from the ZIP archive:

[/share/Public] # unzip blkdevMonitor.zip
Archive: blkdevMonitor.zip
inflating: blkdevMonitor.sh

3. Now you have it ready for future usage:

[/share/Public] # ls -lss blk*
4 -rwxrwxrwx 1 admin administ 3340 Jun 23 15:08 blkdevMonitor.sh*

4. To use, copy the file to the RAM disk, ie. to /root and run from there:

[/share/Public] # cp blkdevMonitor.sh /root
[/share/Public] # cd /root
[~] # ./blkdevMonitor.sh

by **bigkid** » Sun Jun 24, 2012 9:55 am

Thanks for the very detailed and helpful advice schumaku. Appreciate you taking the time. I have made sure that my user id/password pair is on the PC and the NAS (it wasn't on the NAS). Will see if it helps. (edit. my PC now successfully logs on every 20 minutes - still keeping the discs spun up)

In the meantime I have managed to follow your great instructions on blkdevMonitor and managed to get it started. Is the following sufficient to indicate a problem?

Code: Select all: 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: issuing standby command setting standby immediately. /dev/sdd: issuing standby command setting standby immediately. /dev/sde: issuing standby command setting standby immediately. 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: issuing standby command setting standby immediately. /dev/sdd: issuing standby command setting standby immediately. /dev/sde: issuing standby command setting standby immediately. drive state is: active/idle smbd(2203): dirtied inode 416022533 (connections.tdb) on md0 smbd(2203): dirtied inode 416022533 (connections.tdb) on md0 smbd(2203): dirtied inode 13351 (smbpasswd) on md9 qLogEngined(27858): dirtied inode 26580 (conn.log-journal) on md9 qLogEngined(27858): WRITE block 557056 on md9 md9_raid1(1336): WRITE block 1060104 on sda1 md9_raid1(1336): WRITE block 1060104 on sde1 md9_raid1(1336): WRITE block 1060104 on sdd1 md9_raid1(1336): WRITE block 1060104 on sdc1 md9_raid1(1336): WRITE block 1060104 on sdb1 smbd(2203): dirtied inode 416022532 (sessionid.tdb) on md0 smbd(2203): dirtied inode 416022532 (sessionid.tdb) on md0 flush-9:9(1707): WRITE block 557064 on md9 flush-9:0(1708): WRITE block 28174181448 on md0 md0_raid5(2529): WRITE block 5857395368 on sda3 md0_raid5(2529): WRITE block 5857395368 on sde3 md0_raid5(2529): WRITE block 5857395368 on sdd3 md0_raid5(2529): WRITE block 5857395368 on sdc3 md0_raid5(2529): WRITE block 5857395368 on sdb3 jbd2/md0-8(2587): WRITE block 14642713248 on md0 kjournald(2023): WRITE block 18600 on md9 md9_raid1(1336): WRITE block 1060096 on sda1 md9_raid1(1336): WRITE block 1060096 on sde1 md9_raid1(1336): WRITE block 1060096 on sdd1 md9_raid1(1336): WRITE block 1060096 on sdc1 md9_raid1(1336): WRITE block 1060096 on sdb1 jbd2/md0-8(2587): WRITE block 14642713256 on md0 flush-9:0(1708): WRITE block 22459974848 on md0 flush-9:0(1708): WRITE block 22459974856 on md0 flush-9:0(1708): WRITE block 14900097704 on md0 smbd(2203): dirtied inode 416022533 (connections.tdb) on md0 flush-9:0(1708): WRITE block 22459974008 on md0 jbd2/md0-8(2587): WRITE block 14642713264 on md0 smbd(2203): dirtied inode 416022533 (connections.tdb) on md0 smbd(2203): dirtied inode 416022532 (sessionid.tdb) on md0 smbd(2203): dirtied inode 416022532 (sessionid.tdb) on md0 flush-9:0(1708): WRITE block 22459974848 on md0 flush-9:9(1707): WRITE block 557072 on md9 flush-9:9(1707): WRITE block 557080 on md9 flush-9:9(1707): WRITE block 557088 on md9 flush-9:9(1707): WRITE block 557096 on md9 flush-9:9(1707): WRITE block 557104 on md9 kjournald(2023): WRITE block 18608 on md9 kjournald(2023): WRITE block 18616 on md9 kjournald(2023): WRITE block 18624 on md9 kjournald(2023): WRITE block 18632 on md9 kjournald(2023): WRITE block 18640 on md9 kjournald(2023): WRITE block 18648 on md9 md9_raid1(1336): WRITE block 1060104 on sda1 md9_raid1(1336): WRITE block 1060104 on sde1 md9_raid1(1336): WRITE block 1060104 on sdd1 md9_raid1(1336): WRITE block 1060104 on sdc1 md9_raid1(1336): WRITE block 1060104 on sdb1 md9_raid1(1336): WRITE block 1060120 on sda1 md9_raid1(1336): WRITE block 1060120 on sde1 md9_raid1(1336): WRITE block 1060120 on sdd1 md9_raid1(1336): WRITE block 1060120 on sdc1 md9_raid1(1336): WRITE block 1060120 on sdb1 flush-9:0(1708): WRITE block 22459974856 on md0 ---counter=7--- 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: issuing standby command setting standby immediately. /dev/sdd: issuing standby command setting standby immediately. /dev/sde: issuing standby command setting standby immediately. md9_raid1(1336): WRITE block 1060096 on sdd1 md9_raid1(1336): WRITE block 1060096 on sdc1 md9_raid1(1336): WRITE block 1060096 on sdb1 kjournald(2023): WRITE block 18792 on md9 md9_raid1(1336): WRITE block 1060104 on sda1 md9_raid1(1336): WRITE block 1060104 on sde1 md9_raid1(1336): WRITE block 1060104 on sdd1 md9_raid1(1336): WRITE block 1060104 on sdc1 md9_raid1(1336): WRITE block 1060104 on sdb1 kjournald(2023): WRITE block 18800 on md9 md9_raid1(1336): WRITE block 1060104 on sda1 md9_raid1(1336): WRITE block 1060104 on sde1 md9_raid1(1336): WRITE block 1060104 on sdd1 md9_raid1(1336): WRITE block 1060104 on sdc1 md9_raid1(1336): WRITE block 1060104 on sdb1 md9_raid1(1336): WRITE block 1060104 on sda1 md9_raid1(1336): WRITE block 1060104 on sde1 md9_raid1(1336): WRITE block 1060104 on sdd1 md9_raid1(1336): WRITE block 1060104 on sdc1 md9_raid1(1336): WRITE block 1060104 on sdb1 md9_raid1(1336): WRITE block 1060096 on sda1 md9_raid1(1336): WRITE block 1060096 on sde1 md9_raid1(1336): WRITE block 1060096 on sdd1 md9_raid1(1336): WRITE block 1060096 on sdc1 md9_raid1(1336): WRITE block 1060096 on sdb1 md9_raid1(1336): WRITE block 1060104 on sda1 md9_raid1(1336): WRITE block 1060104 on sde1 md9_raid1(1336): WRITE block 1060104 on sdd1 md9_raid1(1336): WRITE block 1060104 on sdc1 md9_raid1(1336): WRITE block 1060104 on sdb1 md9_raid1(1336): WRITE block 1060104 on sda1 md9_raid1(1336): WRITE block 1060104 on sde1 md9_raid1(1336): WRITE block 1060104 on sdd1 md9_raid1(1336): WRITE block 1060104 on sdc1 md9_raid1(1336): WRITE block 1060104 on sdb1 flush-9:9(1707): WRITE block 524304 on md9 md9_raid1(1336): WRITE block 1060104 on sda1 md9_raid1(1336): WRITE block 1060104 on sde1 md9_raid1(1336): WRITE block 1060104 on sdd1 md9_raid1(1336): WRITE block 1060104 on sdc1 md9_raid1(1336): WRITE block 1060104 on sdb1 md9_raid1(1336): WRITE block 1060096 on sda1 md9_raid1(1336): WRITE block 1060096 on sde1 md9_raid1(1336): WRITE block 1060096 on sdd1 md9_raid1(1336): WRITE block 1060096 on sdc1 md9_raid1(1336): WRITE block 1060096 on sdb1 md9_raid1(1336): WRITE block 1060120 on sda1 md9_raid1(1336): WRITE block 1060120 on sde1 md9_raid1(1336): WRITE block 1060120 on sdd1 md9_raid1(1336): WRITE block 1060120 on sdc1 md9_raid1(1336): WRITE block 1060120 on sdb1 md9_raid1(1336): WRITE block 1060104 on sda1 md9_raid1(1336): WRITE block 1060104 on sde1 md9_raid1(1336): WRITE block 1060104 on sdd1 md9_raid1(1336): WRITE block 1060104 on sdc1 md9_raid1(1336): WRITE block 1060104 on sdb1 md9_raid1(1336): WRITE block 1060096 on sda1 md9_raid1(1336): WRITE block 1060096 on sde1 md9_raid1(1336): WRITE block 1060096 on sdd1 md9_raid1(1336): WRITE block 1060096 on sdc1 md9_raid1(1336): WRITE block 1060096 on sdb1 md9_raid1(1336): WRITE block 1060104 on sda1 md9_raid1(1336): WRITE block 1060104 on sde1 md9_raid1(1336): WRITE block 1060104 on sdd1 md9_raid1(1336): WRITE block 1060104 on sdc1 md9_raid1(1336): WRITE block 1060104 on sdb1 md9_raid1(1336): WRITE block 1060120 on sda1 md9_raid1(1336): WRITE block 1060120 on sde1 md9_raid1(1336): WRITE block 1060120 on sdd1 md9_raid1(1336): WRITE block 1060120 on sdc1 md9_raid1(1336): WRITE block 1060120 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: issuing standby command setting standby immediately. /dev/sdd: issuing standby command setting standby immediately. /dev/sde: issuing standby command setting standby immediately. ---counter=9--- Countdown: 10 ^C [~] #

Regards,

Allan

by **bigkid** » Sun Jun 24, 2012 3:55 pm

IT'S ASLEEP!!!!!!

I ran a check on all recently installed programs and Linksys EasyLink Advisor installed on my PC a few weeks ago caught my eye. This could be the culprit - perhaps running some service even if the program itself wasn't running.

Uninstalled it and 15 minutes later, the NAS is asleep.

Thank goodness that is over. With this and NMT sorted I think my work is done! (Famous last words perhaps? :wink:

)

Thanks schumaku.

Allan

QNAP NAS Community Forum

Windows 7 PC spinning up NAS drives - blkdevMonitor.sh??

Windows 7 PC spinning up NAS drives - blkdevMonitor.sh??

Re: Windows 7 PC spinning up NAS drives - blkdevMonitor.sh??

Re: Windows 7 PC spinning up NAS drives - blkdevMonitor.sh??

Re: Windows 7 PC spinning up NAS drives - blkdevMonitor.sh??

Re: Windows 7 PC spinning up NAS drives - blkdevMonitor.sh??

Who is online