Snap Server 2200 Baby Steps <- Help!

[Clique]

This site was the best find. I have a 2200 that my guys ripped the drives from and resused, for some reason - still to be determined - but nonethless - I'm trying to get the Snap back up and running.

I installed 2 - 250 gig drives (one Maxtor and one WD) - jumpers set to Cable Select.

I have read quiet a bit here and understand that I need to get the Snap OS on one of drives.

So -

First - where do I get the Snap OS from ? ( I have downloaded SnapOS 4.0.860 Upgrade from the Adaptec site but not sure if its what I need)

Second - are there command instructions that will assist me in getting the OS on the new drive? Versus me trying to parse together muliple pieces from multiple threads.

BTW the wiki URL is not working.

Any help is greatly appreciated.

Thanks in advance.

Brian

[re3dyb0y]

Yeah

Joe is waiting for a new Server, wiki will be back up them

That os is only a patch from v4

If it was the OS you needed, you still wouldnt be able to get very far.

As the drives have been killed, you need to obtain the Drive Image, which you can image onto the hard drive, and then think about updating the OS and such

[Clique]

Well as I said baby steps. Read many more thread and try numerious options to no avail. So back here seeking more help.

Current situation is as follows:

I have image the snap.bin to both drives (just in case) using the following command: dd if=/mnt/snap1000.bin of=/dev/hdb bs=1024k count=25

It returns in/out totals so I belive all went well.

I have placed the drives back in the Snap Server and regardless of settings the drives to both Master, Master/Slave, both Cable select or just one drive set to Master the results are always the same. ---> System and Disk light Blink in tandem.

Even thought the lights were blinking I tried to allow Assist to locate a Snap Server to no success. (I'm on a 192.168.100.# network) Since I'm not sure of the default Snap Server IP not sure is the workstation running Assist is able to obtain or seek the Snap Server out.

I've tried pressing the reset button with a paperclip 4 times as recommended in another thread and it appears to have no affect. Holding it in does nothing.

The only thing I find a bit strange is that as soon as I plug the power in on the Snap Server it start booting - without me pressing the Power Button.

I'm at a loss at this point as to what to do at this point.

Any help and guaidance is greatly appreciated.

Regards,
Brian

[blue68f100]

The 1000 image file will not work with a 2200, need the 2200img file.

You do not need the block and count options when copying the image file to the drive. What was your current drive configuration before the drives were removed? JBOD RAID 0 or 1.

Reseting to factory does not the drive conifuration. Only clears PW, NET ...

[Clique]

Well I took a signifcant leep forward but and now once again at a road block.

I now have my 2200 with one drive in it and all lights indcate that it has booted correctly. I had to do a factory reset as the system seemed hung previously; couldn't even get the power button to power off the Snap or reboot it.

Nonehtless, Assist now sees the Snap Server and I go through the Initial Setup but for some reason it appears that when it gos to connect to the sever after the IP assignment is complete is "cannot connect to server". If I try to ping the IP I attempted to assign I get no return - thus it appears that it is never assigned of saving the setup values.

I've have tied this a number of times with various IPs, server names, passwords being assigned and not and the results are the same.

I am using the Assit app from SnapOS_4_0_860_upg is this the correct version ?

I'm at a loss and am spinning my wheels.

Any help is appcreaiated.

Regards,
Brian

[blue68f100]

I noticed you are using 2 different brand drives, this is not recommend if you plan on using raid. Mainly is that differnent mfg have different parameters.

Verify that both drives are set to master.

Install the drive with the os on top, disconnect the the bottom one.

See if it boots. if not do the factory reset and try again.

Use assist to do the inital setup.
Now check to see what the drive configuration is setup as. Change to JBOD, reboot.

Check drive capacity, if not correct enter "co de format 10000 /reinit" from debug.
Once completed, install/connect the bottom drive. Use the disk utility to format/init the drive.

Check to see if you are seeing the whole drive (>137gig), need 3.4.805 or v4

Once complete you are free to setup the disk conf as you see fit.

[Phoenix32]

When I first set up my 4000 (with no drives in it), I had to do a facotry reset also. After the first reset, it did the same thing you described about not being able to assign/locate it's IP. I did a second factory reset and it came right up, so I would do as David suggested and reset it again.

[Clique]

First of all thanks to all for thier help and advise. Onward.

I now have both 250 Gig drives installed an being recognized as follows:

Drive1 - Single disk OK 128,533 128,404 9
Drive2 - Single disk OK 128,533 128,400 16

From what I have read I need to ugrade my OS for the system to recognize drives larger then 137Gb.

I have received the SnapOS_4_0_860_upg file from Adeptec however everytime I attempt to upgrade the OS using the Snap_4_x.sup file I receive the following error message:

Problem: Invalid SUP file for the given platform. Try selecting another SUP file and repeating the operation.

Am I doing something wrong or out of sequence?

How do I tell what the current version of the OS is?

Thanks for your help in advance.

Regards,
Brian

[jontz]

Originally Posted by Clique

I have received the SnapOS_4_0_860_upg file from Adeptec however everytime I attempt to upgrade the OS using the Snap_4_x.sup file I receive the following error message:

I don't have an answer for you, but the fact that you got adaptec to do ANYTHING for you is somewhat of a miracle!!!

[blue68f100]

The 860 is a patch, you need a full v4.

[Phoenix32]

Originally Posted by Clique

From what I have read I need to ugrade my OS for the system to recognize drives larger then 137Gb.

Correct, to version 3.4.805 or higher.

Originally Posted by Clique

I have received the SnapOS_4_0_860_upg file from Adeptec however everytime I attempt to upgrade the OS using the Snap_4_x.sup file I receive the following error message:

Problem: Invalid SUP file for the given platform. Try selecting another SUP file and repeating the operation.

The 4.0.860 you can download from Adaptec is a PATCH, not a full OS. It requires 4.x.x to already be on your Snap Server to use.

Originally Posted by Clique

How do I tell what the current version of the OS is?

Log into your Snap Server, then click on the SNAP LOGO in the upper left hand corner of your screen.