D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-343 => Topic started by: nataku316 on February 27, 2009, 09:25:42 PM
-
I’ve posted many issues regarding this product since I purchased it about 4 month ago.
Here is another two. First it’ll report good drive as bad, because i have 4 new hard drives in there but it’ll randomly report bad drives. Secondly I’m seeing it reconfiguring the volume all the time, out of no where it’ll show “The Volume_1 is synchronizing now. Please wait for 302.7 minute(s).” It thinks a bad drive has just been replaced in fact there were not drives replaced or bad.
-
Still waiting for a Firmware from D-Link that will resolve some of these problems, to make this great product a little more usable and a lot more stable please.
-
I just want to draw your attention to something.
You might want to research TLER - Time Limited Error Recovery - http://en.wikipedia.org/wiki/Time-Limited_Error_Recovery (http://en.wikipedia.org/wiki/Time-Limited_Error_Recovery)
TLER is Western Digital's name for a process that, as you can see from the Wikipedia entry, is known to other drive manufacturers by other names - so what we want to look at here is the concept.
The problem you describe may actually be caused by the disks you are using.
-
thanks, i'll have a look at it
-
Good catch Fordem I would definitely look into that perhaps simply disabling TLER will resolve your issues. From what you explain it seems highly likely.
-
I can't promise that enabling/disabling TLER will solve the problem, but, having used SATA RAID for several years, I do know that it is one of the possible causes for drives randomly dropping out of the array, and as such worth investigating.
-
I am not familiar with TLER or similar technology. Just a thought I have.
As different class of HDDs have different default TLER value, is it possible that DNS-343 firmware issue TLER commands to set it to 7 seconds, thus iron out possible HDD dropping out of array because of difference in the factory default settings?
-
I have two of these devices with 1.02A firware and 1.5 Seagate Hard drives and having the same issues.
RAID 5 is Flakey (Drives are dropping Random) copies to the volume one it works is EXtremly slow..
So when does 1.04 come out to fix all of this? can't depend on them, Flakey and SLOW boat anchors!
-
I have two of these devices with 1.02A firware and 1.5 Seagate Hard drives and having the same issues.
RAID 5 is Flakey (Drives are dropping Random) copies to the volume one it works is EXtremly slow..
So when does 1.04 come out to fix all of this? can't depend on them, Flakey and SLOW boat anchors!
IF you're using the Seagate drives which are known to have issues, start by taking that up with Seagate - D-Link cannot fix that, and if the drives are "flakey", then your RAID array is going to be "flakey" and undependable.
-
Dear Fordem,
Pardon me for butting in, here, but I own six Seagate 7200.11 1.5TB HDDs, all with the latest firmware, and am experiencing no problems with the drives, themselves. Seagate claims that only the earliest manufactured drives had the widely reported problem, this involving drives freezing until being reset by Seagate.
So, then, if nataku316 or anyone else contacts Seagate, if they have one of the few hundred bad drives, Seagate will deal with the problem. But if nataku316 has the latest firmware, then Seagate will do no more than you're saying that D-Link will do.
There's a name for this. It's called "finger pointing" and is, frankly, unacceptable, as are all defensive customer service responses. As I'm a loyal D-Link customer and recommender, this fills me with despair. Feh.
Regards,
Jeff
Fordem said, "IF you're using the Seagate drives which are known to have issues, start by taking that up with Seagate - D-Link cannot fix that, and if the drives are "flakey", then your RAID array is going to be 'flakey' and undependable."
-
Just so we are clear fordem is not an employee of D-Link. His thoughts are his own. On another note if you want to see a D-Link "defensive" post please see here, http://forums.dlink.com/index.php?topic=4224.msg26428#msg26428 . Same related issue.