Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[AC3]

My drives keep coming out of hibernate for no reason, with f/w 1.06:

Using 2 Seagates (ES.2 500gb, and Barracuda 1500gb) as single drives (no raid). UPnP, iTunes FTP disabled, no torrents.

Power management set to spin down after 5 minutes inactivity. This works ok. However, at 1 minute past the hour, each hour (and other times at random it seems), the drive spins up again for no apparent reason. After 5 minutes of inactivity, they will hibernate again. This is happening even with the LAN cable unplugged, so it is coming from the DNS-323.

Tech support's only suggestion was "sounds like a defective unit, try returning it"...but I'm not sure, could this be f/w related and not a hardware prob? I just bought the DNS-323 2 weeks ago, and immediately upgraded to 1.06, so can't compare it to anything else.

I've been reading that it could be the BT client searching for new torrents at 1 past the hour?

Any ideas or others having this issue - and what the work-around is? OR, does this sound like it is hardware related and warrants a replacement?

TIA

[abellofi]

No way that soounds like a HW issue; you may want to try restoring factory defaults.
Don't enable anything and see if it still does it or not.  If it doesn't, try re-enabling your settings one by one and testing.  Did you have DDNS enabled?

For what its worth, mine wakes up at odd times too.  Not enough to bother me though.

[AC3]

Those are the factory defaults (everything disabled, including DDNS), but I did one anyways...nothing changed.

I'm not bothered by the noise or anything, but the 24+ unnecessary start/stop cycles each day are just going to be wearing down the drive prematurely. That bothers me.

[fordem]

I'm not bothered by the noise or anything, but the 24+ unnecessary start/stop cycles each day are just going to be wearing down the drive prematurely. That bothers me.

You can take care of that concern by leaving the drives spinning - disable the hubernation.

[kizer_rezik]

Same problem I had so I switched to 1.05. however it doesnt' support the bigger drives.

[conq]

I have the same problem. Answer from dlink is to disable it! Ha. 

http://forums.dlink.com/index.php?topic=3442.0

[ttmcmurry]

How about a litmus test?   Set your computer to spin down its hard drive in 5 minutes.  Sit and listen to it for the next hour, and let us know how many times it spins up when no one's using it.

THEN.. compare the results to your once an hour wakeup with the 323. 

Every OS needs to commit data to the disk from time to time.  Nature of the beast sort of thing.  Next time around you could try solid state drives, you won't have to worry about spinup.   

[AC3]

How about a litmus test?   Set your computer to spin down its hard drive in 5 minutes.  Sit and listen to it for the next hour, and let us know how many times it spins up when no one's using it.

THEN.. compare the results to your once an hour wakeup with the 323. 

Every OS needs to commit data to the disk from time to time.  Nature of the beast sort of thing.  Next time around you could try solid state drives, you won't have to worry about spinup.   

geez, some people just have the smartest answers, don't they? Tell me, when a nas drive is sleeping, with absolutely nothing calling to read or write data...and even the network cable is unplugged, you find this to be the norm? You simply can't compare this to a computer's drive...but uhh, fyi,  if I enabled hibernate or S3, it sleeps till I ask it to wake or it receives a wol or magic packet command to wake....it doesn't spinup for no apparent reason, and 2 times per hour.

Actually, for everybody else who has this issue (and it happens here twice per hour)- I've heard from a senior tech at D-Link, and the techs have been able to reproduce this problem with fw 1.06 themselves. No ETA for a fix (hopefully on 1.07), but I've been told to sit tight.

So for me, since I mainly use this nas for streaming media to my media tanks (usually in the evenings only when I am home), I've decided to just power it up & down manually for now...1 spinup/down cycle per day beats 48.

And yeah, SSD's will be nice, but till the time comes that I can get 2TB in SSD without re-mortgaging my house, I'll be stuck with my HDDs.

[ttmcmurry]

The DNS-323 doesn't ever go to sleep or hibernate.  It only lets the HDDs spin down.  That's why. :-)

Even though the OS is stored in flash, the logs iirc are stored on the drives.  There are more folders and structure to the 323 than what is displayed via Windows Shares. 

[Antti]

I believe you AC3; mine does exactly the same thing.  I'm very relieved to hear that a senior DLink tech has been able to replicate the issue; when I have reported it in the past (and others before me) I've never even had a hint of acknowledgement that it might be a DLink issue.  If I was a tech guy I'd be really curious and want to get to the bottom of things and find out the cause.  Not here...

[ttmcmurry]

Help me understand what you want from your post, I suppose I'm missing your point.  Are you trying  to convey an annoyance, complain about unnecessary drive wear, do you feel your power savings is being diminished, simply want d-link to acknowledge you found a bug, something else?

In terms of power, it's not wasting much energy to spin up for 5 minutes (or whatever your interval is) then send the drives back to sleep.  We're talking so little energy at this point, it would cost you more to run a 100-watt lightbulb for ~3 hours than the 323 at full power for a whole day.

In terms of wear, for example the Seagate 7200.12 series is rated at 50,000 contact start/stop cycles.  If that drive were to start/stop once an hour, 7 days a week, 52 weeks a year, the drive could fail after 5 years and 7 months. 

In terms of finding bugs, congrats!    Welcome to the team!

[ECF]

Thank you we are currently looking into this.