Print

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

[klaus-w]

Hi!

First of all, I feel like I should check, if the HDD I'm using is even supposed to work with the DNS-320. I'm using the WD30EFRX, which doesn't seem to be officially supported according to this thread in this forum. Whereas I bought the HDD based on information found in this PDF from the D-Link homepage.

The bottom of my DNS-320 says: H/W Ver.: A2 F/W Ver.: 2.02

I didn't change that, no firmware upgrade applied, DNS-320 is new, just plugged the HDD in and powered up. Power LED kept blinking all the time and the WebUI menu wasn't accessible, however PING was successful all along. Neither shutdown button nor restart switch did have any effect at all.

DNS-320 without the HDD plugged in works fine.

Is that in any way similar to a known issue? At the moment, I'm trying to test the HDD in another computer, but I don't think, there's going to be a problem with that, because I bought two of them, none is working with the DNS-320 and I refuse to think both were DOA... just doesn't seem to be very plausible.

Nevertheless, I'm going to check them and in the meantime it would be great, if anyone had any suggestions for solving the problem.

Thanks, kind regards

[albert]

You might want to try upgrading firmware to 2.03 (aka 2.03b03) although according to firmware changelog, 3TB is already supported on 2.01 onward.

Remove HDD first from NAS, upgrade firmware and reinstall HDD.

[klaus-w]

Thank you for your answer.

You might want to try upgrading firmware to 2.03 (aka 2.03b03) although according to firmware changelog, 3TB is already supported on 2.01 onward.

Yep, read that as well, so I thought better not change anything. But tried 2.03b03 from here now. No difference.

Remove HDD first from NAS, upgrade firmware and reinstall HDD.

Correct me, when I'm misunderstanding, but that would hardly work with HDD plugged in, since I can't reach the WebUI, right?

[albert]

If your have already upgrade the NAS firmware to 2.03 and still facing the same problem then I can only conclude that your might be a lemon set. Contact D-Link and RMA asap.

According to this, the user was able to get the same drive working just that there is an issue with the LED light.

[klaus-w]

If your have already upgrade the NAS firmware to 2.03 and still facing the same problem then I can only conclude that your might be a lemon set. Contact D-Link and RMA asap.

I assume with "lemon set" you're talking about a technical defect, right? That would have been my next guess, but I tried connecting it to another computer via internal SATA. Ubuntu 12.04 LTS Live DVD was loading forever, so after watching the loading screen for 15 minutes, I turned it off again. I think, Ubuntu tries to automatically mount the existing hdds and had the same problems as the DNS-320. So I tried the BT4 beta Live DVD, of which I knew, wouldn't try to mount anything at startup. QtParted reported, that the drive hasn't been unmounted properly before, which might have resulted in errors. I just created a completely fresh partition table and quit. Plugged it back into the DNS-320, and it worked!

Bottom line: if anyone is experiencing a scenario, similar to mine, just try to completely clear the hdd and the DNS-320 might be able to startup allright again.

According to this, the user was able to get the same drive working just that there is an issue with the LED light.

Yes, I read that. Still, I don't understand why not listed as a supported hdd in this forum even though it's written so in the PDF from the D-Link website.

[ivan]

Just a couple of questions mainly to leave a full record of the problem.

Was this a new drive that had this problem from the start or had you been using it in the NAS or some other unit?

I have seen the problem with a drives that have had the 'dirty' flag set which prevents the NAS doing anything with the drive until that flag is set to 'clean'.

Every time we have seen this problem it has been with used drives.  If yours was a new, unused drive then I'll have to post a note on our notice board to warn my staff of the possibility of problems. 

[klaus-w]

Was this a new drive that had this problem from the start or had you been using it in the NAS or some other unit?

Both hdds were new, when I plugged them into the DNS-320 for the first time. Everything was working well up to the moment, when I tried to access the NAS via CIFS and Ubuntu (approx. 4 hours later). I'm afraid, I can't really exactly remember what I did (sorry), but the result was, that I couldn't reach the NAS anymore. Since the following cold boot I've been experiencing the scenario I've been describing in this thread. After creating a new partition table with BT4 beta Live DVD via QtParted, everything went back to normal.

So I guess the answer to your question is: no, the hdds have been used before and only for some reason, after I did something wrong, they became responsible for the frozen NAS.

The only thing, which I don't understand, is why the DNS-320 didn't offer me the option to create a new partition table, after it couldn't read the hdd. Maybe that's an issue to work on?