Mirror Orphan Repair on 2200 gone wrong. Help Please
 

Hello

I got a 2200 snap appliance back and one of the drives sounded very unhealthy so I decided to just go ahead and change it after finding the following two links:

http://wiki.procooling.com/index.php...air_for_Orphan
http://ezinearticles.com/?Hacking-a-...rive&id=151888

Now I followed the directions in the second link more as it replicated exactly what I had: A broken mirror and one good drive.

I couldn't find a way to backup the data as the snap was set as part of a domain and I didn't want to change it to workgroup as it would lose the permissions. The FTP server didn't work very well either and I wasn't about to download 110+Gb, 1 file at a time. I also didn't have another FAT drive with 120 GB free to do the DD backup. So I thought I would triple check everything.

Without referring to the webpages, here is what I did as I took notes at every step.

1 - Put my good drive in the top bay
2 - Put my new drive in the bottom bay and made sure it was set to master
3 - Rebooted the server and logged into the webconsole and it said it was formatting the new drive and the good drive was showing as missing the 2nd drive of the mirror. So far so good.
4 - I then ran "co de format 10010 /reinit" without the quotes from the debug page
5 - Restarted the snap and waited for it to finish the format of the new drive
6 - I couldn't find a diamondmax10 so we ordered a diamondmax20 160GB which had all other specs similar to the current drive. But I noticed the total size on the new drive was about 2 -3 MB less than the good drive. So I thought I better do the next step of breaking the mirror.
7 - I ran the command "co de config individual 10000 10010" from the debug and restarted
8 - After restart, I had 2 single drives. In the webpanel disk status page, the good drive showed at the bottom and the new drive at the top (though physically they were the other way around). So I thought this looked normal.
9 - I triple checked and compared the above 2 links and then ran the following command "co de config mirror 10000 10010" and rebooted.

At this stage I expected the good drive to mirror its data to the new drive. Instead, after the complete of the mirror, Lo & behold, all the data was gone :cry:


So now you know the history, I have a few questions please.

1 - What did I do wrong?
2 - The drive I am replacing is still a bit usable and has all the data on it
a) How do I backup the data to another drive, preferrably to NAS storage over the network?
b) Will taking a Ghost image be good enough to restore stuff onto the original good drive?
3) If the above 2 methods aren't possible for data backup, is it possible to connect to the snap using UNC without changing the snap from being on a domain?
4) Lets say I have 120Gb of files on the current drive, do I need 120Gb of free space to put the image on created by DD? (I think I know the answer to this, I just need to confirm).

Thanks in advance for any help you can offer.

Re: Mirror Orphan Repair on 2200 gone wrong. Help Please
 

Well you still have all your data on the removed drive, which is good.
Did you verify the drives were addressed correctly? (co de info)
Once I have the drives as seperate shares I like avoiding the debug cmds and use the web interface. I may add a foot note to the wiki.

In order to make a clone of the snap's hd the program must be capable of doing a RAW copy. Ghost likes to inturpet the data and normally does not work unless use use the RAW option. A RAW cmd will copy the HD sector by sector. I have not tested the new v10 so I can't confirm this on the newer version. DD allows you to send to network drives. But you must have full HD space. You can not view the data, with any program. But you have a full backup of the drive, which can be restored to any HD the same size or larger. The smallest HD must be in the 10000 loaction, the raid size is based on this drive.

If the drives were the same size or the source is smaller you can use dd to clone the drive. Most mfg have utilities to adjust the HD size. Most programs do not preform a clone if the drives are not the same size. I know dd live cd is this way. So you must use the cmd line. I use dd for normal full backup to my nas.

I wish the smaller 2 drive units would auto resync like their larger brothers, but they do not.

I have not worked with AD so I can't help you there. Have you tried accessing it using the IP address? It should prompt for a ID & PW, use admin for full control. FTP read speeds are close to 8.5MB/sec. There was a post on how to backup permisions. But this is a S2S backup.


:mad: Well I just checked the wiki and someone wiped out all of the snap specific FAQ's I posted. So at this time I'm checking with Joe to see if he can restore them. The problem with letting every one have edit privileges and not knowing what they are doing. So I may do some major changes to what is in the Snap wiki section. I have a backup, but I'm a little teed off right now.:mad: :mad:

Re: Mirror Orphan Repair on 2200 gone wrong. Help Please
 

Thanks for the response.

Unfortunately I didn't know about that step and not wanting to mess anything up I thought I'd follow the documentation as closely as possible seeing as it seemed to work for someone else (I am not saying the documentation is bad, quite the opposite. I just wasn't aware).

I can't afford any mistakes with the backup of the second drive. I don't have much experience using DD and I would really appreciate it if you could tell me what commands you use to backup to a network drive. There is enough storage on our NAS for the backup.

Is there no way to get the actual files? I can't connect to it using the UNC. I think I may be able to FTP it down now using active mode. I'll post back

Re: Mirror Orphan Repair on 2200 gone wrong. Help Please
 

As stated in the doc you should always back off data before doing any thing that could jepordise your data. I can never express that enough. Mr Murphy seams to be always setting on my shoulder waiting to jump into the works. At least you were proactive and have all of your data.

Take a sharpy pin and label the drives so you know who who. I'm use to 4+ drives being scattered out and my memory is failing.:D

If you can get ftp access to the drive you can back that data off where you can read it. If you make a RAW copy of the HD, you can not read the data.

With the set that does not have data, use the drive utility and change it back to JBOD. easier than using debug.
Now run co de info and print it out. for reference
Now Install the Original HD in what I call the top and boot the snap.
run co de info. This will give you updated drive info (print). compare to your first one.
access the individual drives verify which one has the data.
Now copy all data from your original hd to the new one, now your data is backed up to a new drive. Swap your original HD back out (for save keeping)
You should now have the data on the bottom new hd on top.
Now copy the data from the bottom to the top drive.
You should now have duplicate drives
Now use the web interface and have the snap drive utility setup a RAID1. It will give you a warning that all data will be lost on the second drive, will not matter since you now have the data on both drives.

I have had users use dd and do a raw copy form 1 drive to the next. If you do this with a mirror drive you just resynced the drives. Every rime I use dd I write the drive designation down. Then I write out the dd cmd line I'm going to use, triple checking. Then when I type it in I triple check it again.

If I understand AD correctly. All permissions are controlled by the server. As long as you keep the share names the same and have the correct map there should be no problems.

The document posted for repairing a broken mirror was sent to me from a individual when I bought my 2200. Clamming he was a snap tech that got laid off. It only works if the drives are the same size. And I have never used it. I'm always changing capacity and it does not work.

Re: Mirror Orphan Repair on 2200 gone wrong. Help Please
 

Hi blue68f100

Thank you for all your help so far. Apologies for sounding a bit thick, but how do you do the following step using debug or is it not possible?

While trying to write this post I have been trying to see if I could mirror back from the drive that we are replacing but I can't seem to get it to break the mirror. Mirror drive is identified as "Partition: 10000" and is in the top slot but the command co de config individual 10000 10010 doesn't work, even if I switch the numbers around. Any ideas please?

Re: Mirror Orphan Repair on 2200 gone wrong. Help Please
 

Copy the data using ftp from one drive to the next.

if does not work "co de config individual 10000 10010" try "co de predict individual 100X0" then you will have to Reboot it