D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: PHXHoward on September 14, 2009, 11:23:59 AM
-
Hi, my DNS-323 wakes up on its own every once in a while.
I read the newspaper in the morning and I hear the DNS-323 wake up. It goes back to sleep in a few minutes but I don't know why it is doing this. At this time of day, there are no PCs turned on that might be accessing the NAS.
I don't know how often is is waking itself up. I notice it every few hours when I am working in a quiet room because when on, the DNS-323 vibrates and distracts me.
-
The first step is going to be to determine what triggers the wake up - is it an internal process or an external process - which you can do by unplugging the network cable, if it continues to wakeup, it's something internal, if it no longer wakes up, it was something external.
One known internal cause is the print server - if there is a print job stuck in queue (this will cause it to wake up quite frequently, so I doubt that this is the cause in your case), other possibilities are the iTunes and uPnP AV servers scanning their libraries.
External causes will vary according to your network and it's configuration.
-
Lot of people have the issue. Dlink doesn't care.
-
Lot of people have the issue. Dlink doesn't care.
I think that is being unreasonable - there are lots of us who don't have the issue - AND, since there is a pretty good probability that the issue stems from either something in your configuration (in other words - something that you have told the DNS-323 you want it to do) or something on your network that D-Link has no control over, it is ridiculous to expect D-Link to be able to resolve it.
For the record - I purchased my DNS-323 in December 2006 - I have seen the "not hibernating issue" on two occasions - the first was a job in the print queue - and at that time there was no easy way to clear the queue, D-Link has since added a button that does this, and the second was one of the server settings I mentioned earlier - the default was enabled, I was not using the server so I disabled it - problem solved.
-
Hi, my DNS-323 wakes up on its own every once in a while.
I read the newspaper in the morning and I hear the DNS-323 wake up. It goes back to sleep in a few minutes but I don't know why it is doing this. At this time of day, there are no PCs turned on that might be accessing the NAS.
I don't know how often is is waking itself up. I notice it every few hours when I am working in a quiet room because when on, the DNS-323 vibrates and distracts me.
You might want to try disconnecting your CSL/Cable modem.
Some Cable ISP servers ping the modems periodically to see if the modem's turned off, so it can give that connection to another subscriber. Sometimes that Ping leaks through the modem, and the NAS thinks a computer wants to access data and wakes it up again.
If this is the case, you'd have to take this up with your ISP.
-
Check for scheduled downloads. This will cause it to wake up.
Even if you did not intensionally create a download if you have been in this section it is possible that a download was accidentally created.
-
Thanks for all the suggestions.
I changed from DHCP to static IP, turned off the connection to the NTP server, turned off DDNS, cleared print queue, and confirmed that there were no scheduled downloads or Bit Torrent files.
Will find out tomorrow morning if it helped.
-
FWIW, I run any server type device or system with a static IP address, it's the right way to configure that kind of service.
-
I had a static IP but it was issued through my DHCP server based on the device's MAC address.
Well, I turned off all of those things and the DNS-323 still woke itself up this morning while I was reading the paper. I'll try disconnecting the Internet to determine if the wake up is internal or external.
-
I had a static IP but it was issued through my DHCP server based on the device's MAC address.
Any time the address is issued by a DHCP server it IS a dynamic address - a static address will be assigned at the device and will function even in the absence of a DHCP server - you are probably confusing DHCP reservations with static addresses, they are similar in concept, but not the same.
Well, I turned off all of those things and the DNS-323 still woke itself up this morning while I was reading the paper. I'll try disconnecting the Internet to determine if the wake up is internal or external.
My suggestion was to disconnect the network cable - it's important to understand the difference between the network and the Internet. I'm pointing this out because in my opinion, the first step is to determine whether the wake up is internal to the NAS or not - assuming it's external, the next step would be to determine if it is internal to your network or not.
-
Any time the address is issued by a DHCP server it IS a dynamic address - a static address will be assigned at the device and will function even in the absence of a DHCP server - you are probably confusing DHCP reservations with static addresses, they are similar in concept, but not the same.
My suggestion was to disconnect the network cable - it's important to understand the difference between the network and the Internet. I'm pointing this out because in my opinion, the first step is to determine whether the wake up is internal to the NAS or not - assuming it's external, the next step would be to determine if it is internal to your network or not.
Maybe my terminology isn't correct but my DHCP server will assign a specific address to a machine on my network if I register its MAC address to an IP address of my choosing. This is convenient because when I want to format and reinstall an OS, I can be assured that the machine will receive the same IP address again. Of course this method relies on my DHCP server being up when the machine requests a new lease.
My comment regarding unplugging the NAS from the Internet was in response to the earlier comment that my ISP might be pinging the cable modem and somehow causing the NAS to wake up. Disconnecting the cable modem would allow me to test this theory. As I said in my original post, the NAS is waking up when there are no other computers in my house turned on.
-
However, I agree with the other post, it could be the router. Unplugging the cable from the NAS will assure that NO traffic is waking it up.
-
Ok, going to unplug the cable to the NAS tonight and watch it tomorrow morning.
-
Maybe my terminology isn't correct but my DHCP server will assign a specific address to a machine on my network if I register its MAC address to an IP address of my choosing. This is convenient because when I want to format and reinstall an OS, I can be assured that the machine will receive the same IP address again. Of course this method relies on my DHCP server being up when the machine requests a new lease.
Do forgive me for taking this a little further off topic, but I think it's important to understand why these are different and can be critical.
Yes, I can understand the "simplicity" of using a DHCP reservation to make sure that a given host gets the same IP address after it's has the OS reloaded, however, at least for me reloading the OS is a rarely performed procedure, and even more so on "critical" devices - and configuring a static ip is just one more of the many tasks that needs to be done.
Now to look at it from the other side - DHCP reservations depend on the DHCP server which stores the reservation details to be available. If for any reason that DHCP server is down, or otherwise unavailable, a broken cable, a failed switch, whatever - then every thing that uses a DHCP reservation will eventually lose the ip address, and become unavailable when the lease expires making troubleshooting "unneccesarily challenging".
-
Well, actually, while what you say is true, that's not exactly fatal. If your DHCP server is down, typically your router, I suspect your first step will be to fix that, since you will have no Internet connectivity.
I use dynamic IP addresses for all my machines, however my NAS boxes and network printers are on fixed addresses.
General rule of thumb, server devices have fixed IP addresses, workstations have dynamic IP addresses.
-
I've this same behaviour with my DNS-323. I've tried to disconnect the lan cable, and still the problem exists. Now that I've access via ssh to the internals, and the logs are written via syslogs on files, it's quite apparent there's some job scheduled to run every 90 minutes.
This is an example of last lines of my logs:
Oct 26 18:10:16 RAIDSTORAGE user.warn kernel:
Oct 26 18:10:16 RAIDSTORAGE user.warn kernel: #######################################
Oct 26 18:10:16 RAIDSTORAGE user.warn kernel: # HD0 awake now ! #
Oct 26 18:10:16 RAIDSTORAGE user.warn kernel: #######################################
Oct 26 18:10:23 RAIDSTORAGE user.warn kernel:
Oct 26 18:10:23 RAIDSTORAGE user.warn kernel: #######################################
Oct 26 18:10:23 RAIDSTORAGE user.warn kernel: # HD1 awake now ! #
Oct 26 18:10:23 RAIDSTORAGE user.warn kernel: #######################################
Oct 26 18:17:26 RAIDSTORAGE user.warn kernel:
Oct 26 18:17:26 RAIDSTORAGE user.warn kernel: ***************************************
Oct 26 18:17:26 RAIDSTORAGE user.warn kernel: * HD0 stand by now! *
Oct 26 18:17:26 RAIDSTORAGE user.warn kernel: ***************************************
Oct 26 18:17:26 RAIDSTORAGE user.warn kernel:
Oct 26 18:17:26 RAIDSTORAGE user.warn kernel: ***************************************
Oct 26 18:17:26 RAIDSTORAGE user.warn kernel: * HD1 stand by now! *
Oct 26 18:17:26 RAIDSTORAGE user.warn kernel: ***************************************
Oct 26 18:20:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 32705 cmd /usr/sbin/offl_chk two &
Oct 26 18:30:00 RAIDSTORAGE cron.notice crond[4182]: USER root pid 450 cmd /usr/sbin/offl_chk two &
Oct 26 18:40:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 667 cmd /usr/sbin/offl_chk two &
Oct 26 18:50:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 884 cmd /usr/sbin/offl_chk two &
Oct 26 19:00:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 1101 cmd /usr/sbin/offl_chk two &
Oct 26 19:10:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 1318 cmd /usr/sbin/offl_chk two &
Oct 26 19:20:00 RAIDSTORAGE cron.notice crond[4182]: USER root pid 1545 cmd /usr/sbin/offl_chk two &
Oct 26 19:30:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 1769 cmd /usr/sbin/offl_chk two &
Oct 26 19:40:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 1982 cmd /usr/sbin/offl_chk two &
Oct 26 19:50:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 2200 cmd /usr/sbin/offl_chk two &
Oct 26 19:50:18 RAIDSTORAGE user.warn kernel:
Oct 26 19:50:18 RAIDSTORAGE user.warn kernel: #######################################
Oct 26 19:50:18 RAIDSTORAGE user.warn kernel: # HD0 awake now ! #
Oct 26 19:50:18 RAIDSTORAGE user.warn kernel: #######################################
Oct 26 19:50:25 RAIDSTORAGE user.warn kernel:
Oct 26 19:50:25 RAIDSTORAGE user.warn kernel: #######################################
Oct 26 19:50:25 RAIDSTORAGE user.warn kernel: # HD1 awake now ! #
Oct 26 19:50:25 RAIDSTORAGE user.warn kernel: #######################################
Oct 26 19:57:02 RAIDSTORAGE user.warn kernel:
Oct 26 19:57:02 RAIDSTORAGE user.warn kernel: ***************************************
Oct 26 19:57:02 RAIDSTORAGE user.warn kernel: * HD0 stand by now! *
Oct 26 19:57:02 RAIDSTORAGE user.warn kernel: ***************************************
Oct 26 19:57:02 RAIDSTORAGE user.warn kernel:
Oct 26 19:57:02 RAIDSTORAGE user.warn kernel: ***************************************
Oct 26 19:57:02 RAIDSTORAGE user.warn kernel: * HD1 stand by now! *
Oct 26 19:57:02 RAIDSTORAGE user.warn kernel: ***************************************
Oct 26 20:00:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 2417 cmd /usr/sbin/offl_chk two &
Oct 26 20:10:00 RAIDSTORAGE cron.notice crond[4182]: USER root pid 2634 cmd /usr/sbin/offl_chk two &
Oct 26 20:20:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 2851 cmd /usr/sbin/offl_chk two &
Oct 26 20:30:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 3068 cmd /usr/sbin/offl_chk two &
Oct 26 20:40:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 3281 cmd /usr/sbin/offl_chk two &
Oct 26 20:50:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 3498 cmd /usr/sbin/offl_chk two &
Oct 26 21:00:00 RAIDSTORAGE cron.notice crond[4182]: USER root pid 3715 cmd /usr/sbin/offl_chk two &
Oct 26 21:10:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 3932 cmd /usr/sbin/offl_chk two &
Oct 26 21:20:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 4149 cmd /usr/sbin/offl_chk two &
Oct 26 21:30:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 4372 cmd /usr/sbin/offl_chk two &
Oct 26 21:30:14 RAIDSTORAGE user.warn kernel:
Oct 26 21:30:14 RAIDSTORAGE user.warn kernel: #######################################
Oct 26 21:30:14 RAIDSTORAGE user.warn kernel: # HD0 awake now ! #
Oct 26 21:30:14 RAIDSTORAGE user.warn kernel: #######################################
Oct 26 21:30:22 RAIDSTORAGE user.warn kernel:
Oct 26 21:30:22 RAIDSTORAGE user.warn kernel: #######################################
Oct 26 21:30:22 RAIDSTORAGE user.warn kernel: # HD1 awake now ! #
Oct 26 21:30:22 RAIDSTORAGE user.warn kernel: #######################################
Oct 26 21:36:38 RAIDSTORAGE user.warn kernel:
Oct 26 21:36:38 RAIDSTORAGE user.warn kernel: ***************************************
Oct 26 21:36:38 RAIDSTORAGE user.warn kernel: * HD0 stand by now! *
Oct 26 21:36:38 RAIDSTORAGE user.warn kernel: ***************************************
Oct 26 21:36:38 RAIDSTORAGE user.warn kernel:
Oct 26 21:36:38 RAIDSTORAGE user.warn kernel: ***************************************
Oct 26 21:36:38 RAIDSTORAGE user.warn kernel: * HD1 stand by now! *
Oct 26 21:36:38 RAIDSTORAGE user.warn kernel: ***************************************
Oct 26 21:40:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 4585 cmd /usr/sbin/offl_chk two &
Oct 26 21:50:00 RAIDSTORAGE cron.notice crond[4182]: USER root pid 4802 cmd /usr/sbin/offl_chk two &
Oct 26 21:57:47 RAIDSTORAGE user.notice kernel: egiga0: link up<5>, full duplex<5>, speed 100 Mbps<5>
Oct 26 21:59:51 RAIDSTORAGE auth.info sshd[5011]: reverse mapping checking getaddrinfo for rfc-1918 [192.168.0.38] failed - POSSIBLE BREAK-IN ATTEMPT!
Oct 26 21:59:55 RAIDSTORAGE auth.info sshd[5011]: Accepted password for root from 192.168.0.38 port 54510 ssh2
Oct 26 22:00:01 RAIDSTORAGE cron.notice crond[4182]: USER root pid 5023 cmd /usr/sbin/offl_chk two &
The printer queue is free, no scheduled torrent downloads, all the servers (av, itunes, ftp) are down.
This is the crontab setting:
root@RAIDSTORAGE:~# crontab -l
32 2 * * * /usr/sbin/rtc -s
30 2 2 * * /usr/sbin/rtc -c
59 1 * * * /usr/sbin/daylight &
*/10 * * * * /usr/sbin/offl_chk two &
Any hints on how to find out the process which wakes up my hard drives?
One last thing I've observed, is that in case I remount the hd filesystem readonly the problem does not occur...
Thanks a lot,
Fulvio
-
F1ux - since you appear to be running third party software on your DNS-323, perhaps the best place to seek help would be from someone familar with the third party software.
-
F1uX,
Thank you for very helpful investigation. I'm in the completely same situation as yours. I cleared all possibility which initiates HDD wake up and even tried both disconnecting LAN cable and factory reset. But the problem is still there. Whatever someone told you before, it's true that DNS-323 has unintentional wake up problem. Perhaps D-Link have already noticed the issue. They are ignoring the issue. I'm waiting for 1.08 firmware release to confirm if it will be able to resolve this issue.
-
Mine used to turn on all the time and drove me bonkers. I reset all of my settings, installed 1.07, reset all my settings again and then configured my 323.
Actually I have two of them now and well they both sleep all day until I turn them on.
-
I have confirmed 1.08b can resolve this issue. The reason of 1.07 unintentional wake up is still unknown. I couldn't find any cron setting on Linux side by using funplug. Even if D-Link is still silent for this issue, the fix is very welcome. It's true that 1.08b is effective. I expect release of the official 1.08 soon. Actually I'm waiting for it from last summer :P. Anyway I don't find any problem with 1.08b so far. So, I've decided to use it until the official 1.08 is released.