Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Pages: 1
- DNS-323, Firmware Version 1.03, 2 HDDs a 300 GB, Raid 1;
(- MacBook 2 GHz Intel Core Duo, Mac OS X 10.4.10;
- Printer Canon MP780 connected to USB-Port of DNS-323)
I've got the following issue:
Power Management is enabled and "Turn off hard drives" is set to "After 5 min".
After spinning down correctly after 5 minutes without network access to the HDDs of the DNS-323, the DNS-323 starts again spinning up the drives shortly after about 10 sec automatically. After further 5 min the same procedure takes place. Over and over again.
This happens even without connected USB-Printer (Canon MP780) and without connected network (All plugs except power plug plugged off.)
I know the issues with full printer queue. But I've got the problem even after "System restart" and "Restore to factory default settings" (see DNS-323's "Tools Menu"). All printer jobs should be deletet after these procedures.
Also the line printer daemon of Mac OS shows no remaining printer jobs.
Besides: The printer functionality works fine.
I think power management worked fine after formatting the hdds for the first time but stopped working after first turning off the device manually by the power switch.
Is there help to gain full power management functionality again without formatting the hdds again?
Thank you for your advice in advance.
Offline
I was going to ask - does nobody search - but now I've read your post, I'm going to ask a different question - does nobody read?
It's not an issue with a full printer queue - it's an issue with a not empty printer queue, and the fix is to clear (or delete) the printer queue.
The queue is a directory on one of the disks, so restarting the unit won't fix it and resetting the unit to default won't fix it, and whilst I could be wrong, the line printer daemon on Mac OS won't show it. Unplugging the printer won't fix it and disconnecting the network cable won't fix it - why not - because none of those actions will change what is on the disks - if it were in memory, then maybe, but not on the disks.
What I don't see in your post, is that you followed the suggestions in the wiki article - so how about trying them and then telling us if it didn't work.
Offline
Thank you "fordem" for the thorough discussion.
You are right, at http://dns323.kood.org/information:known_issues there are all informations needed to fix the problem(see "Disc Spin-up Issue").
After deleting the files in the .lpd directory of the hdds (raid1), the power management functions works correctly again.
To see this invisible directory (.lpd) in Mac OS is not trivial even as ROOT.
But as ADMINISTRATOR in WINDOWS it's quite simple to see and delete them.
I'm glad that my DNS-323 is not out of order.
Thank you very much.
Offline
Glad you got it working - I've never used Mac OS and I've never tried to see the files in Windows - but I do know that the issue exists and that I've seen questions about it on almost a daily basis over the past few days.
Offline
You are right "fordem",
he who can read has clearly got the advantage.
Thank you very much,
ENGINEER
Offline
I had the same issue today also with the 1.03 firmware; might want to edit the wiki: known issues to include firmware 1.03 as also having this issue. Following the wiki instructions worked flawlessly to correct my problem.
Tom
Offline
I have tried the solution in the wiki and it does not work for me. My .lpd directory is empty I have never set up a printer on this device.
I have a suspicion that an alternative explanation for the spin-up may have something to do with syslogd.
I have firmware v1.03, chrooted to Debian etch, using the procedure in the wiki, using a modified version of the linuxrc file provided in the wiki.
I'm trying to figure out what piece of code is responsible for spinning down the disks. Could it possibly be that it first spins down the disks, then logs it. Syslogd, of course, would wake the disk back up again in order to write to it.
This is just a guess; I'd appreciate any guidance.
Offline
Chris,
I put my logs on a USB flash.... however it still spun up all disks each time the getdhcp is running. I think it has something todo with the Upnp scanning the disks. getdhcp is running alot of stuff.
Anyway you might want to either not use syslogd in your debian setup or put your logs on a usb flash.
Offline
Chris, I read in http://dns323.kood.org/forum/t203-Disk- … nutes.html (reply by hwahrmann) that syslogd is writing a -- MARK -- into the logfile. He solved the problem by adding the "-m 0" option to the syslogd startup.
As you're running a chroot'ed debian, you might have to do this as well for this debian.
Try to do the following:
* chroot a shell into your debian
* edit the file /etc/sysklogd.conf, find the line SYSLOGD="" and replace it by SYSLOGD="-m 0"
* restart the syslogd by /etc/init.d/sysklogd restart
Search the running processes for the syslogd using ps auxww | grep sys, you'll see the -m 0 option then. Maybe this solves the problem.
Bernhard
Offline
Applying the -m 0 option to the syslogd reduces the disk spin up from 20 minutes to an hourly interval. Reason for the hourly interval is crond.
The crond writes into the following log files:
* /var/log/syslog
* /var/log/messages
* /var/auth.log
/var/log/syslog can be disabled by removing *.* from the list writing into /var/log/syslog.
/var/log/messages can be disabled by removing *.=info from the list writing into /var/log/messages.
But in order to prevent crond from writing into /var/log/auth.log I would have to remove auth from the list writing into /var/log/auth.log. I don't want to do that because I would like to keep other auth reasons writing into /var/log/auth.log, for instance a samba access.
How can I achieve that? How can I disable crond producing auth log messages?
Bernhard
Offline
Two additional data points:
1: My drives were spinning down (and immediately back up) every 10 minutes, even though the power saving setting was supposed to spin them down after 5 minutes of inactivity.
2:My linuxrc (which executes when chrooting to debian etch) contains two lines that start klogd and sysklogd. Commenting these out makes the problem go away (the disk spins down and stays spun down. Of course, without log files it's a little hard to find out what's going on
Offline
Chris,
Buy a USB flash stick and put the logs on this device instead.
Offline
frodo wrote:
Chris,
Buy a USB flash stick and put the logs on this device instead.
That seems to work.
Speaking of Syslog, though, the USB storage driver is unbelievably talkative -- pages and pages and pages of syslog entries every second.
Offline
Get a version without debugging!
The first version found here was with full debug enabled :-(
However there has been sub sequent non debug versions. Do a search and you should find it.
Offline
To write the log files onto a USB flash stick is a good idea but unfortunately not compatible with my idea of making a cron-jobbed backup of the disks onto an external USB harddrive.
I plan to have a time-switched power plug turning on the external USB harddrive once a week for (at least) 8 hours. For the same time period there should be a weekly cron job doing an rsync of /mnt/HD_a2 to the external drive.
Did one ever tried to use a (passive) USB hub? This would enable me to connect both, the USB flash stick as well as the USB harddrive.
Bernhard
Offline
As far as I know you can use a hub. However the issue you will have is device names might change.
So you would have to be careful to mount the correct device.
Offline
frodo wrote:
Get a version without debugging!
The first version found here was with full debug enabled :-(
However there has been sub sequent non debug versions. Do a search and you should find it.
I can't find it; if I look at the wiki instructions on "usb storage", it points here:
http://dev.skcserver.de/dns323/modules_ … storage.ko
and that seems to be the verbose version.
Offline
This should help:
http://dns323.kood.org/forum/t764-usbst … abled.html
Offline
Thanks to all who helped; moving the filesystem to the USB stick solves the problem of the syslogd constantly waking up the hard drives -- with the entire Debian distro on the stick, the hard drives spin down and stay spun down indefinitely, until somebody tries to access the filesystem.
Offline
Pages: 1