Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
No servers running, no daylight savings etc. and no clients connected. The only thing running is telnet. Anyone knows which process that can cause this? And it is exactly every 10 minutes.
/gotdiskey
Offline
I think we already covered this in a previous post. If you have tried to use the printer, there might be failed jobs in your lp queue which is located on disc #1. This will cause spin-ups.
HTH/Apan
Last edited by Apskaft (2007-02-02 11:43:26)
Offline
Thanks. I'll just create a script for deleting old jobs then (if I can't find any built in functionality for that)?
/gotdiskey
Offline
Have to add,
Mine does this now and there are no files in the lpd directory.
It was not doing it, went to the web interface and shut the unit down as I had to move it. Power it back up and it's powering down between 8-9 minutes and back up one minute later.
Any other ideas?
I should add, both drives spin up, not just disk 1 for me
Last edited by LifeTap (2007-02-05 07:11:09)
Offline
LifeTap wrote:
Any other ideas?
Yup one more.....do you have iTunes server or uPnP server enabled? I noticed while looking in the mt-daapd.conf file that it stores it's stuff on /mnt/HD_a2/.systemfiles, and if you have these servers running then they will most likely scan your drives occasionally.
Disable the servers and see if the spin-up disappears. Then; check your /etc/mt-daapd.conf to see if there is anything you can modify within....
HTH/Apan
Offline
Those are disabled, just using this as a plain file and print server. Thou I did fix it in an odd way. I printed. Printed one page from a website and now it spins down and stays that way until I access something on the drive.
So far I have been able to reproduce this. I'll shutdown or restart the unit from the webpage. When it comes back up it will spin the disks up every ~10 or so. If I print something that stops and it will stay in disk power save mode. I'd look into this more, but I'm stumped and don't know where else to look. At least I can make it stop spinning the disks up all the time.
Offline
What FW are you on LifeTap?
/gotdiskey
Offline
I'm running 1.02. disks are in a raid 1 configuration. All services are disabled, I just use file and print sharing right now.
Offline
I've started a Known Issues page on the Wiki where I've included information from this and other threads.
http://dns323.kood.org/information:known_issues
/Apan
Offline
Well, I have the issue again. Drives won't stay spun down. New firmware, tried the above tricks already. Everything disabled, etc. Will look into it when I get back from work.
Offline
At one stage my box was not able to spin down the disks. I don’t uses the printer facility, but anyway I tried the lp-queue clearing workaround currently described in the wiki know issue section, without any improvements. I did a lot of unsuccessfully experiments. First after resetting to factory setting, the disks were able to spin down again (and stay down). I was not able to reproduce the issue again. In this forum I have seen indication of some similar weird cases, but no solid explanation yet.
FW 1.02b
Offline
I think i ran after a similar issue now , after installing debian.
i've used the fun_plug and linuxrc from the wiki, now the disks are waking up exactly every hour.
looks like it is some daemon accessing /mnt/HD_a2 and thus spinning the disks up.
would that be solved, if i run my chroot environment from an USB stick attached to the box?
Offline
hwahrmann wrote:
I think i ran after a similar issue now , after installing debian.
i've used the fun_plug and linuxrc from the wiki, now the disks are waking up exactly every hour.
could be cron. check if there's an hourly cronjob ("crontab -l").
Offline
nope,
crontab is empty.
Offline
I had experienced similar problem, killing the queue (directory deleted), didn't solve it and since I do not use printig via DNS323 I simply kill print deamon in fun_plug - disk spin down normally now
Here's the script (part of it) - I kill both print deamon and fancontrol (I made a custom one, which I start at boot):
kill -9 `pidof fancontrol` && echo Killed fancontrol >> /mnt/HD_a2/messages.txt
kill -9 `pidof lpd Waiting` && echo Killed print deamon >> /mnt/HD_a2/messages.txt
Solves the problem for me, but if you use DNS323 as a print server, it is obviously not a way to go...
Offline
lol
syslogd was writing it's mark, "-- MARK --" , into the log every 20 minutes, causing the HD to spin up again and again.
added the "-m 0" option and now the HD go to sleep and stay there until i access them.
Offline
I don't think syslogd is running (or for that matter - even exists) on my system, and I have the same problem...
Offline
yes, started with me again.
traced it down to fancontrol.
While the standard fancontrol is running the disk spins down.
when i kill fancontrol and use the custom script from the wiki, then the disks keep running.
Offline
Sorry I didn't understand. The standard is working fine? I did not use any hack except for telnet access. The problem started after upgrading to 1.02 for me. Before that everything was OK. However I can't say that the upgrade itself caused the spin down problem.
Offline
My disk has been waking up every 10 minutes after installing the debian chroot. I think I found the problem but I'm not sure what disabling getdhcp will do to me.
I telnet into my non-chroot dns-323 (firmware 1.03):
crontab -l 32 2 * * * /usr/sbin/rtc -s 30 2 2 * * /usr/sbin/rtc -c 59 1 * * * /usr/sbin/daylight& */10 * * * * /usr/sbin/getdhcp&
.. but the syslog in my etch chroot is waking up ~2 minutes and 15 seconds before each getdhcp... hmmm..
anyway, I'm going to put @ondro727's
kill -9 `pidof lpd Waiting'
into my fun_plug before I get rid of my getdhcp - to see if lpd is the evil, instead..
.. and if you really want to see my chroot etch syslog : ):
Apr 9 20:10:01 dns323-1 crond[1069]: USER root pid 6481 cmd /usr/sbin/getdhcp& Apr 9 20:18:05 dns323-1 kernel: Apr 9 20:18:05 dns323-1 kernel: *************************************** Apr 9 20:18:05 dns323-1 kernel: * HD0 stand by now! * Apr 9 20:18:05 dns323-1 kernel: *************************************** Apr 9 20:18:05 dns323-1 kernel: Apr 9 20:18:05 dns323-1 kernel: *************************************** Apr 9 20:18:05 dns323-1 kernel: * HD1 stand by now! * Apr 9 20:18:05 dns323-1 kernel: *************************************** Apr 9 20:18:37 dns323-1 kernel: Apr 9 20:18:37 dns323-1 kernel: ####################################### Apr 9 20:18:37 dns323-1 kernel: # HD1 awake now ! # Apr 9 20:18:37 dns323-1 kernel: ####################################### Apr 9 20:18:45 dns323-1 kernel: Apr 9 20:18:45 dns323-1 kernel: ####################################### Apr 9 20:18:45 dns323-1 kernel: # HD0 awake now ! # Apr 9 20:18:45 dns323-1 kernel: ####################################### Apr 9 20:20:01 dns323-1 crond[1069]: USER root pid 6505 cmd /usr/sbin/getdhcp& Apr 9 20:28:05 dns323-1 kernel: Apr 9 20:28:05 dns323-1 kernel: *************************************** Apr 9 20:28:05 dns323-1 kernel: * HD0 stand by now! * Apr 9 20:28:05 dns323-1 kernel: *************************************** Apr 9 20:28:05 dns323-1 kernel: Apr 9 20:28:05 dns323-1 kernel: *************************************** Apr 9 20:28:05 dns323-1 kernel: * HD1 stand by now! * Apr 9 20:28:05 dns323-1 kernel: *************************************** Apr 9 20:28:38 dns323-1 kernel: Apr 9 20:28:38 dns323-1 kernel: ####################################### Apr 9 20:28:38 dns323-1 kernel: # HD1 awake now ! # Apr 9 20:28:38 dns323-1 kernel: ####################################### Apr 9 20:28:46 dns323-1 kernel: Apr 9 20:28:46 dns323-1 kernel: ####################################### Apr 9 20:28:46 dns323-1 kernel: # HD0 awake now ! # Apr 9 20:28:46 dns323-1 kernel: ####################################### Apr 9 20:30:01 dns323-1 crond[1069]: USER root pid 6529 cmd /usr/sbin/getdhcp& Apr 9 20:38:06 dns323-1 kernel: Apr 9 20:38:06 dns323-1 kernel: *************************************** Apr 9 20:38:06 dns323-1 kernel: * HD0 stand by now! * Apr 9 20:38:06 dns323-1 kernel: *************************************** Apr 9 20:38:06 dns323-1 kernel: Apr 9 20:38:06 dns323-1 kernel: *************************************** Apr 9 20:38:06 dns323-1 kernel: * HD1 stand by now! * Apr 9 20:38:06 dns323-1 kernel: *************************************** Apr 9 20:38:39 dns323-1 kernel: Apr 9 20:38:39 dns323-1 kernel: ####################################### Apr 9 20:38:39 dns323-1 kernel: # HD1 awake now ! # Apr 9 20:38:39 dns323-1 kernel: ####################################### Apr 9 20:38:47 dns323-1 kernel: Apr 9 20:38:47 dns323-1 kernel: ####################################### Apr 9 20:38:47 dns323-1 kernel: # HD0 awake now ! # Apr 9 20:38:47 dns323-1 kernel: ####################################### Apr 9 20:40:01 dns323-1 crond[1069]: USER root pid 6553 cmd /usr/sbin/getdhcp&
I want to be as non-invasive in my surgery as possible..
best wishes, all. I'm having fun, hope you are, too.
Last edited by someguy (2007-04-11 04:16:19)
Offline
someguy wrote:
.. and if you really want to see my chroot etch syslog : ):
Code:
Apr 9 20:10:01 dns323-1 crond[1069]: USER root pid 6481 cmd /usr/sbin/getdhcp& Apr 9 20:18:05 dns323-1 kernel: Apr 9 20:18:05 dns323-1 kernel: *************************************** Apr 9 20:18:05 dns323-1 kernel: * HD0 stand by now! * Apr 9 20:18:05 dns323-1 kernel: *************************************** Apr 9 20:18:05 dns323-1 kernel: Apr 9 20:18:05 dns323-1 kernel: *************************************** Apr 9 20:18:05 dns323-1 kernel: * HD1 stand by now! * Apr 9 20:18:05 dns323-1 kernel: *************************************** Apr 9 20:18:37 dns323-1 kernel: Apr 9 20:18:37 dns323-1 kernel: ####################################### Apr 9 20:18:37 dns323-1 kernel: # HD1 awake now ! # Apr 9 20:18:37 dns323-1 kernel: ####################################### Apr 9 20:18:45 dns323-1 kernel: Apr 9 20:18:45 dns323-1 kernel: ####################################### Apr 9 20:18:45 dns323-1 kernel: # HD0 awake now ! # Apr 9 20:18:45 dns323-1 kernel: ####################################### Apr 9 20:20:01 dns323-1 crond[1069]: USER root pid 6505 cmd /usr/sbin/getdhcp& Apr 9 20:28:05 dns323-1 kernel: Apr 9 20:28:05 dns323-1 kernel: *************************************** Apr 9 20:28:05 dns323-1 kernel: * HD0 stand by now! * Apr 9 20:28:05 dns323-1 kernel: *************************************** Apr 9 20:28:05 dns323-1 kernel: Apr 9 20:28:05 dns323-1 kernel: *************************************** Apr 9 20:28:05 dns323-1 kernel: * HD1 stand by now! * Apr 9 20:28:05 dns323-1 kernel: *************************************** Apr 9 20:28:38 dns323-1 kernel: Apr 9 20:28:38 dns323-1 kernel: ####################################### Apr 9 20:28:38 dns323-1 kernel: # HD1 awake now ! # Apr 9 20:28:38 dns323-1 kernel: ####################################### Apr 9 20:28:46 dns323-1 kernel: Apr 9 20:28:46 dns323-1 kernel: ####################################### Apr 9 20:28:46 dns323-1 kernel: # HD0 awake now ! # Apr 9 20:28:46 dns323-1 kernel: ####################################### Apr 9 20:30:01 dns323-1 crond[1069]: USER root pid 6529 cmd /usr/sbin/getdhcp& Apr 9 20:38:06 dns323-1 kernel: Apr 9 20:38:06 dns323-1 kernel: *************************************** Apr 9 20:38:06 dns323-1 kernel: * HD0 stand by now! * Apr 9 20:38:06 dns323-1 kernel: *************************************** Apr 9 20:38:06 dns323-1 kernel: Apr 9 20:38:06 dns323-1 kernel: *************************************** Apr 9 20:38:06 dns323-1 kernel: * HD1 stand by now! * Apr 9 20:38:06 dns323-1 kernel: *************************************** Apr 9 20:38:39 dns323-1 kernel: Apr 9 20:38:39 dns323-1 kernel: ####################################### Apr 9 20:38:39 dns323-1 kernel: # HD1 awake now ! # Apr 9 20:38:39 dns323-1 kernel: ####################################### Apr 9 20:38:47 dns323-1 kernel: Apr 9 20:38:47 dns323-1 kernel: ####################################### Apr 9 20:38:47 dns323-1 kernel: # HD0 awake now ! # Apr 9 20:38:47 dns323-1 kernel: ####################################### Apr 9 20:40:01 dns323-1 crond[1069]: USER root pid 6553 cmd /usr/sbin/getdhcp&I want to be as non-invasive in my surgery as possible..
I had this problem too, and I pretty sure I've figured it out. That log actually gives a huge hint as to what was going on with me.
What it seems to me is happening, is that when a disk goes to sleep syslogd gets that message "HDX stand by now!" and goes on to write it to /etc/syslog, which in turn obviously wakes it up again a few seconds later ("HDX awake now!"). Weather this happens to one or both disks depends on your RAID configuration.
All this spining down just to spin back up 10s later ruins disks much faster than having them always on, so anyone chrooting Debian should really have a look at this.
I've managed to go around the issue simply by stoping (not killing) syslogd and klogd (/etc/init.d/syslogd stop && /etc/init.d/klogd stop), which prevents the disks from spinning back up immediately after stand by (and apparently confirms the issue).
My next attempt will be to use tmpfs for /var/log (and probably /tmp, /var/tmp, /var/lock and /var/run) to see if it also works.
Offline
I have the same problem, just noticed it the other day. I won't even be connected to the unit and all of a sudden i hear the drives spin up. im not using it for printing and i still have not installed debian on it.
Should i just be adding:
kill -9 `pidof fancontrol` && echo Killed fancontrol >> /mnt/HD_a2/messages.txt
kill -9 `pidof lpd Waiting` && echo Killed print deamon >> /mnt/HD_a2/messages.txt
to my fun_plug?
I bought this unit so my data would be backed up, and the drives constantly spinning up isnt making me feel good about my purchase. Thanks in advance.
Offline
kruzes wrote:
My next attempt will be to use tmpfs for /var/log (and probably /tmp, /var/tmp, /var/lock and /var/run) to see if it also works.
Well, this seems to work. I'm running etch and my problem was syslogd. I've solved it by tmpfs mounting /var/log (along with a couple more directories).
If you're running etch and want to try this solution, just add (something like) this to your funplug:
$busybox/mount -t tmpfs tmpfs $etch/tmp $busybox/mount -t tmpfs tmpfs $etch/var/tmp $busybox/mount -t tmpfs tmpfs $etch/var/log $busybox/mount -t tmpfs tmpfs $etch/var/run $busybox/mount -t tmpfs tmpfs $etch/var/lock
NOTE: this means you lose all contents of these folders on shutdown, as they are stored in (virtual) memory.
Last edited by kruzes (2007-06-07 18:54:31)
Offline
An alternative that i choose is to have etch completey on a usb stick attached to the device.
works perfect and because the syslog is on the usb the disks spin down without any problem.
Offline
I put my debian on a USB stick but it still keeps waking up my box every 10 minutes.
The logs seems to hint to the getdhcp binary:
Jun 8 01:40:01 DNS crond[9091]: USER root pid 9308 cmd /usr/sbin/getdhcp& Jun 8 01:41:01 DNS kernel: Jun 8 01:41:01 DNS kernel: ####################################### Jun 8 01:41:01 DNS kernel: # HD1 awake now ! # Jun 8 01:41:01 DNS kernel: #######################################
A quick check of the dhcp binary seems to indicate it doing plenty of things. Including som upnpn stuff.
getdhcp v1.00.04212006 /web/sib.conf CF-IP-DHCP-ENABLE /tmp/LeaseTime LeaseTime = %ld route add -net 224.0.0.0 netmask 255.0.0.0 dev %s egiga0 buf=%s kill -9 `pidof udhcpc` ifconfig %s 0.0.0.0 /sbin/udhcpc -i %s -H %s -p /var/run/udhcpc.pid -s /usr/share/udhcpc/default.script -x %s -q -b& ps -aux | grep udhcpc > /tmp/udhcpcid /tmp/udhcpcid udhcpc rm /tmp/udhcpcid check upnp ps -aux | grep upnp > /tmp/upnpid /tmp/upnpid /upnp/upnp /bin/upnpscript & rm /tmp/upnpid /sys/custom/default/sib.conf CF-SYS-MODEL-STR CF-IP-STATIC-IP
Offline