Cool thanks. I'm going to get another hard drive and back it all up before I do that.
I appreciate the advice. I'll keep you posted.
That is an excellent idea.... that's what I would do...
Think of it this way... Assuming you are running raid 1, you bought this raid to keep your data safe.
Now one drive has (perhaps) taken a dump. You are allowed to access the data because you had a mirroring system in place. The dns did what it was intended to do as a raid 1 system. Back up all your data now and count your blessings. Money well spent

.
I'm not sure what the process is when or if this happens to me, but I think this is what I would do...
Someone correct me if I'm wrong.
1. write data to the nas and see which one is blinking (for step 4).
2. back up your NAS to an extern usb drive or to your computer if you have enough space.
3. power down the nas
4. remove the offending drive (side not blinking during a copy to nas)
5. replace with new drive.
6. start dns-323
7. log into web interface (might ask you to rebuild). if so, do it, else go to the page that allows you to do it.
8. don't use the nas until rebuild is done. Give it a day or two.
Comments? Suggestions? If any of you think I don't know what I'm doing, you are probably right because I've never been in this situation. Always want to prepare myself just in case it happens so I hope someone can point out my flaw in the process above so I can be ready when this happens to me (which is probably just a matter of time - not IF, but WHEN).
What drive are you using? Would they happen to be seagates 1.5T drives?
Gary