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

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

Tiger problem
 

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

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

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

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

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.

Fixed the access issue!
 

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

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

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

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/sho...&postcount=576. I have also upgraded my memory from 64 MB to 256 MB. System is a Quantum Snap 2000 server.

Ray

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

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

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

Help
 

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:





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

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

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

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

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

Thanks for all your help Leo

Sincerely / Ed

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

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

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/Seaga...oductDetail.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/applicati...8&sku=THD-250A

Off the Wall Mirror Repair Attempt SnapServer 2200
 

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:

Fixed a Broken Mirror -
 

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 :-) !!!!!

WINHEX for drive imaging / cloning....
 

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 ;)