D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-320 => Topic started by: mikedistras on August 24, 2012, 09:14:18 AM
-
Hi,
I bought the dns 320 a few months ago, it was working fine and i managed to back a lot of data up onto the drives.
I was going on holiday for a while, so i shut it down through the admin, unplugged it and left it in a cupboard for about 6 weeks.
Ive returned in the past few days, plugged it all back in, and now there seems to be no power going to either of the drives in there...?
I can login to the admin area, and it doesnt recognise anything in there.
Any ideas why this is happening? and also how to fix it?
-
How were your drives set up?
You could try - after marking which slot the drives are in - to remove them and then plug them back in and see if they work.
If that doesn't work try using a USB/SATA adapter or caddy with one of the drives and plugging it into your PC and use an installable IFS to try and read the drive. See the sticky topic - 'DNS-320 - data recovery (windows PCs)' for more information.
If you can get at your data that way you will then need to check your NAS and power supply.
-
They were set up as Raid 1
Unplugged and Plugged everything out and in
Reset the device
Tried reading the drives individually with a dock, power goes to them, but wasnt able to read them (will try a different program).
When I press the power button on the 320, Power light turns on, all three lights turn on solid, then the drive lights go out completly, and the power light flashes for a minute or two, then after that the power light stays solid, and the drive lights stay off completly. Seemingly as if there were no drives present in the device...
Any other ideas?
-
If your drive(s) is detectable on PC then it's time to send the NAS for RMA if still under warranty.
-
One final check of the drives - since you used RAID 1 then you only need one working drive for recovery - is to boot your PC with a Linux live CD and see what you can find on the drive.
If everything appears then, as Albert says, the NAS is the problem.
If nothing appears then try the other drive.
If you can't read anything from either drive then suspect the drives. It is possible for both drives to fail at the same time but not very likely.
-
Just loaded up Ubuntu, couldnt read any of my files i expected to see from either drive. I could only see an FTP folder on one drive, and on the other drive i could only see Ajaxplorer and an FTP folder, i think im only able to see 1 partition of the drive in Linux for now, not the one where my files are.
However, just booted back into windows and viewing the drive through NAS Data Recovery, and managed to see all my files and data (Hurray!). Im just going to check the other drive, ensure that the data shows up there through NAS Data Recovery, and if it does at least it is a problem with the DNS 320.
-
Before you RMA the DNS-320 - one possibility of it seemingly not starting up is simply that it doesn't like the (corrupted?) filesystem it sees on the drives...
So, a couple of quick tests you could try
(a) Do the drives actually spin up in the DNS-320 - even if the blue "left" or "right" LEDs don't stay on? If you can't hear the hard drives over noise of the fan, try using the old screwdriver trick; place the blade end on the end of the drive's chassis and put your ear to the handle.
(b) If you have access to a spare SATA hard drive that you can "wipe", use a disk erase tool to do a full wipe (e.g. write zeroes in the whole drive) and put that in the DNS-320. If that one spins up, the blue LED stays on and you can format it, then the issue might be due to data corruption, not a hardware failure... after using NAS data recovery to get back your lost data, you could try doing a full erase on the drives and put back into the DNS-320 and see if they start working again.
FWIW, although not in the DNS-320, I have had a PC BIOS not recognise a hard drive when there's been corrupt junk on it; doing a full erase to "all zeroes", the drive was then detected OK and has been working ever since. So the same kind of thing could be going on in the DNS-320?
Regaerds,
Richard