I was able to install a 256MB dimm into my system. The Quantam Snap 2000 has 1 removeable dimm.
06/04/2005 11:10:18 Command: debug memory

Total System Physical Memory: 268435456
File System Memory Allocated: 248721408
Memory To be Written: 24912
Memory On Loan: 16608
Loan Count: 2
Heap Memory: 229127856
Memory In Use: 226356224
Objects Allocated: 29
Communication Memory Allocated: 2059232
Memory In Use: 467604
SDB Non-Volatile Memory Allocated: 65536
Memory In Use: 16122
Handles Allocated:4679
Handles In Use: 361
SDB Volatile Memory Allocated: 98304
Memory In Use: 330
Handles Allocated: 11705
Handles In Use: 12
System has been configured!


Here is my information on the the hard drives in the 2000. Two 160 GB Western Digitals.
06/04/2005 11:17:04 Command: info devices

Logical Device: 10006 Position: 0 JBOD Size (KB): 32296 Free (KB): 22568 Private Mounted
Label:Private Contains system files only
Unique Id: 0x3D59CBB01F234A2E 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): 156290560 Fixed

Logical Device: 10016 Position: 0 JBOD Size (KB): 32296 Free (KB): 22568 Private Mounted
Label:Private Contains system files only
Unique Id: 0x2578B5931D960B26 Mount: /pri2 Index: 13 Order: 1
Partition: 10016 Physical: 10017 FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 10017 Drive Slot: 2 IDE Size (KB): 156290560 Fixed

Logical Device: 50000 Position: 1 Size (KB): 153281104 Free (KB): 25349008 Public Mounted
Label:Mirror Data protection disk
Unique Id: 0x4B3AC73650AA4164 Mount: /0 Index: 0 Order: 2
Partition: 10000 Physical: 10007 M 50000 Size (KB): 155406176 Starting Blk: 110420 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 156290560 Fixed
Partition: 10010 Physical: 10017 M 50000 Size (KB): 155406176 Starting Blk: 110420 Public
Physical: 10017 Drive Slot: 2 IDE Size (KB): 156290560 Fixed

Hey Thanks for the link... now I have a problem... when I upgraded my snap, everything appeared to be rosy... after about 20mins or so, it became inaccessible and now is totally useless to me... Teh system light blinks uncontrollably and the Link light is on.... I can no longer connect to the unit... I read in another forum on this sight that I have just ended up with expensive doorstops; however, I refuse to believe this... Does anyone have any ideas...

Upgraded from 3.x to 4.x.... on two different servers.... HELP...

debonairone

I wonder what are the differences between the snap 2000 and the 2200

good question; however, I am willing to sacrifice one of the servers for testing in order to resurrect the one that I really need... Is the image file named*.bin and how do I copy it back onto the disk...? Will it remove all existing data from the device...? I read somewhere about an application named dolly.exe that I may want to use to make an image of my existing drives if possible, just in case I can get this back up and running, I can extract what I need to it...

debonairOne@gmail.com

the bin were made with knoppix.

If you put the image on it will probably make you lose all the files as the snap will reinit the drive, and possibly format it.

Dolly might be able to make an image, but you will need a bit of drive space.

Thanks for the quick posting... I will try putting the image on one of my servers... If that works, then I will have the necessary space to use Dolly on the other server.... Will give it a go tonight when I get home and post tomorrow if possible...

Good luck with that then

I did pretty much the same thing with my Snap 2000... I upgraded to the os v4 and rebooted... shortly after that, my The System light flashes several times a second, the link light is solid and the Net light flashes occassionally... At this point, it appears as though the server is initializing, but this has been going on for a long time... Just performed the upgrade on another server yesterday and *poof* wouldn't you know it... Destroyed another server... At least, that is what it looks like... Let me know if you come across anything to resurrect your server, and I will do likewise....

I'm assuming you tried the full reset (four times on the reset button in the back). If the system light is flashing more than three times a second (what it'd do when shutting down/rebooting) that means that the system is in panic mode. No joke...it says that in the system logs. Chances are an exception was raised somewhere and the system doesn't have a way to handle it. Since this is happening shortly after upgrading it sounds like the upgrade went wrong somewhere (bad checksum maybe). I'm not quite sure but being a 2000 and not a 2200 might make things a bit more difficult to repair. I'm relatively certain that the bulk of the OS is in one or more flash PROMS on the mobo. If they aren't soldiered on you might be able to reflash them. I haven't really gotten around to messing with a 2000 and OS v4 yet. My suggestion would be to do the hard reset first, then if the system finishes booting properly (system light flashes once/sec) quick try to get in with Assist and downgrade the OS. I have no idea how much help that is to anyone but I figured I'd throw in an idea just in case.
INT 20h

Yeah, I did the full reset to no avail.... I have been looking for a way to get out of Panic mode... not just for the server either... :drool: I will see if I can get into the os quickly as you suggested... I even gave the one server over 72 hours to complete the cycle (what else was I going to do)... I had forgotten that this is how I lost the first server some months ago... I'll keep looking and playing...

Thnxs...

Well, I restarted the server and something must have happened.. it now only flashes twice a second as opposed to the continuous rapid flashing... maybe I'll leave it alone until I get home in about 9 hours... still cannot connect via assist, cannot ping the server by name or number.... Will post more once I get home... :shrug:

S2S and java VM are avaliable from here:

http://www.snapappliance.com/page.cf...2SSync&Nav=NAS

Hey Hey... My one server is back online and operational... I guess OSv4 just took a long time to do what it was supposed to do... anyway, my only issue with this one is the cracked raid that I can't get around... I posted this info in another thread, but haven't found a solution that works for me yet... if anyone has resolved this and can post their process, I would appreciate it..

It was posted to use the following command.. config devices config individual ##### force - where ##### is the number of the cracked raid device... so mine looks like this... config devices config individual 50000 force - and it doesn't repair the raid...

Any thoughts..... and thanks to all registered geeks for their help on getting this server resurrrected in the first place...

Ok...this is a 2000 right? Is this a RAID 0 or RAID 1 setup? If it's a RAID 0, there is an idea you might try. I used this trick when I had a RAID 0 that was getting marginal on me. When I'd boot the server the system would say the array failed. Now the risk you run with this idea is that if something is terribly wrong you might loose data. Then in that case you might want to image your drives. No idea if that'll do any good in case something does go wrong but I'll leave that to you to decide. Then go into Disk Utilities and then Disk Startup Settings. Set the server to perform a disk check always (so it scans when the system is started up or rebooted) and then make sure that it is set to automatically fix errors. After that power the server down (don't just restart it) but shut it down. When the system starts up it will automatically start checking the disks. If you have secure HTTP enabled you probably won't be able to use the web interface. In that case I'd shut that down before shutting down the server so that you can use regular HTTP to monitor the disk check status.

When I had that problem it would run the disk check and the thing would pass. I did that for about a week. I finally got tired of waiting for the system to start up so I backed up everything (was too lazy to do it in the first place) and then reconfigured the drives to JBOD and back to RAID 0. Everything worked fine after that. I'm not sure why it happens. I know that the system had been configured as a RAID 0 for a couple of years by then and hadn't ever been reformatted.

Hope it works.
INT 20h

I managed to snag a broken Snap 2200 from work (a 146GiB model with both drives dead). I ended up purchasing the upgrade to SnapOS 4.0 since the free upgrade didn't do the job for me.

Since I was going the expensive way I decided to buy a couple 400GB drives. Works like a charm. I now have a 372GiB mirrored Snap 2200....

Now if I could just figure out the JVM...

Gern

What is the problem with the JVM? IE what do you want/need to do that you cannot do now? I can inform. If you need the java machine file, it is obtainable from a few different ftp sites.

Thats pretty good to get it running straight off 400GB, did you just stick them in? Please let us know

400GB and JVM woes
 

The JVM is working and I can get the HelloWorld SnapExtension to run from the administration interface. I'd like to start running my own java classes. (I figure that turning my old snap server into a web proxy using muffin would be a good start). What I can't seem to do is run anything from the debug screen using the "java" command. It looks like there a path problem. For example
"java com.snapserver.demo.HelloWorldServer" results in a class not found exception.

If, on another machine, I cd into Java$/Jeode/classes and use the same command (from the local command line) both the HelloWorldServer and the HelloWorldClient
work fine (running on a local JVM), so the classes are OK. I can't figure out how to give the Snap jvm a classpath argument with the "java" command so it can find the classes...

1. Since both the existing drives were dead, I used a PC and Knoppix to copy the first 64MB from the first drive from another Snap2200 (SnapOS 3.x) onto a 30GB drive.

2. I installed the 30GB drive into the Snap. Another 30GB drive went into slot 2.
(It's good to have extra drives around.)

3. I booted the Snap and used the debug interface to unmount all and format /reinit the drives. Then I configured the Snap as a mirror.

4. I then purchased an upgrade to SnapOS 4.x and installed it on the Snap. (I tried using the links posted to the 4.x upgrade, but they didn't work since they are really a 4.0.0 to 4.0.X upgrade).

5. I took out the 30GB drives and copied the first one entirely to the first 400GB drive (again using a PC running Knoppix.)

6. I installed both 400GB drives, and rebooted. The system immediately recognized the 2nd drive as a 400GB, but still thought the first drive was 30GB, so I had to unmount all and format /reinit and mirror once again.

7. It took a long time to fully mirror the 400GB drive, but things have worked fine ever since then.

Gern

Thanks. For the record, what 2200 h/w and bios do you use?

You will need to create an altered manifest file and there is also something to create a snap server class

Try dissasembling the provided java apps

From Rami:

Hope that helps

Thanks

Sam

Don't have the model number handy, but I know it's an early 2200 (the server number is 800607). We got it from Quantum before Snap went to Adaptec.

Plat Bytes 2.0.3 is H/w Version - Same as mine

The board im using at the mo is 802839. But a replacement i got last year is 800448... Strange that the newer is a lower number

Any ideas how you got the 3.4.758 bios? And also i dont think mines got a 'failsafe bios' Maybe it has, ill have to check. I managed to get another board a year or so ago (when we thought it had failed, we managed to buy a new one from them. but before we had the board replaced due to some fault in the boards (this was free) so now im running on the free replacement), and ive got the one we paid for to use if i have a problem.

Both are H/w 2.0.3 and the 3.3.705 bios.

I'm pretty sure the new BIOS was installed as part of the SnapOS 4.0 install.

Eric

Hmm, i know other people have experienced bios upgrades when going to v4.

Can i ask, which version of the OS did you purchase? And would you mind sharing it with us. I know there should be an upgrade to 4.0.830 floating about, as that is what i bought, so if you could allow us an updated version, that would be great.

I got 4.0.860. Normally, I wouldn't have a problem sharing it. However, I'm doing this hack for my employer, a non-profit who received 6 146GiB Snap 2200s as a donation from Quantum. More recently we've gotten a 4500 and an external cabinet from Snap/Adaptec again as a donation. You can see why my employer would have a problem if I jeopardized that relationship.

That is fair enough.

Would you be able to share it some point in the future?

Warning: 4.0.860 + SNAP 2000
 

I have a 2000 model (478xx) with the model changed to a 4 drive configuration. When I applied the 4.0.860 upgrade, my RAID 5 broke because the unit would only recognize 2 drives. I downgraded to 4.0.854 & got the same thing. When I went down to 4.0.830 my 4 drives were once again recognized & the RAID was OK.

Just a warning that something appears to be in the new bios upgrade that forces a 2 drive configuration on the 2000 even if you set it to a 4 drive model.

Anyone see this on the 1000 model where the 2 drive config is lost after upgrading?