Hack a Snap Sever 1000?

[Phoenix32]

If this is an SMD and is labeled FB, it sounds like a Semiconductor Fast Blow Fuse. It has been a long long time since I did any circuit board designs and I am a bit (read a lot) rusty, so I could be wrong, but that is what it sounds like to me.

I have pondered on this supposed other IDE type connector before (well for a few moments anywise) when it has been mentioned here on the forum before. Since a number of people have confirmed it is not another IDE channel, then we can eliminate that. If I was to take a SWAG here (Scientific Wild Assed Guess), I would guess it is a testing header or maybe even a way in which they connected to write the OS onto the blank hard disks? Has anyone ever traced the connections out to see where they go?

[bitor]

Hello and Happy Holidays!

Here are my questions. I hope you can help me.

I have a Snap Server 1000v2 250GB HD.

With my box open at all times, using a two HD connector single ribben with 250GB(OS HD) connected to master end ribben and adding a second HD connect on slave.
Question:
1.) Can I add this second HD ?
2.) On second HD should I set it to slave or CS ? (250GB is set to CS)
3.) If I can add the second HD to the ribben, do I have to be concerned with lossing information from my master HD? Or will it just format the second HD without disturbing the Pri. Master 250GB HD?
4.) Will the motherboard's power supply handle the extra power from the second drive? Or with this fry the power supply over time?

Thanks again for your help in advanced,
Sincerely,
bitor

[blue68f100]

99.99% fail on this conversion. There is a flag that auto reboots the snap once you change it to a 2 drive model. Then it will hang "waiting for IP address".

This is a BIOS Flag setting, You have to unlock it for the change to take, then it KILL's The UNIT with the above error".

I have 1 right here with that error. I have tried everything I and many other to clear it. HAVE NOT BEEN SUCESSFUL. I still hammer it evertime I come up with utilities, NO GO.

[Lharris]

Hi - Thanks - that part was a fast blow fuse. I have my snap server turning on but now I get the following: a "flurry" of disk activity, the link light comes on steady, the system light blinks about every second, and the disk light double blinks every second with the first in sync with the system light. Is that the infamous "blink of death" or is there something simple I can do to reset it. I tried the reset modes and they seem to register - but after reset it goes back to this.
I don't have snap assist so I can't tell if it is an ip problem, and I can't see it on my network.
Any ideas?
Thanks

[bitor]

Hello and Happy Holidays!

Hey, I guess I did not explain myself correctly. I don't want to turn it in to a RAID. I just want to take out the old single ribben with one hard drive connector and put in its place a ribben that has two hard drive connectors. i.e Master and Slave.
So, with that being said and in mind now...can I do this?

Here are my questions. I hope you can help me.

I have a Snap Server 1000v2 250GB HD.

With my box open at all times, using a two HD connector single ribben with 250GB(OS HD) connected to master end ribben and adding a second HD connect on slave.
Question:
1.) Can I add this second HD ?
2.) On second HD should I set it to slave or CS ? (250GB is set to CS)
3.) If I can add the second HD to the ribben, do I have to be concerned with lossing information from my master HD? Or will it just format the second HD without disturbing the Pri. Master 250GB HD?
4.) Will the motherboard's power supply handle the extra power from the second drive? Or with this fry the power supply over time?

Thanks again for your help in advanced,
Sincerely,
bitor

[Phoenix32]

Originally Posted by Lharris

Hi - Thanks - that part was a fast blow fuse. I have my snap server turning on

I don't have snap assist so I can't tell if it is an ip problem, and I can't see it on my

Your welcome...

[Phoenix32]

Originally Posted by bitor

Hello and Happy Holidays!

Question:
1.) Can I add this second HD ?
2.) On second HD should I set it to slave or CS ? (250GB is set to CS)
3.) If I can add the second HD to the ribben, do I have to be concerned with lossing information from my master HD? Or will it just format the second HD without disturbing the Pri. Master 250GB HD?
4.) Will the motherboard's power supply handle the extra power from the second drive? Or with this fry the power supply over time?

1) Maybe
2) CS, but with the SNAP you will probably need a special cable for this function
3) It shouldn't hurt the other drive, but I cannot say for 100%
4) It is a little light for this, but no more so than we push the other SNAP servers, so it will all come down to just how good the power supply is

[blue68f100]

Originally Posted by Lharris

Hi - Thanks - that part was a fast blow fuse. I have my snap server turning on but now I get the following: a "flurry" of disk activity, the link light comes on steady, the system light blinks about every second, and the disk light double blinks every second with the first in sync with the system light. Is that the infamous "blink of death" or is there something simple I can do to reset it. I tried the reset modes and they seem to register - but after reset it goes back to this.
I don't have snap assist so I can't tell if it is an ip problem, and I can't see it on my network.
Any ideas?
Thanks

NO That the siginal saying waiting for IP address. If you reset everthing back to factory it may give the same error as the OS is not there or damage on the HD. Assist will be needed to setup the snap. Older models defaulted to a IP address of 0.0.0.0. Assist locates these and allow you to setup the snap for use. There is only one model of the 1000 that does not require the OS on the HD. Assist will confirm weather the OS is missing. Some units only have part of OS in flashram, will boot but will not have any help files loaded.

[blue68f100]

bitor,

I was serious on a 99.99 % failure rate. It can be done, but requires some carefull planing. I only think v1, 1000 works for this converson.

Do not know if drive are required to be M/S or CS, my guess M/S.

You MUST TURN off Reboot on changes. Because when you change the unit from 1 drive to 2 it will reboot and say good bye to your working snap. You must then reload the OS, before the reboot. Once reloaded, reboot the unit with 2 drives attached and see if it comes up.

As far as loosing data. It MAY be there but you may need another 1000 to read the HD, because your MB will be locked up. I have one here right now, from a user attempting the smae stunt.

My thoughts, When you make this change the snap (trys to) reboot, does not find the hardware it is looking for or software, because it reboots before a user has a chance to load it. The unit is now LOCKED UP, with no way to clear the flashram or change the setting back. If you already have 250 gig and need more space by a larger HD. If you want a RAID, buy a unit that supports it.

Now there is a 2000 board that works on both 2000 & 4000 units. Don't know the PN.

DO THIS AT YOUR OWN RISK, NOT RESPONSIABLE FOR DAMAGES.

[Phoenix32]

And there you have it... From a hardware perspective, maybe it might work. From a software perspective, you are playing with fire and are likely to get burned. I don't think it can be said any clearer than that...

[bitor]

Thank you for all of the input.

After careful concideration and knowing now what David has said about just adding another HD to a ribben without wanting to turn it in to a RAID, I've opted NOT to add an extra HD to my Snap Server 1000v2. It's not worth the risk to me. I just had an extra HD around and thought I would add it. If I want to increase to HD I'll just buy another larger one...say ATA100 Seagate 750GB. I'm going to wait until the price drops down.

I'm still wondering what the diff. between the OS's v3.4.805 and v3.4.807. Does anybody know what was corrected/added/fixed ? Seems such a small update, but I'm not sure.
Also, is there anyway via debug to turn the fan on 24/7?

Thanks again for your help,
Happy Holidays,
Sincerely,
bitor

[blue68f100]

Not on the software side that I know of. You could always wire it in to 12 side of the drive connector. That is where the 2200 powers it fan. Other have reported that it come on with the case closed up. Don't know where they are reading the temp at.

[Lharris]

Well - i have tried everything so far - reimaged the drive (2 different drives) now i get the system led binking rapidly twice, the disk light on steady, the net light on steady and the activity light randomly flashing. I can't see it on my network. I have tried formating the drive as both unix and msdos (i'm using a mac). Is there some problem with the mac partition scheme that prevents an imaged drive from working - I would assume that dd is dd no matter what os it is from. Any ideas?
Thanks to all who have made suggestions so far and have a happy holiday!

[blue68f100]

Thats a indication of the wrong image file, missing OS. The 1000 are odd balls, when it comes to image files. The SnapOS use a odd BSD file structure that nothing short of another snap can read.

dd works the same on mac or pc as long as you are use the raw cmds. Adn adjust ti drive ID if different than the instructions posted on the wiki siection. I know of other users that have done it.

[Phoenix32]

Ummm, David, I do not want to step on your toes here since this is your area of expertise, but;

I know this is for a SNAP 1000, but on my SNAP 4100/4000 units, if you put in a new drive, it starts formatting it (duh). But during this time,

The System Light blinks quickly (like the panic blink)
The Network Link Light is steady
The Network Activity Light blinks random
The Disk Light is on steady

Until the drive is formatted, and in some cases the SNAP will not respond (even to assist) until it completes.

The only difference I see here is he said the System Light blinks "twice" rapidly (I assume he meant double blinks). Is it possible the drive is just being formatted and he just needs to wait a bit? Doubtful, but just a thought/idea.

[blue68f100]

Good Point but not in this case, v2. It's morse code for waiting for IP. It also does this when it doesn't find a sound/working OS.

I don't think they installed a large enough flashram to contain the OS on v2. Don't see very may v1 at all. When the OS is be decompressed it always has a random sequece. When they flash in unison it's error codes.

[Phoenix32]

Okay, I believe you no problem. As I said, it was just a thought (something to check maybe).

[bitor]

Hello & Greetings:

I got a snap 1000v2 mobo and was looking it over with a mag. glass and found something interesting. Don't know if anybody has done this or not. As I was looking at my 1000v2 mobo I saw a green small wire soldered to one leg of the bios chip and this wire leads under and to the IDE controller. Now, that same leg of the bios that has the green small wire soldered to it has a wire embedded in the board going to the ISP controller. Funny thing is, this embedded wire has been disabled by a small div-it that cut in to the surface of the mobo down to the wire embbeded in the mobo which leads to the ISP controller. The wire I believe was disconnected/cut by the factory. There is also one cut/div-it on the back side of the mobo also, but diff. embedded wire I believe. Looks like a small drill came down on the mobo and cut the embedded wire in the mobo. Why do you think they did this. The embedded wire is way to small for me to solder. If I had some mercery then I could put a small drop in the div-it and make the connection. Any thoughts ?? Do you think this ISP could be used as another IDE controller if that wire was reconnected? Check you mobo with a mag. glass around the bios chip and also on the back side too.


bitor

[blue68f100]

I will take a look at the one I have.

Is your a new board or a referb?

We have alway wondered what the ISP header was for?

May have been used to run diagnostic or do the initial programing of the bios or flashram.

[bitor]

It's a refurbished one. Still thow, who ever refurbished it(I believe the oem mfg.) knew what they were doing. In order for them to get that small wire under the IDE controller they would have had to desolder the IDE controller. And by the looks of it with a mag. glass it doesn't look like it has been desoldered. So, I would guess that's maybe from the mfg. Wonder what was wrong with this mobo where they had to refurbished it? My other 1000v2 does not have this wire going from the bios to the IDE controller. But that one is a diff. serial number. It's a 12447 and this one (refurb) is 30156. Both are 1000v2. Maybe the older mobo they disabled them by cutting the mobo wire and the newer mobo they just used a new bios lock out for the ISP controller.

Thoughts?,
bitor

About the ISP controller. My research on the web has led me to believe it IS for programing the bios. And maybe some other features too.

[Adam1V]

Originally Posted by SleepyTiger62

Hello,

I have completed/replace a 15GB Snap 1000 into a 120GB. Here are the steps, read this enttire thread so you will know what I am talking about.

Step 1:

Remove the original Snap Drive and using Linux/Unix O/S.

Copy the entire contect of original Snap hard drive into the new drive using UNIX dd command.

Step 2:

Connect new drive into Snap and log into Snap via the web page. Then redirect the url to:

http://yourserver/config/debug

Type in "config devices info" into the command area to get the partition device
numbers, in my case it was 10000 and 10006. See below:


************************************************** **

08/18/2002 14:16:02 Command: config devices info

Logical Device: 10006 Position: 0 JBOD Size (KB): 32296 Free (KB): 32168 Private Mounted
Label:Private Contains system files only
Unique Id: 0x123C08AD34558ABC Mount: /priv Index: 12 Order: 0
Partition: 10006 Physical: 10007 FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 10007 Drive Slot: 0 IDE Size (KB): 120627200 Fixed

Logical Device: 10000 Position: 1 JBOD Size (KB): 118313472 Free (KB): 118195104 Public Mounted
Labelrive1 Single disk
Unique Id: 0x123C08AD34558ABC Mount: /0 Index: 0 Order: 1
Partition: 10000 Physical: 10007 FS Size (KB): 119953736 Starting Blk: 84055 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 120627200 Fixed

************************************************** **

Then type in "config devices format 10000 /reinit".

Reboot to start the format and re-initialization. After that the full capacity of the new drive will take affect.

Good Luck & Have Fun

SleepyTiger62@Yahoo.com

Hi guys.
Ive came accross this amazing forum for Snap OSs and managed to find the above information. Im going to have a go at updating my Snap 1000 with a larger disk, something like 300gb.
Does anyone know if the above method is working ok?
I dont really want to search through 52 pages to see if its most up to date. By the looks of things, there are some regular members here who know exactly whats going on.

Adam

[blue68f100]

This thread is one on the most informative threads on the forum. Makes good late night reading.

Actually you only need the first 25meg of the drive to boot the new drive, but you may be missing some help files. If you copy the complete drive doesn't hurt just take a long time doing a RAW copy. A RAW copy must be done, nothing but BSD can read the file structure.

The "co de format 10000 /reint" formats the drive and all data will be lost. Instruction are located in the wiki section of the forum. We have found that Digital Dolly is the mist widely used, comes on all dist of linux and bsd's. And there is a live cd version out too.

Most all 1000 support LBA48bit address, bios v2 and greater seams to be the magic number for all snaps os units.

LARGE DISK require OS v 3.4.805 and greater, or your out of luck. To check your version click on the SnapApliance logo from the admin page.

Do you know if you have a version 1 or 2 1000???
Version 1 has OS in flashram and were made by meridian.

[Adam1V]

Originally Posted by blue68f100

This thread is one on the most informative threads on the forum. Makes good late night reading.

The sad thing is your actually right

Originally Posted by blue68f100

Actually you only need the first 25meg of the drive to boot the new drive, but you may be missing some help files. If you copy the complete drive doesn't hurt just take a long time doing a RAW copy. A RAW copy must be done, nothing but BSD can read the file structure.

The "co de format 10000 /reint" formats the drive and all data will be lost. Instruction are located in the wiki section of the forum. We have found that Digital Dolly is the mist widely used, comes on all dist of linux and bsd's. And there is a live cd version out too.

Most all 1000 support LBA48bit address, bios v2 and greater seams to be the magic number for all snaps os units.

LARGE DISK require OS v 3.4.805 and greater, or your out of luck. To check your version click on the SnapApliance logo from the admin page.

Do you know if you have a version 1 or 2 1000???
Version 1 has OS in flashram and were made by meridian.

I dont know what version i have, but im taking the drive home tonight so i can look then. But i do have a sneaky suspicion its in the flashram.
I have a few questions if you have a couple of minutes to answer them.

Ive read on this forum about the previous legal issues of downloading the OS, and without breaching these, is there a free version (open source) version of the 3.4.805 available?

I do not need to keep any of the data thats on the original hard disk, so will i still need to use the dolly program?
I dont know a great deal, but i assume that will depend on the version i have? if the OS is on the disk i will need to copy and if the OS is not on the disk no need to copy?

With regard to the "co de format 10000 /reint" command, i assume that your only formatting the new drive your putting in?

IF you have a link to that wikki to save me looking it would be handy
Thanks very much for your time.

[blue68f100]

Ive read on this forum about the previous legal issues of downloading the OS, and without breaching these, is there a free version (open source) version of the 3.4.805 available?

A few users have reported luck using BT, but I haven't a clue, becuase most say they find nothing.

DD is what most users use because it does what is know as a raw copy. This is a sector by sector copy, ignoring all data. This is where most fail, try to inturpet data.

The /reinit cmd is issued from the snap's debug page.

Look at the top of the page, select wiki (left of forums).

If you have a rare v1 just install the drive, it will do all of the setup. These models are vary rare.

[Adam1V]

IVe checked it out and i have the following info:

Software: 3.4.803 (US)
Hardware: 3.1.2
BIOS: 2.1.366

Is digital dolly the best method to go about copying now?
Im assuming the OS is located on the drive and the DD will copy the os over and then a simple reformat will sort the drive out?

I assume i boot from a CD with DD on, which will recognise the new drive plugged into the snap server?