Hack a Snap Sever 1000?

[re3dyb0y]

The should do....

But with the 1 series, you would have to copy an image onto it!

[blue68f100]

The 1000 would need v3.4.805 to support large disk. Do you know if your is v1 or v2 model? V1 all is needed for hd upgrade is to install it, after upgrading the os. V2 would require you to copy the boot tracks from old to new.

[mgeorge]

Just a follow up. I have a WDC 250 GD installed into my Snap 1100 after I copied the boot tracks over per MY instructions in post#43. It booted just fine, I reformatted with "co de fo 10000 /reinit". Unfortunately, it only formatted out to 128,533 MB. My SnapOS software is 3.4.803. What do I have to install to get the full 250GB and how do I go about getting it?

Yeah, I know I said I was going to give it to a buddy, but I couldn't give up, not just yet.

Thanks,
Mike

[blue68f100]

You need to get your eyes checked, 805

[re3dyb0y]

Some good news

I've had my WD2500JB replaced today

Will try it tonight or something, or wednesday, as i've a day off

[re3dyb0y]

It has also recently being taking ages to boot up.

Any ideas anyone?

[blue68f100]

Look at your log and see if its running check disk or some other repair.

[re3dyb0y]

It is just running the normal checks

I  System Initialization : Initialization Complete! Memory to be released: 22105248 bytes.  System   2/21/2006  10:18:19 AM  
I  File System : Opened FDB for device 0x10010  Disk 10010 
Individual   2/21/2006  10:18:19 AM  
I  File System Check : partition is clean.  Disk 10010 
Individual   2/21/2006  10:18:19 AM  
I  File System Check : Executing fsck /dev/ride2a /fix  Disk 10010 
Individual   2/21/2006  10:18:19 AM  
I  File System : Opened FDB for device 0x10000  Disk 10000 
Individual   2/21/2006  10:18:19 AM  
I  File System Check : partition is clean.  Disk 10000 
Individual   2/21/2006  10:18:19 AM  
I  File System Check : Executing fsck /dev/ride0a /fix  Disk 10000 
Individual   2/21/2006  10:18:19 AM  
I  File System : Opened FDB for device 0x10016  Disk (Priv)   2/21/2006  10:18:19 AM  
I  File System Check : partition is clean.  Disk (Priv)   2/21/2006  10:18:16 AM  
I  File System Check : Executing fsck /dev/ride2g /fix /fixfatal  Disk (Priv)   2/21/2006  10:18:16 AM  
I  File System : Opened FDB for device 0x10006  Disk (Priv)   2/21/2006  10:18:16 AM  
I  File System Check : partition is clean.  Disk (Priv)   2/21/2006  10:18:16 AM  
I  File System Check : Executing fsck /dev/ride0g /fix /fixfatal  Disk (Priv)   2/21/2006  10:18:16 AM

More than anything it is just a long time before it is accessible



Saying that, i just booted it back up again to get that model table, and it was up in reasonable "normal" time...

Maybe its just been having some bad shutdowns and such

  Jrc: exiting  Unknown   2/21/2006   5:02:11 PM  
I  Jrc.execute() starting  Unknown   2/21/2006   5:02:11 PM  
I  Jrc created  Unknown   2/21/2006   5:02:11 PM  
I  SnapOS.init() executed  Unknown   2/21/2006   5:02:11 PM  
I  SnapExtension Framework 1.2 initialized  Unknown   2/21/2006   5:02:10 PM  
I  No startup snaplets  Unknown   2/21/2006   5:02:10 PM  
I  done  Unknown   2/21/2006   5:02:10 PM  
I  building info for serversync.jar  Unknown   2/21/2006   5:02:09 PM  
I  done  Unknown   2/21/2006   5:02:09 PM  
I  building info for FtpSync.jar  Unknown   2/21/2006   5:02:09 PM  
I  done  Unknown   2/21/2006   5:02:09 PM  
I  building info for ssl.jar  Unknown   2/21/2006   5:02:09 PM  
I  done  Unknown   2/21/2006   5:02:09 PM  
I  building info for hello.jar  Unknown   2/21/2006   5:02:07 PM  
I  Java: Native methods linked OK  Unknown   2/21/2006   5:02:04 PM  
I  Jrc.main() starting  Unknown   2/21/2006   5:02:03 PM  
I  System Initialization : Initialization Complete! Memory to be released: 22105248 bytes.  System   2/21/2006   5:01:59 PM  
I  File System : Opened FDB for device 0x10010  Disk 10010 
Individual   2/21/2006   5:01:59 PM  
I  File System Check : partition is clean.  Disk 10010 
Individual   2/21/2006   5:01:59 PM  
I  File System Check : Executing fsck /dev/ride2a /fix  Disk 10010 
Individual   2/21/2006   5:01:59 PM  
I  File System : Opened FDB for device 0x10000  Disk 10000 
Individual   2/21/2006   5:01:59 PM  
I  File System Check : partition is clean.  Disk 10000 
Individual   2/21/2006   5:01:59 PM  
I  File System Check : Executing fsck /dev/ride0a /fix  Disk 10000 
Individual   2/21/2006   5:01:59 PM  
I  File System : Opened FDB for device 0x10016  Disk (Priv)   2/21/2006   5:01:59 PM  
I  File System Check : partition is clean.  Disk (Priv)   2/21/2006   5:01:59 PM  
I  File System Check : Executing fsck /dev/ride2g /fix /fixfatal  Disk (Priv)   2/21/2006   5:01:59 PM  
I  File System : Opened FDB for device 0x10006  Disk (Priv)   2/21/2006   5:01:59 PM  
I  File System Check : partition is clean.  Disk (Priv)   2/21/2006   5:01:59 PM  
I  File System Check : Executing fsck /dev/ride0g /fix /fixfatal  Disk (Priv)   2/21/2006   5:01:59 PM  
I  INIT: Setting IP address to 192.168.0.200  Network   2/21/2006   5:01:54 PM  
S  System Initialization : Server v4.0.860
Build Date: Mar 2 2005 17:50:55
Boot Count: 261  System   2/21/2006   5:01:54 PM

Saying that, when i resintalled the OS earlier, it had a few problems doing it, but i sorted that by using the web interface. But it hasn't really liked assist recently!


And sometimes it seems to boot, and not start up the hard drives

[re3dyb0y]

Its now showing

I  TH_targKill(2577e1c): unable to kill thread waiting for I/O  Unknown   2/21/2006   5:15:16 PM  
I  TH_targKill(257a930): unable to kill thread waiting for I/O  Unknown   2/21/2006   5:15:16 PM

Any ideas?

[mmd30]

I tried to upgrade the java virtual machine, and I changed the BIOS version to 4 0 0 from 3 1 2 (in debug screen). The upgrade worked "fine" but because I forget to change it back to 3 1 2, now the server it's not accesible and the main LED it's blinking very fast. I tried the maintenance mode (to reset to the factory defaults) without results - this procedure doesn't change the BIOS. Is it anything that I could do to make it bootable again? Maybe changing the jumpers on that tiny motherboard ?

[blue68f100]

Poogles,

It looks like something is hapening with JVM reporting unknown. May need to reinstall the OS and JVM again.

mmd30,

Your not the first one to get caught with a reboot. The rapid flashing is panic mode. I think what has worked is ???? oh yea, Do a factory reset, soon as the system light blinks 5/sec panic, turn the snap off with the power button (press hold). Restart after 1 min. Start assist, the unit may still go in panic mode, leave assist running it may take up to 1 hr till it times out and show up with assist. Connect with assist and change your bios setting back.

Loading JVM requires a min of 24 meg to, if you do not have a min of 64 meg, pref 128 to run properly. It all depends on what it is going on.

You failed to mention what you are working on, 1000 with 32 meg.

[re3dyb0y]

Originally Posted by blue68f100

Poogles,

It looks like something is hapening with JVM reporting unknown. May need to reinstall the OS and JVM again.

Yay!

My favourite Activity.....

It has probably got something to do with the fact of me just copying and over writing some of the old Java files..... More apps tho

[re3dyb0y]

I  File System : Closed FDB for device 0x10006  Disk (Priv)   2/22/2006   8:40:15 AM  
I  File System : Closed FDB for device 0x10010  Disk 10010 
Individual   2/22/2006   8:40:13 AM  
I  File System : Closed FDB for device 0x10000  Disk 10000 
Individual   2/22/2006   8:40:13 AM  
I  TH_targKill(2573a78): unable to kill thread waiting for I/O  Unknown   2/22/2006   8:40:03 AM  
I  TH_targKill(245fda4): unable to kill thread waiting for I/O  Unknown   2/22/2006   8:40:03 AM  
I  Java: forcing System.exit(0)  Unknown   2/22/2006   8:39:59 AM  
I  System Shutdown : In Progress...  System   2/22/2006   8:39:59 AM  
I  System Shutdown : in 3 seconds  System   2/22/2006   8:39:56 AM

Me thinks you may be right....

Will try it later on

[eduardo]

Gentlemen,

I salute you for providing all the information on Snap Servers that a man could possibly need. I'm now at about three hours of reading and cross-referencing about my particular problem and wonder if one of the true experts could confirm my findings before I spend some money?

I have a quantity of 2200s that came from a UK Govt site and have therefore been comprehensively wiped.....I guess by removing the drives and hammering them with some generic data-wiping tool. The obvious result is that they are currently without OS and useless!

I believe from reading this and other threads that I could restore them if I had access to either a working 2200 or the image of a working disk. Is this right?

Could anyone help me with either item?

[re3dyb0y]

David - Reinstalled OS with no avail, reinstalling the JVM seemed to sort it, but it has come back agian

Doesn't seem to cause any problem, so i wont worry aobut it

And the new drive - 170GB of data copied with no problems!


eduardo, yes you are correct. They can be revived, please email me for details. Its case of copying the contents of the image onto the drive, stick it in the snap and then you are sort of away when it decides to sort itself out

If they had put it in a windows machine it wouldnt show anything anyway.

[blue68f100]

Googles,

I TH_targKill(2573a78): unable to kill thread waiting for I/O Unknown 2/22/2006 8:40:03 AM
I TH_targKill(245fda4): unable to kill thread waiting for I/O Unknown 2/22/2006 8:40:03 AM
I Java: forcing System.exit(0) Unknown 2/22/2006 8:39:59 AM

You may have need to do a clean install. Before you get to far ahead. If you had some java script running, reinstall it, or try killing it.

Eduardo,

As poogles said, we can get the 2200 snaps back to life. As for hd, most came factory with 2 x 160gig (320gig) or greater. I have 2 300gigs in mine, there was another user looking at installing 500's. Having a quanity of these units must be nice. Hopefully you got the power supply that goes with them. If you got any 2000, or 4x00 series, the OS is stored in flash. All that is need for those in install the drives, then transfer the drive to the 2200's.

As for the reading material, This is a pretty active thread, mainly due to Adaptec wanting to charge $125.00us for support.

[re3dyb0y]

Originally Posted by blue68f100

Googles,
You may have need to do a clean install. Before you get to far ahead. If you had some java script running, reinstall it, or try killing it.

Typical, i've just copied all the files accross and removed some again from the plaecs i had them stored....

I will try removing S2S and stuff to see if that soves it

[re3dyb0y]

Just turned off the snap extensions and upon next reboot, no messages

Also, there is twice as much free ram, nearer 42mb rather than 22 it seems.

I will try manually removing all the java files from the snap server via full FTP access to the os_private.

Restart, and install the JVM and see if it comes up again, then S2S and etc


Or would resintalling the OS Clear the java? - I think it would, wouldn't i (Im sure before this happend ie reinstalling os clears JVM)

[re3dyb0y]

Ive also noticed that it resarts in 60 seconds when it boots correctly (ie, when it boots and starts the drives)

As maybe 1 in 5 it doesnt seem to start up the hard drives

[eduardo]

I'm locked in a semi-darkened room with a Snap Server, an old-favourite PC, a knoppix CD, an image file and bread-and-water rations.....I will let you know what happens when I re-emerge.

[blue68f100]

Poogles,

I think the only way to completely clean it, would be to wipe your drive or manually like you are talking about. Re-installing would only overwrite the files being copied, not any thay you may have added.

Atleast you have a handle on it. You've done the hard part already, pin-pointing the source.

As for eduardo,

Someone baricade the door ...... Since locking the door want keep him in.

[re3dyb0y]

Originally Posted by blue68f100

Poogles,

I think the only way to completely clean it, would be to wipe your drive or manually like you are talking about. Re-installing would only overwrite the files being copied, not any thay you may have added.

At least you have a handle on it. You've done the hard part already, pin-pointing the source.

As for eduardo,

Someone baricade the door ...... Since locking the door want keep him in.

Yeah, i've disabled the JVM for the moment, so that will be able to delete all the files, restart, and try reinstalling

[eduardo]

Eduardo emerges, blinking, into the light, downs a hearty beer and announces to the waiting world, "I have a working Snap Server!"

However, it's on OS 3.4.790: is my upgrade path cut-off? I note that Ad*pt*c website doesn't have upgrades if you are below 4.0.x

[blue68f100]

Have you checked to see what HW and BIOS version you are at.

And what size HD did you install?

It gets better, yours should support HD >137gig.

Save you self some problems and Buy Hitachi or Seagates.

[eduardo]

I'm at H/W 2.0.4 and BIOS 3.4.758.

I've got some 2200s with two 80Gb and some with two 160Gb: I guess I don't need to go to OS 4.x.x. for the Dual 80Gbs as they will work as they are.