D-Link Forums

The Graveyard - Products No Longer Supported => D-Link Storage => DNS-323 => Topic started by: ScottWells on August 27, 2010, 09:14:59 AM

Title: Prompting me for RAID type after replacing/syncing drive
Post by: ScottWells on August 27, 2010, 09:14:59 AM
Hi, I've had a DNS-323 for several years and it's worked great for me.  I've had two WD 750GB HDDs in a RAID 1 configuration.  One of the drives failed so I ordered a replacement which arrived earlier this week.  I popped in that drive and the DNS-323 prompted me to format it, so I did.  Formatting stalled at ~97% and, after a good number of hours, I removed the new disk and started the DNS-323 to make sure my original data was fine, and it was.  Again I added the drive and it then prompted me with the following screen:

 Select a RAID type:       Standard (Individual Disks)
                JBOD (Linear - Combines Both Disks)
                RAID 0 (Striping - Best Performance)
                RAID 1 (Mirroring - Keeps Data Safe)

I originally selected RAID 1 and "Next", but that gave me a rather scary message about reformatting the drives.  This made me nervous so I instead clicked "Skip" which took me to the normal screen.  From that screen I clicked Tools>RAID and clicked "Manually Rebuild Now".  After a few hours the status screen showed:

HARD DRIVE INFO :

Total Drive(s):    2
Volume Name:    Volume_1
Volume Type:    RAID 1
Sync Time Remaining:    Completed
...

which made me think things were in a good state.  However, when I log into the device I'm still prompted to "Select a RAID type".  Right now I'm skipping it, but things seem to be in an inconsistent state.

Any ideas of what I can do here that will NOT erase my data?

Thanks in advance,
Scott
Title: Re: Prompting me for RAID type after replacing/syncing drive
Post by: R-D on August 27, 2010, 12:19:37 PM
http://forums.dlink.com/index.php?topic=11903.msg13919#new
Title: Re: Prompting me for RAID type after replacing/syncing drive
Post by: ScottWells on August 27, 2010, 01:26:50 PM
Thanks!  I posted this on the other thread, but that procedure didn't work for me.  After trying that I upgraded from 1.06 to 1.09 and things look fine again.  I really appreciate the pointer!