D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: tim1 on December 01, 2008, 07:23:13 PM
-
I keep getting a degraded status on my raid1 sync time. I have backed up all data and reformatted the drives. I copy the data back and have a completed sync status for a short time. Within a day it's back to degraded. I have two 300 gig hdd's in a raid1 config and am using firmware 1.05. Does anyone have any ideas why I keep going back to a degraded status?
Thanks ???
-
are both your hard drives same model/brand? Are the both roughly the same age? Have they had very High usage?
-
Yes both drives are the same and were purchased at the same time. They do get quite a bit of usage, I have my itunes library and my movies on them.
-
The only reason a degraded status would come up is if either a hard drive failed or it is causing a critical issue and the device is detecting it. What type of hard drive do you have?
-
I have "2" 320 gig seagate barracudas. Is there some kind of log report that is generated if the device is detecting some problem?
-
Is there a way to diagnose what the problem might be?
-
I have the Same problem with two WD drives purchased at the same time (750gb). I reformatted and set RAID 1, restored files, and ran into degraded status. I ended up formatting "bad" drive, restored RAID 1 and switched drive lcation (left to right & right to left). I'm monitoring status now, and hope "solution" works.
-
Let me know how you make out. If it works I might have to try that to.
-
I have the same problem with mine (firmware v1.05). I'm running two 500gb WD drives in Raid1. From what I've found, if i shut the DNS323 down (even if i do it via the admin panel) I run the chance of the raid going into a degraded mode. I don't think the drives are bad (I've popped both into my PC and run WD datalifeguard tools on them). What's most concerning about this is the fact that the DNS doesn't report it as degraded as all (indicator lights are normal, no emails). The only way I can see it is if i login and check the status.
This problem started for me on v1.05.
-
Please try the manual rebuild option in firmware 1.06.