Snap server 4200 OS image...

[bigdaddystep]

I have 4 4200's, and one when I log in keeps trying to do a snap server recovery. It is a crazy old version 2.6.050 as a matter of fact. Can I copy the image off one of the functioning Servers, or can anyone get me a copy of that image or even a new, I just need these things up and running. Thanks for you time

[blue68f100]

If the unit was setup for diaster recovery, it wants the original HD's, this is the reason for wanting to go into recovery mode. The drive info is store in cmos/flashram so it will not loose it. If you reset the cmos, you must go into the bios and set it backup. I recommend you record the values of the BIOS. I do not recall if the 4200 has a password on the BIOS. Andy (phoenix32) will have more info on the 4200, he is our resident hardware got to guy.

If you do not have any SnapShots Scheduled or AV running, you can use your working unit to transfer the OS to a new HD. The drive must be clean, if the OS sees a file structue it reconizes it will not touch it. If you have a copy of the GSU you can use the recovery mode to reinstall the OS. This is the RECOMENDED Method.

Using an image from a working unit will put you in the same boat, wanting to go to Recovery mode if diaster recovery was setup.

MAKE A BACKUP OF ALL DATA YOU WANT FROM THE WORING 4200, Preferability the one with the newer OS. NOT RESPONSABLE FOR DATA LOSS.

The Guardian OS will NOT Hot sync on cold boots. So you can use this method to transfer the OS to a new HD.

Your best option if you do not have the GSU (Comes with the units on CD), is to use your working unit to setup the one that is not. To do this you must Disable SnapShots, and Disable the AV (if you purchased that option). Power Down the working snap. Remove all drives except #1, make sure you number the drives so they go back into the same position. Install a clean drive in postion #2. Power on the unit, and watch the led's. During the boot process, at around the 5 min mark, the Disk led on drive 2 will lite up for 10+ sec, this is where the OS is copied over. Once everything settles down, normally in the 6-10 min mark, power down and remove drive 2. Reinstall all of the original drives in the order that they came out. Power on the unit every thing should comeup cleanly. Wost case is that it reports a failed HD (#2). If that is the case, you may need do go into the drive utility and have it do a repair. Or just wipe the HD and and hot swap it back in, it will do it automaticly this way.

I normally keep a HD loaded with the OS. That way I can remove all HD and not run into the chance of damaging the array. Requires a min of 20 gig, the os occupies 10 gig of space.

Install the HD in the dead 4200, Boot the snap and verifty that it booted up. If you had a static IP set, do this off line, till you have changed the IP to what you want. Once up you can hot swap your CLEAN HD, the snap will auto format and config. If their is data on the snap it will not touch the drive. Now if it still wants to go into recovery mode, Diaster Recover was active when the original drives were removed. Without the GSU you may need to reset the BIOS to clear the drive info. Let Andy expand on this if you have problems.

I would check on acquiring the OS (gsu). This is need most any time there is corruption. And will save you a lot of time and headaces in the long run.

[Phoenix32]

But remember, that is copyright material and Adaptec guards is very jealously. If you have it, upgrade the OS in the process. The 2.x.x versions are a bit quirky IMO.

[Phoenix32]

.....