Hack a Snap Sever 1000?

[nickirwin]

Can someone supply a link to the Full SnapOS v4.0.xxx?

I've been searching the web for weeks now, and cant find it.
Currently on v3.4.790 and all i want is Win2003 AD support.

Even adaptec dont reply or even care.

Any help would be appreciated.

jon_harley101@hotmail.com

Thanks.

[re3dyb0y]

Originally Posted by nickirwin

Can someone supply a link to the Full SnapOS v4.0.xxx?

I've been searching the web for weeks now, and cant find it.
Currently on v3.4.790 and all i want is Win2003 AD support.

Even adaptec dont reply or even care.

Any help would be appreciated.

jon_harley101@hotmail.com

Thanks.

Give em money and they will care

[dex1304]

Ok So I am trying to increase the harddrive space of my Snap 1000 (not the 1100). I used a program called winhex, because i had it already and I knew it did direct copying, and now even my original hd seems messed up. When I put it back into the snap server it seems to boot, but the System and Disk leds blink togther. I've copyed the first 50000 sectors to many different hds i had laying around and all the same result. Am I screwed?

Cory

[blue68f100]

Not all programs do a RAW COPY correctly. Winkex work if you have the frensic tools. It sounds like you are screwed.

Blink blink =

Slow Flashing Disk Flashing concurrently with the system light = System in Diagnostic mode

I hope nothing was important on it. Winhex add and/or modified the mbr. These modified XFS are very picky.

If you have another snap, you can copy the OS/Boot tracks to the ones you just messed up. But I wouldn't use winhex.

[Prodiem]

Originally Posted by dex1304

Ok So I am trying to increase the harddrive space of my Snap 1000 (not the 1100). I used a program called winhex, because i had it already and I knew it did direct copying, and now even my original hd seems messed up. When I put it back into the snap server it seems to boot, but the System and Disk leds blink togther. I've copyed the first 50000 sectors to many different hds i had laying around and all the same result. Am I screwed?

Cory

I have just successfully debricked my 1100 250GB (Bad Sectors) with a 40GB using winhex... I had to copy the first 100,000(Dec) sectors before it would work.

Examinining the file system I see that the FAT of the file partition seems to be needed before it will boot properly. Also there is some files stored in that area that are nessisary. If at all possible I would copy the entire drive (winhex has the ability to write what it can from the bad sectors) and reinit the new drive when installed.

[blue68f100]

If you are trying to recover the data, you do not want to reinit the drive, It's part of a formating cmd.

It looks like the original drive had a problem. The OS is stored in flashram on SOME 1000, not all. If you have a version 1, the os in fashram. Otherwise stored on the drive.

There was a formatting change to the drives with v2 OS. It's nice to know smething else is capable of working besides dd.

[KWayne]

Originally Posted by KWayne

Thanks for sticking with me on this. I currently have a:

SnapSever Model 2000 Series
S/W 4.0.854(US)
H/W 2.0.0
BIOS 2.0.252
S/N 42872

that is working quite well with two drives that are combined to look like a single drive, not a Raid 1 environment. I want to replace the existing 2 - 20 Gb drives that work just fine, with 2 - 160 Gb (ATA-100) drives so that I can have more space. Ultimately, I want to configure them as Raid 1 but that can come after the changing of the drives. So I have heard two possible methods, (1), backup any existing data I have, change the existing environment to a Raid 1, then take out one of the drives and replace it with one of the new 160 Gb's. The unit would then copy the OS to the new 160 Gb drive, and when finished, move it to primary, and fail the second one again replacing it with a 160 Gb drive. The (2) method appears to remove the second drive without changing to Raid 1 first, replace it with a new 160 Gb drive, then have it come up after the OS is copied, move this new drive to primary (either Primary or CS) and then remove the second drive which was a 20 GB drive. I am also not clear on what wiki is (I HAVE read all 500 plus pages, but dont remember that term) and would appreciate any help.

Wayne

I just wanted to provide an update to the forum as far as my upgrade went. I opened the box (on the 2000, there is a single screw at the back then the two halves slide, one forward the other one backward. I then took the drive plate out with the dries to determine which drive was master and which was slave as both had been C/S (cable selected). The drive closest to the rear (power supply) was IDE-1 so I assumed it was the master and I was correct. I replaced the front drive (assumed to be the slave) with a 160 GB drive, with C/S and started it up. About 1 minute later, it was formatting the new drive. I then swapped the front drive (slave) with the rear one (master) and again started it up. After about two minutes, I had two separate drives, each with about 150 GB's. I am now setting them us as mirrored drives. Thanks to all those who helped here in this forum as it would have been very difficult. The only hard part was reading the 500 plus pages.

Thanks, Wayne

[harddisque]

Originally Posted by 227

I have a snap server 1100, the hard disk has crashed and does not turn anymore, so i got myself a new seagate exact harddisk and installed it, the system and disk lights are flashing together and this thing will not come up. I have tried the dhcp and assist tool but no luck. I have been reading on this forum and understand that I need some boot files first on the new hard disk. Does anyone have these files? Please help

I'm in the same boat, except I have a Maxtor disk i'd like to use. Any info on installing a replacement disk in the 1100 when you have a failed hard drive and no possibility of recovering files.

Is the OS on the 1100 on the NVRAM?

[blue68f100]

Do you have web interface access? if so (v1) yes

If not you guessed it ON the DRIVE.

If the Maxtor is one of the ATA133 EIDE, you may have problems getting the drive to work with the snap.

[harddisque]

Looks like the maxtor drive is an ATA-100 (???).

So as I understand it, if the OS is on the NVRAM, I should be able to access this device with the web interface? Even with NO drive installed?

This is my first experience with a Snap server from a repair standpoint, so excuse my ignorance.

[blue68f100]

Yes on Flashram, If you can access the snap with no drives.

Up grading is easier too, just install the drive, it will see it and set it up.

[harddisque]

Originally Posted by blue68f100

Yes on Flashram, If you can access the snap with no drives.

Up grading is easier too, just install the drive, it will see it and set it up.

Is there a way of identifying on the motherboard whether it has NVRAM or not?

There is one chip tagged similar to the NVRAM in one in the pictures in the "hacking a snap server" although they are different models.

[blue68f100]

If you are wanting to upgrade the drive, you have 2 choices with the 1100.

1. Install the new drive and see it the snap will prepare and use the drive.

2. Copy the boot tracks from your working drive to the new one using the instruction in the wiki section of the forum.

[harddisque]

Originally Posted by blue68f100

If you are wanting to upgrade the drive, you have 2 choices with the 1100.

1. Install the new drive and see it the snap will prepare and use the drive.

2. Copy the boot tracks from your working drive to the new one using the instruction in the wiki section of the forum.

Looks like I'm stuck with option 1.....original hard drive was toast. How long do you thing it will take to prepare a 40 GB drive?

[blue68f100]

If option 1 works you should be able to connect to the drive in 10 min.

If the sys an disk leds are sending mores code (repeat 1 +2), you will need to load a image file.

[harddisque]

Originally Posted by blue68f100

If option 1 works you should be able to connect to the drive in 10 min.

If the sys an disk leds are sending mores code (repeat 1 +2), you will need to load a image file.

looks like I'll need an image file. Any suggestions?

[evoaz1]

Hello everyone. Been following this thread for over a year. Thanks for all the help already - this thread has been a great resource for Snap owners!

Have a Snap 2000 with the following:

OS: 3.4.803 (US)
Hardware: 2.0.0
BIOS: 2.0.282
SN: 55556
128MB Upgraded memory, 2x80GB WD, stock fan (will replace)

I upgraded my Snap very early on with 2x80GB WD drives and the additional memory. It has been working for almost 3 years flawlessly! Well one of the drives just died yesterday, and I want to upgrade both drives above the 137GB limit, so I am assuming from what I have learned here that I need OS v4.0.830. I have OS v4.0.860 available, but I think the consensus is NOT to use this version. Can anyone point me in the right direction to find OS version 4.0.830? or send it to me? I would greatly appreciate it. Thanks so much!

[blue68f100]

You have a v2 2000, with extra ram. It will run 4.0.860. v4.0.860 is a patch for the 4.0.830 version, that added MS2003 AD support. Or you could just move up to 3.4.805.

[evoaz1]

You have a v2 2000, with extra ram. It will run 4.0.860. v4.0.860 is a patch for the 4.0.830 version, that added MS2003 AD support. Or you could just move up to 3.4.805.

blue 68f100 - Make sure I have this right - OS v3.4.805 will support drives >137GB?

[blue68f100]

Yes

[evoaz1]

Thanks to blue68f100 and re3dyb0y for their help. It seems I had some misinformation about how to get above the 137GB limit on my 2000. I had assumed that I needed v4 of the Snap OS to get 48-bit lba enabled, but that isn't true. I did find something interesting thru the process that I wanted to share.

To recap, my Snap (after upgrades):
OS: 3.4.807 (US)
Hardware: 2.0.0
BIOS: 2.0.282
SN: 55556
128MB Upgraded memory, 2x300GB Seagate ATA/100 (woohoo!), 50x50x15 fan

OK, here is what I found. I registered my Snap 2000 very early when I got it a few years ago. I logged into Adaptec's site (http://profile.adaptec.com/licenseAgreement.aspx yesterday and found my information there. I noticed that there was a new OS listed for the 2000, version S2Sv2 (not actually sure it works with the 2000, but it was listed). I was curious so I tried to request an SLK (Software License Key) thru the Adaptec Site which apparently you need to actually upgrade to S2Sv2 (if even possible). At this point I thought I needed AT LEAST v4 of the OS to break the 137GB limit, so I thought I would explor the S2Sv2 options if possible. Well, the site had some kind of errors, and I was redirected to an FAQ page here: http://profile.adaptec.com/licenseAgreement.aspx

On that page is a link to a division of Adaptec's customer support. I emailed them requesting the "most recent version of the Snap OS for the 2000". Within an hour I had the following email from them:

Your case, 0000000000xxxxx, was updated. Please refer to the information below for our response. Please Click here if you need additional support on this issue.
Please do not reply to this email as it will not be seen by a live representative.

To download the latest version of SnapOS, please visit
http://xxxxxx

File Name:
SNAPOS_34807.EXE

Password:
xxxxxxxxx

Notes: The weblink above requires the Snap Server to be registered with Adaptec, Inc.

Sure enough, I was able to get the v3.4.807 OS version from Adaptec without paying anything. I upgraded the OS without a problem, and everything is working well. Just wanted to share this with anyone who is trying to upgrade a2000/2200 to the latest v3 OS. It looks like if you ask the right people, they will give you the free OS upgrade.

I know (now, thanks to those on this thread) that the 3.4.805 version gives 48-bit lba support, and of course so does this newer 3.4.807 version, but I don't know what else it upgraded/changed. If anyone has any idea on the other differences please post them.

Thanks again to all!

[re3dyb0y]

It will just have some minor bug fixes and such

As ther eare quite a few versions with small changes in them

[Phoenix32]

an 807 version? Interesting, since I have also chosen to stick with the v3 OS. I truly wonder what was "fixed" in this version over 805 and if it is worth while. And ideas Dave? Or sources to find out for sure?

[blue68f100]

If you read the post, he was able to get the file from Adaptec. I told him 3.4.805 supported large disk. He requested the file and they gave him a link to the 807. Have NO IDEA what was changed or fixed in 807.

[harddisque]

Well...was able to load an image file, and it appears to be doing something. The drive was installed with NTFS and loaded with an image with knoppix. The unit goes into the 1 + 2 light sequence and is working on the disk. My first attempt showed that the disk must have been reformatted in the process because the NTFS system was not present when testing the drive in another PC.

Does this process take a LONG time? I let the box run overnight and it was still in the same mode it was in. when I woke up the next morning..if so I'll just put in in a corner and let it run. Does it finally move out of this mode (sys light - one blink, drive -two blinks) and on to a point where I can get into it on the network?. It apparently hasn't reached to the stage where it goes out for an IP address yet.

Any info is appreciated! Thanks to all for the help...better than tech support!!!! and cheaper, too!!!

I feel like I'm almost there...just need to get over the hump (so to speak)

John