Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Pages: 1
I've got 3 identical drives. I put two drives in the 323 v1.03 and Mirror them...life is good. To test the Mirroring abilities, I shutdown and replace one of the drives with the alternate drive. On starup, the 323's Admin GUI sees the change and gives me the only option to format the drive so it can resync the mirror. I format and it resyncs...life is great...it works.
I copy more data to the new Mirrored pair. I shut down and replace one of the drives with the one I had in the initial Mirror. I restart and select to format the drive...which brings us to the crux of this message: sometimes the 323 formats the newly inserted drive (intended functionality) and sometimes it will reformat the CURRENT drive and resync with the OLD data...effectively deleting your data!
I would have thought that the 323 would ALWAYS format the older drive/data, but this doesn't appear to be the case. I've tried swapping the disk positions thinking that one bay is the primary and secondary, but it doesn't appear to care.
My questions are: is there something I'm doing wrong? If not, how can I target the format to occur on the newly inserted drive?
I've already emailed and called DLink support about this and was told that this feature is available is out of scope on this level of device, but their more expensive RAID box does this. This is BS as the 323 has the potential to lose data...and it's just that no one has really had a drive fail yet to find this out. Other than this problem, the 323 works great for my use...especially for the price.
My overarching goal is to use this third drive as a backup that I can store in a safe...so instead of backing up the device, I just pull a mirror and let it format/resync to an older drive that came out of the safe.
Thanks for the use of your brain cells
Offline
If you remove a disk and want to reinsert it you really need to wipe the disk outside of the DNS first.
It will contain a raid header and even though it really "should" pick the disk with the latest data this is not 100% fool proof on the DNS. So you really need to repartion the disk outside of the DNS before reinserting it if it has been used before in the DNS.
Offline
This would be very nice to fix - or to work around; as hot-swapping would seem to make a good offsite backup plan:
Let's say I buy 3 identical drives, A, B, and C. I start with A and B in the DNS323, formatted as RAID 1. After a month, I swap out B and take it offsite, and put in C, and I tell the DNS323 to reformat C and resync. Now the drive has A and C in it, also in Raid 1, and B is an offsite backup.
Continuing routine operations, another month passes, and I swap out A and put B in. Now the DNS323 has B and C in it. C is up to date, and B is a month old. What I want the DNS323 to do is to reformat B and resync C onto it. Can I tell it to do this?
I guess another way to ask the same question is: If the DNS323 wakes up and finds it has two drives in it, and each drive is half of a RAID 1 set, but they are from different RAID 1 sets, what happens? Do I get a choice which one to recover?
Thanks!
Offline
The answer may depend on the firmware version - up to 1.03 you had no control - with 1.04 there have been some changes made to the disk format routines, but I have not yet had a chance to upgrade or test the later firmwares as I have been out of office for the past few weeks.
Offline
Pages: 1