TS-119 after setting to factory defaults does not spin-down

Discussion on setting up QNAP NAS products.

TS-119 after setting to factory defaults does not spin-down

Postby muko » Sun Jan 30, 2011 10:38 pm

Hello,

I have some problems with my newly bought TS-119, which I want to use witha Logitech SqueezeBox Touch.

The first installation went like a breeze: I installed Squeezecenter / SSOTS and all worked fine.

After some days, I recogized, that the disk spin-down did not work anymore. I'm sure that initially the spin-down did work. I'm not exactly sure if it still did after the SqueezeCenter installation.

I searched though the forums and found multiple reaons why this could happen and so I disabled all unnecessary services (even Samba) and also moved the SqueezeCenter directory to a USB memory stick.

But, still no luck...

Then I used the block dev monitor script to see if there were accesses to disk /dev/sda. I could not see anything suspicious.

Since the installation was that quick and simple, I decided to reset the device to factory defaults, upgrade the firmware and do the installation again.

The NAS now runs with firmware 3.3.9 Build 0105T after reset and upgrade. No SqueezeCenter installed yet. "Enable hard disk standby mode (if no access within 5 mins" active.

But the disk will not spin-down!

I did a "ps ax" (what is the dd writing to /mnt/HDA_ROOT/.logs/kmsg for, BTW??? the proc vanishes after some time) also used the block dev monitor again (I only see accesses to the ram disk). You can find the output of both below.

Any hint what might cause the disk not spinning down is greatly appreciated!

=========
ps ax:
=========
[~] # ps ax
PID Uid VmSize Stat Command
1 admin 644 S init
2 admin SW [kthreadd]
3 admin SW [ksoftirqd/0]
4 admin SW [events/0]
5 admin SW [khelper]
8 admin SW [async/mgr]
100 admin SW [sync_supers]
102 admin SW [bdi-default]
103 admin SW [kblockd/0]
109 admin SW [ata/0]
110 admin SW [ata_aux]
114 admin SW [khubd]
117 admin SW [kseriod]
143 admin SW [kswapd0]
144 admin SW [aio/0]
145 admin SW [crypto/0]
292 admin SW [scsi_tgtd/0]
294 admin SW [scsi_eh_0]
295 admin SW [scsi_eh_1]
309 admin SW [mtdblockd]
345 admin SW [kstriped]
374 admin SW [usbhid_resumer]
386 admin SW [scsi_eh_2]
387 admin SW [usb-storage]
398 admin SW [flush-1:0]
441 admin SW [md9_raid1]
477 admin SW [md13_raid1]
550 admin SW [kjournald]
637 admin 648 S /sbin/daemon_mgr
674 admin SW [rpciod/0]
683 admin SW [nfsiod]
690 admin SW< [kslowd000]
691 admin SW< [kslowd001]
696 admin 500 S < qWatcodogd: keeping alive every 5 seconds...
743 admin SW [kjournald]
754 admin SW [md1_raid1]
889 admin 556 S /sbin/modagent
946 admin SW [jbd2/sda3-8]
947 admin SW [ext4-dio-unwrit]
957 admin 992 S /sbin/hotswap
967 admin 904 S /sbin/qsmartd -d
1067 admin 216 S N /sbin/dhcpcd -h NASC0D42E -t 30 eth0
1263 admin 632 S /usr/sbin/mDNSResponderPosix -f /etc/config/mDNSResponderPosix.conf -b -P /var/lock/bonjour.normal
1499 admin 1188 S /usr/local/sbin/_thttpd_ -p 8080 -nor -nos -u admin -d /home/httpd -c **.*
1573 admin 1176 S /usr/local/sbin/Qthttpd -p 80 -nor -nos -u admin -d /home/Qhttpd -c **.*
1636 admin 740 S /usr/sbin/crond -l 9
1659 admin 720 S /usr/sbin/ntpdated
1673 admin 2296 S /usr/sbin/stunnel /etc/stunnel/stunnel.conf
1753 admin 1948 S /usr/sbin/sshd -f /etc/ssh/sshd_config -p 22
2577 admin 1240 S /sbin/bcclient
2593 admin 1324 S /sbin/picd
2650 admin 956 S /sbin/gpiod
2668 admin 1056 S /sbin/hwmond
2713 admin 960 S /usr/sbin/upsutil
2726 admin 888 S N /usr/bin/rsyncd --daemon --sever-mode=1
2777 admin 1112 S /sbin/hd_util
2790 admin 556 S /sbin/gen_bandwidth -r -i 5
2859 admin SW [iscsi_eh]
2867 admin SW [qnap_et]
2874 admin 448 S /sbin/iscsid --config=/etc/config/iscsi/sbin/iscsid.conf --initiatorname=/etc/iscsi/initiatorname.iscsi
2875 admin 2200 S < /sbin/iscsid --config=/etc/config/iscsi/sbin/iscsid.conf --initiatorname=/etc/iscsi/initiatorname.iscsi
2883 admin 1396 S qLogEngined: Write log is disabled...
2888 admin 796 S /sbin/qsyslogd
2894 admin 836 S /sbin/qShield
2927 admin 504 S /usr/sbin/upsd -u admin
2943 admin 976 S /bin/sh /etc/init.d/klogd.sh start
2951 admin 456 S /bin/dd if=/proc/kmsg of=/mnt/HDA_ROOT/.logs/kmsg bs=1 count=1024000
3259 admin 588 S /sbin/getty 115200 ttyS0
3330 admin 2700 S sshd: admin@pts/0
3333 admin SW [flush-9:9]
3334 admin 1300 S -sh
3341 admin SW [flush-9:13]
3346 admin 780 R ps ax

=======================
blkDevMonitor.sh
=======================
[~] # dmesg | more
ush-1:0(398): WRITE block 32794 on ram0
flush-1:0(398): WRITE block 65558 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
qwatchdogd(695): dirtied inode 2606 (.qwatchdog) on ram0
flush-1:0(398): WRITE block 24192 on ram0
_thttpd_(1498): dirtied inode 3574 (?) on ram0
_thttpd_(1498): dirtied inode 7047 (NAS) on ram0
_thttpd_(1498): dirtied inode 7047 (NAS) on ram0
_thttpd_(1498): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5288): dirtied inode 3574 (?) on ram0
gen_bandwidth(2789): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2789): dirtied inode 3564 (bandwidth_record.conf) on ram0
flush-1:0(398): WRITE block 16878 on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 32772 on ram0
flush-1:0(398): WRITE block 32794 on ram0
flush-1:0(398): WRITE block 65558 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
flush-1:0(398): WRITE block 24192 on ram0
_thttpd_(1498): dirtied inode 3574 (?) on ram0
_thttpd_(1498): dirtied inode 7047 (NAS) on ram0
_thttpd_(1498): dirtied inode 7047 (NAS) on ram0
_thttpd_(1498): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5318): dirtied inode 3574 (?) on ram0
flush-1:0(398): WRITE block 37890 on ram0
qwatchdogd(695): dirtied inode 2606 (.qwatchdog) on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 32772 on ram0
flush-1:0(398): WRITE block 32792 on ram0
flush-1:0(398): WRITE block 32794 on ram0
flush-1:0(398): WRITE block 65558 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
flush-1:0(398): WRITE block 24192 on ram0
gen_bandwidth(2789): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2789): dirtied inode 3564 (bandwidth_record.conf) on ram0
_thttpd_(1498): dirtied inode 3574 (?) on ram0
_thttpd_(1498): dirtied inode 7047 (NAS) on ram0
_thttpd_(1498): dirtied inode 7047 (NAS) on ram0
_thttpd_(1498): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
manaRequest.cgi(5341): dirtied inode 3574 (?) on ram0
sh(5363): dirtied inode 5281 (more) on ram0
muko
New here
 
Posts: 5
Joined: Sun Jan 30, 2011 10:30 pm
NAS Model: TS-109/209 Pro II

Re: TS-119 after setting to factory defaults does not spin-d

Postby AlexKe » Mon Jan 31, 2011 7:03 pm

Hi muko

Please close the browser when you run the script blkDevMonitor.sh.

_thttpd_(1498) --> web service
gen_bandwidth(2789) --> bandwidth monitor
manaRequest.cgi --> resource monitor

Triggered process:
flush-1
qwatchdogd
AlexKe
Experience counts
 
Posts: 1829
Joined: Wed Jan 06, 2010 2:49 pm
NAS Model: Not Selected

Re: TS-119 after setting to factory defaults does not spin-d

Postby muko » Tue Feb 01, 2011 6:10 am

Hi Alex,

thanks for your reply.

But why would accessing the ram disk (what I suppose ram0 is) cause the hard disk not to spin down?

For verifying, I started the TS-119 without a network connection. Did not change anything. Still did not spin downn the disk.

Maybe unrelated, but I still don't get what this process' purpose is (and that process *is* accessing the hard disk, it seems, althoug it stops after some time, so cannot be the only cause).

2776 admin 456 S /bin/dd if=/proc/kmsg of=/mnt/HDA_ROOT/.logs/kmsg bs=1 count=1024000

Thanks for any additional hint,
Muko
muko
New here
 
Posts: 5
Joined: Sun Jan 30, 2011 10:30 pm
NAS Model: TS-109/209 Pro II

Re: TS-119 after setting to factory defaults does not spin-d

Postby AlexKe » Tue Feb 01, 2011 5:36 pm

Hi Muko,
2776 admin 456 S /bin/dd if=/proc/kmsg of=/mnt/HDA_ROOT/.logs/kmsg bs=1 count=1024000

The process is a demand, to record system log on the dmesg and also add the new system log from dmesg into klog. Event without network connection, some application services might be running and keep HDD awake.

You can try to post the dmesg here to check what happen on your system. Also, you can try to set the HDD standby time at 5 minutes and run the blkDevMonitor.sh again after waiting for 5 minutes. [System Admin] > [Hardware] > Enable hard disk standby mode (if no access within "5" minutes Status LED will be off)

By the way, please make sure that after the HDD enter the standby mode, only the system status led will be turn off and the HDD led will keep lighting freen.
AlexKe
Experience counts
 
Posts: 1829
Joined: Wed Jan 06, 2010 2:49 pm
NAS Model: Not Selected

Re: TS-119 after setting to factory defaults does not spin-d

Postby muko » Wed Feb 02, 2011 4:32 am

Hi Alex,

You can try to post the dmesg here to check what happen on your system. Also, you can try to set the HDD standby time at 5 minutes and run the blkDevMonitor.sh again after waiting for 5 minutes. [System Admin] > [Hardware] > Enable hard disk standby mode (if no access within "5" minutes Status LED will be off)


So I did again. I closed the browser to not cause web accesses as you said might lead to disk access. The configuration already was set to spin-down after 5 mins.

Please find the dmesg output after 10 mins below. Again (as in the dmesg I pasted before), I only see ram0 access and still do not understand why that potentially could prevent the HDD from spinning down.

By the way, please make sure that after the HDD enter the standby mode, only the system status led will be turn off and the HDD led will keep lighting freen.


I'm not sure I understand... You say that when the HDD goes in stand-by, the "status" led will be switched off and the HDD led will stil be on? Yes, that is the behaviour when I force a spindown with "hdparm -y /dev/sda" (I use the blkDevMonitor.sh with the shutting down removed, in my understanding that is not necessary to track unwanted accesses, anyway).

Thanks for any help,
Muko

==============================
dmesg after using blkDevMonitor.sh
==============================

ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
flush-1:0(398): WRITE block 16878 on ram0
flush-1:0(398): WRITE block 16880 on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 65558 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
flush-1:0(398): WRITE block 36866 on ram0
qwatchdogd(694): dirtied inode 2606 (.qwatchdog) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 32792 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
flush-1:0(398): WRITE block 36866 on ram0
qwatchdogd(694): dirtied inode 2606 (.qwatchdog) on ram0
flush-1:0(398): WRITE block 16878 on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 32792 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
flush-1:0(398): WRITE block 36866 on ram0
flush-1:0(398): WRITE block 16878 on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 32792 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
qwatchdogd(694): dirtied inode 2606 (.qwatchdog) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
flush-1:0(398): WRITE block 36866 on ram0
qwatchdogd(694): dirtied inode 2606 (.qwatchdog) on ram0
flush-1:0(398): WRITE block 16878 on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 32792 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
flush-1:0(398): WRITE block 36866 on ram0
flush-1:0(398): WRITE block 16878 on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 32792 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
qwatchdogd(694): dirtied inode 2606 (.qwatchdog) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
hd_util(2778): dirtied inode 3591 (?) on ram0
hd_util(2778): dirtied inode 7047 (NAS) on ram0
hd_util(2778): dirtied inode 7047 (NAS) on ram0
hd_util(2778): dirtied inode 2610 (ledvalue) on ram0
hd_util(2778): dirtied inode 2610 (ledvalue) on ram0
hd_util(2778): dirtied inode 3591 (?) on ram0
hd_util(2778): dirtied inode 3591 (?) on ram0
flush-1:0(398): WRITE block 36866 on ram0
qwatchdogd(694): dirtied inode 2606 (.qwatchdog) on ram0
flush-1:0(398): WRITE block 16660 on ram0
flush-1:0(398): WRITE block 16878 on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 32772 on ram0
flush-1:0(398): WRITE block 32792 on ram0
flush-1:0(398): WRITE block 32798 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
flush-1:0(398): WRITE block 24192 on ram0
flush-1:0(398): WRITE block 26626 on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
flush-1:0(398): WRITE block 16878 on ram0
flush-1:0(398): WRITE block 16880 on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 65558 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
flush-1:0(398): WRITE block 36866 on ram0
qwatchdogd(694): dirtied inode 2606 (.qwatchdog) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 32792 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
flush-1:0(398): WRITE block 36866 on ram0
qwatchdogd(694): dirtied inode 2606 (.qwatchdog) on ram0
flush-1:0(398): WRITE block 16878 on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 32792 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
flush-1:0(398): WRITE block 36866 on ram0
flush-1:0(398): WRITE block 16878 on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 32792 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
qwatchdogd(694): dirtied inode 2606 (.qwatchdog) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
flush-1:0(398): WRITE block 36866 on ram0
qwatchdogd(694): dirtied inode 2606 (.qwatchdog) on ram0
flush-1:0(398): WRITE block 16878 on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 32792 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
flush-1:0(398): WRITE block 36866 on ram0
flush-1:0(398): WRITE block 16878 on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 32792 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
qwatchdogd(694): dirtied inode 2606 (.qwatchdog) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
hd_util(2778): dirtied inode 3591 (?) on ram0
hd_util(2778): dirtied inode 7047 (NAS) on ram0
hd_util(2778): dirtied inode 7047 (NAS) on ram0
hd_util(2778): dirtied inode 2610 (ledvalue) on ram0
hd_util(2778): dirtied inode 2610 (ledvalue) on ram0
hd_util(2778): dirtied inode 3591 (?) on ram0
hd_util(2778): dirtied inode 3591 (?) on ram0
flush-1:0(398): WRITE block 36866 on ram0
qwatchdogd(694): dirtied inode 2606 (.qwatchdog) on ram0
flush-1:0(398): WRITE block 16660 on ram0
flush-1:0(398): WRITE block 16878 on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 32772 on ram0
flush-1:0(398): WRITE block 32792 on ram0
flush-1:0(398): WRITE block 32798 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
flush-1:0(398): WRITE block 24192 on ram0
flush-1:0(398): WRITE block 26626 on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
flush-1:0(398): WRITE block 16878 on ram0
flush-1:0(398): WRITE block 16880 on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 65558 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
muko
New here
 
Posts: 5
Joined: Sun Jan 30, 2011 10:30 pm
NAS Model: TS-109/209 Pro II

Re: TS-119 after setting to factory defaults does not spin-d

Postby AlexKe » Wed Feb 02, 2011 10:44 am

Hi muko
Please find the dmesg output after 10 mins below.

Please help to connect to NAS and run the command below and port here to check if there is any abnormal system status.
[~] # dmesg

By the way, we are having Chinese new year vacation from 2/2 to 2/7. We will check the issue again after the vacation.
AlexKe
Experience counts
 
Posts: 1829
Joined: Wed Jan 06, 2010 2:49 pm
NAS Model: Not Selected

Re: TS-119 after setting to factory defaults does not spin-d

Postby muko » Mon Feb 07, 2011 1:07 am

QNAPAlex wrote:
Please find the dmesg output after 10 mins below.

Please help to connect to NAS and run the command below and port here to check if there is any abnormal system status.
[~] # dmesg


Hi Alex,

I must admit that I'm confused now. The output of dmesg is what I posted multiple times by now.

What I attach this time is again two dmesg outputs: the first right after the system has booted, the second after running "blkDevMonitor.sh 500".

Please let me know if you need anything else.

Thanks,
Muko

=======================================
dmesg after booting
=======================================

brd: module loaded
loop: module loaded
serial8250_PIC_init..uartclk = 200000000,baudDivisor = 651,irq = 34
qnap_pic_init: succeed to register misc device
tsinfo: create proc systemp successfully
tsinfo: create proc systemp successfully
Integrated Sata device found
IRQ 21/mvSata: IRQF_DISABLED is not guaranteed on shared IRQs
Spin up ...(0:0)
Spin up ...(0:1)
scsi0 : Marvell SCSI to SATA adapter
scsi1 : Marvell SCSI to SATA adapter
scsi 0:0:0:0: Direct-Access Hitachi HDS5C1010CLA382 JC4O PQ: 0 ANSI: 5
Check proc_name[mvSata].
Check proc_name[mvSata].
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512.
sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
sd 0:0:0:0: [sda] 0-byte physical blocks
SPI Serial flash detected @ 0xf4000000, 16384KB (64sec x 256KB)
Creating 6 MTD partitions on "spi_flash":
0x000000000000-0x000000080000 : "U-Boot"
0x000000200000-0x000000400000 : "Kernel"
0x000000400000-0x000000d00000 : "RootFS"
0x000000d00000-0x000001000000 : "RootFS2"
0x000000080000-0x0000000c0000 : "U-Boot Config"
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 23 00 10 00
0x0000000c0000-0x000000200000 : "NAS Config"
Loading Marvell Ethernet Driver:
o Cached descriptors in DRAM
o DRAM SW cache-coherency
o 1 Giga ports supported
o Single RX Queue support - ETH_DEF_RXQ=0
o Single TX Queue support - ETH_DEF_TXQ=0
o TCP segmentation offload (TSO) supported
o Large Receive offload (LRO) supported
o Receive checksum offload supported
o Transmit checksum offload supported
o Network Fast Processing (Routing) supported - (Disabled)
o Proc tool API enabled
o SKB Reuse supported - (Disabled)
o SKB Recycle supported - (Disabled)
o Rx descripors: q0=128
o Tx descripors: q0=532
o Loading network interface(s):
o register under mv88fx_eth platform
o eth0, ifindex = 2, GbE port = 0

mvFpRuleDb (00000010): 0 entries, 0 bytes
Marvell debug tracing is on
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512.
sda:
ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
sda1 sda2 sda3 sda4
ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512.
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
uhci_hcd: USB Universal Host Controller Interface driver
Initializing USB Mass Storage driver...
sd 0:0:0:0: [sda] Attached SCSI disk
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usb: create proc systemp successfully
usb: create proc systemp successfully
mice: PS/2 mouse device common for all mice
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid10 personality registered for level 10
md: raid6 personality registered for level 6
md: raid5 personality registered for level 5
md: raid4 personality registered for level 4
device-mapper: ioctl: 4.16.0-ioctl (2009-11-05) initialised: dm-devel@redhat.com
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 5
rtc kw_rtc: setting system clock to 2011-02-05 15:19:01 UTC (1296919141)
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=noautodetect
md: Autodetecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
RAMDISK: gzip image found at block 0
usb 1-1: new high speed USB device using ehci_marvell and address 2
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usb 1-1.3: new high speed USB device using ehci_marvell and address 3
scsi2 : usb-storage 1-1.3:1.0
VFS: Mounted root (ext2 filesystem) on device 1:0.
Freeing init memory: 136K
kjournald starting. Commit interval 5 seconds
EXT3-fs (sda1): mounted filesystem with writeback data mode
md: md9 stopped.
md: bind<sda1>
raid1: raid set md9 active with 1 out of 1 mirrors
md9: bitmap initialized from disk: read 5/5 pages, set 0 bits
created bitmap (65 pages) for device md9
md9: detected capacity change from 0 to 542769152
md9: unknown partition table
kjournald starting. Commit interval 5 seconds
EXT3-fs (md9): using internal journal
EXT3-fs (md9): mounted filesystem with writeback data mode
md: md13 stopped.
md: bind<sda4>
raid1: raid set md13 active with 1 out of 1 mirrors
md13: bitmap initialized from disk: read 4/4 pages, set 0 bits
created bitmap (57 pages) for device md13
md13: detected capacity change from 0 to 469893120
md13: unknown partition table
kjournald starting. Commit interval 5 seconds
EXT3-fs (md9): using internal journal
EXT3-fs (md9): mounted filesystem with writeback data mode
kjournald starting. Commit interval 5 seconds
EXT3-fs (md9): using internal journal
EXT3-fs (md9): mounted filesystem with writeback data mode
kjournald starting. Commit interval 5 seconds
EXT3-fs (md13): using internal journal
EXT3-fs (md13): recovery complete
EXT3-fs (md13): mounted filesystem with writeback data mode
scsi 2:0:0:0: Direct-Access CBM Flash Disk 5.00 PQ: 0 ANSI: 2
sd 2:0:0:0: Attached scsi generic sg18 type 0
sd 2:0:0:0: [sds] 8215552 512-byte logical blocks: (4.20 GB/3.91 GiB)
sd 2:0:0:0: [sds] Write Protect is off
sd 2:0:0:0: [sds] Mode Sense: 0b 00 00 08
sd 2:0:0:0: [sds] Assuming drive cache: write through
sd 2:0:0:0: [sds] Assuming drive cache: write through
sds: sds1
sd 2:0:0:0: [sds] Assuming drive cache: write through
sd 2:0:0:0: [sds] Attached SCSI removable disk
usbcore: registered new interface driver usblp
sysinfo: Module loaded.
ufsd: module license 'Commercial product' taints kernel.
Disabling lock debugging due to kernel taint
ufsd: driver U82 (Jan 5 2011 01:54:24) LBD=OFF with ioctl loaded at bf065000
NTFS read/write support included
Hfs+/HfsX read/write support included
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Slow work thread pool: Starting up
Slow work thread pool: Ready
Enable WDT...
eth0: mac address changed
eth0: link down
eth0: started
eth0: link up, full duplex, speed 100 Mbps
kjournald starting. Commit interval 5 seconds
EXT3-fs (md9): using internal journal
EXT3-fs (md9): mounted filesystem with writeback data mode
md: bind<sda2>
raid1: raid set md1 active with 1 out of 1 mirrors
md1: detected capacity change from 0 to 542769152
md1: unknown partition table
Adding 530040k swap on /dev/md1. Priority:-1 extents:1 across:530040k
active port 0 :139
active port 1 :445
active port 2 :20
EXT4-fs (sda3): mounted filesystem with ordered data mode
eth0: stopped
eth0: link down
eth0: started
eth0: stopped
eth0: started
eth0: link up, full duplex, speed 100 Mbps
active port 0 :139
active port 1 :445
active port 2 :20
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev sds1.
ufsd: Force nocase=1
ufsd: sds1 without journal
active port 0 :139
active port 1 :445
active port 2 :20
warning: process `pic_raw' used the deprecated sysctl system call with 8.1.2.
rule type=2, num=0
Loading iSCSI transport class v2.0-871.
iscsi: registered transport (tcp)

=======================================
dmesg after blkDevMonitor 500
=======================================

flush-1:0(398): WRITE block 24192 on ram0
flush-1:0(398): WRITE block 26626 on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
flush-1:0(398): WRITE block 16878 on ram0
flush-1:0(398): WRITE block 16880 on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 65558 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
flush-1:0(398): WRITE block 36866 on ram0
qwatchdogd(694): dirtied inode 2606 (.qwatchdog) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 32792 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
flush-1:0(398): WRITE block 36866 on ram0
flush-1:0(398): WRITE block 16878 on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 32792 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
qwatchdogd(694): dirtied inode 2606 (.qwatchdog) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
flush-1:0(398): WRITE block 36866 on ram0
flush-1:0(398): WRITE block 16878 on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 32792 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
qwatchdogd(694): dirtied inode 2606 (.qwatchdog) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
flush-1:0(398): WRITE block 36866 on ram0
flush-1:0(398): WRITE block 16878 on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 32792 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
qwatchdogd(694): dirtied inode 2606 (.qwatchdog) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
flush-1:0(398): WRITE block 36866 on ram0
flush-1:0(398): WRITE block 16878 on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 32792 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
qwatchdogd(694): dirtied inode 2606 (.qwatchdog) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
hd_util(2778): dirtied inode 3591 (?) on ram0
hd_util(2778): dirtied inode 7047 (NAS) on ram0
hd_util(2778): dirtied inode 7047 (NAS) on ram0
hd_util(2778): dirtied inode 2610 (ledvalue) on ram0
hd_util(2778): dirtied inode 2610 (ledvalue) on ram0
hd_util(2778): dirtied inode 3591 (?) on ram0
hd_util(2778): dirtied inode 3591 (?) on ram0
flush-1:0(398): WRITE block 36866 on ram0
flush-1:0(398): WRITE block 16660 on ram0
flush-1:0(398): WRITE block 16878 on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 32772 on ram0
flush-1:0(398): WRITE block 32792 on ram0
flush-1:0(398): WRITE block 32798 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
qwatchdogd(694): dirtied inode 2606 (.qwatchdog) on ram0
flush-1:0(398): WRITE block 24192 on ram0
flush-1:0(398): WRITE block 26626 on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
flush-1:0(398): WRITE block 16878 on ram0
flush-1:0(398): WRITE block 16880 on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 65558 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
flush-1:0(398): WRITE block 36866 on ram0
qwatchdogd(694): dirtied inode 2606 (.qwatchdog) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 32792 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
flush-1:0(398): WRITE block 36866 on ram0
flush-1:0(398): WRITE block 16878 on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 32792 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
qwatchdogd(694): dirtied inode 2606 (.qwatchdog) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
flush-1:0(398): WRITE block 36866 on ram0
flush-1:0(398): WRITE block 16878 on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 32792 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
qwatchdogd(694): dirtied inode 2606 (.qwatchdog) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
flush-1:0(398): WRITE block 36866 on ram0
flush-1:0(398): WRITE block 16878 on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 32792 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
qwatchdogd(694): dirtied inode 2606 (.qwatchdog) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
flush-1:0(398): WRITE block 36866 on ram0
flush-1:0(398): WRITE block 16878 on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 32792 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
qwatchdogd(694): dirtied inode 2606 (.qwatchdog) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
hd_util(2778): dirtied inode 3591 (?) on ram0
hd_util(2778): dirtied inode 7047 (NAS) on ram0
hd_util(2778): dirtied inode 7047 (NAS) on ram0
hd_util(2778): dirtied inode 2610 (ledvalue) on ram0
hd_util(2778): dirtied inode 2610 (ledvalue) on ram0
hd_util(2778): dirtied inode 3591 (?) on ram0
hd_util(2778): dirtied inode 3591 (?) on ram0
flush-1:0(398): WRITE block 36866 on ram0
flush-1:0(398): WRITE block 16660 on ram0
flush-1:0(398): WRITE block 16878 on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 32772 on ram0
flush-1:0(398): WRITE block 32792 on ram0
flush-1:0(398): WRITE block 32798 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
qwatchdogd(694): dirtied inode 2606 (.qwatchdog) on ram0
flush-1:0(398): WRITE block 24192 on ram0
flush-1:0(398): WRITE block 26626 on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
flush-1:0(398): WRITE block 16878 on ram0
flush-1:0(398): WRITE block 16880 on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 65558 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
flush-1:0(398): WRITE block 36866 on ram0
qwatchdogd(694): dirtied inode 2606 (.qwatchdog) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
gen_bandwidth(2788): dirtied inode 3564 (bandwidth_record.conf) on ram0
flush-1:0(398): WRITE block 32770 on ram0
flush-1:0(398): WRITE block 32792 on ram0
flush-1:0(398): WRITE block 2 on ram0
flush-1:0(398): WRITE block 4 on ram0
muko
New here
 
Posts: 5
Joined: Sun Jan 30, 2011 10:30 pm
NAS Model: TS-109/209 Pro II

Re: TS-119 after setting to factory defaults does not spin-d

Postby muko » Sat Feb 12, 2011 1:55 am

Hi Alex,

any new idea? Did I provide the info you asked for? Is there anything else I can do / check to help in identifying the problem?

Thanks,
Muko
muko
New here
 
Posts: 5
Joined: Sun Jan 30, 2011 10:30 pm
NAS Model: TS-109/209 Pro II

Re: TS-119 after setting to factory defaults does not spin-d

Postby koblmkh » Fri Apr 25, 2014 2:48 am

Hi all,

I know that this is an old post but I am facing the exact same Problem on my QNAP TS 669L with Firmware 4.0.7 and 6 disks from HGST (Hitachi HDS724040ALE640 MJAOA3B0). Since my reset a few days ago (and reacreate Storage Pool, Volume, ...) the initial synchronization is done but the disks won´t spin down even if I unplug the NAS from the Network so that there is definitely nothing accessing the Services from external.

I´ve checked the process Manager and it Shows not really a working process, sometimes it is "hal_daemon" running with 0.2% of CPU then it is "daemon_mgr" with about the same usage and so on but I cannot see any pattern in this Situation.

I´ve googled/binged some time and wasn´t very successfull but I´ve found this Forum entry with the same Problem and even the log entries look similar to me - I´ve checked with the following commands and I will Show the Output below:

"[...]Find out which process wakes up your hard drive
echo 1 > /proc/sys/vm/block_dump

This will turn on disk activity logging and you can read the output by:
dmesg

To turn this logging off:
echo 0 > /proc/sys/vm/block_dump [...]"

This is the result of dmesg:
[~] # dmesg
25): dirtied inode 2873 (?) on ram0
[ 3013.507066] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.507236] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.507405] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.507591] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.507768] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.507950] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.513197] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.513473] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.513758] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.513901] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.514097] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.514284] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.514520] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.514736] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.515093] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.515311] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.515604] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.515853] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.516102] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.516344] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.516604] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.516855] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.517100] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.517344] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.517604] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.517853] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.518117] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.518376] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.518602] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.518788] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.518972] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.519159] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.519341] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.519537] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.519723] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.519903] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.520085] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.520263] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.520455] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.520654] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.520802] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.520948] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.521094] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.521241] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.521387] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.521548] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.521698] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.521846] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.521992] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.522138] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.522282] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.522457] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.522608] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.522774] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.522893] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.522987] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.523101] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.523196] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.523304] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.523400] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.523527] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.523627] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.523734] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.523833] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.523943] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.524190] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.524447] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.524567] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.524673] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.524821] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.524921] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.525059] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.525214] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.525369] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.525532] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.525817] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.526038] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.526264] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.526367] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.526451] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.526518] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.526585] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.526649] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.526713] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.526777] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.526842] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.526905] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.526970] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.527190] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.527519] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.527623] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.527714] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.527804] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.527897] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.527988] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.528080] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.528170] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.528260] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.528350] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.528456] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.528549] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.528654] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.528759] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.529024] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.529291] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.529410] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0
[ 3013.529630] manaRequest.cgi(6325): dirtied inode 2873 (?) on ram0

Is anyone having an idea what I can/should do against this as it is quite annoying that the disks ran all the time...

Thank you very much in advance!

BR
Karl
koblmkh
First post
 
Posts: 1
Joined: Thu May 09, 2013 3:47 pm
NAS Model: TS-x69L

Re: TS-119 after setting to factory defaults does not spin-d

Postby schumaku » Fri Apr 25, 2014 2:24 pm

Hello Karl,

How wonderful to necro-post reopen a thread form 2011, and file "proof" of processes prohibiting HD spin down. Nota bene: Processes accessing the RAM disk.

1. There is a sub-forum dedicated to HDD Spin Down (HDD Standby).

2. There is a process (no doubt making use of the similar approach like yours) to Find out which process prevents the hard drives from spindown. Please use the script as provided, use exactly as shown, avoid keeping the QTS GUI or any management apps open concurrently, and file your finding to the sub-forum referenced above.

Regards,
-Kurt.
User avatar
schumaku
Guru
 
Posts: 30518
Joined: Mon Jan 21, 2008 4:41 pm
Location: Kloten (Zurich), Switzerland -- Skype: schumaku
NAS Model: TS-x79 Pro


Return to Turbo Station Installation & Setup

Who is online

Users browsing this forum: No registered users and 3 guests