Pro/Forums - View Single Post - 2200 Orphan Mirror Repair

teek · 02-01-2007, 07:15 PM

Ok sure...here's the background...

Got an old Snap 2200 that I wanted to put into action for file archiving. Always used to use it in JBOD, and was curious how the RAID 1 was implemented. So I set it up to mirror and put about 20 gigs of files on it and set up some shares, users and file security.

I wanted to test what would happen if one of the drives failed (and how I would go about retrieving data and re-establishing the mirror should I have to replace a drive). So first thing I did was open her up and remove the TOP drive (Logical Device: 10000, Partition: 10000, Physical: 10007). I threw that drive into a WXP box and then a YellowDog box just to see if those OSs could read the file system (in case the whole things ever crapped out I needed to retrieve files).

When I powered up the 2200, it showed that one disk had failed, breaking the mirror. All the data was still there on the bottom drive (Logical Device: 50000, Partition: 10010, Physical: 10017) and everything operated exactly the same as before (all shares, users, permissions intact).

I reinstalled the top drive that I had removed and powered it back on. The top drive was recognized as an orphan and much to my dissapointment, I could not simply go into the config page and rebuild the mirror. So I started looking around and found the wiki on this site "Mirror Repair for Orphan."

I followed the instructions but kept getting the error "Device Configurations require Public Partition Ids" that I mentioned in my first post. Not being sure if the instructions "co de config mirror 100SS 100DD" refered to the #s for the Logical Devices, Physical, or partitions, I tried combinations of all 3 to no avail. I looked at your post:

"Your cmd line is wrong, 10000 is the new drive, where 10010 is the original raid.
co de config mirror 10010 10000 should be the correct cmd."

but I got a "Unknown Error -4 in configuring a MIRRORRED device with members: 10010 10000" error.

I then did as Hallis suggested (well actually he had it backwards, but I figured out what he meant) and configured the BOTTOM drive (the one in the Cracked Mirror with the data still on it) as JBOD. So now I had two JBODs.

I then swapped the drive positions as per your suggestion and rebooted. I went to the Configure Disks page and choose data protection. It warned me that I would lose all data on drive 2 (the one that had been the orphan, now on the bottom).

When it was done, I did a reboot and a disk check before trying to connect to it. When I did connect, I saw that only a new default share was there (Share1) and assumed all my data was gone. In fact, it was not. My data is there, in a subfolder of Share1, but all my shares, users, and file permissions were gone. My Network Settings and master password were saved however.

The only new thing I’ve found is that whenever I go to the View File/Folder Security Status page, it says: "This page is not available because no disks were found." This sounds scary but it doesn’t seem to affect anything.

Hope that makes the situation clearer. Thanks again for your help.

02-01-2007, 07:15 PM	#13
teek Cooling Neophyte Join Date: Jan 2007 Location: NY Posts: 15	Re: 2200 Orphan Mirror Repair - Error Ok sure...here's the background... Got an old Snap 2200 that I wanted to put into action for file archiving. Always used to use it in JBOD, and was curious how the RAID 1 was implemented. So I set it up to mirror and put about 20 gigs of files on it and set up some shares, users and file security. I wanted to test what would happen if one of the drives failed (and how I would go about retrieving data and re-establishing the mirror should I have to replace a drive). So first thing I did was open her up and remove the TOP drive (Logical Device: 10000, Partition: 10000, Physical: 10007). I threw that drive into a WXP box and then a YellowDog box just to see if those OSs could read the file system (in case the whole things ever crapped out I needed to retrieve files). When I powered up the 2200, it showed that one disk had failed, breaking the mirror. All the data was still there on the bottom drive (Logical Device: 50000, Partition: 10010, Physical: 10017) and everything operated exactly the same as before (all shares, users, permissions intact). I reinstalled the top drive that I had removed and powered it back on. The top drive was recognized as an orphan and much to my dissapointment, I could not simply go into the config page and rebuild the mirror. So I started looking around and found the wiki on this site "Mirror Repair for Orphan." I followed the instructions but kept getting the error "Device Configurations require Public Partition Ids" that I mentioned in my first post. Not being sure if the instructions "co de config mirror 100SS 100DD" refered to the #s for the Logical Devices, Physical, or partitions, I tried combinations of all 3 to no avail. I looked at your post: "Your cmd line is wrong, 10000 is the new drive, where 10010 is the original raid. co de config mirror 10010 10000 should be the correct cmd." but I got a "Unknown Error -4 in configuring a MIRRORRED device with members: 10010 10000" error. I then did as Hallis suggested (well actually he had it backwards, but I figured out what he meant) and configured the BOTTOM drive (the one in the Cracked Mirror with the data still on it) as JBOD. So now I had two JBODs. I then swapped the drive positions as per your suggestion and rebooted. I went to the Configure Disks page and choose data protection. It warned me that I would lose all data on drive 2 (the one that had been the orphan, now on the bottom). When it was done, I did a reboot and a disk check before trying to connect to it. When I did connect, I saw that only a new default share was there (Share1) and assumed all my data was gone. In fact, it was not. My data is there, in a subfolder of Share1, but all my shares, users, and file permissions were gone. My Network Settings and master password were saved however. The only new thing I’ve found is that whenever I go to the View File/Folder Security Status page, it says: "This page is not available because no disks were found." This sounds scary but it doesn’t seem to affect anything. Hope that makes the situation clearer. Thanks again for your help.