Hacking a Snap Server 2200 - How do you replace a defective

I had a Snap Server 2000 with 2x250GB hard drives. The disks were set to
mirror for data redundancy. Fortunately, I did as after about 18 months, one of
failed drives! If it was set up as a band, all data would be lost. (I
knows all about the failed disk so that the Snap Server is a backup of another
workstation as another layer of redundancy.)

The drive that failed was the boat ride, but on the Snap Serverright
the mirror unit and continued to run. Attaching the Snap Server 2200 has been much more
problems that I thought it would! I thought that I would be able to simply change the
damaged disc with a good drive, and would not be under reconstruction. I was wrong! I
finally working well together, but it took Tome and research. The following steps
I had to do was to server to get the snap back up and running.

The first thing I had to do was todetermine which drive was bad. I just got the Snap Server and solve each station until the server
startup. It would have been much easier to go to the web interface for the disc to see
was to determine the faulty unit. But when I did this, said the startup disk,
Disk 0 failed. Looking at the hardware did not indicate that the ship was
race and that was the next station! It seems, Disk 0, or the bootdisc
the top unit. The secondary drive is down.

I removed the faulty drive and ordered an exact replica of the failed disk. It is
important for a mirror of an exact replica of the disc's nice to have. I ordered two of
hard drive immediately if not successful in the near future.

I put the new drive in the Snap Server (both drives to be configured as
"Master" IDE drives) and I switched. The Snap Server was unable toboot! It would be
Entering in recovery mode (the power and the disk would blink in tandem) and non-
further. I cold not even communicate with the server. So I called Adaptec tech
Support (Adaptec SNAP purchased.) And they told me that there was no way that I do
wanted to do and that the server had to be returned for repair! How untrue!
What I discovered from research is that the Snap Server can start mirroring
Driving (substation), but theA new unit will not rebuild from there! The Snap Server
and the operating system to boot from the master disk (disk 0 or the top
disk) to a mirror to rebuild.

I have the new disk into the slot and moved the good, original drive to the bottom
the top slot. I turned on the Snap Server. Only then remove the flashing
light, the recovery mode. I have the Snap Server via the web interface and looked at the
Disk Status page. L 'result, I had two discs! My boot disk as a logical unit
10000 and the new blank disc was logical disk 10,010.

Once I had the backup disk mirror (the one with all my data) on top (it was time
Drive 10000), the Snap begun. Now it was time to rebuild the mirror. However,
status of the disk has a broken mirror. I could not rebuild the mirror, because it seemed
the new drive as a separate disk and was still looking for the rest of the mirror. So I
had to breakmirror by both units each unit, then re-adopt
the mirror. This has begun to rebuild without losing data.

The steps are below.

1. Set a good drive in the top slot of SNAP.

2. Insert the new drive in the lower band of SNAP. September SNAP.

3. Format the new disk with the following command from the ipaddress /
config / debug web. (For example: [http://192.168.1.1/config/debug])
Note: DD is the number of units difficult problem.
Co deSize 100DD / reinit
In my case it was
Co. classification 10010 / reinit
(After the restart, 100DD configured as a single disk and formatting.)

4. Restart the Snap Server.

5. Now smash the mirror with this command
Co de config individual 10000 10010

6. Reboot.

7. After the orphan and the drive is formatted disks are converted into individual
drives, execute this command from the ipaddress / config / debug page. (Example
[HTTP: / / 192.168.1.1/config/debug])
Co de config mirror 100SS 100DD
SS is the source disk, DD is the target disk.
In my case the command was
co mirror configuration 10000 10010
(This step reflects the data on disk, no data.)

5. Restart the Snap. If everything works as expected, the state of the disk image
page must include "Rebuilding the backup unit, when it comes back online.

Once I went through this whole process, the mirrorhas been restored and all
The data were reconstructed. The whole trip took about 5-6 hours 250GB rebuild. But now
I have a Snap Server 2200 with a new station. The server is reflected, so that it can rest
assured that my data is secure.

Thanks To : Electrical Power Systems Garmin GPS Nuvi Store Canon 500D DSLR Camera Store Best Price