Snap Server 2200: one disk died in a Mirror config

[splufdaddy]

I had one of my disks die in my Snap Server 2200. I replaced the drive and powered it up, hoping the mirror would be rebuilt. Instead, now I can't see the device on my network. The system and disc lights are blinking at the same time, and the link light is solid. I've tried resetting the device, but the power button won't power the server down.

I did search around a bit (this is by far the best resource for Snap Servers), and I couldn't find anything helpful. Does anyone have any suggestions or links that could help? My main objective is to get the data off of the server. I have a server running FC4 on it, and I have an XP machine. Any suggestions are welcome.

[blue68f100]

Here is the instructions fo repairing a broken mirror.

MIRROR REPAIR FOR ORPHAN

1. Data should remain but as precaution backup your data.
2. Execute the following command from the ipaddress/config/debug web page.
Note: DD is the number of the problem hard disk.
co de format 100DD /reinit
(After reboot, this configures 100DD as a SINGLE drive and FORMATS it.)
3. Reboot the Snap server.
4. After the ORPHANED disk is formatted, execute this command from the ipaddress/config/debug page.
co de config mirror 100SS 100DD
SS is the source disk, DD is the destination disk.
(This step mirrors the drive with data to the drive without data.)
5. Reboot the Snap. If everything works according to plan, the View Disk Status
page should report ?Rebuilding backup disk? when it comes back online.

[splufdaddy]

Thanks, these instructions look very helpful. The only problem is, the device isn't accessible on my network. I've run the CD utility to find all snap servers on my network, and the server doesn't appear. I've tried to access it by http://snapserver# and that doesn't work. The System and Disk lights are blinking in tandem at a steady pace, my guess is that's an indication of something, but I haven't been able to find any LED Diagnostic information.

Also of note, when one of the drives failed, the device stopped working. We do have a mirror set up, so I was surprised by this. I figured it was common to all snap servers and just a poor design, but apparently that's not the case.

Thanks for the instructions above, if anyone else has any ideas, I'm all ears!

[blue68f100]

If the system light and disk light are blink in tandem, that means the unit is service mode. Press the reset button 4 times to clear password and all settings. It should blink back at you 4 times. Then Press and Hold the reset button till both the SYS and Disk lights go out, then release the reset button. The snap will reboot, then use assist to do the setup.

3 blinks clears PW only.

Reseting the snap will not change the drive configuration. ( JBOD, Raid 0 & 1).

If you go over to 5, just keep pushing the reset button till you get the proper blinks. "DO NOT REBOOT WITH 5 BLINKS" This is firmware update mode.

If you were running raid 0 stripping, all data will be lost on a failed drive. If this is the case you may have to reload the hd image. The 2200 can boot from any drive. I do not know it the os is stored on both drives during Raid0, I suspect not.

[deano]

I have the exact same problem! I removed the dead Maxtor drive and replaced it with an exact same drive. Now it won't boot.

I tried the 4 button reset and it still won't boot.

So I called Adaptec and paid the $199 for the bronze support. They told me it can't be fixed and needed to be sent back! There is no provision for replacing a failed mirror drive in the 2200!!

What a bunch of junk!

So, any other ideas? My Snap runs fine on one drive. I just can't add the 2nd drive to the mirror. As soon as I add a new 2nd drive, the Snap won't boot. Just the POWER and DRIVE lights blinking in tandem. I can't access via web or Snap Tool.

HELP!! I need to get this server mirrored and up and running!

Thanks!

[blue68f100]

The cmd above are correct. If it was in raid 0 = sol. There is no redundacy.

If it actually has a broken mirror the above procedure is correct.

Your drive id for a 2200 are either 10000 or 10010.

Issue "co de info" from the debug screen.
Copy and post or send email to me and I will tell you what the id of the drive that failed.

If the new drive is not showing up recheck your jumpers (master) and cable connectons.

[deano]

It's not that the new drive doesn't show up. If a new drive is installed the Snap won't boot. It just goes into the power/disk blink mode.

If this helps, the drive that died was on the top. And the jumpers for both are set to Master.

The drive that is good is named "Mirror Drive Failsafe".

Do you think that I should move the good drive to the top and the new drive to the bottom? Does it matter for booting?

Thanks!

Dean

[blue68f100]

When you look at the disk utility, what drive does it indicate is bad/missing.
I'm wandering if the new drive has a problem?

[deano]

The new drive is fine. I put it into a Mac and formatted as UFS (suggested by Adaptec). This had no effect on how the SNAP would boot. Whether a fresh drive out of the box or formatted as UFS, the SNAP never boots. It just blinks together with the disk.

I will have to look at the log that I printed out yesterday to answer the rest of your query...it is at the office.

Thank you for your patience!

Dean

[blue68f100]

Another option is use dd to clone your good drive to a new one. It should then be mirrored.

Make sure you mark the orginal drive, you don't want to get them swapped.

[re3dyb0y]

I was able to jack in a second drive on my 2200 when the mirror broke

I just had to then reinit (i came up with the base idea for the orphan mirror repair), restarted and then was then able to do as please


We've been told before its XFS, but you shouldnt need to format it before sticking it into a snap

[deano]

Pardon my ignorance but how do you dd a drive? I am unfamiliar with the term...

Here is a part of the boot log. Maybe it can help me get a new drive in and wirking!

E File System: Logical set member 0 not found. (original device ID: 50000)
W File System: 1 member missing in logical device (original device ID: 50000)
W File System: Logical device 8005000: no spares found to perform hot replacement


So it appears that my original boot drive failed. So, should I try putting the spare drive in the top slot and adding the new drive in the bottom slot?

Or is a dd the way to go and how do I do this?

Thanks!!!!

[splufdaddy]

I took the new hd out, put the old, failed drive back in, and the device now shows up on my network. The device now recognizes that a drive failed, and it's working off of one drive until I replace the failed drive. I have since copied all of the data off of the snap and am researching an alternative that's less propriatery. I was getting quotes of $10k++ for data recovery if I couldn't get the snap to boot. Not worth taking that risk again.

[blue68f100]

Originally Posted by deano

Pardon my ignorance but how do you dd a drive? I am unfamiliar with the term...

Here is a part of the boot log. Maybe it can help me get a new drive in and wirking!

E File System: Logical set member 0 not found. (original device ID: 50000)
W File System: 1 member missing in logical device (original device ID: 50000)
W File System: Logical device 8005000: no spares found to perform hot replacement


So it appears that my original boot drive failed. So, should I try putting the spare drive in the top slot and adding the new drive in the bottom slot?

Or is a dd the way to go and how do I do this?

Thanks!!!!

Member "0" refers to the drive 1 = top ID 10000
Its easy to verify, If you remove it The snap will not come up. If it does try the oter one. When it boots with just 1 drive, install the ne drive and follow the procedure posted above. You must use either 10000 (top) or 10010 (bot)

50000 is what the mirror partition is called.

dd = digital dolly found on unix system Knoppix CD
it is similar to ghost.

[blue68f100]

Originally Posted by splufdaddy

I took the new hd out, put the old, failed drive back in, and the device now shows up on my network. The device now recognizes that a drive failed, and it's working off of one drive until I replace the failed drive. I have since copied all of the data off of the snap and am researching an alternative that's less propriatery. I was getting quotes of $10k++ for data recovery if I couldn't get the snap to boot. Not worth taking that risk again.

I think you are removing the wrong drive.

Try the other and see.

Logical drive 0 = top = 10000
Logical drive 1 = bot = 10010

Partition 50000 = mirror set

Hope this helps.

[deano]

OK, I finally got mine to work and there are a few steps more involved than above.

First of all, my problem was that the BOOT drive had failed (the top drive). It will boot off the mirrored drive (bottom drive) but it won't rebuild a new drive from there!

So, I bought an exact replica drive (Maxtor 250GB IDE) and put it in the bottom slot. I moved the bottom drive to the top slot. Only then did I eliminate the blinking light, reset mode.

Once I had the backup mirror drive on top (it was now drive 10000), the Snap booted up. However, disk status showed a cracked mirror. I could not rebuild the mirror because it saw the new drive as a separate drive but was still looking for the rest of the mirror. So I had to break the mirror by making both drives individual drives, then re-establish the mirror. This started the rebuild with no loadd of data! Yeah!

The exact steps are below.

1. Put good drive in top slot of SNAP.
2. Put new drive in bottom drive of SNAP. Turn on SNAP.
3. Reformat the new drive by executing the following command from the ipaddress/config/debug web page.
Note: DD is the number of the problem hard disk.
co de format 100DD /reinit
In my case it was
co de format 10010 /reinit
(After reboot, this configures 100DD as a SINGLE drive and FORMATS it.)
4. Reboot the Snap server.
5. Noww break the mirror with this command
co de config individual 10000 10010
6. Reboot.
7. After the ORPHANED disk is formatted and the drives are converted to individual drives, execute this command from the ipaddress/config/debug page.
co de config mirror 100SS 100DD
SS is the source disk, DD is the destination disk.
In my case the command was
co de config mirror 10000 10010
(This step mirrors the drive with data to the drive without data.)
5. Reboot the Snap. If everything works according to plan, the View Disk Status
page should report ?Rebuilding backup disk? when it comes back online.

Mine took about 4-5 hours to rebuild all 250GB!

Whew!

Hope this helps someone else!

[blue68f100]

That's one way to repair it, The Hard way.

Once the new disk has been formated (co de format 100XX /reint) and ready for use, just enter "co de config mirror 100SS 100DD" Where SS is the good drive. This will mirror the good drive to the clean one. You will need to reboot for the cmd to execute.

[deano]

Originally Posted by blue68f100

That's one way to repair it, The Hard way.

Once the new disk has been formated (co de format 100XX /reint) and ready for use, just enter "co de config mirror 100SS 100DD" Where SS is the good drive. This will mirror the good drive to the clean one. You will need to reboot for the cmd to execute.

That didn't work in my case. Because the status of the mirror was CRACKED MIRROR, the new drive showed up an another individual drive.

When I entered

co de config mirror 10000 10010

I would get a -4 error and it would not create the mirror. Hence, my long-winded explanation.

[blue68f100]

Cracked Mirror and Orphan are one in the same. Others have used it, and has worked. The bottom line is that you got it working and thats all that counts. I've been through the same problems. And if you keep them long enought you will go through the process again. HD just fail over time.

Bottom line RAID 1 Preserved all DATA, just like is suppose to. Good Work

[aureliano]

Originally Posted by blue68f100

[...] You will need to reboot for the cmd to execute.

not always really, I could do that also by simply unmounting and remounting all the drives.

[blue68f100]

Technically. Cracked mirror refers to a broken set. Where Orphan refers to a drive that has been replaced but has not joined the set.

[shadowman]

I would strongly suggest that you do not use Maxtor hard drives. I have taken apart a failed Maxtor and Western Digital. Maxtor most plastic and WD has got plenty of steel parts. Hence, the failures and all the headaches that go along with replacing hard drives. I would use WD, Seagate, Hitachi, and Samsung hard drives.

[Phoenix32]

Originally Posted by shadowman

I would strongly suggest that you do not use Maxtor hard drives. I have taken apart a failed Maxtor and Western Digital. Maxtor most plastic and WD has got plenty of steel parts. Hence, the failures and all the headaches that go along with replacing hard drives. I would use WD, Seagate, Hitachi, and Samsung hard drives.

As a Hardware Engineering Tech who has replaced what seems like a zillion hard drives, I would reduce that list down to WD and Seagate, and I agree 10,000% with the negative on Maxtor drives. I had hoped when Maxtor and Quantum merged we would get Quantum quality drives, but alas, that never happened. Hitachi drives are not bad, but you can do better. Samsung may get there some day, but they are still behind the power curve compared to WD and Seagate. JMO