D-Link Forums

The Graveyard - Products No Longer Supported => DNS-323 => D-Link Storage => Beta code! => Topic started by: Arinoth on August 02, 2009, 02:10:27 PM

Title: Hibernation and Network Activity
Post by: Arinoth on August 02, 2009, 02:10:27 PM
Well i'm having a fun time with my dual problems. It seems that the NAS refuses to hibernate volume_1 hard drive and also seems to be randomly communicating with anything on my network even if it is not inquiring about anything. I have reflashed the firmware, i have uninstalled twonky, i have reset to default, i have unplugged the internet and just had it within the network, i have had all my computers off and still it refuses to hibernate or turn off network activity like it used to (a couple months ago). I have even gone to the extremes to formatting the hard drive and put everything back on it and i still get this, what the hell is going on and how do i fix this (i am not a fan of seeing system temp at 44C since i dont know what the hdd temp is and i like things to be in their lower end of operating temperatures if i can help it)

Edit: tried with 0 drives with/without network connection and it still has either network activity or does not idle
Title: Re: Hibernation and Network Activity
Post by: Tonytoronto on August 03, 2009, 07:18:22 PM
 It seems when i read thru this forums i always find new problems  :-)
 Mine does exactly the same, for a while i've noticed the fan will go to minimum not stop like it did some time ago and temperature will never go lower than 44C, just like yours. I left the network unplugged and shutdown every service possible and doesn't help, always 44c or more. I belive there's a bug somewhere where the temperature doesn't drop below 44c. i had upfdated to 1.08 and didn't make any diference-- had to revert back to 1.06, still have the same issue. annoying to have the fan going all the time
Title: Re: Hibernation and Network Activity
Post by: ECF on August 11, 2009, 10:11:19 AM
Did you reset the unit to Factory Defaults after the firmware update and manually reconfigure the unit?
Title: Re: Hibernation and Network Activity
Post by: fordem on August 11, 2009, 10:28:53 AM
Edit: tried with 0 drives with/without network connection and it still has either network activity or does not idle

The question just has to be asked - exactly what do YOU mean be 'idle'.

The title of the thread you started is "Re: Hibernation and Network Activity", when the unit is not in use (ie "idle"), it hibernates or spins down the drives.  With no drives, it certainly can't be active - not as a NAS, because it can neither write nor read the storage, and not as any form of server, since there is no media to serve.

Before deciding that network activity is caused by the DNS-323, get a network analyzer and capture it - what sort of packets are you seeing?  What's the source address?  What's the destination address?
Title: Re: Hibernation and Network Activity
Post by: fredrokk on August 23, 2009, 12:55:25 PM
Recently updated to beta 1.08:5, did the reset (to solve my permissions problem), but the only effect is that drive 2 never spin down anymore, even when disconnected from router. If i turn it off i hibernates properly for a while, but goes bonanza after a while. no addons is running.
Title: Re: Hibernation and Network Activity
Post by: AndyB on August 29, 2009, 04:23:05 AM
I suppose you do not have any scheduled downloads, torrents in the background?

What Harddrives do you use in the NAS?
Title: Re: Hibernation and Network Activity
Post by: gunrunnerjohn on September 01, 2009, 05:04:20 PM
I'm using firmware 1.08-b5 currently, and they've added a fan control that has three modes for the fan.

Auto (off / low / high)
Auto (low / high)
Manual (high)

I als don't see any problem with the drives going into standby mode and spinning down.  I did reset to factory defaults and reconfigure for the firmware update.
Title: Re: Hibernation and Network Activity
Post by: marsandme on September 02, 2009, 06:59:05 AM
yeah it doesn't hibernate. You hear the drive spinning all the time. In a previous post I asked to get the older version of 1.08 b/c i don't recall having this problem with that FW. Someone was kind enough to post it so hopefully the issue is remedied.