Print

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

[lvn]

Hi All

I have a DNS 323 with two Seagate 1 TB in RAID1. I had no problem for about 6 months. Recently i disconnected and connected back a drive that was shown as degraded in the status. After formatting the reinstalled drive, the NAS shows synchronizing for multiple days in a row (i have data of only 240 GB). The NAS gets heated and doesn't seem to stop the synchronizing process. Have anyone faced this problem and any possible solution? Thanks in advance,

Cheers
LVN

[gunrunnerjohn]

Could the drive have a problem?  You say it was showing as degraded, perhaps the drive is the reason.

I've removed and replaced a drive and the sync took a long time, but it was finished after some hours, and I have about 800gigs of data on a pair of 1.5TB drives in mine.

[lvn]

Thanks for response. I am not sure if there is a problem in the drive since the drive failure indicator light didn't come up and formatting went thru ok. Do you remember how long it took for it to sync 800 GB in your case?

Cheers
LVN

[gunrunnerjohn]

It all happened in one day, but I didn't watch it like a hawk.    I started it in the morning and around noon it was still working away.  I didn't look at it until the evening, and it was finished.

[markbowman]

I'd consider not using Raid 1 on the DNS-323 even though you were lucky and it worked for 6 months. I've seen enough posts on it not working to think that you can't really rely on it 100%. I'd just take the 2nd drive out and use it as your external backup device.

[gunrunnerjohn]

With that kind of attitude, why use the DNS-323 at all?

[hilaireg]

I suspect one of the HDD's is intermittently failing. 

I've had my DNS-323's since version 1.02 of the firmware (H/W A1) in RAID1 configuration using matched Seagate 500GB HDD's without issues.  One of DNS-323's fell to "degraded" state without LED indication (only WebGUI Status).  Reformatting the HDD's and rebuilding the RAID1 worked for a few weeks before it fell to "degraded" again.  Running the Manufacturer HDD Diagnostics at that point revealed S.M.A.R.T. data indicating that the HDD was indeed failing.

If the RAID sub-system operates like others I have worked with, the data is written to the disk and re-read for confirmation.  The "read-back" is likely incorrect causing the data to be re-written again, re-read again, and so forth.

HTH,

[markbowman]

"With that kind of attitude, why use the DNS-323 at all?"

What attitude? It's a valid suggestion for a problem that may in the end not have a solution to it.

Your not seriously going to argue that the 323 can be really be called reliable when it comes to Raid 1 on it vs what you get with other implementations of Raid 1 are you? I've been lurking here and on the other site for long enough to know there are issues with the 323 that joe user can easily run into.

The DNS-323 is neat piece of hardware and I'm glad I bought one, but it has flaws. Pointing that out isn't giving "attitude".

[gunrunnerjohn]

Maybe you should read the post I was responding to.  I never said the box didn't have flaws.  You must suffer from selective comprehension.

[hilaireg]

If the unit was purchased with the intention of using it primarily for RAID, then the problem needs to be isolated so as to ensure that a solution may be provided.  Removing the HDD and using it separately doesn't achieve that result ... it would be better to simply return the product.   

The challenge is that the DNS has issues and hard drive manufacturers have issues.  The problem could be entirely DNS related, entirely HDD, or an incompatibility between both.

IMHO, 'markbowman' suggestion to use the HDD separately was not an attitude as much as a sign of frustration experienced by many folks as a result of unclear marketing/sales information and slow technical support response provided by D-Link.

In D-Link's defense, they experience the same challenges that other companies experience - short product lifecycle VS return on investment VS customer retention.

Cheers,

[ECF]

Reset the unit to factory defaults and allow the resync and see if the issue persists.