Print

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

[remy9070]

Hi all,

I've got this reoccurring problem with my DNS-323 -- almost a daily occurrence if not multiple times daily.

First of all, I'll let you know I've got a MacBook Pro and two PCs on a network (all using the DNS-323) with the DNS-323 wired into the router (an Apple Extreme Base Station).  The DNS-323 has two Seagate 1.5TB hard drives.

Now, randomly, the DNS-323 will disappear from the Mac Finder and Windows Explorer.  Where it was once accessible, it will no longer be and an error message will appear to the effect of "connection failed" and "server does not exist or it is not operational at this time."  Physically, a solid blue light will remain illuminated on the front of the DNS-323.  The only way I've found to bring it back up is to power down the DNS-323 and power it back up.  However, it will not conventionally power down via the button on the front.  The only way to bring it back up in the Mac Finder/Windows Explorer is to actually pull the power plug out of the back of the DNS-323 (I know, I know...) and reconnect it, then press the button on the front to turn it on.  Voila.  It reappears in Mac Finder/Windows Explorer.  But... only to go down again in the same way at some random moment in the future.  Sometimes days later, sometimes hours later, sometimes minutes later.

Any ideas at all?  It's really perplexing me and getting downright irritating.

Thanks in advance.

[christine]

it seems that the DNS is rebooting by itself. have you tried to update the firmware?

[remy9070]

I am running the latest firmware.

[ECF]

When you power the unit down using the button on the front are you holding it down until you see the front LED start to flash?

[remy9070]

Sure am.  The only thing that turns it off is pulling the plug.

[ECF]

Try taking the cover off and pressing and holding the power button there below the right HD LED. Maybe they are not connecting when you press the button on the cover. If that doesn't work there is something wrong with your unit I would contact support by telephone.

[remy9070]

I don't think the problem lies in the power button.  The button works fine when the 323 itself is running (and staying connected) properly.  The problem is the 323 randomly disconnecting from the network and needing a hard shut off (unplugging) to get it back up.

[darkmantis]

I don't know if you are having this issue or not, but I had this problem when the drives overheated. It would randomly disconnect and reconnect. The hard drives will shutdown/restart if they get to hot. I originally purchased this linksys nas device with 2 bays and my hard drives got so hot, I couldn't even touch them and that device was disconnecting and reconnecting each and everytime. I took it back and bought this one instead. At first it was getting too hot, but I ran the device without the face cover on it and the temperature drop significantly. It sits around 111 degrees with no problem. I only found the problem to occur when I was transferring large amounts of data and the closet that I put it in was awefully hot. I fixed that problem and now I don't have a problem at all.

Just thought I'd share my experiences with the overheating issues and disconnecting.

[remy9070]

I appreciate you sharing that.  I'll monitor the temperature for the next little while.

Anyone have any other ideas?

[ECF]

Check for a firmware update for your drives. Those drives have had known issues and Seagate has release firmware updates to address these issues.

[gosta]

Have you solved your problem?

Have the same problem with my 2 week old DNS-323.
Run 1.07, XP SP2, two WDEADS10 1TB Caviar Green, Raid 1. During high load it reaches max 111°F. Runs normally around 102.
Tryied to run without the cover. The temperature than sunk to around 100°F but the problem still exist. Comes rather often every 10 min about but only during high load.

[remy9070]

Since I last reported on this (July 12, 2009), I have not had the issue occur.  It just stopped happening.

Granted, I messed with some settings here and there.  I wish I could say what fixed it, but unfortunately I cannot.  Personally, I do not believe mine had anything do with temperature.  And I definitely didn't change any environmental conditions in that regard.

Good luck with yours.