Hack a Snap Sever 1000?

[re3dyb0y]

OzDave is doing some java creation instructions, and im trying to use them to create some java stuff..

[INT 20h]

What you should realize is that the SnapOS-based servers are considered "legacy" products - after all, these date all the way back to Meridian Data (that's 3 owners of the Snap product line ago). Even the 4100 is a 5-year-old+ design at this point.

They were never intended to be field-upgradable. They were targeted at companies who would install it and forget about it. The fact that end users have figured out ways to expand the units and make them do new tricks is a tribute to the flexibility of the original design.

Comparing a 5- (or more) year-old design to a current product isn't really a fair comparison. Likewise, comapring any Adaptec product to an intentionally-open product isn't fair either - they're competing in very different market spaces.

I haven't looked at any of the GuardianOS-based Snap units, so I can't say if they are better performers (though I'd expect they are, simply because they're newer designs). I did look at some of Adaptec's offerings before I built my own servers from scratch, but the minute I saw they required special Adaptec drives (available in a limited number of sizes and at very high prices) I stopped looking.

I've kinda wandered away from the SnapOS units for the time being. I have one of the old Guardian 4400s (still says Quantum on the front) and it does seem to out perform the SnapOS units. My Guardian is running four 120GB drives in a RAID 5 with GuardianOS 3.1 on a half gig of RAM. I have a 4100 (Dell PowerVault 705N) that's running OS 3.7.8xx and also four 120s in a RAID 5. A RAM upgrade would probably help performance a bit but from what I've seen so far, the Guardian 4400 out performs the 4100 by almost 50%. The newer design definitely helps. It also helps that it comes with a dual head gigabit Ethernet adapter. While it's not hooked up to a gigabit network the performance is still nice.

Then again it's not an apples-to-apples comparison. The 4400 runs off of a PIII 1GHz processor, 256-512MB PC100 SDRAM, and has dual gigabit Ethernet capabilities. The 4100 I think (not swearing to this) a PII 233MHz processor, 64-128MB RAM and 100Base-TX Ethernet adapter. There are at least two major shifts in technology between the two and the 4400 is a discontinued product! It's already been replaced by the 4200 and 4500 which have if memory serves a P4 1.4 GHz and 512-1GB of ?DDR? RAM. Again, there's another one or two shifts in technology.

You're also right in that making these older SnapOS units do neat tricks (field upgrades with new and more drives than the original spec) is pretty nice, you can only get them to do so much. Eventually (if it hasn't happened already) the servers on today's market will leave even the modified Snap servers in the dust just because of advances in technology.

I have a feeling (and I might be completely wrong so don't shoot me just yet) that these little departmental SnapOS servers are dying a slow death to faster, larger, cheaper, and possibly more open storage solutions. They're a great idea but are being out paced by technology.
INT 20h

[itsmeagain]

One request for newbies. Please do not email me regarding images, as as i have said, i have not got one.



Thats what i did, i will try removing the drive, reformatting it (not on the snap) and start fresh. I have tried reformatting it while its in with no luck. i will try running it after removal of files by itself in the snap server.

meister_sd i cant even get the image to be made, it takes 10 secs, and there is no image. Some detailed instructions would help please.

Thanks to dvscreen for all this info.. Could you do the same for the java one please?


www.icoffice.co.uk
for diskjocky details

We mean it, the Disk Jockey is versatile, useful, clever and unmatched in value. It's got 7 modes built-in which allow you to do just about anything for less.

Fast Disk to Disk Copies - Fast, block-level, hard disk to hard disk copies, no computer required. Copy hard disks without the use of extra software at speeds that will blow your mind! Imagine setting up your companies systems in less time than ever before!

[re3dyb0y]

Yeah fair enough.

But £200....

[re3dyb0y]

On knoppix 3.6 & 3.4, This will allow read/write access to a NTFS Hard drive. Click on the cog thing, go to knoppix, utilities, then captive ntfs. Follow it through to enable NTFS read write.

This will allow an image to be copied to the hard drive. How do i make an image of my snap server drive using knoppix?

Will this work:
'1. boot up your knoppix cd and login as root user.
2. type "dmesg|grep hd" to find out the drive numbers for your snap drive and windows drive, mine is hdb and hda5 respectively.
3. type "mount -t auto /dev/hda5 /mnt" and press return
4. type "dd if=/dev/hdb of=/mnt/snap.os bs=1024k count=40" and press return and in a few minutes you will get an image (snap.os) of 40meg in your windows drive (root directory). You can adjust the size by altering the count value.'

[itsmeagain]

i would love to down load these file but cant seam to log on

alan :cry:


Hello everyone.
Sorry I have not been on the forum for some time but I made a lot of progress that some might be interested in. Especially if you have a unit without a working drive to copy the operating system from.
Anyway I have successfully got my 2200 and 1000 up and running.
I have also been able to upgrade the drives on both.
I was also able to copy just the first 50,000 block (25MB) of each of the drives to a file that can be used to restore the operating system on a blank drive. (I tested it and it works)
I put the files on my FTP site let me know if it is working properly.
ftp://**********
user:****
pwd:****
There is a compressed file that contains both data files. It is snap1000-2200.zip
I will try to detail the method a little more later.
Here is a short summary.
1. Download the snap1000.bin file to a place you can get to using knoppix.
2. Download the knoppix cd.
3. install the drive you want the OS on. I installed it as the master on the Primary IDE port.
4. Insert the knoppix cd and boot from the CD.
5. Open a terminal window
6. Type "sudo su"
7. transfer the snap1000.bin file to the /tmp directory
8. Type "dd if=/tmp/snap1000.bin of=/dev/hda
This just takes a minute and it is done.
9. Now power down and remove the drive and install it in the snap as the only drive.
10. Power on the snap.
11. Let it initialize.
12. Now use assist or whatever method to get to the debug screen.
13. Type "config devices format 10000 /reinit
14. Reboot the server and it should reformat the drive to.
These files are of the 3.4.805 version of the OS so you won't get over 130MB.
However you should then be able to upgrade the OS and reinit the drives again to get the max size.

[Davesworld]

i would love to down load these file but cant seam to log on

alan :cry:

Actually, if you go to the Adaptec site and not Snap's site, you can download the latest version 4 without the support. It needs windows to unpack but it came with the latest os, java, and windows manager software. http://www.adaptec.com/worldwide/support/drivers_by_product.jsp?sess=no&language=English+US&cat=/Product/Snap_Server_4100

[meister_sd]

Well, I haven't been here for a while. But I can backup the tutorials offered here on making your own image. I've done it using the Knoppix CD 3.6 and it's quick. I've also just bought a Snap 1100. I took it apart last night, and it is the same MB as a 2200. A few exeptions are only one IDE and Power cable and this (1100) is a P166 vs the P233 in the 2200. I threw in a second HD, Power Splitter and regular IDE, and it booted and formatted the second drive. It did NOT, however allow me to RAID them. I suspect it's becase it is an 1100 and it "knows" it can't. I read earlier you can "tell" it that it is something else. I'm going to try this as soon as I upgrade the software to the 4.0.860 in the above post. I have a sneaking suspicion that the same OS used for all the models can use the same HD imaged with a generic OS install........

[meister_sd]

Just did another interesting thing. I took my 1100 and went into debug mode. From there I typed:

bios model

and came up with the following:

04/19/2005 10:57:07 Command: bios model

Model Byte currently is:
0 - 2 drive IDE: "Minnie"
==> 1 - 1 drive IDE: "Mortie"
2 - 4 drive IDE: "Laser"
3 - 12 drive IDE: "Clipper"

------------
Command executed without error.



So I went to my 2200 and came up with this:

Command: bios model
Snap 2200 answer:
04/19/2005 10:31:23 Command: bios model

Model Byte currently is:
==> 0 - 2 drive IDE: "Minnie"
1 - 1 drive IDE: "Mortie"
2 - 4 drive IDE: "Laser"
3 - 12 drive IDE: "Clipper"

------------
Command executed without error.



Now, reading a couple of pages back, someone said to try and change the model.
So I typed:
unlock bios
bios model 0 <-- Thats a zero
lock bios
reboot

From there I figured that it would "act" like a 2200. I put in another
HD and after the reboot it formatted the second hard drive. The main
drive is Master and the newly added HD is slave. So now, I figured with
the bios in Model 0, I would be able to see the configuration screen allowing
me to mirror the drives, but it wasn't there. So I went into the debug screen
again and typed: config devices config mirror. I rebooted and, HEY!! I have
a mirrored system, just like my 2200!!!

Just another mile stone!

[re3dyb0y]

Yes, i think that had been figured out before.

But that proves it for some people.

[2kcrewcab]

Well, I should have looked here a few months ago before I took the 30 GB hard drive out of my 1000 to use for something else. I just assumed (and we know what that does) that I would be able to put another HD in and it would reformat itself.

Anyway, now that I've found out the hard way that it doesn't work that way, does anyone have an image they could send me of the 1000 O/S?

I would greatly appreciate it!!!!

Thanks,
Mike W.

[meister_sd]

Check your PM.

[upstech]

Can anyone PM or Email me a link to SNAP OS 4 for the SNAP 1000 and 1100.

[upstech]

I am having problems upgrading a SNAP 1000 to a WD 120GB Drive. I have upgraded several SNAP 1100's with no problem but everytime I use dolly to copy the old drive to the new one and reinstall the new drive the SNAP Server doesn't see any hard drive installed. Any help with this will be appriciated!

[tobionekenobi]

I've recently gone thru an upgrade process on an old Snap 2000. Added 2x WD 200GB drives, of which i could only see 127GB. Upgraded to OSv4 and now i see 190GB, but when the snap tries to format the disk it fails:

File System : Format terminated unsuccessfully Disk 10000
Individual 4/22/2005 9:04:24 AM
W File System : mkfs failed!!! Error = 5 Disk 10000
Individual 4/22/2005 9:04:24 AM
W File System : _mkfs_WriteBlock - Undefined internal error Disk 10000
Individual 4/22/2005 9:04:24 AM
W File System : Cannot Write: Blk 266354816 Disk 10000
Individual 4/22/2005 9:04:24 AM
E Disk Driver : Cannot Write Device 80070000 Block 266354816 Disk FFFFFFFF 4/22/2005 9:04:24 AM

My last ditch effort is to upgrade the BIOS from 1.2.180 to something else. Anyone know where i can get that upgrade from ?

Thanks

[upstech]

What drives have everyone used to upgrade a SNAP 1000? SNAP 1100?
__________________________________________________ _______________
I have upgraded a SNAP 1000 using a Western Digital Caviar 80GB ATA100 Model#WD800BB. (currently having trouble getting this one to see a 120GB HDD)
__________________________________________________ _______________
I have also upgraded a SNAP 1100 using a Maxtor DiamondMax 16 120GB ATA133.

[kozel]

I have a model 1000, HW ver 3.1.1, bios 2.1.363, SW ver 4.0.830 with a WD 120gb WD1200BB cloned using dolly. I tried a WD200 gb and it worked but was limited to 137gb. I also tried a Maxtor 120gb/ata133 5400rpm and could not get it to work at all. I think the ata133 is a hard limititation for the model 1000. Your wd120 should be okay, have you run diags on the drive and checked jumper settings? (obvious questions, I know)

[tobionekenobi]

Anyone got a copy of this file to upgrade my snap2000 to BIOS v2.0.282 ?

thanks

[gernblanston]

Actually, if you go to the Adaptec site and not Snap's site, you can download the latest version 4 without the support. It needs windows to unpack but it came with the latest os, java, and windows manager software. http://www.adaptec.com/worldwide/support/drivers_by_product.jsp?sess=no&language=English+US&cat=/Product/Snap_Server_4100

Does this work if you've got a server running version 3.XX.XXX? Or do you have to pay for the upgrade?

I may try it anyway on a 2200 that has a bad drive.....

Gern

[re3dyb0y]

Very few, if any bios upgrades have been released.... So which file are you refering to? Shouldn't the question be - Has anyone got a bios upgrade file for the snap 2200??

http://www.adaptec.com/worldwide/support/drivers_by_product.jsp?sess=no&language=English+US&cat=/Product/Snap_Server_4100

Will work on snap 2000 i believe, its fine on my 2200

[rami]

the answer is probly no because the ide controller on it may not support it. but is it possible to use 8 drives on a 4100 ?

using such a change in the settings?

[cringer]

Greetings All,
I'm in dire straits and would appreciate help from the SNAP community.
I have a SNAP 4000 in a RAID 5 configuration with a FSCK Fatal Error = 15. I have (trust me) run all possible fixes to recover this RAID, but to no avail.
Adaptec tech support has been of no help (NOTE: This not a slam, they just can't fix the problem). Apparently Fatal 15 is a controller issue. Adaptec does not provide replacement motherboards. Further, they cannot or will not check their boneyard (which I'm sure exists in either Milpitas or Denver) for a replacement motherboard that I could beg, borrow, buy, or steal. Before I send these drives to a data recovery company, I'd like to know if anyone has a working motherboard that I can borrow. If the motherboard is truly the issue, I should be able to swap it out with mine, boot the SNAP, and download my files.

Clearly I would not expect to receive this assistance for free. Nor would I expect someone to lend me their motherboard without some insurance on the hardware. Suffice it to say, I am willing to negotiate a reasonable arrangement and work with a safe financial harbor (i.e. PayPal) to provide peace of mind for both parties.

My motherboard is running SNAP OS 4.0.855, Hardware 2.0.1, BIOS 2.0.252. It will be necessary to have an exact match.

Please PM me if you are willing to assist.

Many thanks,

chris

[2kcrewcab]

OK...another question.....

I used the Knoppix method to get the sbin1000.bin loaded on a 30 GB hard drive on my Snap 1000 just to make sure I knew what I was doing. After loading it, SnapAssist could find the server, and give me the option to login. Since I didn't know what the Administrator password was set to, I did a manual reset to clear the settings. SnapAssist then gave me the option to setup the server....which I did with success..... :D

So now, the goal was to upgrade the HD to a 120 that I just had laying around. It's a Maxtor ATA133 120 GB. I read a couple of posts out here where people are having trouble with those, but I'm not sure if I'm seeing the same problems or not....

Using the same Knoppix method that worked on the 30 GB drive, I was able to get the image installed onto the 120GB drive. I put it in the Snap Server and powered it up. It comes up and Snap Assist can see it. Just like before, since I don't know the Administrator password, I performed the same type of manual reset. Now when the server reboots, the system light blinks twice a second the Disk light stays on solid, and Snap Assist can no longer see the server.

Am I doing something wrong? :shrug:

Any help would be greatly appreciated!!!!!

Thanks,
Mike W.

[kozel]

Tha't pretty much the same behavior I saw when I tried it. On a 1000, stay with a <137gb ata100 drive. 7200 rpm is ok if it runs cool enough. Some drives that run ata133 may be configurable for ata100 via a utility, like the samsung drives. I did not see that with Maxtor. I'm using a wd1200BB drive.


OK...another question.....

I used the Knoppix method to get the sbin1000.bin loaded on a 30 GB hard drive on my Snap 1000 just to make sure I knew what I was doing. After loading it, SnapAssist could find the server, and give me the option to login. Since I didn't know what the Administrator password was set to, I did a manual reset to clear the settings. SnapAssist then gave me the option to setup the server....which I did with success..... :D

So now, the goal was to upgrade the HD to a 120 that I just had laying around. It's a Maxtor ATA133 120 GB. I read a couple of posts out here where people are having trouble with those, but I'm not sure if I'm seeing the same problems or not....

Using the same Knoppix method that worked on the 30 GB drive, I was able to get the image installed onto the 120GB drive. I put it in the Snap Server and powered it up. It comes up and Snap Assist can see it. Just like before, since I don't know the Administrator password, I performed the same type of manual reset. Now when the server reboots, the system light blinks twice a second the Disk light stays on solid, and Snap Assist can no longer see the server.

Am I doing something wrong? :shrug:

Any help would be greatly appreciated!!!!!

Thanks,
Mike W.

[HLouie]

Currently I have a Snap Server 1000, 2000, 4100.
Is there a software program for testing network traffic performance?

Has anyone other been able to update there BIOS on any model with any BIOS?

[re3dyb0y]

I have a Maxtor Diamond max 9? 80gb (133 i think) and they both work fine in it.

Errm, there are loads of free network software..... Let me think

[rami]

Currently I have a Snap Server 1000, 2000, 4100.
Is there a software program for testing network traffic performance?

Has anyone other been able to update there BIOS on any model with any BIOS?

1000, 1100, 2000, 2200, all are fairly slow

the 4000 and 4100 are MUCH faster, and upgrading the Ram on them to 256mb or more improves response when 20-30 users are accessing them at the same time.


other than file transfers and monitoring from the pc with network traffic monitors, there are no other tools to monitor these snapservers.

the newer , higher end units do allow this level of monitoring with snap manager software.

[re3dyb0y]

If you want transfer rate monitoring, that will be able to be done with some network software

[meister_sd]

Cringer,
I think I might be able to help. I have a couple of snap servers (1100, 2200 and soon a 2000) and if I throw one of your HDs in my system - it should boot. From there we can get the data back over the network. Email me at:

meister_sd [at] hotmail [dot] com

[meister_sd]

Now to the "biggest hard drive" question.

My 2200: 200 gig x2 Mirrored
My 1100: 250 gig

[kasandoro]

Inspired by earlier posts I just successfully upgraded the hdd on my Snap 1000.

FWIW, here's the details.

Model: 1000 series
Software: 3.4.803
Hardware: 3.1.1
BIOS: 2.1.363

Hard Disk: Quantum Fireball lct15
Capacity: 30GB nominal

New Disk: Hitachi 7K250 120GB UDMA100 7200 rpm 8MB cache

Here's the steps I used.

1. Backed up all the data from the Snap.

2. Connected to http://<snap1000>/config and formatted the disk.

3. Connected Quantum disk as Primary Master and Hitachi disk as Primary Slave. Used an 80 wire IDE cable connected to built in UDMA100 controller on Abit VP6 motherboard.

4. Booted Knoppix 3.7 from DVD-ROM drive.

5. From a terminal window

$ dmesg | grep hd

reports...
hda: QUANTUM etc.
hdb: HDS722512VLAT80 (HITACHI)

$ su
# dd if=/dev/hda of=/dev/hdb bs=1M

reports
28629+1 records in
28629+1 records out
30,020,272,128 bytes transferred in 2161 seconds (36 minutes)

Why the 1M block size for the dd command?
Earlier posts reported success with this!

Why dd the whole of the disk?
To reproduce all the file system metadata on the new disk.

6. Rejumpered the Hitachi as Master and fitted to Snap.

7. Booted Snap, checked a ping to its IP, and connect to http://<snap1000>/config.

Disk Utilities, View Disk Status showed disk capacity as about 29MB.

8. Connect to http://<snap1000>/config/debug and do

'config devices format 1000 /reinit'

then

'reboot'.

9. On the reboot the new disk formats and is then ready for use.

View Disk Status now shows 115,424 MB free.

10. Kept the old Quantum drive as a backup in case the OS is needed again. I also made a copy of the drive to an old Maxtor 5T040H4 just in case.


Nothing here that hasn't been on this forum before, except that the upgrade works with the Hitachi Deskstar 7K250 120GB drive. The Snap is now a lot faster and quieter, although the speed of data transfers is limited by the network interface. The best I've seen is 2MB/sec.

Thanks to all on this forum who made this upgrade possible.

zcx


This method worked PERFECTLY for me! I'm using a WD 80GB, ATA-133 drive now in a Snap 1100. Bravo! Finally, after a couple of years of tinkering, it works!

[re3dyb0y]

How do i decompile the .sup files like people did before to find out the contents of them?


Thanks

Sam

[stav99]

Is it my imagination, or has www.snapappliance.com redone their site and no longer has a path to that latest 'free' Snap OS upgrade: ver.3.4.803? I thought the site used to work differently, and I'm looking for that file there but can't seem to land it. Am I out to lunch - or have they reorganized their site offerings since joining Adaptec? If that is the case, does anyone have that ver.3.4.803 download and update instructions? Thank you.

stav99

[kasandoro]

Is it my imagination, or has www.snapappliance.com redone their site and no longer has a path to that latest 'free' Snap OS upgrade: ver.3.4.308? I thought the site used to work differently, and I'm looking for that file there but can't seem to land it. Am I out to lunch - or have they reorganized their site offerings since joining Adaptec? If that is the case, does anyone have that ver.3.4.308 download and update instructions? Thank you.

stav99


I'd just like to download the 4.0 version...the one I got from Adaptec wont' install on my server..says it's the wrong version or something like that.

[Terry Kennedy]

I'd just like to download the 4.0 version...the one I got from Adaptec wont' install on my server..says it's the wrong version or something like that.The 4.0.860 you can download from Adaptec will only upgrade an existing 4.0 server - it doesn't have the 3-to-4 upgrade passkey in it. 4.0.830 does have the passkey - I'm not sure about other 4.0 versions.

[stav99]

I'd just like to download the 4.0 version...the one I got from Adaptec wont' install on my server..says it's the wrong version or something like that.

#1) Kasandoro, what version of OS do you have currently? if you downloaded the Adaptec offering of 'SnapOS 4.0.860 Upgrade', that patch was expecting you to have an earlier version of 4.x loaded already. In an earlier post, I think I see you reporting the following diagnostics - "Software: 3.4.803". This might be a reason for the 4.0.860 failure.

#2) Actually, I transposed the numbers on the version I'm looking for. The last 'free' 3.x version was "3.4.803" and I'm wondering if anyone has it and can post it to the Snappers FTP site: ftp://********/ ? I'm late to the HDD upgrade game by a couple of years, but am working on getting my Snap 1000 15GB Quantum replaced by a 80GB drive I just bought. I'm still at ver.3.4.790 and just want to optimize the process.

#3) Not long ago in this thread (April 19 2005), DavesWorld mentioned that Adaptec was allowing a download of the "latest version 4 without the support". Would that download allow an upgrade from ver.3.4.x to ver.4.x? Does anybody still have that download if it allowed 3x to 4x? If it did allow upgrades from 3.x to 4.x that would also be a great posting the the FTP site - as I'm not so sure it is still hanging around Adaptec.

#4) There are posts suggesting to use the FTP site's snap1000.bin file to overlay your HDD using the dd command. The .bin file apparently has version 3.4.805 of the OS. Is this really the most direct way I should go about my HDD & OS upgrade? Kind of like getting both things I want in one procedure. And it is ..805 which is a patch or two above ..803!

- Any thoughts appreciated. Thank you.

[meister_sd]

Does anyone actually have the bios update program for the 2000 or other models? My 2000 is 1.2.180 but I've seen another at 2.0.252. How can I get it? Snaps old download links don't work anymore and Adaptec doesn't supply it.

[tricklebowski]

Hi folks, finally i found your discussion on Snap Servers. I've been working for weeks to install new harddrives to our Snap 2200. If I had found this discussion earlier, it would have saved much time. So I had to figure it out the hard way. I cloned the disks with dd_rescue under Knoppix and it seems to work, except the server does not recognize the real size of the new harddisks, but I hope i can see to that soon. By the way, the new drives are Maxtors with 200 GB. I hope they work with full space.
Earlier in this discussion someone asked for pictures of the motherboard of the Snap 2200. Is there still a need for that? I can post a picture within the next week, as soon as i can lay my hands on the server.
Finally I've got a question regarding to the reinit command. How do I figure out, what Logical Device I need to reinit? My server contains 2 harddisks, but i don't have a "config devices info" output at the moment.

[meister_sd]

To fix the drive space problem, you have to reinitalize the disk from debug:

http://{servername}/config/debug
type: config devices info

Then you will see your hard drive, and probably 10000 but maybe 10010.

type: config devices format 10000 /reinit

It will tell you at next reboot it will be done. Then reboot the server and it will be done.
Remember, it is going to format the disk too, so dont' have any info on it.

[ISPDr]

G'Day Guys,

Moved everything over to commercial hosting so have some spare snap bits for sale (guessing this will be most useful for Australia readers etc - Im based in Sydney NSW).

1 x SNAP 4100 - v4.083 / Java / ServerSync (reg) w/ 4x WD 60gb Hds, 256Mb Ram, all SW
1 x SNAP 4100 - v4.083 / Java / ServerSync (reg) w/ 4x WD 40gb Hds, 256Mb Ram, all SW
1 x SNAP 4100 for parts: Board Good, Case / Rails Good, No HD Brackets, PS Needs Fuse

If anyone is interested, then please contact me directly and we'll see what we can do!

Matt: matt@ispdr.net.au - 0416241624

[tricklebowski]

So, now i'm about to fix the size problem. I typed the command in the debug line as you told me, and it seemed to work, but i can't access the server now. The system light is flashing rapidly and i don't hear anything going on my harddisk. How long does it take for a server to come up after an "reinit"? I installed two 200GB disks and "reinited" one. It already takes half an hour and i am unsure if to wait longer.

[meister_sd]

The server should come up in under 5 minutes. If unplugging the server and rebooting it doesn't work, try doing a factory reset - the big one where the reset is pushed 4 times. If all else still fails, put the old hard drives back in and let it boot to see if it will come back up.

[ron310]

To fix the drive space problem, you have to reinitalize the disk from debug:

http://{servername}/config/debug
type: config devices info

Then you will see your hard drive, and probably 10000 but maybe 10010.

type: config devices format 10000 /reinit

It will tell you at next reboot it will be done. Then reboot the server and it will be done.
Remember, it is going to format the disk too, so dont' have any info on it.


This is what I see:

05/11/2004 7:26:17 Command: config devices info

Logical Device: 10000 Position: 1 JBOD Size (KB): 131650600 Free (KB): 131518896 Public Mounted
Label: Drive1 Disk 1
Unique Id: 0x21D1275B6E73CD4E Mount: /0 Index: 1 Order: 1
Partition: 10000 Physical: 10007 FS Size (KB): 133475800 Starting Blk: 92549 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 134217216 Fixed

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

Logical Device: 10008 Position: 2 JBOD Size (KB): 131650600 Free (KB): 131518896 Public Mounted
Label: Drive2 Single disk
Unique Id: 0x09D78DB62698ACC6 Mount: /1 Index: 2 Order: 2
Partition: 10008 Physical: 1000F FS Size (KB): 133475800 Starting Blk: 92549 Public
Physical: 1000F Drive Slot: 1 IDE Size (KB): 134217216 Fixed


------------
Command executed without error.

If I reinitialize disk 10000 and 10008 (assuming those are the ones I should do),
It reboots but still shows only 128GB on each disk (they are 250GB each)

Here are the rest of my specs:

Model Software Hardware Serial# BIOS
2000 series 3.1.608 (US) 1.1.0 20589 1.2.180

Any suggestions?

[meister_sd]

ron310,

Your problem is the Snap 2000. With Hardware Version 1.1.0, it will only go upto 120 Gig. One with version 2.0.0 will go upto 160 Gig. You could get a snap 2200, which will hold upto 250 gig drives each, total of 500 Gig. A Snap 1100 will go over 300 Gig, I've heard 400!

[Terry Kennedy]

Your problem is the Snap 2000. With Hardware Version 1.1.0, it will only go upto 120 Gig. One with version 2.0.0 will go upto 160 Gig. You could get a snap 2200, which will hold upto 250 gig drives each, total of 500 Gig. A Snap 1100 will go over 300 Gig, I've heard 400!Are you sure that's it? 48-bit addressing didn't make it into SnapOS until 3.4.805, and the poster is running 3.1.608, so he'd never get over 128GB anyway.

[ron310]

so there is no possible way I can get this thing to see over 120 - 160 Gigs per drive?? :mad:

Theres no upgrading, flashing, anything right?

I just want to make sure before i buy (2) 120 gig drives, throw them in and ebay it.....

[Davesworld]

Are you sure that's it? 48-bit addressing didn't make it into SnapOS until 3.4.805, and the poster is running 3.1.608, so he'd never get over 128GB anyway.

Actually, the limit is around 137GB which is really what a 140GB drive would yield if anyone made 140GB drives. Without lba 48, a 160GB would show up as 137 so you would have 20GB wasted. Yes, you are correct, his version of SnapOS would never go over the 137GB (approximately) limit. Without upgrading to version 3.4.805 first or preferably and more attainable, version 4.x, any efforts would be a complete waste of time.

[Davesworld]

The 4.0.860 you can download from Adaptec will only upgrade an existing 4.0 server - it doesn't have the 3-to-4 upgrade passkey in it. 4.0.830 does have the passkey - I'm not sure about other 4.0 versions.

I hadn't considered this since I was already running 4.x. I did find the last 4.x released in December that I believe is complete with the passkey so I snagged it.

[ron310]

So I'm not limited by the hardware, but rather the OS?

If I purchase version 4 of the software, could I drop [2] 250 gig drives in there?

I'm really confused now :shrug:

[meister_sd]

I have a few Snaps now and have seen minor variations based on hardware version. I have a Snap 2000 with a hardware version of 1.1.0 and the Snap will "see" over 200 Gig, but can't format it or handle a formatted drive. It will "see" over 200 gig, but won't format it - it will error out. I know someone with a 2000 and hardware version 2..0.0 that took the pre-formatted 160 I had and could see it and use it. Mine with hardware version 1.1.0 won't. The bios will upgrade to a version based on your hardware version and the base numbers are equal. Example, my hardware version is 1.1.0 and my bios is 1.2.180. My friends hardware is 2.0.0 and the bios is 2.0.252. It all goes hand-in-hand. When you do an OS upgrade, your bios will get upgraded to the maximum of the hardware version (at least from what I have personally experianced).

Also, you don't have to purchase v4. It's free from adaptec. The OS update is the same for the 1000, 1100, 2000, 2200 and 4100. I can say this because I own all of those and used the same .sup file to upgrade them all. You may be able to upgrade the 4200 and higher, but I don't know. Here is a link to adaptec, and remember, the OS is the same for all of them.

http://www.adaptec.com/worldwide/support/suppbyproduct.jsp?sess=no&language=English+US&cat=%2FTechnology%2FExternal+Storage&fromPage=supportindex

I don't see this as a violation for linking, because it comes from the vendor.

I've also seen that the 4100 can "see" very large drives, but will only format to 130 gig. I put a 200 gig into mine and it saw it all, but after the format, it was only 130... :-(

So, from what I see, the real limit is a combination of hardware version and biod.. When Snap/Adaptec wants to put out a version that has larger drives, it is done at their bidding. The two exeptions I've seen are the 1100 and 4000. They can use very large drives.

The version 4 that has the total upgrade, that I've seen, is v4.0.830. I believe there is one other under 830.

[re3dyb0y]

If it aint on the adaptec site try here:
***** Down *****

Think it is there also!

[cringer]

Greetings All,
Anyone have a non-functioning SNAP4000 motherboard I can have or buy? I don't need the chassis, drives, or sleds. Just the motherboard.

Many thanks.
chris

[re3dyb0y]

Anyone know how to decompile .sup files?

[tjwillia007]

Does anyone have 3.4.803?

I have searched high and low without success. I have 4.0, though specifically need to get a 4100 from 2.x to 3.4.803 (I can't recell from my last time whether it is two separate steps - first to 3.2 then from 3.2 to 3.4.803?). I moved drives from a 4000 with hardware failures which was running 3.4.803 to this 4100 and it won't see the drives. So I was going to disconnect the drives, upgrade the appliance, then reattach the drives in order to get my data back as my last good backup was 2 weeks ago.

[re3dyb0y]

dvscreen

Has anyone noticed that the .sup files provided by Snap are text files of some kind of Intel Hex dump (starting with colon ?

Can they be used to rebuilt an image without assist?

I have a Snap 1000 that is drive-less and I would like to use it some day and I can't find an image for it.


Ok, got a bit further.

The .SUP file (support files) are some kind of uncompressed archives. Assist uses them to upload to the Snap Server. I have looked at .SUP files for SnapOS V3 and V4.

The files contains 3 areas:

1. Hex dump of binary files .HEX
2. Resource files .RES
3. HTML files (.HTML, .CSS, and .GIF)

The hex section contains one binary file for each model of Snap Server:
MOAI110.HEX
MOAI200.HEX
MOAI300.HEX
MOAI20X.HEX
MOAI400.HEX

Those are Intel HEX records and the clue is that they begin with a colon. There are four types of records, but only 3 are used here. Here's how each row is decoded:

:nnaaaattdddddddddddddddddddddddddddddd ... cc

Where:
- nn is the record-length field that represents the number of data bytes (dd) in the record.

- aaaa is the address field that represents the starting address for subsequent data in the record.

- tt is the field that represents the HEX record type, which may be one of the following:
00 - data record
01 - end-of-file record
02 - extended segment address record
04 - extended linear address record

- dd is a data field that represents one byte of data. A record may have multiple data bytes. The number of data bytes in the record must match the number specified by the ll field.

- cc is the checksum field that represents the checksum of the record. The checksum is calculated by summing the values of all hexadecimal digit pairs in the record modulo 256 and taking the two's complement.

Example: in the SnapOS v3 file, the first two lines are:

:02 0000 04 0004 F6
:nn aaaa tt dddd cc

0x02 + 0x00 + 0x00 + 0x04 + 0x00 + 0x04 = 0x0A
0x100 - 0x0A = F6 (ok)

:20 0000 00 2600B0C1870070912D00FF0770892D001800FFFFFFFF300010 00236B10006092 84
:nn aaaa tt dddddddddddddddddddddddddddddddddddddddddddddddddd dddddddddddddd cc

0x20 + 0x00 + 0x00 + 0x00 + 0x26 + 0x00 + 0xB0 + 0xC1 + 0x87 + 0x00 + 0x70 + 0x91 + 0x2D + 0x00 + 0xFF + 0x07 + 0x70 + 0x89 + 0x2D + 0x00 + 0x18 + 0x00 + 0xFF + 0xFF + 0xFF + 0xFF + 0x30 + 0x00 + 0x10 + 0x00 + 0x23 + 0x6B + 0x10 + 0x00 + 0x60 + 0x92 = 0xB7C

0x100 - 0x7C = 0x84 (ok)

Note: you can cut and paste the equation (before the =) in Google if you don't have a Hex calculator.

The records used are:
- 1 Type 04 record (address).
- 2048 Type 00 records (data).
(this sequence of two is repeated repeated 25 to 30 times)
- 1 Type 01 record (EOF) with data.

This file is quite small, around 1.7 MB once converted to binary.

I can not read any ASCII text after converting the dump to a binary. However, I don't believe these are from compressed files because they are padded with hundreds zeroes. The last character, after the zeroes, is 0xEB.

Then the resource files are:
UK\Snap_00_UK.Res
Fr\Snap_00_Fr.Res
Ge\Snap_00_Ge.Res
Sp\Snap_00_Sp.Res

There is no US file, so the resource must be contained in the .RES files. I can read ASCII text in these files, but some binary data is also present. It must be possible to compare the .RES to the .HEX to find if any binary shit has been used to hide the OS in the .HEX file.

Finally, the html files follow:
US\AccessGuideFolderSend.html
US\AccessGuideDriveSend.html
US\AccessGuideMenu.html
etc.

Some .GIFs are present and a single .CSS file.

Conclusions:
1. Most of the OS must be in the .HEX files and that's where we need to investigate.
2. The .CSS could be easily modified and uploaded to customize the look of the server.
3. Same is true with the .HTML files to change the layout and the functions.
4. There must be a reason why the .HEX files are not in plain binary. Possible clues are: the need to hide the OS, the need to upload the data to the Snap Server in a special way.
5. My findings supports other poster's observations that one .SUP file contains all server models and all supported languages.

Requests:
1. I would need an ISO file from a Snap 1000 or 1100 to go any further. Mine is toasted, and that is why I am doing this work. I would love to run the SnapOS on a regular PC.
2. Has anyone found information about hardware? I know it revolves around an embedded x86 compatible "PC on a chip" and that has a built-in video card. It would be great to put Linux on it and to attach monitor.


scottz

Nice to see someone is thinking along the same line.
I went through the same manuvers last month but had to give up on it due to time.

What I found:

It looks like after the .SUP file is uploaded it is broken out by the SnapOS upgrade process.

If you look at the end of the .sup file you will find html code for minimal help screens. So there are sections to the .sup file that the upgrade process knows how to break out.

From what I found, the .HEX file seems to be either:

1) a Patch (not a full image) for the current BIOS/OS and isn't in a contigious format.

2) a compressed image.

3) Combination of both.

With the padded 0's being there, it could be a section that isn't being used, OR what I'm guessing is that these are sections that is used for saving settings when you switch off the power (i.e. you need some room in flash to store IP address, disk shares, passwords, etc) so you don't want to put code there. They could be ignored by the upgrade utility, but are there for continuity.

I started going through some of the PC BIOS and Flash utils/hacks to see if there is any related format that has a similar process and can give us a clue as to how this one maybe setup. I did find a case where a flash was upgraded with a .HEX file where the data was compressed and then decompressed on the fly during the upgrade process, so one theory is there.

The E28F016S5 Intel Chip is a 16Mbit (2MB) Flash Memory though, so I'm leaning towards it being a compressed image that decompresses on boot. Gives more room for the modified BSD OS to to fit in memory rather than disk.

Again, on the 4100 the majority of the OS lives on the Flash rather than disk.
You can boot up a 4100 with no disks installed and it will function.
Java and help/language files live on the disks, but it doesn't need them to operate.

If I could get my hands on a boot partition from a system that has it's OS on the drives, then I could do some comparisons to how the 4100 is broken out and how to modify it.

Scott

I found these posts about decompiling sups, anyone know how they did it?

I believe 3.4.830 also works for upgrading from v2. Look on the snap ftp site above

[stav99]

Please check the ftp site. There is copy of the files for 3.4.803 upgrade there now. Let me know if there are any problems opening the zip. Hope it works for you.

PS: see the SnapServerUpgrd_Notes3.4.803 file as well for some advice from an old SnapAppliance page talking about 2.x upgrades.

Does anyone have 3.4.803?

I have searched high and low without success. I have 4.0, though specifically need to get a 4100 from 2.x to 3.4.803 (I can't recell from my last time whether it is two separate steps - first to 3.2 then from 3.2 to 3.4.803?). I moved drives from a 4000 with hardware failures which was running 3.4.803 to this 4100 and it won't see the drives. So I was going to disconnect the drives, upgrade the appliance, then reattach the drives in order to get my data back as my last good backup was 2 weeks ago.

[upstech]

I have upgraded several SNAP 1000's from 2x to 3.4.803 without any problems. 3.4.803 is also available from SnapAppliance.

[re3dyb0y]

Where abouts a link would be useful.....

Thanks

Sam

[bumpyone]

I am looking for an bios updates for the Snap 2000. I have a Hardware version of 2.0.0 and my bios is 2.0.282.

I am running 4.0.860 (US) version of the Snap OS, with 2 160 MB WD drives. I have searched through the posts but have not found anything.

Thanks.

[re3dyb0y]

I am looking for an bios updates for the Snap 2000. I have a Hardware version of 2.0.0 and my bios is 2.0.282.

I am running 4.0.860 (US) version of the Snap OS, with 2 160 MB WD drives. I have searched through the posts but have not found anything.

Thanks.


All that people seem to have worked out is that some os's seem to include a bios update, so you may have a new version.

There aren't really any files (apart from the really old os v2/early 3) that are specifically for bios updates.

What do you need the bios upgrade for? How much of the hd space on the 2000 do you get?

Thanks

Sam

[bumpyone]

I was just curious if there was a new version. No specific reason. I get 149,688 MB. I have the system set as a mirror. I am going to try and upgrade the ram to 128, 256 or 512, if it will work.

Ray

[re3dyb0y]

If you divide 149,688 MB by 1024 that is 146GB. Which seems a little on the small size. Max you could get is another 10gb possibly on each.

You can only upgrade the ram if it has removable ram, which i think are only the 4000 series. My 2200 has it built onto the board. I think most of the others do

[re3dyb0y]

Anyone changed the fan on one of them yet? What did you do about the special 2 pin connector thing??

[2kcrewcab]

OK...another question.....

I used the Knoppix method to get the sbin1000.bin loaded on a 30 GB hard drive on my Snap 1000 just to make sure I knew what I was doing. After loading it, SnapAssist could find the server, and give me the option to login. Since I didn't know what the Administrator password was set to, I did a manual reset to clear the settings. SnapAssist then gave me the option to setup the server....which I did with success..... :D

So now, the goal was to upgrade the HD to a 120 that I just had laying around. It's a Maxtor ATA133 120 GB. I read a couple of posts out here where people are having trouble with those, but I'm not sure if I'm seeing the same problems or not....

Using the same Knoppix method that worked on the 30 GB drive, I was able to get the image installed onto the 120GB drive. I put it in the Snap Server and powered it up. It comes up and Snap Assist can see it. Just like before, since I don't know the Administrator password, I performed the same type of manual reset. Now when the server reboots, the system light blinks twice a second the Disk light stays on solid, and Snap Assist can no longer see the server.

Am I doing something wrong? :shrug:

Any help would be greatly appreciated!!!!!

Thanks,
Mike W.

I'm finally getting around to playing with this again. Can anyone else confirm that the problem I'm seeing is because of the type of HD I'm trying to use?

Thanks,
Mike W.

[stav99]

Mike,
You mentioned you are trying to copy the bin files. Have you tried using the Knoppix method of copying your 'good' 30GB drive SnapOS over on top the 120GB Maxtor? I realize it may take some time, but maybe something went wrong the one time you tried the Maxtor. Maybe even trying the bin copy again in the same way you got the 30GB to work, just in case something got corrupted the first time. I recently did a Western Digital 80GB (Best Buy special!) successfully and I had seen a post saying someone had trouble with WD drives. I used the Knoppix copy of hda to hdb that is detailed one or more times in earlier posts. (I intend to summarize my steps and post them but haven't done so yet). Anyways, maybe someone can talk to Maxtor issues specifically.


I'm finally getting around to playing with this again. Can anyone else confirm that the problem I'm seeing is because of the type of HD I'm trying to use?

Thanks,
Mike W.

[re3dyb0y]

Right, another breakthrough by me.

Download it here DOWN

Only 2 problems, when you click close it shows errors, dunno how to get round this, other than you can get out by clicking home in the top right corner. The other is there is no help file.

Will look into these

[re3dyb0y]

Also, another FTP site for you snappers

DOWN

You will have to input the username and password manaully, because there is something that stops it working in the user:pass format

Please could someone upload all the snap server files to there?

[re3dyb0y]

user : pass format

[re3dyb0y]

Or for uploading you can use this:
*************

file list viewable here:
**************

NOT ALLOWED

[stav99]

Sam,
I can work on some of the transferring this weekend. Do we know the owner of this site? I guess, what I'm getting at, do we know if this site will be around for awhile and have some assurance we can use it?

- Thanks,
- Mark

Also, another FTP site for you snappers

***** DOWN ******

You will have to input the username and password manaully, because there is something that stops it working in the user:pass format

Please could someone upload all the snap server files to there?

[re3dyb0y]

Its my site so feel free, ive got around a 9 month lease left on it, and after that i shall be renewing it.

Theres 30gb of space and around 100gb of bandwith a month. So knock yourselves out

[re3dyb0y]

The zip has been updated to include instructions and the help file.

Thanks

Sam

[edcetera]

Hello, how is this possible this guy has a 2000 with 500 gigs for sale

has screen shots that show its a
2000
3.4xxxx software
2.0.0 Hardware
48xxxx serial number
2.0.282 bios

see it

http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=5778927788&ssPageName=ADME:B:SS:US:1

This guy is not forthcoming with info, perhaps one of you can explain this.

/ Ed

[DebonairOne]

Again if anyone wants snap os v4 (bought for 2200) ive been told it works on 2000,2200,1000,1100, i can email the file or give the link to the download site.


I am definitely looking for the link to download os v4... please email to jerome.j11@comcast.net...

Thnks...

[re3dyb0y]

Didn't someone else before manage to get the 1000 or the 2000 over 120gb drives?

Im not sure about 250gb drives tho.

He is selling a lot of similiar upgraded items.

He could be lying, but he would get a bad reputation, or he may work at snap and therefore know some tricks to the trade

[bumpyone]

If you divide 149,688 MB by 1024 that is 146GB. Which seems a little on the small size. Max you could get is another 10gb possibly on each.

You can only upgrade the ram if it has removable ram, which i think are only the 4000 series. My 2200 has it built onto the board. I think most of the others do

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

[DebonairOne]

I am definitely looking for the link to download os v4... please email to jerome.j11@comcast.net...

Thnks...


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 (debonairone@gmail.com)

[re3dyb0y]

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

[DebonairOne]

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

[re3dyb0y]

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.

[DebonairOne]

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...

[re3dyb0y]

Good luck with that then

[DebonairOne]

OK...another question.....

I used the Knoppix method to get the sbin1000.bin loaded on a 30 GB hard drive on my Snap 1000 just to make sure I knew what I was doing. After loading it, SnapAssist could find the server, and give me the option to login. Since I didn't know what the Administrator password was set to, I did a manual reset to clear the settings. SnapAssist then gave me the option to setup the server....which I did with success..... :D

So now, the goal was to upgrade the HD to a 120 that I just had laying around. It's a Maxtor ATA133 120 GB. I read a couple of posts out here where people are having trouble with those, but I'm not sure if I'm seeing the same problems or not....

Using the same Knoppix method that worked on the 30 GB drive, I was able to get the image installed onto the 120GB drive. I put it in the Snap Server and powered it up. It comes up and Snap Assist can see it. Just like before, since I don't know the Administrator password, I performed the same type of manual reset. Now when the server reboots, the system light blinks twice a second the Disk light stays on solid, and Snap Assist can no longer see the server.

Am I doing something wrong? :shrug:

Any help would be greatly appreciated!!!!!

Thanks,
Mike W.

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....

[INT 20h]

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

[DebonairOne]

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...

[DebonairOne]

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:

[re3dyb0y]

S2S and java VM are avaliable from here:

http://www.snapappliance.com/page.cfm?name=NASS2SSync&Nav=NAS

[DebonairOne]

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:


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...

[INT 20h]

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

[gernblanston]

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

[re3dyb0y]

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

[gernblanston]

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.


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...


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


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

[re3dyb0y]

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:

Anyway I worked out how java apps work on the snap server by examining the example provided. BTW java apps running on the snap server are commonly known as snaplets - I didn't make this up.
After you have installed java onto your snap server, check out the share called os_private. It is usually hidden and has restricted access rights. You can of course change those in the snap server access pages, I am sure you know how it works.
Snaplets are stored in the path:
\os_private\Java\Jeode\snapserver\snaplets\jars

There should be a Hello.jar located there. That is the example app I was talking about above. The source code to Hello.jar is located here:
\os_private\Java\Jeode\classes
(ignore the files in the 'demo' directory, the files that went into Hello.jar are in the 'hello' subdirectory, ie
\os_private\Java\Jeode\classes\com\snapserver\demo \hello)

Snaplets are made up of two components, a UI and a server. The server runs on the snap, and the UI component is the piece that you see in the SnapExtentions link on the configuration page.
The UI is simply a standard Applet. It uses RMI to communicate to the server component. You can check the file (HelloUI.class) to see how that is done.
The Server side is the more interesting piece.
The server class must implement the 'Snaplet' interface. This class is defined in the jar file:
\os_private\Java\snapex.jar
Copy the jar file and add it to your development area class path, or if you are using Eclipse as your environment, then just add it as an external jar.
The interface defines 2 methods (stop() and isRunning()) of it's own, plus as it also implements Runnable, you must also implement the run() method.
For my apps, I read a config file in the constructor for the main class. When run() gets called, I start the app, and set a flag that I am running. Then when stop() is called, I stop my app, and clear the flag. When isRunning() is called, I just return the flag status.
Remember that the server side can not have any UI, and to debug, you can write information to System.out.xxxx methods. The output will appear in the snap server log file.

Putting it all together into a jar file. If you check the manifest file in the Hello.jar, you will see that there are some extra pieces, ie:

Name: SnapletConfig
Snaplet-AppletClassName: com.snapserver.demo.hello.HelloUI
Snaplet-Description: Hello World of SnapExtension
Snaplet-MainClass: com.snapserver.demo.hello.HelloService
Snaplet-License: N

*Name is self explanitory.
*Snaplet-AppletClassName is the class name of the UI component of the snaplet.
*Snaplet-Description is the description text that you see in the SnapExtentions web page, mentioned above.
*Snaplet-MainClass is the class that implements the server component of the snaplet, ie implements the Snaplet interface.
*Snaplet-License is self explanitory.
There is also one other I have found,
Snaplet-IconFile: file.gif
This is the image that is placed next to the title and description on the SnapExtentions page.

Also, in the jar file you will see a .ser file. This is some sort of serial number. To generate this file, you need to execute the java class:
com.snapserver.ext.SnapletIDWriter
This class exists within the snapex.jar file.
Run the class, provide the name of your server class, and bang, it generates a .ser file.

Hope that helps

Thanks

Sam

[gernblanston]

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


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.


06/15/2005 11:22:03 Command: bios version


Failsafe Bios Exists
Failsafe v3.3.703.FS Thu Aug 30 12:59:39 2001

Bios stamp 3.4.758 Wed Dec 12 14:12:18 2001

Plat Bytes 2.0.3

Model Byte 0

06/15/2005 11:30:10 Command: config devices info

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

Logical Device: 10016 Position: 0 JBOD Size (KB): 32296 Free (KB): 30976 Private Mounted
Label:Private Contains system files only
Unique Id: 0x7F2CFA484ED8C0C8 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): 390711296 Fixed

Logical Device: 50000 Position: 1 Size (KB): 383340320 Free (KB): 275076704 Public Mounted
Label:Mirror Single disk
Unique Id: 0x109900332ED30089 Mount: /0 Index: 0 Order: 2
Partition: 10000 Physical: 10007 M 50000 Size (KB): 388654808 Starting Blk: 256933 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 390711296 Fixed
Partition: 10010 Physical: 10017 M 50000 Size (KB): 388654808 Starting Blk: 256933 Public
Physical: 10017 Drive Slot: 2 IDE Size (KB): 390711296 Fixed

[re3dyb0y]

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.

[gernblanston]

Any ideas how you got the 3.4.758 bios?



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

Eric

[re3dyb0y]

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.

[gernblanston]

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.

[re3dyb0y]

That is fair enough.

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

[relkin]

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?

[re3dyb0y]

Well, when it is suppose to be a 2 drive machine, from what we've found out about snap, im not really suprised.

Did you make a note of the bios versions? If so what were they

[Kraico]

Hello ALL...

I am 2 weeks into an upgrade of a 1000 and honestly am about to give up. This post is a last ditch attempt to fix my issues before I just go buy a new NAS.

My Hardware is as follows:

Snap 1000
Software ver: 3.4.803
Hardware ver: 3.1.2
Bios: 2.1.366
HD: Quantum 40 gig

Proposed upgrade: Western Digital 120GB, 7200rpm, ATA100

Before I even found this site I tried to clone my existing drive (with all data and settings) using a program called G4U. I let the clone finish (entire drive) and thought I was on the right tract when the OS was working fine. The problem was any disk utility's indicated "this screen is not available because no disks were found".

Enter the Procooling forum.....

I have read every post in this thread so please don't flame me if I have missed something but I do not believe anyone has posted regarding the problem I am experiancing. I started over and tried the Knoppix method (Reformat original, set to factory specs, DD etc.) only to experiance the same issue.

The good news is that it appears as if G4U accomplishes the same thing as DD, I found it eaiser and faster than the knoppix method, it includes the utilities to save images even to an FTP site and the download is only about 5 megs vs. 650 for Knoppix.

The bad news is I still have no upgraded Snap.

This forum has enlightened me to the "debug" screen, I determined that the Public Partition of my original drive is 10000 (fairlly typical from my readings) and I have tried the "device info" and the "format reinit" commands.

The device info command throws my Snap into a loop and the screen just keeps scrolling with the error message"

Invalid logical device : 0". In some portions of the screen the 0 is replaced by different characters such as "C" and others that appear to be a "hex address".

Skipping the device info command and going straight to the ".. format 10000 /reinit" returns the error:

Invalid device id 10000 requested

------------
Command returned with console error 1.

Obviously after the clone the partition table or something else is messed up and the public partition is not defined. WHY??

Any help on this issue would be greatly appreciated and since I am writing I would like clarification of a couple more issues (these have probably been covered already but my eyes are tired..please be kind)

I would like to create an image of my original drive, upgrade it to version 4 (already downloaded) and try everything again. My hesitation is that if it dosent work I would like to reinstall the 3.4.803 image and be back where I started. I would then just sell this unit and be done with it.

With this being said my question is: does upgrading to version 4 also upgrade the hardware version and bios? In my thinking this would cause the unit to "stuck" at version 4 and unable to be reverted to version 3.xxx.

Thank you all in advance for your time. I appreciate it.

[re3dyb0y]

G4U - http://www.feyrer.de/g4u/

Right. OS v4 upgrade will in some cases upgrade the bios. But not the hardware, the version is related to the actual hardware version.

The v4.0.830 doesnt seem to, but it might have done.

You can upgrade yours to 3.0.830, which most people seem to have upgraded from and had access.

If you look back through the posts there are 2 ftp servers that have the files on.

I can give you some more info later.. I need to read over your post in more detail first

[Kraico]

Poogles,

Was this a typo or do you mean "downgrade" to 3.0.830? I am currently at 3.4.803. Let me know and thanks for the reply!

[INT 20h]

Hello ALL...

I am 2 weeks into an upgrade of a 1000 and honestly am about to give up. This post is a last ditch attempt to fix my issues before I just go buy a new NAS.

My Hardware is as follows:

Snap 1000
Software ver: 3.4.803
Hardware ver: 3.1.2
Bios: 2.1.366
HD: Quantum 40 gig

Proposed upgrade: Western Digital 120GB, 7200rpm, ATA100

Before I even found this site I tried to clone my existing drive (with all data and settings) using a program called G4U. I let the clone finish (entire drive) and thought I was on the right tract when the OS was working fine. The problem was any disk utility's indicated "this screen is not available because no disks were found".

Enter the Procooling forum.....

I have read every post in this thread so please don't flame me if I have missed something but I do not believe anyone has posted regarding the problem I am experiancing. I started over and tried the Knoppix method (Reformat original, set to factory specs, DD etc.) only to experiance the same issue.

The good news is that it appears as if G4U accomplishes the same thing as DD, I found it eaiser and faster than the knoppix method, it includes the utilities to save images even to an FTP site and the download is only about 5 megs vs. 650 for Knoppix.

The bad news is I still have no upgraded Snap.

This forum has enlightened me to the "debug" screen, I determined that the Public Partition of my original drive is 10000 (fairlly typical from my readings) and I have tried the "device info" and the "format reinit" commands.

The device info command throws my Snap into a loop and the screen just keeps scrolling with the error message"

Invalid logical device : 0". In some portions of the screen the 0 is replaced by different characters such as "C" and others that appear to be a "hex address".

Skipping the device info command and going straight to the ".. format 10000 /reinit" returns the error:

Invalid device id 10000 requested

------------
Command returned with console error 1.

Obviously after the clone the partition table or something else is messed up and the public partition is not defined. WHY??

Any help on this issue would be greatly appreciated and since I am writing I would like clarification of a couple more issues (these have probably been covered already but my eyes are tired..please be kind)

I would like to create an image of my original drive, upgrade it to version 4 (already downloaded) and try everything again. My hesitation is that if it dosent work I would like to reinstall the 3.4.803 image and be back where I started. I would then just sell this unit and be done with it.

With this being said my question is: does upgrading to version 4 also upgrade the hardware version and bios? In my thinking this would cause the unit to "stuck" at version 4 and unable to be reverted to version 3.xxx.

Thank you all in advance for your time. I appreciate it.

Greetings,
When you put the upgraded drive in, before you try to do the format, does the server work (i.e. save files, work normally except not seeing the entire capacity of the drive)? If so one thing you might try is before running the format command, get a copy of the current OS (the SUP file...should be around somewhere on one of the servers Sam mentioned) and see if you can update the OS. I know it won't be a "real" update since you'll be sticking the the version you already have, but if there is an error in the operating system that might clear that up and allow you to run the format command without any problems.

There should also be an OS image out there that someone has created that you might also try DDing or G4Uing on the drive. If you can't find one I can post the image I used on my 1000 and send you the link.

Yeah...those are the only "safe" options I can think of at the moment. If they don't work...don't give up. I have a couple of other ideas but they're pretty risky and I don't know how far you want to push this. There is a solution...just a matter of making it up. ;)
Cheers,
INT 20h

[Kraico]

INT 20h,

The server does NOT work at all after the upgrade as NO drives are found. The os boots and performs fine but does not see the public partition.

As far as giving up...not really in my nature, but I did purchase a Buffalo Terra Station today as I needed something for business purposes. The Snap has now become a "hobby".

I believe I have the .sup of my current version and will give that a try. Actually come to think about it I tried to update it to 3.4.805 and it failed. I believe this is because the upgrade process stores some files on the Public partition and then accesses them from there. Not sure about this but it did in fact "fail".

Thank you very much for the offer of the image. If you are so inclined it is worth a shot.

I would still like to see what "options" you have available, but time is not critcal now so feel free to post at your lesiure. A 40 gig paper weight is no better than a 120 gig one.

Thanks a LOT...

[aznwizkid]

I am new to this forum, and been trying to read up on whats been done with the snap 4100, and was wondering has anyone tried to change the ide cable for one with a master and slave ide connector and plug in 2 drives on 1 channel. This seems really obvious to me to try, but my snap isn't here yet, so was wondering if anyone else had try or is wondering the same thing?

Thanks.

[re3dyb0y]

I mean upgrade to v3.0.830 from v3.0.803

[re3dyb0y]

I am new to this forum, and been trying to read up on whats been done with the snap 4100, and was wondering has anyone tried to change the ide cable for one with a master and slave ide connector and plug in 2 drives on 1 channel. This seems really obvious to me to try, but my snap isn't here yet, so was wondering if anyone else had try or is wondering the same thing?

Thanks.

Errm.

I believe (im not certain tho) but the 4100 already does this.

It should have 4 drives, and 2 ide channels so i believe snap has already done this

No sorry, looking at some info i have on it, it looks to have 4 channels, 1 to each drive. But i dont know whether anyone has done the 4100 with more than 4 drives.

I know it has been done successfully with the 1100, putting it up to 2 drives on 1 channel, and also on the 2200 having 4 drives on 2 channels (i believe).

IT may be possible. However, there wont be enough room for the drives inside it. And you will probably experience a preformance loss.

How much space are you after?


Thanks

Sam

[aznwizkid]

Errm.

I believe (im not certain tho) but the 4100 already does this.

It should have 4 drives, and 2 ide channels so i believe snap has already done this

No sorry, looking at some info i have on it, it looks to have 4 channels, 1 to each drive. But i dont know whether anyone has done the 4100 with more than 4 drives.

I know it has been done successfully with the 1100, putting it up to 2 drives on 1 channel, and also on the 2200 having 4 drives on 2 channels (i believe).

IT may be possible. However, there wont be enough room for the drives inside it. And you will probably experience a preformance loss.

How much space are you after?


Thanks

Sam

Thanks for the information, currently there will be 480gb in there, however, if possible I would like to get that closer to 1tb total storage, and be able to put in place a raid 1. but it might be unrealistic given the space consideration. Another thought I had was to just make an external casing for it, or moddify an 8 bay cd-rom tower to fit the drives the board and use the power supply in the 8bay along with the power of the snap ps, because I am not sure the p/s in the 4100 can actually supply an extra 4 hdd with juice.

Thanks
Allen

[papasmurf]

Which is better, the Snap 4000 or 4100? I know that it appears that the 4000 doesn't have the drive size limitations of the 4100, but what about transfer speeds and noise levels? Can anyone perform a direct comparison?

[re3dyb0y]

aznwizkid - Wouldn't you just be best building a normal pc with a couple of raid cards in? And then just having some 200 or 250GB hard drives?
www.tmk.com/raidzilla/ May be of use, as that is what you are after.

Im sure it would be a lot easier, and then run windows or something and use a remote desktop. Just a thought. Then you are not going to have the accommodation problems from the snap.

papasmurf - Doesn't one have gigabit? Have you checked snap appliances website?

Thanks

Sam

[aznwizkid]

Sam,
Thanks for that link, I guess I will just complete my snap as planned with 480gb since I got the whole thing for super cheap. As for a raidzilla, I guess that is probably the way to go, I just wanted to avoid having another computer to manage/crash, and having a snap server seem fairly self contained with little my family could do to screw it up.
Thanks
Allen

[re3dyb0y]

Well, the guy building the raid zilla was trying to get away from the Snap Server

They aren't 100% stable, but they aint bad.

The raid zilla would be very stable if you could get it to run FreeBSD, and you dont need that many drives. He has nearly god 2TB

[Terry Kennedy]

Well, the guy building the raid zilla was trying to get away from the Snap Server

They aren't 100% stable, but they aint bad.

The raid zilla would be very stable if you could get it to run FreeBSD, and you dont need that many drives. He has nearly god 2TBSnap Servers are fine if they meet your speed and storage capacity requirements. In my case (I'm the RAIDzilla guy) I had files spread over a dozen 480GB Snap 4100's and I was bottlenecked by the speed of the Snap server. Newer Snap models are almost certainly much faster, but aren't cost-effective compared with the RAIDzilla.

I'm running FreeBSD 5.4 on the RAIDzillas, and a single RAIDzilla (16 400GB drives) has 2 2TB data partitions (along with a large OS area and 2 150GB work partitions). More details (and benchmarks) on the RAIDzilla web page (http://www.tmk.com/raidzilla).

Quick reponses to other replies in this thread:

The 4100 treats all 4 drives as masters (2 Promise dual-channel IDE controllers). As far as I can tell, there's no code in Snap OS to even detect slave drives on those IDE buses. It might be possible to add 2 drives using the chipset IDE, but you'd need to pick it off the chipset IC, add bus drivers, etc.

I don't have any 1000's here, but I did do an upgrade with 2 WD1200BB's on a Snap 2000, so it is possible. If the original poster of the problematic 1000 wants to PM me with access info to his server, I'll see if I can tweak it remotely.

[re3dyb0y]

Yeah, if he port forwards to the snap server, you can get access to them over the web!


Cheers for the Info Terry



Sam

[z0ner]

First of all, thanks to (most) everyone on this thread for taking the time to document this nice easter egg. The process couldn't have been smoother for me:

In the beginning...
Model: 1100 40GB (Seagate)
Software: 3.4.790 (US)
Hardware: 2.0.2
BIOS: 3.4.758

Destination: Seagate 300GB ATA-100 ST3300831A-RK

1) In another PC, I hooked up the 40GB as MASTER and the 300GB as slave (same IDE channel)
2) Using a boot floppy with GHOST.EXE, ran the following command as mentioned earlier in this thread:
ghost.exe -clone,mode=copy,src=1,dst=2 -ir
The whole clone process took only about 70 minutes.
3) Installed the 300GB and changed it to Master. Booted up the Snap and it was recognized as a 40GB drive.
4) Using the SuperSecret url (tm), (http://mysnapserver/config/debug), I put in
config devices format 10000 /reinit
5) Viola 137GB :-(
6) Realized I need SnapOS 4. Got a copy of it (THANKS AGAIN) and installed it.
7) Rebooted, and still 137GB. Go back to step #4, and
6) Viola 300GB :-) !!!!!

The final result:
Model: 1100 300GB (still Seagate)
Software: 4.0.860 (US)
Hardware: 2.0.2
BIOS: 3.4.758

Now I'm on the hunt to get a 500GB drive to see what can be done. Wish me luck boys, I'm going in :-)

[Dave_in_Dallas]

S2S and java VM are avaliable from here:

http://www.snapappliance.com/page.cfm?name=NASS2SSync&Nav=NAS

I was able to upgrade only to 3.4.805 on my Snap2200. All attempts to load 4.029,30, 55 etc failed during the main download.

Is it possible to run the newer JVM etc using the 3.4.805 OS????


Regards, and thanks in advance.

[Dave_in_Dallas]

The 80GB mirrored drives in a SnapServer 2200 corrupted in the OS area and created a panic each time the machine booted. About 60GB of mirrored data may be gone.

With the help of the forum, [and extra help from Misterbill and The Doc] I now have two 200GB replacement drives up and running with 48bit addressing. 380GB of blank space. Thanks to both the ftp sites and the excellent notes available to walk a newbie through all of this.

Back to the 80 GB drives. Nothing seems to recognize the drives. I've tried Knoppix, DiskDolly, and some mounting utilities.

An older SnapAppliances link suggested I format one of the mirrored pair, which did not work, leaving me with one drive [hopefully] containing intact data.

Does anyone know of a way to only replace the OS section on the one drive with data and leave the remaining data intact so it can be retrieved? This contains photos of my daughters recent wedding. It would be nice to sleep in my own bed again. :shrug:

Any input would be appreciated.

[re3dyb0y]

Hmm.

Let me ask, how did you get 48 bit enabled? As i didn't know a solution had been obtained. Is it just running reinit a few times? Like z0ner mentioned?

Only the Snap servers will be able to see the data. Have you tried putting one of the 2 80gb drives in on the 2nd ide channel with the 200gb on the primary.

Thats the easiest suggestion, and the most possible to work, if that doesn't, im not too sure.

[Dave_in_Dallas]

I did run the reinit twice, then I had to format each drive to gain the space. It's good that I had no data at that point. I had read that the 3.4.805 would support 48bit addressing, so....................
Now I have to figure a way to recover my data from the broken mirror drive with errors.
Any idea why I can't upgrade to 4.x? And do you think there is a reason to go to 4.x at all?
Dave_in_Dallas



Hmm.

Let me ask, how did you get 48 bit enabled? As i didn't know a solution had been obtained. Is it just running reinit a few times? Like z0ner mentioned?

Only the Snap servers will be able to see the data. Have you tried putting one of the 2 80gb drives in on the 2nd ide channel with the 200gb on the primary.

Thats the easiest suggestion, and the most possible to work, if that doesn't, im not too sure.

[Leomania]

Hello,

I've just come into possession of a 20GB Quantum Snap Server 2000, and the good news is that it appears to be in mostly good working order. I've read through this entire thread, and it has been immensely informative. Thanks to all who took the time to post such thoughtful comments!

I do have one issue on my Snap that has me stumped; I hope someone here has an idea about it. I have reset the system to factory defaults, updated the firmware from 2.x to 3.4.805 and all seems to have gone well except that I don't seem to have permission to access the SHARE1 directory. I can browse to it, but all I've managed to do thus far (via both Windows Explorer and via ftp) is to create a directory that I can't write into or a zero-length file. I can't even delete the zero-length file!

During the full reset (code 4) the permissions for the SHARE1 directory were set to "Full Access (Everyone)" so I don't see why I wouldn't have permission to write a file. I went so far as to change from a 20GB striped set to a 10GB mirrored set, thinking that would reinitialize things... no dice, same problem.

Any guidance would be greatly appreciated. There's no way I'll move forward with any disk upgrade until this is resolved.

- Leo

[Leomania]

I do have one issue on my Snap that has me stumped; I hope someone here has an idea about it. I have reset the system to factory defaults, updated the firmware from 2.x to 3.4.805 and all seems to have gone well except that I don't seem to have permission to access the SHARE1 directory. I can browse to it, but all I've managed to do thus far (via both Windows Explorer and via ftp) is to create a directory that I can't write into or a zero-length file. I can't even delete the zero-length file!
DOH! I bet it is due to that Microsoft hotfix MS05-011/8885250. I'll remove that when I get home tonight and report back.

[Leomania]

DOH! I bet it is due to that Microsoft hotfix MS05-011/8885250. I'll remove that when I get home tonight and report back.
Nope... that's not it.

I connected to the Snap Server from my Mac (looks like it connected via SMB) and I was able to delete the zero-length files and the "New Folder" dirs that had been created from WinXP. But I still am told I have no permission to create a new directory from the Finder!

However, I was able to ftp into the box, create a directory and transfer a file from the Mac.

Any thoughts as to what is going wrong, and what I might try to fix it?

Thanks in advance...

[re3dyb0y]

Again, i'd like to take this moment to post the file ftp sites:
ftp://**************/

Oh, and i believe 0s v 4.0.855 (i think), if on the site is a v3 upgrade. If not, i will have to upload it.

Also, there is my site:
http://******************/

FTP details are in a prior post

Leomania - You could try doing a ip, admin and share reset

Cheers

Sam

[Leomania]

Leomania - You could try doing a ip, admin and share reset
Hi Sam,

I've reset things a couple of times, no joy thus far.

I did pick up the OS upgrade from the ftp site, which was very helpful. I'll have to go back through the posts to see if the 2000 is recommended to get the 4.x upgrade or not, but I'm hesitant to do any more upgrading until I can get this unit running with 3.4.805 since so many others have.

Thanks,

- Leo

[z0ner]

Hi Sam,

I've reset things a couple of times, no joy thus far.



Leo, are you joining your SNAP to a Windows domain? I seem to remember when I did that, the SHARE1 folder was inaccessible because I didn't import the user database and the security on the drive had all my domain users (including me) set to DENY, and of course that takes precedence over the Everyone group and full control.

I was going nuts until I joined it to a workgroup to test my theory - sure enough access was fine.

[Sid2000]

Hi Sam,

I've reset things a couple of times, no joy thus far.

I did pick up the OS upgrade from the ftp site, which was very helpful. I'll have to go back through the posts to see if the 2000 is recommended to get the 4.x upgrade or not, but I'm hesitant to do any more upgrading until I can get this unit running with 3.4.805 since so many others have.

Thanks,

- Leo

I'm new to this but I also have a Snap 2000 (Meridian) and I would like to know what is the bios version are you ugrading from.

SOFTWARE: 3.1.608 (US)
HARDWARE: 1.1.0
BIOS: 1.2.180

Please let me know if your 2000 is the same as mine and what the result is. I'm trying to figure out if my 2000 can take 2X300 GB HD. I successfully upgraded it to 2X20 GB HD from 2X8 GB HD without any problems.

[Sid2000]

I have upgraded several SNAP 1000's from 2x to 3.4.803 without any problems. 3.4.803 is also available from SnapAppliance.


Hi there. I'm new to this but I have a 2000 Meridian

SOFTWARE: 3.1.608 (US)
HARDWARE: 1.1.0
BIOS: 1.2.180

Can I upgrade to 4 without first upgrading to 3.4.803? Will the software upgrade also upgrade the bios? The reason for questions is because I want to upgrade to 2x300 GB HD's. Is it possible?

Many thanks...

[Dave_in_Dallas]

meister_sd,
I too am dealing with a cracked mirror. Have both 2200 drives booting with OS 3.4.803. One shows the cracked mirror, the other as a single Disk1.
Tried using the commands below to get my mirror available, but received the following error:
07/14/2005 23:24:56 Command: config devices config individual 50000 force

'Individual' JBOD devices require a single Logical Device Id or a Public Partition Id
Any idea where to go from here? There is a Share1 and Share2 on the drive. I can see that it has 65,000+ files on it that I'm trying to recover.... Any help would be appreciated.
Dave_in_Dallas

OK, I now have my "Cracked Mirror" error fixed. I did what poogle_uk told me, but there were a few more steps I needed to take.

1) Remove the second HD - Just work with the single primary drive.
2) In debug, type: 'config devices info' - write down the "Logical Device" that shows the "Cracked" error. Mine was 50000
3) In debug, type: 'config devices unmount all'
4) THEN I had to type: 'config devices config individual 50000 force' (Where 50000 was mine, your's might be different)
5) Last, I rebooted from debug typing: 'reboot'

After that it took not too much longer than normal to boot, but a few extra seconds. But in the main home page, I still have the "lost" shares, but my disks aren't mirrored or showing errors.

Next, I'm going to try Digital Dolly or Ghost and mirror the main drive to another and see if that works.....

[Leomania]

Leo, are you joining your SNAP to a Windows domain? I seem to remember when I did that, the SHARE1 folder was inaccessible because I didn't import the user database and the security on the drive had all my domain users (including me) set to DENY, and of course that takes precedence over the Everyone group and full control.

I was going nuts until I joined it to a workgroup to test my theory - sure enough access was fine.
I don't have a system set up to be a domain master, so (I think) I have things set up for WORKGROUP sharing. I saw in an "Advanced" menu that there's a "Domain Master" checkbox; not sure if that should be set, cleared or what (currently set, by default apparently).

I guess I'll need to remove that one service pack then start mucking with all the settings on the box. I'll reread the documentation I downloaded from snapappliance.com or adaptec.com (they sure are intertwined!) to see if that gives me any clues.

- Leo

[Leomania]

I'm new to this but I also have a Snap 2000 (Meridian) and I would like to know what is the bios version are you ugrading from.

SOFTWARE: 3.1.608 (US)
HARDWARE: 1.1.0
BIOS: 1.2.180

Please let me know if your 2000 is the same as mine and what the result is. I'm trying to figure out if my 2000 can take 2X300 GB HD. I successfully upgraded it to 2X20 GB HD from 2X8 GB HD without any problems.
Mine is as follows:

SOFTWARE: 3.4.805 (was 2.1.340 when I got it)
HARDWARE: 2.0.0
BIOS: 2.0.252

From what I read in this thread (all of it... took days off and on) the 1.x.x hardware seems to not be able to handle 48-bit LBA. Can anyone chime in here and confirm?

- Leo

[OzDave]

Nope... that's not it.

I connected to the Snap Server from my Mac (looks like it connected via SMB) and I was able to delete the zero-length files and the "New Folder" dirs that had been created from WinXP. But I still am told I have no permission to create a new directory from the Finder!

However, I was able to ftp into the box, create a directory and transfer a file from the Mac.

Any thoughts as to what is going wrong, and what I might try to fix it?

Thanks in advance...

I had problems also with using my Snap Server and Mac. The problem is not the Snap, but the Mac. It seems that there were problems with Tiger (10.4). The latest update (10.4.2) corrected the issue. There is a discussion on some of the Mac forums about the write problem on smb and afp mounted drives.
OzDave

[OzDave]

Mine is as follows:

SOFTWARE: 3.4.805 (was 2.1.340 when I got it)
HARDWARE: 2.0.0
BIOS: 2.0.252

From what I read in this thread (all of it... took days off and on) the 1.x.x hardware seems to not be able to handle 48-bit LBA. Can anyone chime in here and confirm?

- Leo
My 2.0.0 Snap 2000 can handle 48-bit LBA. My 1.1.0 Snap 2000 definitly can't support 48-bit LBA. My experience has been that 1.1.0 boxes will detect the larger drive, and try to format it. Formatting fails.

-OzDave

[Sid2000]

My 2.0.0 Snap 2000 can handle 48-bit LBA. My 1.1.0 Snap 2000 definitly can't support 48-bit LBA. My experience has been that 1.1.0 boxes will detect the larger drive, and try to format it. Formatting fails.

-OzDave


Does anyone know how to upgrade from 1.1.0 to 2.0.0? Is it even possible to upgrade the hardware version? Can upgrading to a new SOFTWARE version also upgrade the BIOS and HARDWARE?

Many thanks...

[Leomania]

Does anyone know how to upgrade from 1.1.0 to 2.0.0? Is it even possible to upgrade the hardware version? Can upgrading to a new SOFTWARE version also upgrade the BIOS and HARDWARE?
Not that I know of; typically, companies change hardware revs to cost-reduce a product or fix significant shortcomings. The hardware is sufficiently different that the firmware/software needs to be different for the new hardware.

I saw a good example of this last night in two Netgear FS516 16-port 10/100 switches; they looked almost identical but were different like night and day inside. One had a dozen or so largish chips, maybe even one chip per port. The other had just two chips of the same physical size and one of the circuit boards was a lot smaller. Both the same model number, same function, but very different in side (clearly a cost reduction).

- Leo

[Sid2000]

Not that I know of; typically, companies change hardware revs to cost-reduce a product or fix significant shortcomings. The hardware is sufficiently different that the firmware/software needs to be different for the new hardware.

I saw a good example of this last night in two Netgear FS516 16-port 10/100 switches; they looked almost identical but were different like night and day inside. One had a dozen or so largish chips, maybe even one chip per port. The other had just two chips of the same physical size and one of the circuit boards was a lot smaller. Both the same model number, same function, but very different in side (clearly a cost reduction).

- Leo


Thanks for the info!!! So what's the maximum drive capacity can I upgrade my 2000? I sucessfully upgraded the SOFWARE to 3.4.803

[Leomania]

Thanks for the info!!! So what's the maximum drive capacity can I upgrade my 2000? I sucessfully upgraded the SOFWARE to 3.4.803
120GB is the available size that fall below the 137GB barrier; that's the size others have reported using to good effect.

I saw a post somewhere recommending replacement of the cheap CPU fan in the 2000 with a better unit; I managed to track down links to buy the one recommended by the poster. It's inexpensive and has a 5V dual-ball bearing fan.

GlobalWin FAC08
http://www.gigaparts.com/parts/profile.php?sku=FN0054
http://keysource.net/store/product.phtml?ID=40&DIR=9

My fan was making noise when I got it, but I lubed it and it has since been happy; still, I think I'll go for the GlobalWin heatsink/fan when I upgrade the drives in case they aren't as cool running as I hope.

Hope that helps,

- Leo

[Dave_in_Dallas]

SnapOS Update: 2200 Cracked Mirror
I just spent 45 minutes with Adaptec Tech support on the phone trying to solve my broken mirror issue. They confirmed that the disk format is based on a "highly customized" FreeBSD operating system. That was mentioned earlier in this thread I belive by an ex Snap employee.

Prior to calling Adaptec, my attempts with debug commands: Config device config individual 50000 force, I got error: 'Indivudual' JBOD devices require a single Logical Device Id or a Public Partiton Id.
The "Cracked Mirror" designation did go away however. The mirrored disk just reported itself as
"Mirror - Primary disk
Data protection disabled. Backup disk has failed. Primary disk is OK."

Adaptec's suggestion [of course] was data recovery as any attempt to force the Data protection disk into a single disk mode would more than likely result in the disk being They reluctantly refunded my $120 tech support call fee since they were unable to help.

The tech did note however, that had I not formatted the other drive that was part of the mirror, that they could have done a successul recovery.... ??? There are some "tricks" to get past the panic system light and access the server... We need an ex Snap technician as part of this thread don't we....

Ideas and suggestions are welcome and solicited.

[Leomania]

It was caused by the Microsoft SMB patch after all. Removed the patch, access seems to be just fine now.

I'm thinking to go ahead and install 4.0.860 to eliminate this issue going forward. I have no intention of putting my 2000 into a four-drive configuration or anything, so I think it's the way to go.

I'll review the documentation in the upgrade package, but is there anything I should do after following their installation instructions?

Thanks,

- Leo

[Leomania]

It was caused by the Microsoft SMB patch after all. Removed the patch, access seems to be just fine now.

I'm thinking to go ahead and install 4.0.860 to eliminate this issue going forward. I have no intention of putting my 2000 into a four-drive configuration or anything, so I think it's the way to go.
I downloaded the upgrade archive from the ftp site Sam mentioned, unpacked it and tried to use Assist to perform the upgrade; it claims that the file (Snap_4_x.sup) isn't valid for my 2000. The docs talk about the 1100/2200/4400, but not the 2000... so maybe it isn't compatible?

Hmmm... seems to me I've seen someone mention upgrading their 2000 to 4.0.860... is that right?

- Leo

[re3dyb0y]

Leo - Are you on v 3 at the moment, if so you need to download and instal v4.0.830 or i think 4.0.855, as they are the upgrades from v3, then you can put v4.0.860 on.

Usually if it mentions 1100, that includes/means also the 1000, the same with the 2200 and the 2000. If my knowledge serves me correctly. The units are very similar, and im not sure what the difference is.

[Leomania]

Leo - Are you on v 3 at the moment, if so you need to download and instal v4.0.830 or i think 4.0.855, as they are the upgrades from v3, then you can put v4.0.860 on.

Usually if it mentions 1100, that includes/means also the 1000, the same with the 2200 and the 2000. If my knowledge serves me correctly. The units are very similar, and im not sure what the difference is.
Yes, I'm on 3.4.805 currently. The documentation talks about being able to upgrade from "2.x or above" so I had no idea about this; but come to think of it, the docs look like they date back to SnapAppliance (little if any info about Adaptec) so I guess it shouldn't come as any surprise.

Thanks a bunch for the tip, Sam!

- Leo

[edcetera]

Hello

Been away for a while, has anyone actually broken the 137 gig barrier on the 2000.

I see statments here that say it but they seem to only be assuming.

Who has actually done it.

I am going to get the Buffalo box and sell my 2000 with 2x120 gig drives if I cant get above this 137 gig constraint.

Please reply with facts, assumptions dont cut it.

Thank you for your time.

Sincerely / Ed :cool:

[bumpyone]

Hello

Been away for a while, has anyone actually broken the 137 gig barrier on the 2000.

I see statments here that say it but they seem to only be assuming.

Who has actually done it.

I am going to get the Buffalo box and sell my 2000 with 2x120 gig drives if I cant get above this 137 gig constraint.

Please reply with facts, assumptions dont cut it.

Thank you for your time.

Sincerely / Ed :cool:

Ed,

I have installed two WD 160 GB drives in my 2000. Please see post http://forums.procooling.com/vbb/showpost.php?p=141490&postcount=576. I have also upgraded my memory from 64 MB to 256 MB. System is a Quantum Snap 2000 server.

Ray

[Leomania]

Okay, 4.0.830 went on my 2000 just fine. Upgraded using three of the four .sup files (skipped ServerSync) and all appears to be working well. In fact, better than I expected. Using a Win2k system that has the patch for KB885250 installed, I was able to access and copy files to the Snap without issue. I'm going to reinstall the security patch on my WinXP box and see if things are also okay. If so, I'll be a bit surprised; the security bulletin came out in February 2005, and 4.0.860 came out in March supposedly (according to the Adaptec site) to address the SMB problem it caused.

On a related note, has anyone assembled the cumulative knowledge about what each known version of the SnapOS does? That would be a handy file to have on the ftp site.

- Leo

[Leomania]

Been away for a while, has anyone actually broken the 137 gig barrier on the 2000.
Ed, the key seems to be the hardware rev of your 2000 motherboard. If you have 2.0.0 or above, it will work. From my reading on this form, it requires upgrading the SnapOS to at least 3.4.805 but 4.0.830 or above works as well. Conversely, if you have rev 1.x.x, it won't work.

I need to procure my second 160GB drive to prove it, although it appears that bumpyone has already confirmed that those work.

Lastly, see my recent post about the CPU fan; that has been described as a weak link especially with the hotter-running 7200 RPM drives. I already had to lubricate the fan on my unit, so it clearly is only a stopgap measure until I can install the low-profile dual-ball bearing fan. I consider that a must for the disk upgrade unless I find a good price on some 5400 RPM fluid dynamic bearing drives that are known to run cool, and even then the fan has me concerned.

Even still, at the end of the day these boxes are a bargain; where can you get a RAID0/1 NAS chassis for anything approaching what these sell for on Ebay?

As a note, I bought a Buffalo LinkStation from a friend and after moving up the firmware rev a couple of numbers it works pretty well. But the fact it has a single drive worries me; I'm going to have to yank out the drive, image it, and use that to recover the box should the disk go bad. As long as the Snap remains reliable after the fan/heatsink modification, it will be a better choice IMHO.

Good luck with your upgrade,

- Leo

[Leomania]

Been away for a while, has anyone actually broken the 137 gig barrier on the 2000.

I see statments here that say it but they seem to only be assuming.

Who has actually done it.
Ed, here are the posts I found regarding upgrading the 2000:

144 - 160GB
155,334 - 200GB
428 - 300GB

bumpyone posted about his 160GB a couple of times.

In each case, when mentioned, the hardware rev is 2.0.0 or above. I found posts (including yours) that indicate failure to break the 137GB limit with rev 1.x.x; no one has done it that I've seen mentioned.

I am going to get the Buffalo box and sell my 2000 with 2x120 gig drives if I cant get above this 137 gig constraint.
I just realized after I posted that you probably meant a Buffalo TeraStation, not a LinkStation. Those look pretty sweet. :D

- Leo

[Neil]

Hi, a friend of mine has a Quantum 1000 Snap that is in need of repair, I’m not sure what’s wrong with it but the symptoms are below:




This unit powers up but is not accessible from the browser interface, however the Link light glows steady green when connected to the network.

After a couple of minutes of being powered up the System and Disk lights flash. The disk light flashes twice as fast as the System light. He can hear the hard disk spin up.



I said I would try and find out what’s wrong with it and fix it if possible. Could these symptoms be caused by a corrupt OS on the hard disk?

I was hoping this was the case, so that I could follow the instructions provided in this forum to install a new drive.


Any help would be greatly appreciated.

Thanks
Neil

[edcetera]

Hello Leo

I have 3.4.803 software 2.0.0 hardware and bios 2.0.282 in my 2000 and have a copy of 4.08something around here.

I never tried any disk bigger than the 120 becuase at the time I did the upgrade to 120 gig there was no one successful above 137 gig, it was deemed impossible by hardware limitations.

Its still scary IMHO to buy 2x 250 gig drives to find out if this wil work.

Thanks for the help

/ Ed

Ed, here are the posts I found regarding upgrading the 2000:

144 - 160GB
155,334 - 200GB
428 - 300GB

bumpyone posted about his 160GB a couple of times.

In each case, when mentioned, the hardware rev is 2.0.0 or above. I found posts (including yours) that indicate failure to break the 137GB limit with rev 1.x.x; no one has done it that I've seen mentioned.


I just realized after I posted that you probably meant a Buffalo TeraStation, not a LinkStation. Those look pretty sweet. :D

- Leo

[edcetera]

Hello Ray

What OS software is in your 2000,
mine is 3.4.803
hardware 2.0.0
Bios is 2.0.282

I have 4.0.829 here but wonder if its neccessary to do an upgrade to 2x 250 gig drives.

What are your thoughts regarding these parameters above.

Thanks / Ed



Ed,

I have installed two WD 160 GB drives in my 2000. Please see post http://forums.procooling.com/vbb/showpost.php?p=141490&postcount=576. I have also upgraded my memory from 64 MB to 256 MB. System is a Quantum Snap 2000 server.

Ray

[Leomania]

Its still scary IMHO to buy 2x 250 gig drives to find out if this will work.
I hear you there! Since you're in Oceanside, you can make the trek over to Fry's to take advantage of one of their sales; pick your brand, wait for the sale with a rebate, and you should be able to get at least one of the 250GB or 300GB units for $89 or $99... thereabouts, anyway. And I've seen that they don't pull that stunt about "one rebate per address per year"; I've been able to do two rebates on (nearly) the same drive a couple of weeks apart and they both came through. The discounts are steep enough that it sure beats paying full price!

Your hardware looks right... if I had anything bigger than 160GB to test I'd verify it for you. Since others have already done 200GB, that's not likely to be helpful. That 500GB unit being offered on Ebay (still available) sure makes it look like your unit can do it, though.

- Leo

[edcetera]

Hello Leo

I spoke by phone with that guy on ebay, and asked for a screen dump of the actaul reported size of the hard drives, and he said he would ask his tech, all this was the first time they tried to sell that 2000 and now its on eBay again as it didnt sell.

Im wondering why they are reluctant to put a screen dump there, maybe if a few of us ask him to show the screen dump of actaul size he will do it.

click on this link---> ebay snap2000 (http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=5789656063&rd=1&sspagename=STRK%3AMEWA%3AIT&rd=1)

Thanks for all your help Leo

Sincerely / Ed

=============================

I hear you there! Since you're in Oceanside, you can make the trek over to Fry's to take advantage of one of their sales; pick your brand, wait for the sale with a rebate, and you should be able to get at least one of the 250GB or 300GB units for $89 or $99... thereabouts, anyway. And I've seen that they don't pull that stunt about "one rebate per address per year"; I've been able to do two rebates on (nearly) the same drive a couple of weeks apart and they both came through. The discounts are steep enough that it sure beats paying full price!

Your hardware looks right... if I had anything bigger than 160GB to test I'd verify it for you. Since others have already done 200GB, that's not likely to be helpful. That 500GB unit being offered on Ebay (still available) sure makes it look like your unit can do it, though.

- Leo

[z0ner]

I hear you there! Since you're in Oceanside, you can make the trek over to Fry's to take advantage of one of their sales; pick your brand, wait for the sale with a rebate, and you should be able to get at least one of the 250GB or 300GB units for $89 or $99...

Sure enough, today Circuit City put the Segate 300GB ATA100 on sale for a net of $99 after $90 worth of rebates.

[Dave_in_Dallas]

In Dallas today, the Seagate 300 at Circuit City is $139 with only $60.00 in rebates..... :mad:
go figure......


Sure enough, today Circuit City put the Segate 300GB ATA100 on sale for a net of $99 after $90 worth of rebates.

[z0ner]

In Dallas today, the Seagate 300 at Circuit City is $139 with only $60.00 in rebates..... :mad:
go figure......

You should be able to buy it online:

http://www.circuitcity.com/ssm/Seagate-Internal-Hard-Drive-ST3300831A-RK-/sem/rpsm/oid/118287/rpem/ccd/productDetail.do

Also, TigerDirect has a great deal on a 250GB Seagate for $79. It's OEM but comes with a 5-year warranty:

http://www.tigerdirect.com/applications/searchtools/item-Details.asp?EdpNo=1265028&sku=THD-250A

[Dave_in_Dallas]

I'm taking wagers on if this desperate measure will work..........sorry if it is unclear.

Snap Appliance tech support told me that I could not repair my broken mirror since my 80GB primary drive "knew" that it was part of a mirrored set. Installing a new blank replacement drive with the OS on it would not allow it to rebuild because it would be seen as a single drive [ID 10000 or 1000010] and not part of a mirrored set.
Sooooooooooo... desperation creates some fuzzy logic.

I've cloned my broken 80 GB Primary Snap Mirror drive to a larger 200GB drive with ghost.

I then used two separate new 200GB drives and created a mirror with no data on the Snap Server.
Now I have a clean 187GB primary mirror and a backup mirror each ID'd as 50000.
with no data on it, plus a 76,319 Primary mirror drive clone on a 200 GB drive [this came from the 80GB remaining Snap drive]. Don't know what will happen with the extra unused space...

Next planned step is to insert the remaining drive in position One. [Physical position does matter according to Snap Tech Support] and see if the system is faked out to rebuilding the mirror.........
Thoughts and input are appreciated... :rolleyes:

[Dave_in_Dallas]

GOT IT!!! :D
Most of the gyrations from my last post were unnecessary. After cloning the primary mirror drive to the other 80GB drive which I had formatted, I put it in the Snap Server 2200 to verfity that the copy was good. It booted up with both shares visible, and all the data intact!!!
Apparently the cloning process broke the mirror and all is well. My new 200GB drives will go into the 2200 as a 187GB mirror.
What a trip.... THANK YOU to all of the contributors and posters to this forum. There is no way in the world I could have succeded without your help.
Sam, Zoner, Misterbill.... Kudos. I'm staying a part of this forum.

For just a bit more than I would have spent on a billed SnapAppliance tech support call, I have 3 new 200GB Seagate drives as well!!!

Quoted from Zoner post 627
Destination: Seagate 300GB ATA-100 ST3300831A-RK

1) In another PC, I hooked up the 40GB as MASTER and the 300GB as slave (same IDE channel)
2) Using a boot floppy with GHOST.EXE, ran the following command as mentioned earlier in this thread:
ghost.exe -clone,mode=copy,src=1,dst=2 -ir
The whole clone process took only about 70 minutes.
3) Installed the 300GB and changed it to Master. Booted up the Snap and it was recognized as a 40GB drive.
4) Using the SuperSecret url (tm), (http://mysnapserver/config/debug), I put in
config devices format 10000 /reinit
5) Viola 137GB :-(
6) Realized I need SnapOS 4. Got a copy of it (THANKS AGAIN) and installed it.
7) Rebooted, and still 137GB. Go back to step #4, and
6) Viola 300GB :-) !!!!!


I'm taking wagers on if this desperate measure will work..........sorry if it is unclear.

Snap Appliance tech support told me that I could not repair my broken mirror since my 80GB primary drive "knew" that it was part of a mirrored set. Installing a new blank replacement drive with the OS on it would not allow it to rebuild because it would be seen as a single drive [ID 10000 or 1000010] and not part of a mirrored set.
Sooooooooooo... desperation creates some fuzzy logic.

I've cloned my broken 80 GB Primary Snap Mirror drive to a larger 200GB drive with ghost.

I then used two separate new 200GB drives and created a mirror with no data on the Snap Server.
Now I have a clean 187GB primary mirror and a backup mirror each ID'd as 50000.
with no data on it, plus a 76,319 Primary mirror drive clone on a 200 GB drive [this came from the 80GB remaining Snap drive]. Don't know what will happen with the extra unused space...

Next planned step is to insert the remaining drive in position One. [Physical position does matter according to Snap Tech Support] and see if the system is faked out to rebuilding the mirror.........
Thoughts and input are appreciated... :rolleyes:

[netwizz]

Hello everyone. I recently got a snap server and needed to upgrade it for a client of mine. While reading through the forums it became apparent to me that everyone seems to struggle with the upgrade process in some way or another. THere are several methods that indeed work but are somewhat cumbersome. Not being a LINUX person that was a little out of the question especially since I i dont know the commands. I did however find a much simpler way of doing things using winhex.

Take a bin file or iso or whatever you have for an image of the os and simply copy it to the drive in windows. Insert the drive and use the /config/debug format it and done. I noticed that 4.0.855 worked best for me with my quantum 1000.

Here is a link to the working bin with .855 on it. http://***********************


Also there is a copy of winhex there as well. please ask questions if there are any.


Jason Murphy

[re3dyb0y]

Hello everyone. I recently got a snap server and needed to upgrade it for a client of mine. While reading through the forums it became apparent to me that everyone seems to struggle with the upgrade process in some way or another. THere are several methods that indeed work but are somewhat cumbersome. Not being a LINUX person that was a little out of the question especially since I i dont know the commands. I did however find a much simpler way of doing things using winhex.

Take a bin file or iso or whatever you have for an image of the os and simply copy it to the drive in windows. Insert the drive and use the /config/debug format it and done. I noticed that 4.0.855 worked best for me with my quantum 1000.

Here is a link to the working bin with .855 on it. http://*******************


Also there is a copy of winhex there as well. please ask questions if there are any.


Jason Murphy

Cheers for that jason, another method that'd be useful for people.

Also dave, No Problem ;)

[Dave_in_Dallas]

When I tried this using the .855 image above, my Quantum 2200 would never boot up to let me do the config/debug/format command. Simpy Alternated with with blinking system and disk access lights. Access and browser failed to see the server.

I'm pretty sure this is pilot error. Anyone else with success using this technique, please post.
I had to use the clone comand in Winhex. rather that copy to get the program to see the Snap drive.
Take care.

PS.... the repaired mirror drive which allowed me to get data off my server is very flaky. Have to copy 10 or fewer jpeg files at a time to get data off. Very time consuming, but almost done. Any large transfer fails with item not found.

[z0ner]

I don't mean to hijack the thread (not like it hasn't been a hundred times already, :cool: ), but I was wondering if any of you know where I can get my hands on GuardianOS 3.2. If you guys think SnapOS is expensive (which it is), it's 3x more for GuardianOS :eek:

[aznwizkid]

Quick question does anyone know what file structure snap os is using? For instance if I was doing a raid 1 and the server died, what could I use to recover the data from my drive? linux? or windows? etc. Thanks

[z0ner]

Quick question does anyone know what file structure snap os is using? For instance if I was doing a raid 1 and the server died, what could I use to recover the data from my drive? linux? or windows? etc. Thanks

It's been mentioned a few times in this 26 page thread, but it's a modified version of FreeBSD. Whether you'll be able to recover using Linux is a mystery to me. :shrug:

[Dave_in_Dallas]

Quick question does anyone know what file structure snap os is using? For instance if I was doing a raid 1 and the server died, what could I use to recover the data from my drive? linux? or windows? etc. Thanks

aznwizkid,
Depending on how dead your system is, look back at some of the earlier posts. I was able to clone my remaining drive which had a broken mirror with Ghost to another hard drive and the clone became readable. In an earlier conversation, Snap tech support did say that if the raid was intact, they could get it back up and running if hardware was not the issue. [no idea how] Cost is $120 just to do a tech support call, but I devoted A LOT more than that in time an frustration.

If Snap tech support can't help you, they will refund the service call. At least they did for me. Knowing what I know now, I would try that first before going through what I just endured. Not very macho, but very pragmatic unless you would rather put that $120 in larger hard drives for the Snap!! :)

[aznwizkid]

Dave,
Thanks for the response, I am not sure that is exactly what I meant though, I was wondering what would happen if say the snap server died, and the hard drives where still intact, would I be able to say plug them into a computer running freebsd or fedora (which can read UFS) UFS being the file structure besides ext2 and ext3 that freebsd creates to recover the data from the drives?

[Dave_in_Dallas]

Dave,
Thanks for the response, I am not sure that is exactly what I meant though, I was wondering what would happen if say the snap server died, and the hard drives where still intact, would I be able to say plug them into a computer running freebsd or fedora (which can read UFS) UFS being the file structure besides ext2 and ext3 that freebsd creates to recover the data from the drives?


That is exactly what I've been trying to do for the last 3 weeks. My Snap failed and I was out of luck.
I was unable to see the drives with Knoppix or Mandrake Linux or Live FreeBSD. Nothing I had would see the drive at all or mount it. Search my other links and you'll see the odyssey.
Best of luck.

[Leomania]

That is exactly what I've been trying to do for the last 3 weeks. My Snap failed and I was out of luck.
I was unable to see the drives with Knoppix or Mandrake Linux or Live FreeBSD. Nothing I had would see the drive at all or mount it. Search my other links and you'll see the odyssey.
Dave, this may be more than you want to take on, but check out this article about the filesystems on the Tivo and see if it has any techniques that you might be able to use to figure out the Snap filesystem:

http://www-128.ibm.com/developerworks/linux/library/l-lobtivo/?ca=dgr-lnxw01LidOffTivo

Also, I saw this tool discussed *somewhere* (saved the link on some darned computer or other...) which can guess at the partition table on a disk:

http://www.stud.uni-hannover.de/user/76201/gpart/

I've not used it, be careful with that one.

Hope that helps,

- Leo

[Dave_in_Dallas]

Dave, this may be more than you want to take on, but check out this article about the filesystems on the Tivo and see if it has any techniques that you might be able to use to figure out the Snap filesystem:

http://www-128.ibm.com/developerworks/linux/library/l-lobtivo/?ca=dgr-lnxw01LidOffTivo

Also, I saw this tool discussed *somewhere* (saved the link on some darned computer or other...) which can guess at the partition table on a disk:

http://www.stud.uni-hannover.de/user/76201/gpart/

I've not used it, be careful with that one.

Hope that helps,

- Leo

Thanks Leo,
Aznwizkid [Jason ] and I spoke, and he has used the Winhex program to dup Tivo Disks very successfully. I did use Winhex to apply one of the Snap2200 bin images to a Snap drive with success instead of the Knoppix dd method.
Unfortunately, I couldn't use his Snap1000 image which had the 4.x software already installed.
I was able to get all my data finally by using a ghost clone which for some reason let the Snap have access to all the files. Something was still flaky as the data was devilishly hard to get off the server. Kept losing the copy during download if it was over 25mb.

New 200GB drives with 3.4.805 are working fine now in Mirror mode.
thanks for the input..... Think I'm still going to reByte. Don't trust my Snap any longer.

[re3dyb0y]

Files system is XFS i believe from what snap tech told me.

Can i ask where the 2000 bios update came from on my webspace? Does it work with other snap versions?

Would people be able to up the rest of the snap files to my space?

[edcetera]

For what its worth

reByte needs a cutomer relations department

I wrote a whole story just now and erased it, about a rebyte fiasco and decided that they were so much trouble to deal with then that I decided I would just mention;
The rebyte, and the computer you need to make a nearly good file server costs as much as the Buffalo Tech devices see links below;
Bufallo300 gig (http://http://www.buffalotech.com/products/product-detail.php?productid=97&categoryid=19)
or the
Buffalo 1 Terrabyte (http://http://www.buffalotech.com/products/product-detail.php?productid=97&categoryid=19)

Thanks

Sincerely / Ed

I have nothing to do with Bufallo and I own a Snap server 2000 and a 4100, sold my rebyte on ebay and gave the computer I built for it to a neighbourhood budding geek boy.

/ Ed

===========================

Thanks Leo,
Aznwizkid [Jason ] and I spoke, and he has used the Winhex program to dup Tivo Disks very successfully. I did use Winhex to apply one of the Snap2200 bin images to a Snap drive with success instead of the Knoppix dd method.
Unfortunately, I couldn't use his Snap1000 image which had the 4.x software already installed.
I was able to get all my data finally by using a ghost clone which for some reason let the Snap have access to all the files. Something was still flaky as the data was devilishly hard to get off the server. Kept losing the copy during download if it was over 25mb.

New 200GB drives with 3.4.805 are working fine now in Mirror mode.
thanks for the input..... Think I'm still going to reByte. Don't trust my Snap any longer.

[Leomania]

Can i ask where the 2000 bios update came from on my webspace? Does it work with other snap versions?
Hi Sam,

Did someone mention success in updating their BIOS version? During my OS updates the BIOS version stayed at 2.0.252, no change there at all. The forum contains a good collection of knowledge about what certain OS versions contain feature-wise, but it sure seems that the BIOS versions are much more of an unknown.

- Leo

[blue68f100]

Does anyone know how to upgrade from 1.1.0 to 2.0.0? Is it even possible to upgrade the hardware version? Can upgrading to a new SOFTWARE version also upgrade the BIOS and HARDWARE?

Many thanks...

Sid2000

I have the bios upgrade that will take you to 1.2.180 . This version does not enable LBA,, HD >137gig. But is required for the update to v 2. I have been looking for the update to v2. The upgrade process requires you to put your server in to updated mode 4 flashs with the reset, take about 30 sec to get active then you run the biosupdat.exe. It will ask for the IP address and off it goes, takes less than 5 minutes. I know that some hardware can not be updated, hardware restriction.

If need be I can upload it to snapserver that has most of the update avaliable.

I hope this helps.

blue68f100

[blue68f100]

Files system is XFS i believe from what snap tech told me.

Can i ask where the 2000 bios update came from on my webspace? Does it work with other snap versions?

Would people be able to up the rest of the snap files to my space?

I dont know which ones you have. BIOS upgrade I got from SnapApplance were only good for the 1000 & 2000. I had 2. One took verson 1 up to 1.1, then the second wone to 1.2.180 . These models have software loaded in rom/bios. Upgrade are easy. Just install new drives and the server takes care of the formating/setup. 1100/2200 OS is stored on the hard drive, the resaon for having a image file of your hard drive. If it fails you loose you OS. I was talking to a person that use to be a snap tech. He said there was an update to take 1.2.180 to v2. I'm still looking for that.

I hope this helped.

Blue68F100

[Sid2000]

Sid2000

I have the bios upgrade that will take you to 1.2.180 . This version does not enable LBA,, HD >137gig. But is required for the update to v 2. I have been looking for the update to v2. The upgrade process requires you to put your server in to updated mode 4 flashs with the reset, take about 30 sec to get active then you run the biosupdat.exe. It will ask for the IP address and off it goes, takes less than 5 minutes. I know that some hardware can not be updated, hardware restriction.

If need be I can upload it to snapserver that has most of the update avaliable.

I hope this helps.

blue68f100

Thanks but my snap is already running bios ver 1.2.180. Here is my snap's info:

Software: 3.4.803
Hardware: 1 1 0
Bios: 1.2.180

I can change the hardware from 1 1 0 to 2 0 0 but I'm having problems trying to upgrade to version 4. I've tried running the following upgrades:

ver 4.0.829
ver 4.0.830
ver 4.0.855

but all above versions gave me an error. If there's anyone who can help me with this I'll be very thankful. My snap is still running but I just wat to upgrade to a larger HD capacity (2X300GB).

Thanks alot...

[admin69]

If you want either S2S (no code) or Snap Extensions here they are:

**** DOWN *****

I dont have an image for the os on a hd yet.

I had a copy of a modified java applet that I found somewhere and had my Snap 4000 get hit by lightning. Needless to say, all data was lost and I didn't have another copy of that software anywhere else. These may have been the links I used but no they longer work. Can anyone point me in the right direction? tia

[admin69]

Right, another breakthrough by me. First i brought you snap os v4. Now i brin S2S with no license!!!!!!

Download it here @ ***********************

Only 2 problems, when you click close it shows errors, dunno how to get round this, other than you can get out by clicking home in the top right corner. The other is there is no help file.

Will look into these

Tried this link to no avail... Is the file mirrored somewhere else?

[admin69]

I upgraded the OS to 4.0.860, have 256MB RAM, installed 300GB ATA100 Seagate drives (originals were 30GB) and have an early version Quantum 4000 - #70700042-001 (pretty sure it requires master / slave config #242 (http://forums.procooling.com/vbb/showpost.php?p=123401&postcount=242) ).

:cry: All went well *UNTIL* I set up a RAID 5 array (it has no errors when configured with individual disks). I now get an error that the logical drive 60000 (RAID array) cannot synchronize. I have "broken" the set and reconfigured twice and it does the exact same thing. :shrug: Any ideas?

UPDATE: I again went to this set of directions #105 (http://forums.procooling.com/vbb/showpost.php?p=113921&postcount=105) and followed them exactly. Even though another post (#242, etc.) talked about using master / slave and my original drives were configured that way, I am using cable select now. Originally I thought that cable select was keeping my 4000 from booting. I left it alone for ~ 5 min. and now I have a steady disk activity light and no system light. I cannot ping nor open the web interface to the Snap 4000 but I believe that is because the system light is off. I plan on waiting the 23+ hours like #105 talked about and see if mine behaves correctly then. I'll keep everyone posted...


More info now:

"About" page:
Model 4000 series
Software 4.0.860 (US)
Hardware 2.0.1
BIOS 2.0.282
Framework 1.2
VM 14.3


Disk Status:
RAID5 - Large data protection disk
OK Unknown disk operation error.


Error Log:
E File System : Failed to resynchronize logical set 60000, error -1 Disk 60000 27/7/2005 5:44:02 PM
I File System : Format complete Disk 60000 27/7/2005 5:43:32 PM
I File System : Opened FDB for device 0x60000 Disk 60000 27/7/2005 5:43:32 PM
I File System : All ACLs for device 0x60000, reset to defaults Disk 60000 27/7/2005 5:43:32 PM
I File System : Successfully initialized empty FDB for device 0x60000 Disk 60000 27/7/2005 5:43:32 PM
I File System : Process formatting device /dev/rraid0 Disk 60000 27/7/2005 3:58:52 PM
I File System : Closed FDB for device 0x60000 Disk 60000 27/7/2005 3:58:52 PM



Debug:
07/28/2005 7:18:23 Command: info devices

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

Logical Device: 1000E Position: 0 JBOD Size (KB): 32296 Free (KB): 23936 Private Mounted
Label:Private Contains system files only
Unique Id: 0x414700757C551001 Mount: /pri2 Index: 13 Order: 1
Partition: 1000E Physical: 1000F FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 1000F Drive Slot: 1 IDE Size (KB): 293036032 Fixed

Logical Device: 60000 Position: 1 RAID Size (KB): 862254296 Free (KB): 861391968 Public Mounted
Label:RAID5 Large data protection disk
Unique Id: 0x3B3E426E22460FD1 Mount: /0 Index: 0 Order: 2
Partition: 10000 Physical: 10007 R 60000 Size (KB): 291402712 Starting Blk: 204037 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 293036032 Fixed
Partition: 10008 Physical: 1000F R 60000 Size (KB): 291402712 Starting Blk: 204037 Public
Physical: 1000F Drive Slot: 1 IDE Size (KB): 293036032 Fixed
Partition: 10010 Physical: 10017 R 60000 Size (KB): 291402712 Starting Blk: 204037 Public
Physical: 10017 Drive Slot: 2 IDE Size (KB): 293036032 Fixed
Partition: 10018 Physical: 1001F R 60000 Size (KB): 291402712 Starting Blk: 204037 Public
Physical: 1001F Drive Slot: 3 IDE Size (KB): 293036032 Fixed

[Roadster-2]

Help !!
Through the many helpful posts here I have tried upgrading the original 20Gb drive to an ATA133 120Mb and more recently an ATA100 40Gb. I have used both the early small version of Dolly (with a DOS strartup disk) and the later bootable CD-Rom version.

when I look at the Config Devices Info results I can see that it has not copied the Private partition. Consequently if the copy is made the boot drive it doesn't boot and just sits there with the lights flashing until I remove the power connector (after 24 hours the first time).

My software version is only 3.0.566 but I am reluctant to upgrade this on the original drive - it's on its last legs and I don't want to lose it. I was hoping to copy it and then upgrade the software.

Config results are -

Logical Device: 10000 Position: 1 JBOD Size (KB): 19496984 Free (KB): 19265840 Public Mounted
Label: Drive1 Single disk
Unique Id: 0x6E3E702C690BAB90 Mount: /0 Index: 1 Order: 1
Partition: 10000 Physical: 10007 FS Size (KB): 19767776 Starting Blk: 21124 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 19937792 Fixed

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

Logical Device: 10008 Position: 2 JBOD Size (KB): 19496984 Free (KB): 19265840 Public Mounted
Label: Drive2 Single disk
Unique Id: 0x6E3E702C690BAB90 Mount: /1 Index: 2 Order: 2
Partition: 10008 Physical: 1000F FS Size (KB): 19767776 Starting Blk: 21124 Public
Physical: 1000F Drive Slot: 1 IDE Size (KB): 19937792 Fixed

What am I doing wrong to not get the Private partition ?

[bumpyone]

Hello Ray

What OS software is in your 2000,
mine is 3.4.803
hardware 2.0.0
Bios is 2.0.282

I have 4.0.829 here but wonder if its neccessary to do an upgrade to 2x 250 gig drives.

What are your thoughts regarding these parameters above.

Thanks / Ed

Ed,

Here is my information from the about screen on the server:

Model Software Hardware Server # BIOS
2000 series 4.0.860 (US) 2.0.0 #### 2.0.282

I started out with version 3.4.x. I was able to install the upgrade to 4.x and then installed the new drive, one at a time. I know there are many post about doing various steps but took the KISS (keep it simple stupid) approach first and it worked.
I was in the same boat, did I spend the cash on two drives that may or may not work. I bought my 160 at Fry's for $99.00 with $40.00 rebates.

Ray

[blue68f100]

Has anyone figured how to recovery when the server will not connect to the lan. I had an upgrade go south. The unit powers up, access disk, but no NET light.

Looking over the Mother Board I found a RS232 Serial Port header. Has any one tested this port. Chip MAX241CAT.

There is also a Floppy Disk Controller on board to, SMC FDC37C669QF P.

On the 2000 I think that the software is loaded in to the AM29F800BT , boot sector flash memory.

There are also to jumpers on the board, JP1 and JP6, has any one figured out what these are used for? Reset ? Forced Disk Boot? Load software from disk?

Blue68F100

[Sid2000]

I'm new to this so please excuse me for what I am about to ask. Can anyone please tell me how I can retrieve hidden files and folders from my snap server? If it is not possible? Does anyone have the help file for a snap server?

I have 2 old 7 GB drives that works great but I upgraded to 2 80GB drives to increase capacity. The upgrade was successful but when I click on help, i get an error message of file not found then instructs to use assist to upload the help file. I don't have the file so there's nothing to upload. It also states that I can go out on the web and download it. When I click on the provided link, it takes me to adaptecs web site which does not have the file available for download.

I hope comeone can help me. Many thanks...

[yvette176]

I upgraded the OS to 4.0.860, have 256MB RAM, installed 300GB Seagate drives (originals were 30GB) and have an early version Quantum 4000 - #70700042-001 (pretty sure it requires master / slave config).

:cry: All went well *UNTIL* I set up a RAID 5 array (it has no errors when configured with individual disks). I now get an error that the logical drive 60000 (RAID array) cannot synchronize. I have "broken" the set and reconfigured twice and it does the exact same thing. :shrug: Any ideas?

(snip)



i'm not sure about your opsys settings; i gave up on getting mine to work and finally built my own servers with six 300Gb drives in each, in a RAID10 config. i never fully resolved this problem with my Snap Server 4000's.

the Snap needs memory in which to build the RAID arrays. i bumped my memory up to 256Mb, which i had on-hand. it may allow more memory than that; i'm not sure if i remember whether i read that you can only upgrade to 256Mb max or if i quit at 256Mb because i didn't want to buy memory for an aging device that was running in PIO mode and might not accept the memory in the first place.

despite the memory upgrade, after a power-on i would randomly get "rebuilding" messages - which were unacceptable. this only happened in RAID5, iirc; when i split the box into two stripe sets, then the problem went away. however, i needed one massive array, not two smaller arrays. and taking 26+ hours to rebuild the arrays in PIO mode really... was not all that "desirable", to be polite.

so i spent the money for the two extra drives, raid adapter, case with dual power supplies, twin gigE cards, and an OEM copy of W2K and i was so delighted that i then built an exact duplicate of that system! so now i run two W2k (pro) boxes, each with 900Gb of RAID 10 and teamed gigE throughput, and Robocopy sync them four times a day. it's not a perfect solution, but hey, i haven't lost any data, and i've got roughly 2Tb on-hand. nowadays, with 400Gb drives available, you could have 2.5Tb on-hand.

sorry i can't provide you with a resolution....
hth
Yvette

[aznwizkid]

Has anyone figured how to recovery when the server will not connect to the lan. I had an upgrade go south. The unit powers up, access disk, but no NET light.

Blue68F100

I had that happen, I just used the hard reset, where you get into a reset mode. This is quoted from their manual

To reset the server settings:
1 Turn the Snap Server off (as described on page 7) and
wait for all of the lights to turn off.
2 Press and hold down the Reset button. While you are
still pressing Reset, turn the Snap Server back on; wait
until both the System and Disk lights start flashing in
sync. (To press the Reset button, push a pencil point or
similar object into the reset button.)
3 Release the Reset button.
4 To select the settings you want to clear and reset, briefly
press the Reset button:
Once to clear the server's IP address.
Twice to clear the Administrator password.
Three times to clear the server's network settings.
Four times to clear all system settings.
5 Watch the Disk light and verify that the number of times
it flashes corresponds to the number of times you
pressed the Reset button. For example, if you pressed
Reset three times to clear the network settings, the
Disk light should flash three times repeatedly to
confirm the reset. If the number of flashes exceeds the
number you intended, repeat steps 4 and 5 of this
procedure.
6 When the light confirms the level of reset you intended,
press and hold down the Reset button until both the
System and Disk lights turn off, and then release the
Reset button. The server then restarts, and resets the
settings you cleared to the factory defaults.

If you have already tried that then I don't know.

[blue68f100]

Help !!
Through the many helpful posts here I have tried upgrading the original 20Gb drive to an ATA133 120Mb and more recently an ATA100 40Gb. I have used both the early small version of Dolly (with a DOS strartup disk) and the later bootable CD-Rom version.

when I look at the Config Devices Info results I can see that it has not copied the Private partition. Consequently if the copy is made the boot drive it doesn't boot and just sits there with the lights flashing until I remove the power connector (after 24 hours the first time).

My software version is only 3.0.566 but I am reluctant to upgrade this on the original drive - it's on its last legs and I don't want to lose it. I was hoping to copy it and then upgrade the software.

Config results are -

Logical Device: 10000 Position: 1 JBOD Size (KB): 19496984 Free (KB): 19265840 Public Mounted
Label: Drive1 Single disk
Unique Id: 0x6E3E702C690BAB90 Mount: /0 Index: 1 Order: 1
Partition: 10000 Physical: 10007 FS Size (KB): 19767776 Starting Blk: 21124 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 19937792 Fixed

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

Logical Device: 10008 Position: 2 JBOD Size (KB): 19496984 Free (KB): 19265840 Public Mounted
Label: Drive2 Single disk
Unique Id: 0x6E3E702C690BAB90 Mount: /1 Index: 2 Order: 2
Partition: 10008 Physical: 1000F FS Size (KB): 19767776 Starting Blk: 21124 Public
Physical: 1000F Drive Slot: 1 IDE Size (KB): 19937792 Fixed

What am I doing wrong to not get the Private partition ?

Roadster-2

From what I see you are upgrading a 2000, the 2200 I think start at 160/240 gig. You do not need to install the boot tracks on a 2000 server. From all of the threads, and experience from upgrading my initialy, the easyest way is to set the unit up as RAID 1. This way you can fail 1 drive at a time. Installing new ones one at a time. I took the high risk mode by replacing both drives at once. The only problem I had was that it took hours to format both drives this was with v3.4.803, went with out an hitch. Start with the second drive. I also discovered that the drive works best when using Partition magic to prepare the drives, format pri/fat32 or unformated. You should be able to login to the servers Disk Utility and check on the drive status. Once completed powerdown and change the other drive. This procedure works on the 2200 too.

All of the threads say that a ATA 133 will not work. You will have to use the utility software to change the speed prior to installation.

Good Luck

Blue68f100

[blue68f100]

I had that happen, I just used the hard reset, where you get into a reset mode. This is quoted from their manual

To reset the server settings:
1 Turn the Snap Server off (as described on page 7) and
wait for all of the lights to turn off.
2 Press and hold down the Reset button. While you are
still pressing Reset, turn the Snap Server back on; wait
until both the System and Disk lights start flashing in
sync. (To press the Reset button, push a pencil point or
similar object into the reset button.)
3 Release the Reset button.
4 To select the settings you want to clear and reset, briefly
press the Reset button:
Once to clear the server's IP address.
Twice to clear the Administrator password.
Three times to clear the server's network settings.
Four times to clear all system settings.
5 Watch the Disk light and verify that the number of times
it flashes corresponds to the number of times you
pressed the Reset button. For example, if you pressed
Reset three times to clear the network settings, the
Disk light should flash three times repeatedly to
confirm the reset. If the number of flashes exceeds the
number you intended, repeat steps 4 and 5 of this
procedure.
6 When the light confirms the level of reset you intended,
press and hold down the Reset button until both the
System and Disk lights turn off, and then release the
Reset button. The server then restarts, and resets the
settings you cleared to the factory defaults.

If you have already tried that then I don't know.


Tried that, did not help.

Blue68F100

[blue68f100]

Tried that, did not help.

Blue68F100

I have recoverd from my BIOS/Server not found/Lost.
I was playing around with the J1 & J6 jumpers on the motherboard. One of the jumpers caused the server to shut down NOW. The other I do not know if it had an affect on my recovery or not. Since I could not find the server, after several resets. I decided to format the hard drives, to remove any corruption I may had down.

The unit took 5-10 minutes before the harddisk started formating, I only installed 1 drive.

I was still having problem on startup, the system ether goes in to panic mode or starts disk check on the mirror drive.

A X Snap service tech said the extra ports (serila etc.) are turned off to speed up operations.

I did find someting of interest for you telenet users.

08/01/2005 13:43:44 Command: info nvram

NFS: ENABLED
HTTP: ENABLED
Telnet remote console: DISABLED (0)
RCP server: DISABLED (0)
BOOTP server: DISABLED
HTTPd Port: 80
SMTP Port: 25
SCSI Termination: INTERNAL, external devices illegal.
Protocol Daemons: 32
Raid Cache: 0
Raid Threads: 0
Current Code Page: 437 = US English
File System FSync: ENABLED
FileSystem Full Alert: 90%

It lookes like telenet may be an option.

I hope this info will help someone.

I am still trying to figure how I can reload the software in nvram.

Thanks for all of the info.

David :)

[blue68f100]

Sound like you are having the same type of problem I am having on a 2000. I can only run single disks NO RAID 0 or 1. If I try it hangs up. Have to wipe disk in order to recover.

David

[deadsenator]

Well, I found v4 on Adaptec's site. But the 860 rev of v4 won't load since I'm wayyyy down the chain on v3 (3.4.803 to be exact and v2.0.252 bios). Where can I get the fabled 'keyed' upgrades? Like 830 or 855? Googling has brought zero results.

Also, will an upgrade get me past the 137GB barrier? I've got 250's lying around (though 5400rpm drives are better for cooling). But first, I need an upgrade....

Thanks, everyone!

DS

[deadsenator]

Well, I found v4 on Adaptec's site. But the 860 rev of v4 won't load since I'm wayyyy down the chain on v3 (3.4.803 to be exact and v2.0.252 bios). Where can I get the fabled 'keyed' upgrades? Like 830 or 855? Googling has brought zero results.

Also, will an upgrade get me past the 137GB barrier? I've got 250's lying around (though 5400rpm drives are better for cooling). But first, I need an upgrade....

Thanks, everyone!

DS


Well, thanks to blue68f100 and Leomania, I've downloaded all the appropriate software, but I consistently get the error:

"This file is not a valid upgrade for your server."

It matters not which file I try. It matters not which version of Assist I use. This is very frustrating. What am I missing?

[boogie]

I have replaced my 80gb with a 320gb wd drive using winhex to clone. It boot up okay but I only see a 80gb drive and cannot change its size, is there anything special I need to do ? upgrade firmware or something? Thanks all suggestions are highly appreciated.

[blue68f100]

I have replaced my 80gb with a 320gb wd drive using winhex to clone. It boot up okay but I only see a 80gb drive and cannot change its size, is there anything special I need to do ? upgrade firmware or something? Thanks all suggestions are highly appreciated.

You need to get into debug and issue a reinit command.
in debug issue "config devices info"
then
Type "config devices format ????? /reinit"
where ????? = to your drive id, 10000, 10008, ...

I hope this helps you.

David

[upstech]

Well, thanks to blue68f100 and Leomania, I've downloaded all the appropriate software, but I consistently get the error:

"This file is not a valid upgrade for your server."

It matters not which file I try. It matters not which version of Assist I use. This is very frustrating. What am I missing?


v4.0.860 can only be used to upgrade from 4.0.855. I ran into the same problem until I finally received a copy of 4.0.855. Once you upgrade to 855 you can then upgrade to 860.

[boogie]

You need to get into debug and issue a reinit command.
in debug issue "config devices info"
then
Type "config devices format ????? /reinit"
where ????? = to your drive id, 10000, 10008, ...

I hope this helps you.

David

Hi and thanks for the help. Unfortuneatly I have already tried this and it does not work. I get an error that keeps saying switch is invalid for that drive. I can format it but can not /reinit or remove drive from mirror set.

[kogvos]

I get exactly the same error on a Dell 705N which has been told it's a 4100 that was originally a 240G model and I have put 4 x 160G drives in. It takes several hours to try to configure the Raid 5 which has about 385G in it but it then fails in exactly the same manner.

In JBOD mode, I get 128M on each drive as you would expect and I can add thm all together as a large single disc OK

Original OS was 3.4.803 and I have just upgraded to 4.0.860 (thank you very much poogles_uk) It has the original 64M of RAM.

By the way, what improvements does OS4 bring? Everything looks the same, same options in the various screens, etc and the 31 character limitation on the filenames.

Regards,

kogvos

I upgraded the OS to 4.0.860, have 256MB RAM, installed 300GB ATA100 Seagate drives (originals were 30GB) and have an early version Quantum 4000 - #70700042-001 (pretty sure it requires master / slave config #242 (http://forums.procooling.com/vbb/showpost.php?p=123401&postcount=242) ).

:cry: All went well *UNTIL* I set up a RAID 5 array (it has no errors when configured with individual disks). I now get an error that the logical drive 60000 (RAID array) cannot synchronize. I have "broken" the set and reconfigured twice and it does the exact same thing. :shrug: Any ideas?

UPDATE: I again went to this set of directions #105 (http://forums.procooling.com/vbb/showpost.php?p=113921&postcount=105) and followed them exactly. Even though another post (#242, etc.) talked about using master / slave and my original drives were configured that way, I am using cable select now. Originally I thought that cable select was keeping my 4000 from booting. I left it alone for ~ 5 min. and now I have a steady disk activity light and no system light. I cannot ping nor open the web interface to the Snap 4000 but I believe that is because the system light is off. I plan on waiting the 23+ hours like #105 talked about and see if mine behaves correctly then. I'll keep everyone posted...


More info now:

"About" page:
Model 4000 series
Software 4.0.860 (US)
Hardware 2.0.1
BIOS 2.0.282
Framework 1.2
VM 14.3


Disk Status:
RAID5 - Large data protection disk
OK Unknown disk operation error.


Error Log:
E File System : Failed to resynchronize logical set 60000, error -1 Disk 60000 27/7/2005 5:44:02 PM
I File System : Format complete Disk 60000 27/7/2005 5:43:32 PM
I File System : Opened FDB for device 0x60000 Disk 60000 27/7/2005 5:43:32 PM
I File System : All ACLs for device 0x60000, reset to defaults Disk 60000 27/7/2005 5:43:32 PM
I File System : Successfully initialized empty FDB for device 0x60000 Disk 60000 27/7/2005 5:43:32 PM
I File System : Process formatting device /dev/rraid0 Disk 60000 27/7/2005 3:58:52 PM
I File System : Closed FDB for device 0x60000 Disk 60000 27/7/2005 3:58:52 PM



Debug:
07/28/2005 7:18:23 Command: info devices

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

Logical Device: 1000E Position: 0 JBOD Size (KB): 32296 Free (KB): 23936 Private Mounted
Label:Private Contains system files only
Unique Id: 0x414700757C551001 Mount: /pri2 Index: 13 Order: 1
Partition: 1000E Physical: 1000F FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 1000F Drive Slot: 1 IDE Size (KB): 293036032 Fixed

Logical Device: 60000 Position: 1 RAID Size (KB): 862254296 Free (KB): 861391968 Public Mounted
Label:RAID5 Large data protection disk
Unique Id: 0x3B3E426E22460FD1 Mount: /0 Index: 0 Order: 2
Partition: 10000 Physical: 10007 R 60000 Size (KB): 291402712 Starting Blk: 204037 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 293036032 Fixed
Partition: 10008 Physical: 1000F R 60000 Size (KB): 291402712 Starting Blk: 204037 Public
Physical: 1000F Drive Slot: 1 IDE Size (KB): 293036032 Fixed
Partition: 10010 Physical: 10017 R 60000 Size (KB): 291402712 Starting Blk: 204037 Public
Physical: 10017 Drive Slot: 2 IDE Size (KB): 293036032 Fixed
Partition: 10018 Physical: 1001F R 60000 Size (KB): 291402712 Starting Blk: 204037 Public
Physical: 1001F Drive Slot: 3 IDE Size (KB): 293036032 Fixed

[blue68f100]

Hi and thanks for the help. Unfortuneatly I have already tried this and it does not work. I get an error that keeps saying switch is invalid for that drive. I can format it but can not /reinit or remove drive from mirror set.


You will need to unmount the drive before the issuing the reinit.

David

[jrmvt]

OK, I'm at a complete loss, so I thought I would try running it past the group here.

Back in the Spring, I had my Dell 705N die on me. Finally got it to tell me that one of the four drives in my RAID5 array was bad. Replaced it - still didn't work. :eek: I limped by, storing the data on our SBS2003 server until I had more time to play with it.

Last week was that time. I decided since it was dead anyway and I didn't need the data on it anymore (I had a good backup thankfully), I would do a mind-wipe on it and turn it into a SNAP 4100. I broke the RAID5 set up into 4 individual drives, did the debug trick to make it forget it was a Dell, then proceeded with upgrading the OS. Once all of that was done, I ran the Disk Check on the 4 individual drives and all checked out OK.

So I built the RAID 5 Array and copied the data back over. A few days later, I started getting complaints that a lot of the picture files were corrupt. So I ran the disk check on the RAID 5 Array and got a fatal error while it was checking the cylinder groups. I broke the RAID apart again and ran the disk check on each drive - all registered as OK. Rebuilt the RAID and ran the disk check - Fatal Error! :mad:

I checked the Knowledge base on Adaptec's website and it says that for severe errors, sometimes you have to run the Disk check with error correction activated repeatedly. So after 15 successive runs, I was still getting errors. I broke the RAID apart again, thinking that if I rebuilt the RAID 5 array utilizing only 3 of the disks instead of all 4, that maybe I could narrow down if a bad drive was causing the problem. Ran Disk Check on the 3-disk RAID 5 Array and on the remaining disk and got errors on both! I tried again, setting it up so that the one non-RAID disk was the new drive I just added and the 3-drive RAID5 array was the old drives - still errors all around! :mad: :cry:

So, I'm guessing the problem is one of three things. 1) There are multiple bad hard drives that need to be replaced. 2) The OS is corrupt, in which case I think I'm screwed because the only non-upgrade version I have is a 3.x version from Dell and SNAP does not allow you to roll back from a 4.x version to a 3.x version. 3) There is another hardware error causing the problem (RAM, Promise controller, CPU, etc.)

Anyone have any ideas what I should try next? Thought about pulling each hard drive out one at a time and formatting it on another computer, but I'm not really convinced that the problem won't just perpetuate as I put each drive back in.

Thanks,
J. R.

[bob156]

I recently upgrade our Snap Server 4100 to o/s v3.4.803, and have been having problem with the drives ever since. Whenever I boot it up, the first 2 drives come up ok. The 3rd and 4th drives lights come up as yellow. On the web browser configuration screen, on the first 2 drives appear.

I have rebooted it, and reset the the Snap Server (using the reset button 4x), and it comes with the same problem - 2 drives OK and 2 bad. I swapped the IDE cables around a bit, and have found that the first 2 drives always come up ok. Here's the results:

-----------------
IDE 1 - empty
IDE 2 - empty
IDE 3 - 40GB Drive
IDE 4 - 40GB Drive

I see 2 drives...

-----------------
IDE 1 - empty
IDE 2 - 40GB Drive
IDE 3 - 40GB Drive
IDE 4 - 40GB Drive

I see 2 good drives, IDE2 and IDE3. IDE4 status light is yellow.

-----------------
IDE 1 - 40GB Drive
IDE 2 - 40GB Drive
IDE 3 - 40GB Drive
IDE 4 - 40GB Drive

I see 2 good drives, IDE1 and IDE2. IUDE3 and IDE4 status lights is yellow.

Has this happened to anyone else? Does anyone know what I can do to fix the problem?

[Mattallyc]

After 1.5 days I've finally come to the end of this thread(!) but have not found a solution to my problem. The closest mention is Neils post (#649).

I've two snap servers. A 1000 and an 1100. The HDD in the 1100 died so I bought a new one and cloned the good drive in the 1000 to it (thanks to this thread for the info on this). The new drive works fine in the 1000 server (gone up to 80GB from 30GB).

The problem is still with the 1100. Either drive fails to work in it. When I apply power to the 1100 it comes on straight away. Waiting a bit longer (10 - 20 secs) it settles down and I get the following led pattern:

System: on 2 secs / off 0.5 sec
Link: always on
Net: intermittant rapid flashing
Disk: copies system led except double flash in on period

Assist can't find the drive and I've IP scanned the network to try and find it to no avail so its not getting an IP address. It won't perform a reset either. I don't know the details for the 1100 as I can't access it. The details for the 1000 are:

Software version: 3.4.803(US)
Hardware version: 3.12
Bios: 2.1.366

Anyone got any suggestions??

Thanks in advance,

Matt.

[Mattallyc]

Further to my post above (#699) I've managed to fix my snap 1100 thanks to help from blue68f100 (thanks again David!)

Should anyone else have a similar problem it is worth noting that an image of a 1000 will not work on an 1100. You can use a 2200 image on an 1100 server though and it will work. My solution was to get an image of a 2200 (search this thread) and use knoppix to transfer it (again see earlier in this thread).

Hope this helps.

Regards,
Matt.

[re3dyb0y]

Well, I found v4 on Adaptec's site. But the 860 rev of v4 won't load since I'm wayyyy down the chain on v3 (3.4.803 to be exact and v2.0.252 bios). Where can I get the fabled 'keyed' upgrades? Like 830 or 855? Googling has brought zero results.

Also, will an upgrade get me past the 137GB barrier? I've got 250's lying around (though 5400rpm drives are better for cooling). But first, I need an upgrade....

Thanks, everyone!

DS

They are on the snap server ftp site (ours)

Email me and i will pass on the details too you

[cborjon]

I did one of these upgrades on an original Snap 1000 a while back with the help of this forum. I was thinking about getting a Snap 2000 and doing the upgrade on it and I see from this forum that the 137mb barrier has been broken.
Two questions:
1. Are the drives that are being used ATA100 or can an ATA133 be used?
2. It seems the key is the OS upgrade for breaking the 137mb. Is this correct?

Thanks,
Chris

[re3dyb0y]

I presume you mean 137GB

It would seem so with Os v4, but not always, give it a try and see. Dont go all the way to 4.0.860, as that seems to cause a few problems.

I think better results have been obtained with ATA100, but ATA133 have been used

[shfawaz]

I just upgraded my Snapserver 4100 to Snap OS 4.0805 using the upgrade file and apparently the upgrade took without a hitch. However my disks are no longer accessable. Looking at Disk status it says "Uninitialized. Disk has not been validated yet. Please wait."

It has been like that for over two hours. This is a Raid 5 setup with four discs. I had recently replaced Disk one I with a 120Gb drive prior to this upgrade and set it up as a spare and the Raid used it and joined it with the other three, and it has been working fine with the three other 80Gb drives without any problems.

Am I missing something here? Is there something I should do to get the Snap to initialize? When the unit boots up, it checks all four drives and no drive lights stay on, nor does the disk light stay lit after it has rebooted.

In the log, it shows: File System : Set-up of logical disk failed. Device ID: 60000 (hex)

[shfawaz]

I just upgraded my Snapserver 4100 to Snap OS 4.0805 using the upgrade file and apparently the upgrade took without a hitch. However my disks are no longer accessable. Looking at Disk status it says "Uninitialized. Disk has not been validated yet. Please wait."

It has been like that for over two hours. This is a Raid 5 setup with four discs. I had recently replaced Disk one I with a 120Gb drive prior to this upgrade and set it up as a spare and the Raid used it and joined it with the other three, and it has been working fine with the three other 80Gb drives without any problems.

Am I missing something here? Is there something I should do to get the Snap to initialize? When the unit boots up, it checks all four drives and no drive lights stay on, nor does the disk light stay lit after it has rebooted.

In the log, it shows: File System : Set-up of logical disk failed. Device ID: 60000 (hex)


Figured it out. The upgrade didn't like the oddball hard drive size compared to the stock 80Gb units, so I unplugged it entirely and voila! the Snap server is up and running like a charm. I replugged in the 120Gb unit, reformatted it, and now it is in the process of repatriating it into the raid. Best part is no data loss. Cool!

[mdguy]

I was recently sent a 'failing' snap server 2200. The data on the device is important to its owner, and I'm in the process of trying to recover whatever I can from the device.

I was provided with no documentation/software. I was only given the 2200 unit and its power supply. The system is no longer under warrantee.

From what I'm told, the device was left in its default raid configuration (raid 0).

The hard drives have been imaged in their original state, so messing around with various approaches to getting the data off is fine, plenty of spare hard drives witht he same LBA to use.

Heres where I need help:

Upon booting up, the system light comes on while the LAN light never does. There is some initial hard drive activity, but that doesnt last for more than a second or two.

If you modify the jumper settings on the hard drive you can get the system/disk lights to alternate. According to the snap appliance website this means you should call tech support... Not exactly helpful as the device is no longer under warantee. While the device is in this state, the lan light does come on and network activity is acknowledged by the activity light. The device itself does not appear to be addressable.

I have run through the process of 'resetting' the device through the sequence provided on the snap appliance website. The device resets fine by exhibits the same behavior as before the reset.

The options I have available (unless you all can come up with something else) seem to be either:

A) Buy a an identical 2200 and place the hard drives with the data into it. This is already in the works, but I still have time to also try:

B) Trying to rebuild the array manually to recover the data... This is where I need a lot more information maybe some of you could provide.

I am assuming (unless told otherwise) that the stripe was configured with IDE1 as the first device followed by IDE2. I'm also guessing (by analyzing the data on the drives looking for patterns) that the stripe size seems to be abnormally large (16384 sectors, or 8192KB). If this information is correct (which I have been unable to verify with any degree of certainty) I am still unable to determine the file system in use on these devices. I have heard that it is a variation of FFS (Open FFS?) or possibly UFS. Other snap devices I've worked with have used XFS. I can't seem to locate any clues on the drive that would point towards a valid partition table or information telling me what file system is in use. If I could determine what file system is in use, rebuilding the array (using the default settings) and mounting the raid image to recover the files may be possible.

So questions:

Has anyone successfully recovered the data off of a raid in this scenario? If so, how?
What file system is in use on the 2200 models?
What is the default stripe size for a raid 0 configuration?
Which is the first device in a 2 hard drive raid 0 default configuration?
Does the actual raid begin at an offset of the drive, or at the first sector?

Any other clues are welcome, I have some time before the replacement unit comes in to try more stuff out.

I made an effort to read every post that looked relevant in this thread, so I apologize if any of these questions have been answered before.

Thanks.

[re3dyb0y]

To my knowledge the only way that people have got data off is via another snap

The filesystem is believed to be XFS (as told by eu snap support)

[blue68f100]

I was recently sent a 'failing' snap server 2200. The data on the device is important to its owner, and I'm in the process of trying to recover whatever I can from the device.

I was provided with no documentation/software. I was only given the 2200 unit and its power supply. The system is no longer under warrantee.

From what I'm told, the device was left in its default raid configuration (raid 0).

The hard drives have been imaged in their original state, so messing around with various approaches to getting the data off is fine, plenty of spare hard drives witht he same LBA to use.

Heres where I need help:

Upon booting up, the system light comes on while the LAN light never does. There is some initial hard drive activity, but that doesnt last for more than a second or two.

If you modify the jumper settings on the hard drive you can get the system/disk lights to alternate. According to the snap appliance website this means you should call tech support... Not exactly helpful as the device is no longer under warantee. While the device is in this state, the lan light does come on and network activity is acknowledged by the activity light. The device itself does not appear to be addressable.

I have run through the process of 'resetting' the device through the sequence provided on the snap appliance website. The device resets fine by exhibits the same behavior as before the reset.

The options I have available (unless you all can come up with something else) seem to be either:

A) Buy a an identical 2200 and place the hard drives with the data into it. This is already in the works, but I still have time to also try:

B) Trying to rebuild the array manually to recover the data... This is where I need a lot more information maybe some of you could provide.

I am assuming (unless told otherwise) that the stripe was configured with IDE1 as the first device followed by IDE2. I'm also guessing (by analyzing the data on the drives looking for patterns) that the stripe size seems to be abnormally large (16384 sectors, or 8192KB). If this information is correct (which I have been unable to verify with any degree of certainty) I am still unable to determine the file system in use on these devices. I have heard that it is a variation of FFS (Open FFS?) or possibly UFS. Other snap devices I've worked with have used XFS. I can't seem to locate any clues on the drive that would point towards a valid partition table or information telling me what file system is in use. If I could determine what file system is in use, rebuilding the array (using the default settings) and mounting the raid image to recover the files may be possible.

So questions:

Has anyone successfully recovered the data off of a raid in this scenario? If so, how?
What file system is in use on the 2200 models?
What is the default stripe size for a raid 0 configuration?
Which is the first device in a 2 hard drive raid 0 default configuration?
Does the actual raid begin at an offset of the drive, or at the first sector?

Any other clues are welcome, I have some time before the replacement unit comes in to try more stuff out.

I made an effort to read every post that looked relevant in this thread, so I apologize if any of these questions have been answered before.

Thanks.

There are some firms that specialize in data recovery including RAID's. Toms Hardware Guide had an article on them last month. Like Mr Google_uk said the only other way is by another snap, but I think they need to be the same OS version. Snap has made XFS file systems changes with different OS's. After you reset to factory setting you need to use Assist to locate and set the drive up. Default is 2 shares. The jumpers should me set as master on both drives. I run RAID 1 so if a drive fails I don't loose any data.

David

[HLouie]

Could any user of the Snap Server 2200 EM the information of the power supply information. I know it a external unit similar to the 1000 and 1100.

Thank-you

[re3dyb0y]

ftp://**** DOWN *****/

Is the Snap FTP

It does annoy me when people say they have read all the posts and cant find working links

That has been posted by me and others a few times, and therefore is there

Im not bothered about giving it out, it just annoys me when peiople says' something like that

[re3dyb0y]

There are some firms that specialize in data recovery including RAID's. Toms Hardware Guide had an article on them last month. Like Mr Google_uk said the only other way is by another snap, but I think they need to be the same OS version. Snap has made XFS file systems changes with different OS's. After you reset to factory setting you need to use Assist to locate and set the drive up. Default is 2 shares. The jumpers should me set as master on both drives. I run RAID 1 so if a drive fails I don't loose any data.

David


It's Poogles

And anyway, mine are on C/s and it works

[dami2550]

OK, I've also read bunch of this thread, tried all kinds of workarounds and don't seem to get anywhere.

I have SnapServer 4100. Used to be BIOS 2.4.437, OS 3.4.807. Original 80GB hard drives.
Put WD 300GB hard drives in, 137GB each. no problems with creating RAID.

With help of Poogles (I swear I've tried that link long time ago, it didn't work, that's why I emailed you) I upgraded to 4.0.830. Same 137GB disks. Tried cable select, same issue. Tried reinit, still 137GB. Tried only single drive, same problem.

So I guess I just have wrong hardware, huh?

[re3dyb0y]

Thats fair enough, i was just making a point.

My FTP is down/has been down for a while, and aint going back up.

It would seem that you may have. Usually a reinit gives you some more space.

Some other work around may be avaliable

[boyelectric]

I have a 4000, Hardware 2.01, Bios 2.0.282, Software updated to 4.0.855, then .860.

The old drives are fine, raid is fine. Done the debug/ide command and the new drives (Hitachi 250GB) all come out at 137GB. They work fine like this, and I can make a raid fine, but just not the LBA support.

Does anyone have tricks for those of us who are left out in the cold?

I also tried adding the drives in one at a time or all at once, and still not seeing the full capacity.

I also have done the reinit, several times, I've even tried a cold restart to try to jog its little brain... no avail.

(4) Hitachi DeskStar 7K250 - 250 GB - ATA-100, 7200 rpm, 8MB buffer

[blue68f100]

I have a 4000, Hardware 2.01, Bios 2.0.282, Software updated to 4.0.855, then .860.

The old drives are fine, raid is fine. Done the debug/ide command and the new drives (Hitachi 250GB) all come out at 137GB. They work fine like this, and I can make a raid fine, but just not the LBA support.

Does anyone have tricks for those of us who are left out in the cold?

I also tried adding the drives in one at a time or all at once, and still not seeing the full capacity.

I also have done the reinit, several times, I've even tried a cold restart to try to jog its little brain... no avail.

(4) Hitachi DeskStar 7K250 - 250 GB - ATA-100, 7200 rpm, 8MB buffer

I remember reading on the forum that the LBA is locked out on the 4000. Snap did not want the 4000 out preform there newer 4100.

There is a "ide 48bitLBACounter" flag that is turned off. But I do not know the command to turn it on. Use the debug to set.

Poogles_uk may be better qualified to answer this question.

David

[spamman]

I am trying to convert my Snap 1100 into a Snap 2200 using the info supplied in the forum.

I have :
Added additional drive
debug mode
bios unlock
bios model 0
bios lock

I can now see 2 drives and format them. What I really want to do is configure them as JBOD (or raid0)
I was expecting there to now be a 'Configure Disks' option under disk utilities but there is not. I have tried a hard reset and have re-applied the firmware but still no option.

Has anyone got this to work?And if so what did I miss?

Can someone give the the url in snap that gives you the 'Configure Disks' page to see if I can forcibly get there . ie http://203.4.71.116/config?Func=xxxx

[INT 20h]

I am trying to convert my Snap 1100 into a Snap 2200 using the info supplied in the forum.

I have :
Added additional drive
debug mode
bios unlock
bios model 0
bios lock

I can now see 2 drives and format them. What I really want to do is configure them as JBOD (or raid0)
I was expecting there to now be a 'Configure Disks' option under disk utilities but there is not. I have tried a hard reset and have re-applied the firmware but still no option.

Has anyone got this to work?And if so what did I miss?

Can someone give the the url in snap that gives you the 'Configure Disks' page to see if I can forcibly get there . ie http://203.4.71.116/config?Func=xxxx

I got it to work once a few months ago. I wasn't able to get the configure disks option to pop up though so I used debug commands to set it up instead. The URL for Configure Disks (I pulled this off of my 2200) is:

http://snapserverIP/config?Func=DiskConfigureSend

Hope this helps.
Cheers,
INT 20h

[re3dyb0y]

Yeah.

I presume by updating the firmware you mean the OS?


Blue - I'll have to get back to you, its been a while since i played with my snap.

Rob (int 20h) may be able to help in the mean time.



Also, im going to have a look at altering the OS. Somepoint this weekend. Rob, if you got any further can you give me a shout to say what you've done!


Cheers


Sam

[Brooklyn]

Hello,

I just wanted to leave a message saying thank you to all who have posted information on modifying snap servers to accommodate larger drives. I have been looking for this information for a long time and this was the shining star find. I purchased a new snap server 1100 from ebay with a puny 80gb drive, and after following the helpful hints from previous posters, I was able to slap a nice 400gb seagate into it with absolutely 0 problems! Once again, thank you very much.

Oh, and here is how I did it in case that would help anyone else.

Made the digital dolly boot cd.
Removed snap HD and set it as master.
Set new larger drive as slave.
Connected them into my PC.
Booted from DD cd.
Chose copy raw data/partition.
Selected master as source, slave as destination.
Let it copy 3% of 80gb (2.4GB), then turned off PC.
Set the new drive as master and slapped it into the snap.
Logged into http://snapserver/config/debug and gave it the:
"config devices format 10000 /reinit" command.
Rebooted the snap and waited for the format.
Was greeted with a pleasing drive space of 377GB (lost quite a bit to format waste but oh well)
Thats it. Thanks again!

[re3dyb0y]

I dont think it is format waste

Most hard drives when formatted lose some space. So that would probably be about right, i have seen on 200gb drives, losing up to 13gb, and there aint really much you can do about it.

How come you let it copy 3%? Was that your guess on the OS and a bit more space?



Sam

[re3dyb0y]

Just did a port scan:
Started scan
192.168.0.200:21 -> ftp (File Transfer [Control]) -> 220 Service ready for new user...
192.168.0.200:110 -> pop3 (Post Office Protocol - Version 3) -> -ERR AVG POP3 Proxy Server: Cannot connect to the mail server!..
192.168.0.200:80 -> www-http (World Wide Web HTTP) -> HTTP/1.0 200 OK..Server: Snap Appliance, Inc./4.0.860..Content-type: text/html; charset=ISO-8859-15..Date: Sat, 01 Oct 2005 16:06:02 GMT....<HTML>.<HEAD>.<TITLE>Snap Server SNAPSERVER [Home]</TITLE>.<S
192.168.0.200:111 -> sunrpc (SUN Remote Procedure Call)
192.168.0.200:139 -> netbios-ssn (NETBIOS Session Service)
Stopping scan


Anyone got any ideas about putting telnet onto this?

[re3dyb0y]

I know the guardian os does support this

[re3dyb0y]

Another port/ip scan


Round Trip Time (RTT): <10 ms
Time To Live (TTL): 255
MAC: 00:C0:B6:0C:40:17 (MERIDIAN DATA, INC.)
Comment: Snap Server 192.168.0.200
Platform: 400
Version: 4.0
Roles: (4) LAN Manager workstation
LAN Manager server
Unix server
Windows NT/Windows 2000 server that is not a domain controller

Remote Supports Supported Remote Administration Protocol

Remote Time of Day Time of Day: 01/10/2005 17:11:32
System loaded: 01/10/2005 17:11:32
Time Zone: -60 minutes from the Greenwich Mean Time (GMT) zone

Shared ressources (8) ADMIN$
Drive1
Drive2
IPC$
Java$
OS_Private$
RPC$
WebRoot$

TCP ports (4) 21 ftp => File Transfer Protocol 220 Service ready for new user.

80 http => World Wide Web HTTP HEAD / HTTP/1.0
HTTP/1.0 200 OK
Server: Snap Appliance, Inc./4.0.860
Content-type: text/html; charset=ISO-8859-15
Date: Sat, 01 Oct 2005 16:11:43 GMT
<HTML>
<HEAD>
<TITLE>Snap Server SNAPSERVER [Home]</TITLE>
<SCRIPT LANGUAGE = "JavaScript">
<!-- Hide script from old browsers.
function _ShowAbout()
{
// open the About window
window.open("/config?Func=AboutSend","AboutSnap","toolbar=no,location=no,status=no,menubar=no,scroll bars=no,width=500,height=463,resizable=yes,depende nt=yes");
} //_ShowAbout()
// End the hiding here. -->
</SCRIPT>
</HEAD>
<BODY TEXT=#000000 LINK=#0033CC VLINK=#0033CC
TOPMARGIN="0" LEFTMARGIN="0" RIGHTMARGIN="0" MARGINHEIGHT="0" MARGINWIDTH="0"
STYLE="background: URL('/config/resource/Title_Bg.gif'); background-repeat: repeat-x; background-color: #CCCCCC">
<CENTER>
<TABLE WIDTH="100%" HEIGHT="64" CELLSPACING="0" CELLPADDING="0" BORDER="0">
<TR>
<TD WIDTH="1%" ALIGN="CENTER" VALIGN="CENTER" BGCOLOR="#FFFFFF">
<A HREF="javascript:_ShowAbout()" onMouseOver="window.status='Abou
t Snap Server'; return true;" onMouseOut="window.status=''; return true;"><IMG SRC="/config/resource/About.gif" ALIGN="TOP" NATURALSIZEFLAG="3" BORDER="0" ALT=""></A>
</TD>
<TD WIDTH="61%" ALIGN="CENTER" VALIGN="CENTER">
<TABLE WIDTH="100%" HEIGHT="100%" CELLSPACING="0" CELLPADDING="0" BORDER="0">
<TR>
<TD WIDTH="1%" ALIGN="CENTER" VALIGN="CENTER">&nbsp;

</TD>
<TD WIDTH="99%" ALIGN="LEFT" VALIGN="CENTER">
<FONT FACE="Arial" COLOR="#FFFFFF">
<FONT SIZE=+0 FACE="Arial"><B>SNAPSERVER</B></FONT>
<FONT SIZE=+0 FACE="Arial"><B>•</B></FONT>
<FONT SIZE=+0 FACE="Arial"><B>Home</B></FONT>
</TD>
</TR>
</TABLE>
</TD>
<TD WIDTH="38%" ALIGN="CENTER" VALIGN="CENTER" BGCOLOR="#3366CC">
<TABLE WIDTH="100%" HEIGHT="100%" CELLSPACING="0" CELLPADDING="0" BORDER="0">
<TR>
<TD WIDTH="45%" ALIGN="CENTER" VALIGN="CENTER">&nbsp;
</TD>
<TD WIDTH="40%"

110 pop3 => Post Office Protocol - Version 3
139 netbios-ssn => NetBios Session Service

UDP ports (4) 68 bootpc => Bootstrap Protocol Client
137 netbios-ns => NetBios Name Service
138 netbios-dgm => NetBios Datagram Service
161 SNMP => Simple Network Management Protocol

[Brooklyn]

Poogles,

As far as the 3%, yea.. im sure the OS wasnt larger than a 100MB or so, but I just did 3% cause I thought it was better to err on the large side.


Question: Since I have been playing with this thing for the past ten hours.. I have dumped about 170GBs onto it but it seems to peak at a transfer rate of 4.98MB/sec, man thats slow. Is everyone else getting something similar to that too? I can live with it because its alot of space up 24/7 but if there is a way to optimize it I would like to know. Thanks.

[re3dyb0y]

That sounds about what most people have got. Read joes article. well to windows anyway

I believe if you have NFS with linux box you can copy quicker


The OS is ~ 30mb in the .sup file

[blue68f100]

Just did a port scan:
Started scan
192.168.0.200:21 -> ftp (File Transfer [Control]) -> 220 Service ready for new user...
192.168.0.200:110 -> pop3 (Post Office Protocol - Version 3) -> -ERR AVG POP3 Proxy Server: Cannot connect to the mail server!..
192.168.0.200:80 -> www-http (World Wide Web HTTP) -> HTTP/1.0 200 OK..Server: Snap Appliance, Inc./4.0.860..Content-type: text/html; charset=ISO-8859-15..Date: Sat, 01 Oct 2005 16:06:02 GMT....<HTML>.<HEAD>.<TITLE>Snap Server SNAPSERVER [Home]</TITLE>.<S
192.168.0.200:111 -> sunrpc (SUN Remote Procedure Call)
192.168.0.200:139 -> netbios-ssn (NETBIOS Session Service)
Stopping scan


Anyone got any ideas about putting telnet onto this?

On most unix system, telnet is controlled with the inetd demon, throught the "inetd.conf" file located in /etc. Looking through my 2200 I was unable find them using the "ls" command. The /debug/info lists info inet. No telnet or inetd comands listed. PuTTY connection was refused.

I have the early BIOS update for the 2000, v 1.0 or 1.1 to 1.2.180 and the OS from v1 to v2 if needed. I believe you can jump from v2 to v4 directly. But the bios must be at least 1.2.180.

Has anyone had any problems when they change the CR2032 battery in the 1100/2200 models?

David

[misterbill]

Hello everyone.
I have a little bad news for the forum.
I am going to have to shut down the ftp site ftp://***************/

here in the very near future.
If there is anyone else that can host the files that would be great.
I'll leave them up for about one more week then it's gotta go.

Sorry!!

[re3dyb0y]

Ok, cheers for letting us know misterbill

Thankyou very very much for this.

Can anyone help us out?

I think i may be able to get some free space, but it will be b/w limited.

Cant see changin the battery causnig many problems than losing time and date. However, shares and stuff *could* be lost.



Telnet, we really need to be able to customise the O/S. Anyone know how to decompile the .sup files??



Sam

[blue68f100]

Hello everyone.
I have a little bad news for the forum.
I am going to have to shut down the ftp site ftp://****************/

here in the very near future.
If there is anyone else that can host the files that would be great.
I'll leave them up for about one more week then it's gotta go.

Sorry!!

Misterbill,

Sorry to hear that the snap site is being shut down.

Thankyou so much for your support and kindness for hosting the snap site.
With out there would be alot of expensive door stops.

I downloaded every thing from the site last month, It apears to be around 188 meg, is this correct?

My isp limits me to 25 meg, well below whats needed.

But I will be able to send mail attachments if need be.

Thank you again for your kind support.

David
Blue68F100

[re3dyb0y]

I too believe i have everything, but will check over the weekend

David, if i am able to get some more webspace, would you be able to help me with uploading all the files back up?

Cheers


Sam

[blue68f100]

I too believe i have everything, but will check over the weekend

David, if i am able to get some more webspace, would you be able to help me with uploading all the files back up?

Cheers


Sam


Yes I would gladly help you with the upload. My upload speed is 750k.

David

[re3dyb0y]

Nice one

I have only got 256 upload, but it does do around 300 kbps

Just need to check that i have go them all. i think i have most things


Sam

[re3dyb0y]

My ISP gives 250mb, dont know about bandwith.

Will have a look

Also, found another site with a 1gb storage, 100gb montly space, but 15mb max file size



Will keep looking

[conehead]

I have a SNAP 2200 that was running in Mirrored Mode when the backup drive failed. I backed up the data with retrospect, found a duplicate Maxtor drive model p/n 5325301593 mx4k080h4 80 gb d540x-4k and replaced it in the snap server. When I tried to reformat the primary drive from the config mode it still indicates the backup disk has failed and primary is ok, the new drive shows up as a single disk (OK). Being a newbie to hacking I’m looking for a step by step to enable the drives to function in Mirror mode again. I’m more a mac guy, but I have a windows machine and have downloaded winhex, and bios bin files. Do I need to upgrade my BIOs before starting? Not to clear on how to dup the drive bios on to the new one or clear the error message.
Thanks much for anyone who can help. Here's the info on the device:

Model Software Hardware BIOS
2000 series 3.4.803 (US) 2.0.3 3.4.758

Disk Status Total<MB> Free<MB> Files
Drive2 - Single disk OK 74,799 74,724 9
Mirror - disk 1 Data protection disabled. Backup disk has failed. Primary disk is OK. 74,799 74,724 25

10/08/2005 14:23:17 Command: config devices info

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

Logical Device: 10016 Position: 0 JBOD Size (KB): 32296 Free (KB): 22368 Private Mounted
Label:Private Contains system files only
Unique Id: 0x60BB81E71853BA45 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): 78150656 Fixed

Logical Device: 10010 Position: 1 JBOD Size (KB): 76595040 Free (KB): 76517928 Public Mounted
Label:Drive2 Single disk
Unique Id: 0x60BB81E71853BA45 Mount: /2 Index: 2 Order: 2
Partition: 10010 Physical: 10017 FS Size (KB): 77656968 Starting Blk: 61583 Public
Physical: 10017 Drive Slot: 2 IDE Size (KB): 78150656 Fixed

[re3dyb0y]

You need to reinit the drives to remove the cracked raid.

When the 2nd drive is sorted out, the mirror can be re-enabled in the web admin panel


Winhex isn't needed, adn which bin files have you downloaded for the bios updates?

[re3dyb0y]

config devices format 10000 /reinit

There is an item that can be run from the debug page that involves all, will unmount, and remount the hard drives. This should remove the 'cracked raid' and reformat the new drive

http://snapserver/config/debug


Someone else should be able to tell you with more info, i cant remember, if you just need to do it for each drive


But im sure there is an all option or something similar

[conehead]

You need to reinit the drives to remove the cracked raid.

When the 2nd drive is sorted out, the mirror can be re-enabled in the web admin panel


Winhex isn't needed, adn which bin files have you downloaded for the bios updates?

I downloaded snap2200.bin which was modified Nov 2004.

[conehead]

config devices format 10000 /reinit

There is an item that can be run from the debug page that involves all, will unmount, and remount the hard drives. This should remove the 'cracked raid' and reformat the new drive

http://snapserver/config/debug


This is the one that worked for me:
config devices config individual 50000 force

Thanks for the help. I'm back on line.

[blue68f100]

This is the one that worked for me:
config devices config individual 50000 force

Thanks for the help. I'm back on line.


I received this procedure from a Service tech that use to work for snap appliance. I used it on mine. Dive will generaly be 10000 or 10010

MIRROR REPAIR FOR ORPHAN

1.Data should remain but as precaution backup your data.
2.Execute the following command from the ipaddress/config/debug web page.
Note: DD is the number of the problem hard disk.
co de format 100DD /reinit
(After reboot, this configures 100DD as a SINGLE drive and FORMATS it.)
3.Reboot the Snap server.
4.After the ORPHANED disk is formatted, execute this command from the ipaddress/config/debug page.
co de config mirror 100SS 100DD
SS is the source disk, DD is the destination disk.
(This step mirrors the drive with data to the drive without data.)
5.Reboot the Snap. If everything works according to plan, the View Disk Status
page should report ?Rebuilding backup disk? when it comes back online.

:) David

[kogvos]

Any Snap 4400 experts in the house? I've just got one without drives and while it appears to fire up OK, I just can't get into it. I've run the Snap program which sends out discovery requests.

I've tried the reset button which doesn't behave as expected as it doesn't reboot as the admin manual says but does seem to put it into maintenance mode - I still can't access it. Both ethernet connections seem OK with the occasional activity flash but it can only be configured using port 1.

I've put a spare 40g drive into it to see if I can format it but the other 3 slots are empty at the moment. I would have thought I would still be able to configure it without drive in it.

Regards,

Jamie

Any ideas's

[blue68f100]

Any Snap 4400 experts in the house? I've just got one without drives and while it appears to fire up OK, I just can't get into it. I've run the Snap program which sends out discovery requests.

I've tried the reset button which doesn't behave as expected as it doesn't reboot as the admin manual says but does seem to put it into maintenance mode - I still can't access it. Both ethernet connections seem OK with the occasional activity flash but it can only be configured using port 1.

I've put a spare 40g drive into it to see if I can format it but the other 3 slots are empty at the moment. I would have thought I would still be able to configure it without drive in it.

Regards,

Jamie

Any ideas's

Jamie,

On the newer snap the OS resides on the hard drives. So you are missing the OS needed to boot. You will need to copy the boot trackes over, then reinit /format the drive. Most use Digital Dolly on the Knoppix Disk to do this.

Blue68F100

[2monty]

Hello,
I have a vintage Meridian Snap 2000 S/N 26k. I am looking to put 2 120GB drives into it. Right now the software is limiting the HD to 8GB.

software 1.1.157 - hardware 1.1.0 - board# 26xxx - Aug 27 1998 16:13:36

bios: v1.0.077 Wed Apr 01 17:26:02 1998

Here are the specs on the software. From what I have read I need to update the bios then the software. I think I have the correct software but I cannot find a bios update. If anyone knows where to get this please let me know.

Thanks,
Mike

[re3dyb0y]

Hello,
I have a vintage Meridian Snap 2000 S/N 26k. I am looking to put 2 120GB drives into it. Right now the software is limiting the HD to 8GB.

software 1.1.157 - hardware 1.1.0 - board# 26xxx - Aug 27 1998 16:13:36

bios: v1.0.077 Wed Apr 01 17:26:02 1998

Here are the specs on the software. From what I have read I need to update the bios then the software. I think I have the correct software but I cannot find a bios update. If anyone knows where to get this please let me know.

Thanks,
Mike

Yup, you need a couple of versions to get updated.

To V2 to update file system, then to v3/v4

[John Woods]

:mad:

I have replaced both drives in the snap server 2200 and now I can not access the web interface. The original drives are totally pooched, dead as a door nail. Is there a way to get this unit up and running it appears that the "OS" was running off the old drives?

Does someone have the OS and instructions to rebuild?

[meister_sd]

Hi,

You're right, on the 2200 the OS is on the drives. A few pages back is detailed instructions on how to get your snap back up and running. You will need the Knoppix CD and the image snap2200.bin. From there you image the bin file to your new HD (just one) then put it back into the 2200 and reboot. Put the 2nd HD in after the first has initialized and formatted.

-Mike

[blue68f100]

Hello,
I have a vintage Meridian Snap 2000 S/N 26k. I am looking to put 2 120GB drives into it. Right now the software is limiting the HD to 8GB.

software 1.1.157 - hardware 1.1.0 - board# 26xxx - Aug 27 1998 16:13:36

bios: v1.0.077 Wed Apr 01 17:26:02 1998

Here are the specs on the software. From what I have read I need to update the bios then the software. I think I have the correct software but I cannot find a bios update. If anyone knows where to get this please let me know.

Thanks,
Mike

Mike,

You will be required to upgrade the bios to v 1.2.180, before you can upgrading the OS to v2.

David


David

[JPB]

Have a 4100 here, still OS 3.x
Machine went down with flickering system-LED, called Adaptec. Machine has no warranty left, so they told me, they won't repair. :eek:
Nice way of doing business, but that underlines what I think of this company for several years now - /dev/null is the best place for them. Support told me too, that the drives have XFS - but I was unable to mount them on Linux, FreeBSD or NetBSD - will try further, perhaps they use a rare partition-scheme. I doubt, that the machine has a "normal" BIOS, I suggest them to have something like OpenFirmware or simular.
I removed all drives (4x40) and machine came up again, now I try with 4x120 WD - new RAID5 with one spare is resyncing atm, guess that might take some hours.. ^^
I'm still interested in getting this machine to boot Linux or a more "normal" BSD like OpenBSD or NetBSD, but without more information it's hard to predict if we ever see a Snap booting a custom Linux. The machines has standard PC-hardware, so it should even boot with a vanilla 2.4.x or 2.6.x-kernel. Still the BIOS is a big "?"...
If I find the time, I will look into these .sup-files to get any information about the BIOS or the booting process, all we need is a bootloder..
I did not test 48bitLBA yet but I doubt Adaptec will ever provide a BIOS-update for the Promise-controllers.. :/

[2monty]

[QUOTE=blue68f100]
Mike,

You will be required to upgrade the bios to v 1.2.180, before you can upgrading the OS to v2.

David
[/QUOTE


Thanks for the info, any idea where I can get that upgrade?? The support pages at Adaptec leave a lot to be desired...

Mike

[JPB]

Well.. RAID5 built without problems (2+1+1 = 240 netto + spare), then updated to OS4. Did some stress testing since with Helios Lan Test (100 times reading/writing 300MB etc.) with no problems, write rate 4,5MB/s, read rate 7,8MB/s which is ok regarding the old hardware. But..

Before the machine went down I made a copy of all stuff (105GB) via AFP. Now, with the new OS4, I cannot save the files back - several errors complaining about folders not found, illegal filenames etc. etc. pp. No idea what they did to the AFPd, but it is complety shit now :mad: , useless in an AFP-enviroment. Helios AFP test fails 50% of the newer AFP-features. If anyone plans to use these machines with AFP - forget it. Even a dumb Windows server is a better choice.

[FirebirdTN]

... Machine has no warranty left, so they told me, they won't repair. :eek:
Nice way of doing business, but that underlines what I think of this company for several years now - /dev/null is the best place for them....:/

LOL, I signed up for this forum JUST to reply to your thread.

We too have a few SNAP servers around here. When we first bought them I thought they were the greatest thing since sliced bread. We had one crap out, and sent it back (to then SnapApplicace), and the service was top notch. This was probably a couple years ago.

A while back, I had powered off one of our Snap Servers, and it sat for months, but connected to the network in the powered off state. When I finally went to go and turn it back on, it wouldn't.

I called support (now Adaptec), and in not so many words, I was told to take a flying leap. I am *very* knowledgable with DOS and Windows, but since I do not know unix, FreeBSD, or any of the alternative OSs, there was no way for me to retrieve my data off the drives of the failed SNAP server (drives are probably good, its the electonics that failed). Luckily I had a DVD backup set, so I didn't loose anything.

I had asked Adaptec "what if I had mission critical data on here, I have no way of recovering it"-there response was "you should have a backup" to which I replied "but these Snap server *HAVE* redundant backups; that is one of the selling points you tout in your sales brochure". Hmmmm...

Yeah, I could probably finger it out if I had the time to tinker, but I don't. So I have recently put together a simple Win2K Pro box that acts as a file server with RAID 1 array that provides email failure notification that has more storage capacity than all the Snaps we have combined, and have recently put all our Snap servers on ebay except for a couple small ones (1000 and 1100).

Sorry so long, I was just completely pissed off at Adaptec's attitude towards SnapAppliance/Quantums customers. I can't believe they wouldn't even take a look at it FOR A FEE. We would have gladly paid to have our server repaired, but their stance was "out of warranty, throw it away".

Again, way to do business. Don't get me wrong, I still love the Snap server with the features it provides in the small physical footprint it provides it in, but since Adaptec now owns the product, we have purchased our last one, and definately will not be buying any more.

Just like JPB said, you can put together a box (using Win2k, Linux, whatever suits you) that will do the same thing, and not have to worry about "proprietary" file systems when crap hits the fan.

Sorry for my rant...

-Alan