D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: MeatMan on September 29, 2008, 12:51:11 PM
-
Greetings all...
We've been using our DNS-323 as a general data vault at the office to store various documents, images etc. It's worked well for us until I applied the 1.05 patch. Now, after a short amount of time (undetermined) the mapped drive to the DNS becomes unreachable, examining the unit shows the power button (and both drive lights) lit amber.
No settings have been changed on the unit, just a firmware application... Although the unit appears to have gone asleep, the web interface is still responsive -- issuing a Reset from the Tools menu brings it back on-line. Has anyone else experienced this behaviour? Is there a fix or a setting that's new to 1.05 that I'm not aware of or should I revert to 1.04 (which worked fine)?
-
I would suggest for now since it is used in an office environment to revert back to 1.04 until you can determine what is causing the device to fail.
1. What type of harddrives make/size are you using in the device.
2. The web interface will always be accessible even when the unit sleeps the harddrives because the the WEB server is actually running from flash not from the hard drive.
3. When you say the unit becomse unreachable, is this just by SMB or all together? If the unit can still be accessed from the WEB gui but the harddrives can not it means that the hard drives are causing errors in the unit.
-
Thanks for the quick response...
The unit is stocked with two Seagate Barracuda's (9BJ148-308 750 Gig). I understand the web interface still responding -- Server Message Block dies, however I'm not sure if FTP services are still active, guess I should have checked that just to see if it's one service that's having an issue.
I will revert to 1.04 -- again this morning, all lights were amber and the drives were unreachable until the unit was reset.
-
I had the exact same issue with mine. I have two 500 Gb Western Digital drives. I just reverted back to 1.04 and everything is fine.
Hoping that 1.06 doesn't have the same issue.
-
...agreed Juhealy...
It was a little disappointing but after reverting to 1.04 all was well again.
-
I had this problem as well ( I went from 1.04 to 1.05 also). However, I fixed mine by reseting the software via the web interface and reconfiguring the device. I DID NOT reformat the drives or change the RAID config -- I just used the reset to factory from the web interface. After the reset I went back in and reconfigured the unit and have not had a problem since. Still running 1.05.
-
Interesting...
Does the reset clear all your users, groups and FTP accounts? Cuz if that's the case, I'll just stick with what's working now.
-
Interesting...
Does the reset clear all your users, groups and FTP accounts? Cuz if that's the case, I'll just stick with what's working now.
Yes, Everything resets to defaults.
-
(Danger Will Robinson, danger!)