Snap Server Boot Image

[gw1500se]

I have acquired an old Snap Server (can't see any model number on it) and I have a couple of drives I want to throw in. Where can I find a boot image that I can copy onto one of the drives so when I put them in I can boot it up and configure it? TIA.

[blue68f100]

Some models do not require images. Just install the drives and see what happens.

[gw1500se]

Thanks for the reply but nothing is ever that easy (for me).

Just lights flashing (except disk light) and the http port never opens. It never even gets a DHCP address.

[blue68f100]

What is the light sequence. Snaps use the leds for error codes.

[gw1500se]

The system light is flashing slowly but seems consistent, the link light is on steady, the net light is flashing rapidly and also seems consistent and the disk light is off.

[Phoenix32]

Originally Posted by gw1500se

The system light is flashing slowly but seems consistent, the link light is on steady, the net light is flashing rapidly and also seems consistent and the disk light is off.

Go to the Wiki section and look up doing a reset. Do a factory default reset (4 presses). Then after rebooting, use Assist and see if you see the unit.

For normal operation, the System light does flash slowly (like a heart beat). The link light should be on. And if it is seeing network activity, that light would be flickering.

Now if you did install a BLANK hard disk, give it some time to format the drive.

BTW, you have not said what model SNAP this is (there should be a sticker somewhere on the unit (bottom, back) with a model number. Is this a 1 drive, 2 drive, 4 drive, or even 12 drive unit? Describe it if you can't find a model number (or a picture). It will make things easier if we know what we are working with here.

[gw1500se]

Progress. It has an IP address now and I got assist to come up.

I don't see a model number on it. There is a sticker with a SN and one other unidentified number:

70700059-003

Now I just need to find what commands to use but its past my bed time. Thanks for the help, this was a great step forward. I may be back tomorrow if I can't find what I need to do with assist.

[blue68f100]

It's proably a 2000 v2 rev3, OS in flashram.

He did mention a couple of drives.

[dandrews]

Not giving up but a bit frustrated... SNAP 4000 with SnapOS 4.0.860 ( purchased it yesterday from the vendor's web site) the hardware rev is 2.0.1 and the BIOS is 2.0.252. Ok now the issue: Don't seem to be able to format the drives above 128,404 mb. The installed drives ( and the purpose of project ) are 4 ea 250gb drives. Hoping to get a TB running. Is there something I am missing? Yes, stupid me did format the drives initially using an older version of Snap OS before I figured out I needed a higher rev. Comments? Suggestions? Thanks, Don

[rpmurray]

dandrews, try formatting Drive1 at the command line with the command:

config device format 10000 /reinit /nocore

If that works, do the other three.

[dandrews]

ermmm... do I telnet to box to access the cmd line? I have a printout of the debug commands but am not sure how to access it except via the web interface.

[blue68f100]

To gain access to the debug section add /debug to the address (http://IPAddress/config/debug).

before you go to debug. Click on the SnapAppliance Logo for the admin page and post vitals.

[dandrews]

The config curently is: SNAP 4000 SnapOS 4.0.860 Hwr 2.0.1 Bios 2.0.252

[dandrews]

Using the suggestion from Mr. Murray of config device format 10000/reinit/nocore it did in fact reformat the drive but again it formatted it to 128,404 same as when using the Assist tool... wonder if it would help to unmont the device and then format it??? Don

[blue68f100]

You will need to remove all drives but drive 1.

Then issue "co de format 10000 /reinit"

Then check you capacity is should be good to go.

If this is a 4000, change disk type to JBOD

Install the other drives.

Issue "co de format xxxxxx /reinit" where xxxxx is 10008, 10010, 10018 to reformat the remianing drives.

[dandrews]

Thanks, I will get right on that approach and see how it comes out.

[dandrews]

Run before walking... well now when I remove all the drives except no. 1, the system does not come all the way up. Link LED is lit, and the system LED flashes twice over and over. Never gets to the point I can connect to the box from the web browser.... will keep after it... open to ideas

[dandrews]

Dang... never mind... I need to learn to be more patience. Waited for quite some time and the brower did connect and I see the disk is being checked.

[dandrews]

A special thanks to both rpmurray and blue68f100. My Snap 4000 is in the final stage of creating a raid 5 config of 4 250gig drives which will provide me with 700+ gigs of storage. Can't thank those two guys enough. Whooohooo bring on those big files now.

[blue68f100]

Glad to to see everything worked out for you. Were here to help.

Once you get the raid 5 built you will then need to learn how to setup users and security. The built-in security check will drive you nuts till you understand security.

Run "debug memory" from debug and see how much ram (PC100/133 DIMM) is installed. I recommend a min of 128meg, max is 256meg. Some units only came with 64meg. These units only work with low density, chips on both sides.

[gw1500se]

Let me add my thanks as well. This thread expanded beyond my problem but I'm on the air and you folks deserve all the credit. We are quite fortunate that you are willing to spend your time helping total strangers. Thanks again.

[dandrews]

Blue68f100... on a reply here in this thread you mention that if it were a 4000 it would probably be best to have disk type as JBOD. Did you mean that as instead of Raid 5? Reason I ask is I was able to raid the set and everything worked fine except it seems very unstable. Yesterday when doing a backup to disk, the OS seemed to have crashed and then it went through the entire process of checking the array and as of now it is still rebuilding the backup disk. I am a bit suspecious of power. Could I be over driving the 120 watt supply? Just some thoughts. If it is still unstable by the end of the day I plan to break the raid array and go back to just for individual disk of 250 g each. Don

[dandrews]

BTW: upgraded memory to 128 which was the largest of this vintage I had around the house.

[blue68f100]

dandrews,

There seams to be a problem that has poped up with early version of the 4000, v1 & 2. These units use a M/S setup for the drives. All 4000 have weak power supplies. To confirm the problem fail one drive in a raid 5 set, like drive 2. See if it reports the problem correctly. Re-boot the server then recheck drive status. You will discover what I'm talking about. If you have the v3+ it does not have this problem. Most all of these problems showed up when users started installing drives large than OEM. It wasnt till lately that Phoenix32 started doing some intensive testing of the 4000. Purposely failing drives to see how it responds. He has both v2 and v4 models.

There are no problems reported in JBOD, no one normaly uses these units in that configuration.

If your hd is not reporting the proper size. You either have to set the unit up as JBOD or remove all execpt drive 1, Before you can correct the size of the drive. Raid 5 is based off of drive 1 or the smallest in the set. Sorry I wasn't very clear with this.

The max ram the 4x00 can handle is 256meg. These must be low density. To check to see if the ram is read properly use the debug cmd "debug memory".

[dandrews]

Ok I am hard headed but not completely stupid. I let it go through another near 24 hours of repair of the array, again tried to do a backup to the snap and it crashed again. That's it.. This one does not seem to want to run as a raid 5. Therefore back to JBOD... which is fine for home use.

If I can resolve the power supply issue in the other one I have I will try to put a beefier supply in that one, load it up with 230g units and see if that resolves it... afterall, it is all about learning right?

Thanks again for all the post in this wiki... I have learned a great deal in the past few days.

Don