I'm in the middle of configuring a DNS-320 to replace a DNS-321 with 2 X WD20EARS (2TB) drives in a RAID1 configuration that I've been using primarily to back up multiple MAC Lion systems. I moved the drives to the 320, formatted them as standard, and have been trying to RAID1 them using the web interface "Disk Management/Hard Drive Configuration/Set RAID Type and ReFormat" function, (which shows the 2 drives as "Standard"). The drives with 1863GB (each) are displayed by the Configuration wizard, I select RAID1 from the four choices, select Disable AutoBuild, attempt to enter the RAID1 drive size (ideally, the entire capacity of 1863GB, as it was in the 321) and am told:
"The size of the RAID volume can only be between 1- GB."
and the input field will not accept any value greater than 1GB.
Note: It took at least a dozen reformats and restarts from out of the box to get to the point where I got the RAID1 size question. Previously, I would get the four RAID choices, select RAID1, and get a drive list with no drives and capacities in it ; when I told it to format, I got back the same standard drives that I had previously had. When I finally got past that issue after a dozen restarts and reformats, I ran into the 1GB issue described above.
Anyone have any ideas or similar issues?
Thanks
Update: This problem was solved very simply by a suggestion from the DLink support person to try a different browser. When I logged into the DNS-320 from Firefox instead of Safari, the RAID1 (re)configuration worked properly on the first shot. Apparently, Safari doesn't process the Configuration HTML dialog properly.
DLink telephone support was excellent, considering this is a discontinued model which I purchased so many months ago that I couldn't even remember who I bought it from, and that I initially called their premium support number prepared to pay for the call. The premium folks transferred me to the free "warranty" support, where the tech spent close to an hour walking me through the usual resets, reloads, and retries before suggesting the browser change that immediately solved the problem.