Hack a Snap Sever 1000?

[re3dyb0y]

I agree

Myself, like a lot of others picked them up (in some cases) for free from company's taking them out of action.

Mine sits on the side, usually not on....

[kcrossley]

Just as an FYI, I did try installing OSv4 and my Snap Server 2000 is now dead.All I can recommend to those who were thinking of upgrading:
DON"T UPGRADE TO SNAP OS v4

This is untrue. I'm using OS v4.0.860 on a hacked Snap Server 2000 with (2) 120 GB drives. It's been running great for 6 months! :)

Kelly

[re3dyb0y]

Yes, most people have been ok , but as it shows, some people have had problems

The hardware revision and the bios make a difference

OzDave is one of a few of us who are in the know.


Sam

[blue68f100]

This is untrue. I'm using OS v4.0.860 on a hacked Snap Server 2000 with (2) 120 GB drives. It's been running great for 6 months! :)

Kelly

Kelly,

There are ways to recover, some what. You will need to backup to 4.0.855, this is a complete OS, not a patch. To see the snap again try doing reset to factory several times. I fould out by changing the hardware config (freshly formated fat32), net inteface would show up with assist after being on for 10 minutes. Then try to reinstall the software, through assist. You may also try installing the image file to the drive.

David

[kcrossley]

Kelly,

There are ways to recover, some what. You will need to backup to 4.0.855, this is a complete OS, not a patch. To see the snap again try doing reset to factory several times. I fould out by changing the hardware config (freshly formated fat32), net inteface would show up with assist after being on for 10 minutes. Then try to reinstall the software, through assist. You may also try installing the image file to the drive.

David

I'm not sure I'm following you. My Snap Server is work fine, save the occassional file naming issues from using a Snap Server with the Mac OS X operating system.

Kelly :)

[blue68f100]

I'm not sure I'm following you. My Snap Server is work fine, save the occassional file naming issues from using a Snap Server with the Mac OS X operating system.

Kelly :)

Opps,

Wrong post. This was for OzDave

I too use a old Mac with OS 9.1, NO Problems.

David

[Anubis]

i have web space 30gb on unlimted b/w i think it uploads at 512ksec well thats the max ispeed iv pullled off it at so as long as its a private distro i dont mind letting the space be used

[JPB]

Opps,

Wrong post. This was for OzDave

I too use a old Mac with OS 9.1, NO Problems.

David

Since OS 9.x Apple made some great changes to the filesystems and AFP. OS9 still uses AFP version 2.x, all OS X use AFP v >3.1 - the latest is AFP 3.3 AFAIR. Some advantages are:
- support for filenames up to 255 chars
- support for filesize up to 2TB

SnapOS still uses 2.x or a crappy 3.0, the former developer Excel/Meridian Data, Inc. also uses AFP 3.0 which also lacks support for long filenames just the same as eg. Windows 2k/2003 (both use AFP 3.0). So IMHO neither Snap nor Excel/Meridian Data's NAS-devices can be used in a MacOS X enviroment though you might want to use smb or perhaps NFS (never tested with Snap). I still found no way to copy the files back, so SnapOS 4 is a pos regarding AFP and renders the device unusable in my case. I guess we will not use the 4100 any more. I'm quite sure that SnapOS is using netatalk 1.x and the developers (if there are any more) just refuse to use netatalk 2.x - which supports AFP 3.1 = long filenames etc.

Btw., Adaptec is looking for a new owner for their NAS department. No wonder why..

[re3dyb0y]

$100 dollars for it!

[blue68f100]

Don't over pay for the Snap Division?

Adaptec needs help if they want to keep clients.

Blue68F100

[dog_guy1990]

Hi ALL,
Can anyone help me with snap server 1000. I have a snap server 1000 my old 160GB HDD is dead. I got a new replaced. I removed old HDD and put new HDD in snap server it wont let me use snap asst or http://yourserver. Do i need install OS? if yes how?

[re3dyb0y]

You'll probably need to use an image to recreate the hard drive to make it snap compatible

[blue68f100]

Hi ALL,
Can anyone help me with snap server 1000. I have a snap server 1000 my old 160GB HDD is dead. I got a new replaced. I removed old HDD and put new HDD in snap server it wont let me use snap asst or http://yourserver. Do i need install OS? if yes how?

Did you set the jumper on the drive to match the original, Master or CS.

Are you getting in activity with the disk, net, link lights on the front panel?

The 1000 is suppose to have the OS in flashram. After replacing the drive on restart, the snap should format and install the necessary system files. It takes about 10 minutes before you can access it, if it is seting up the drive. Do you by chance know which version of the OS you were using? Apparently you have a version 2 bios, and v4.0.? OS if you had full capacity.

David

[soundidea]

Thank you all for posting such interesting info.

I have a dead Snap 1000. The hard drive was failing and I replaced it in the network from where it came with a new 250GB 1100. Although I could not log on to the server, I was able to see it and copy the data to the new 1100 to provide the shared data in a 6 workstation peer-to-peer network.

This is the first NAS I have met and I like the genre.

I have not opened up the dead 1000 yet, but my tour through the forum has led me to believe that if I put in a new drive in it, will it boot and copy the OS to the hard drive?

Does the hard drive have to be formatted first or should I re-partition it first and not format it? I will be happy with a 120GB drive in it. Is a 7200 ATA133 drive fine?

Nelson



Did you set the jumper on the drive to match the original, Master or CS.

Are you getting in activity with the disk, net, link lights on the front panel?

The 1000 is suppose to have the OS in flashram. After replacing the drive on restart, the snap should format and install the necessary system files. It takes about 10 minutes before you can access it, if it is seting up the drive. Do you by chance know which version of the OS you were using? Apparently you have a version 2 bios, and v4.0.? OS if you had full capacity.

David

[blue68f100]

Just install the drive, NO formating required. The snap1000 will take care of the formating and copying the system from flash to the hard drive. The Snap1100 does not have the system in flash. If it fails you will have to copy the boot trackes to another drive. I have seen some 2000 have problems, but come back after they cool off. Check to see if the coolling fan failed.

You said you were able to copy the data, I assume by putting the drive in another snap. Is this correct. If you copied the files from the snap1000, it has not completely given up.

David

[soundidea]

David,

Thanks for the response. The company that was using the 1000 reported inconsistant data access. I came in and could not logon to the 1000, but could access the folders via the workstations on the network. I tried to BU all the data, but the BU failed somewhere in the process. The hard drive on the 1000 was VERY noisy. I was able to copy the folders from the 1000 to the new 1100 and got them going. It took a long time! I hate to throw the 1000 away.

I have seen the posts about going beyond 32GB. I would like to put in a 120GB drive, get it to recognize the 32GB and then config it for the remainder.

Is a standard ATA133 7200 8MB cache Seagate Barracuda drive OK?

Nelson

[blue68f100]

If you have a v2 bios you can go beyound the 137gig barrier with v4 OS.
The snap WILL NOT WORK with ATA133. must be ATA100.

Do you know how to reset the admin password, using the reset button?
If you can log in as admin, look at the log file, see what kind of errors you are getting.

Depending on the age, your fan may be failing causing the unit to overheat. Which will cause errors. I got one so hot it fried the hard drives as well as the systemboard.

Remember the original hard drive is a 5400rpm, you will add more heat with a 7200.

David

[soundidea]

David,

Thanks for the ongoing info.

I reset the server (four clicks). Loaded the orig disk and snap assist found the server once past the workstation firewall.

SnapAssist sees the server and reports the Details:
IP: 192.168.0.2
Software: 2.2.393
Hardware: 3.1.1
DHCP, BOOTP, RARP: No
SN: 108360

but cannot reach the server at that address. My local subnet is at a different address, so I don't think it is an address conflict.

In W2K Pro, the server is not seen. Ditto for XP.

The web browser cannot reach either the snapSN or listed IP address.

Will a new drive make it all good?

I'll get a 5400 ATA100 drive. How big can it be with the hacking resources of the group?

Thanks again,

Nelson

[blue68f100]

To find out which version of bios you have, click in the upper left corner of the banner (SnapAppliance). It will popup a window with the info.

Did you do an initial setup?
DHCP requires NetBeu for it to work. Do a maunal setup and issue a static IP. It need to be stationary anyway.

David

[soundidea]

Hi David,

Although the Snap Assist can scan and see the server, it cannot connect for configuration. Ditto for web access. So I cannot get in to see the BIOS version. Nor configure!

Hopefully, a new drive will fix this. I am suspecting that the section of the drive that holds config info and OS for the Snap is bad.

Nelson

[blue68f100]

It's sound like the browser is reading cashed data. Reseting the server, sets the IP back to 0.0.0.0 . The older unit need NetBiue to set DHCP. The assist program will allow you to manually set it.

The net configuration settings are stored in flash. The HTML configuration screens can be accessed without any harddrives installed.

I sent you more detail in a private message.

David

[soundidea]

David,

Thanks for the help. I was able to reset the 1000 and assist v.4 was able to configure it. I have access to it now.

Snap 1000 specs:

Server # 108360
Software Version: 2.2.393
Hardware Version: 3.1.1
Bios Version: 2.1.363

I have a Seagate ATA100 200GB 7200 8MB cache drive on the way. 3.5" 5400 drives are not common and not as good a value when you can find them. The new 7200 drives are quieter and run cooler as the technology improves....hopefully it will not run hot! I will keep an eye on it and look at the fan/cooling state as I progress.

I have the upgrade info you sent and will tackle that after I get the drive installed and am limited to 32MB. Any tips are appreciated. It is nice to see it on the network again.

I will look for a used, more advanced Snap for my network as well. Any model suggestions?

Thanks again,

Nelson

[blue68f100]

If the cooling fan hasn't been replaced, it may be time. I think the 1000 use the same fan as the 2000 which is a Sunon KD1205PHB3, 52x52x15mm, 4300 rpm, 8.5 cfm, 0.7w, 22.5dba. The 52mm fans are harder to locate, just stay under 30 dba if you want it quite. I was able to fit in a 50mm with out any problems, since it only uses 2 mounting holes. The upgraded fan delivered 13cfm, with slighly more noise 28dba.

You will need to update the snapos, you are setting on version 2. Your bios >2 will allow for harddrives >137 gig. Your current os will limit you to 130 gig, remember there is some overhead for the os. V4 opens the door for larger drives. If you are not seeing full capacity of you current drive, you will need to issue "config devices format 10000 /reinit" from debug. The snap will restart then reformat the harddrive, you will have full capacity when it is completed.

As for updates, I would upgrade to v3.4.803 first. You can jump to v4 with out going through v3 if you like. Then up to v4.0.830. DO NOT UPGRADE TO V4.0.860. There are numerous reports that v4.0.860 turns the Snap1000 & 2000 into door stops, the 4.0.855 seams not to have the problem. Don't take the chance. If you replace the drive before doing the upgrade, you may have to issue the format /reinit cmd to gain full capacity.

As for replacement snaps. I prefer the raid versions 2200, 4100 etc .... The 2200 can run raid 0 & 1, where the 4100 have 0,1 & 5. The performance of the 2200 blows away the older 2000's. I run in redundacy (data protection) mode Raid 1. There is a fundamental difference between the early models and the later ones. All of the newer models store the OS on the hard drive, NO FLASHRAM, standard boot bios. If you have a harddisk failure (not in raid 1 or 5) you will have to copy the boot tracks to your new harddrive before installing it.

The 4X00 are rack mountable. MisterBill or poogles_uk can give you more detail on the 4X00. I only have the 2000 and 2200 model (600gig), with the 2000 dead right now.

David

[Raceit]

Hello all,
I have a Snap 1000 with a dead 40gb hard drive. The OS is on the hard drive and simply installing another drive does not work. I am in search of an image that I can put on a new bare hard drive.

I know in the previous posts there was talk about the ftp site going down, but I don't see where another one has been posted. Any help on getting an image for a Snap 1000 would be greatly appreciated. (Preferably with a newer OS so I can put a hard drive in larger then 137gb).

Thanks.

[blue68f100]

The OS is stored in flashram on the 1000 model. Make sure the drive you installed is set as master, and ATA100, the WD drives with ATA133 will have to be configured for ATA100, prior to installation. The snap will not talk to ATA133. Watch you activity lights on startup, It take about 10 minutes for the snap to copy the system files from flashram to the harddrive. You will not be able to access it while it is doing this. Then use assist or your browser to connect to the snap setup html. If you performed a reset to factory you will have to use Assist.

David

[Raceit]

The OS is stored in flashram on the 1000 model. Make sure the drive you installed is set as master, and ATA100, the WD drives with ATA133 will have to be configured for ATA100, prior to installation. The snap will not talk to ATA133. Watch you activity lights on startup, It take about 10 minutes for the snap to copy the system files from flashram to the harddrive. You will not be able to access it while it is doing this. Then use assist or your browser to connect to the snap setup html. If you performed a reset to factory you will have to use Assist.

David

Thanks... I finially tracked down another hard drive. However it has been fully reset but I don't have the Assist software. I looked on Adaptecs web site, but didn't see that as a download. Is there anyway to get that software?

Thanks again.

[soundidea]

David,

Thanks again for your help. I will look for a 2200. I like the idea of the data redundency. Retrospect BU works well with the 1100 in the office where I installed it. I am working out BU scripts to automate backing up the data now.

Nelson

[Cubanallstar]

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

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


I've just gladly discovered this thread whilst on a mission to upgrade my 4400 OS to v4. Gotta say i'm well impressed with the length of this thread and the great beta on here! Mister Bill i'm so gutted you've had to shut down your FTP, it looks like i'm three weeks to late! Can anyone else please help me out? I'd be so greatfull!

Ta muchos,

Cuban.

[blue68f100]

Yes, :)

This is one of the more active thread.

It has become technical support for Snap Servers, since Adaptec is killing it off.

David

[teknotoyz]

Ok... I'm new to this. My IT guy at work talked me into the snap server as a NAS rather than the simpletech or other new consumer models. He was right! After reading some of this thread, I managed to determine either the 2000 or 4000 was the models of choice for me due to the ROM based OS. I just didn't want to mess with the idea of having to image a drive before using it (or replacing a dead drive hoping to get my data from any remaining drives). The model 2000 looked to have potential heat problems with the faster drives, so I picked the 4000. Anyway, a trip to EBAY has produced a $265 Snap 4000 with (4) 30 gig drives and SNAP os v4.0.860 and motherboard rev 2.0.1, BIOS 2.0.252 (I think I did well, these look to be newer versions). I just dropped 2 brand new 160gig drives into one of the drive caddy's (a WD and Seagate) and they formatted at 151 gigs each. GREAT! no problem with the LB48 size limitation then. I'll drop 2 more Maxtor 160GB drives tomorrow to finish it off at a total of 640GB of storage (about $400 total with new drives). NOW MY QUESTION FOR THE EXPERIENCED FOLKS: which RAID should I choose? I want data protection, so RAID 0 is out. I just don't know what to choose between RAID 1 or 5? I understand the mirror concept, but if RAID 5 gives me 75% of the drive space with protection, sounds tempting to me! (if I understood how RAID 5 works, I'd be more comfortable with it). Also, any way to set a drive sleep time? If anybody has any of the software that goes with this, let me know, I'd like to have the system complete (the seller included a disk with some files: assist, Snap_4_x.sup, snap_jvm.sup, snap_ServerSync.sup, and a pdf users manual). I wasn't sure what the .sup files are for, thoughts?

[blue68f100]

I will send you a word doc on how the different raids work.
My choice would be Raid 5.
Some have had problem using 4 disk in the array and dropped back to 3 with 1 spare.
It is allways best to use the same make and model harddrives. And preferably the same hardware revision. Make sure all of the interfaces are ATA100, snaps don't like ATA133 (WD). WD can be set back to ATA 100 with the utility disk.
Expanding the ram helps performance.

The sup file is the SnapOS.

David

[Chips]

Hate to sound like a stuck record, but can anyone email/PM me the location of the various OS upgrades?

Snap Server 4100
S/W 3.4.803(UK)
H/W 2.2.1
BIOS 2.4.437

Thanks,
Chips.

[WolfWorks]

First off thanks for all the info, upgraded a snap 2200 to two 250GB hdd.
I also upgraded to V4 os.
Here is the kick and I am not sure what is the cause. The performance sucks, worse now than before. What happens is that the snap server will handle little files no problems but with large files forget about it. I mean take a 4GB image (these are usually broken down into 1GB size files). Copy says 122min. After about 30 minutes it times out stating can not copy. Little files can be read and written in sort order. Is there something that can be done with this or is this a MB problem. :cry:
Anyone have this problem besides me.
Thanks again

[blue68f100]

Never had to transfer a single file that large. The largest I've transfered has been image files (700meg), No problem.

Try transfering to another PC and see if you get the same results.

Which version of 4 are you using.

David

[WolfWorks]

Software Version: 4.0.860
Hardware Version: 2.0.4
Bios Version: 3.4.758

I am worried about this as I have another 2200 that is running a revision of version 3 of the OS with smaller drives and it does not seem to have this problem. I just worried that if I can not fix this I might not want to take the chance on messing up another one.

Another funny issue with this unit is that since upgrading to V4 OS the Assist utillity can not auto find the unit. I have to search by the name of the server.

I did a test of breaking the files into RAR 100mb (42 files). Ran ok until the 42 and seemed to hang. Had to cancel and then recopy #42.

Not sure what it might be. I have tried several systems and networks for that matter and this unit still does it.

[re3dyb0y]

The transfer to windows files always is slow

NFS transfers are supposedly quicker

[WolfWorks]

I understand slower but not be able to copy a file is the problem. I mean on a snapserver with V3 I can copy these large files and on a same model snap server with V4 I can't, it is just weird.
I also have a Dell 750 (I think, or is it 705, whichever one with two drives) that has V4, even though it seems slower since V4 at least it copies files of any size.

[blue68f100]

This may be a ram problem. The 2000 has 32 meg of edo ram. If you get into debug there are some commands to see how the snap is using the ram, "nvram demonds number (fsync enable/disable ( filesystem fsync suport )" you can also set file cache size. I would compare the 2 units and see what is different.

The command "debug memory display current memory stats" will show how much is being used by OS and process.

There has been some reports of a MS security patch causing problems with 4.0.855, thus the reason of 4.0.860. No such problems with v4.0.830.

David

[soundidea]

David,

I installed the new Seagate 200MB ATA100 drive. The 1000 did not see it. I connected the new drive as a slave and the Snap recognized it and formatted it for 32GB. It worked properly as a 2nd drive.

How should I prepare the drive so the Snap will see it as the boot/master drive. Should it be formatted? FAT32? What size partition? Is a 2GB FAT16 partition better? Should it be formatted as the primary drive? A logical, active drive?

Again, thanks for your time.


Nelson

[soundidea]

David,

I have the new Seagate drive and installed it in the Snap, which did not recognize it. Assist could not find the server. I installed the new Seagate as the slave on the same IDE adapter along with the original drive. The Snap booted and recognized the Seagate as the second drive and formatted it. Both were recognized by Assist.

How can I prepare the new drive so the Snap will see it as the primary drive?

Thanks again for any pointers,

Nelson

[asnking]

Can someone please email me the v4 OS upgrade file. I need it to upgrade my Snap2000 and 4100. Thanks

[teknotoyz]

First off thanks for all the info, upgraded a snap 2200 to two 250GB hdd.
I also upgraded to V4 os.
Here is the kick and I am not sure what is the cause. The performance sucks, worse now than before. What happens is that the snap server will handle little files no problems but with large files forget about it. I mean take a 4GB image (these are usually broken down into 1GB size files). Copy says 122min. After about 30 minutes it times out stating can not copy. Little files can be read and written in sort order. Is there something that can be done with this or is this a MB problem. :cry:
Anyone have this problem besides me.
Thanks again

I have version 4.0.860 on my snap 4000. Just installed and formatted 4-160 gig drives as Raid 5 ending with 450gigs of useable space (about 12 hrs formatting time). Transfered a 3.59 gig file in roughly 10 minutes. No error messages. Transfer was from a PC to the SNAP then from the Snap to a MAC and also from the Snap to a XBOX, there were no issues on these transfers. I don't know what to tell you as I am just learning this system myself. I am using a linksys 54G router with a hacked sveasoft bios, static IP's on my home network. Only trouble I have had was when I renamed the Snap and forgot to tell the router to use the new name with the Mac address to assign the IP.

Let us know if you find out the cause of the slow transfers and errors on your Snap.

[blue68f100]

There has been reports of problems using 4 large capacity drives in raid 5 on 4000. Most have dropped back to 3 drives with 1 spare. There have been some problems reported with some of the old units on 4.0.860, but mainly on the 2000's. I know the 4.0.860 uses more ram. You may consider add more ram. Turn off jvm if you are not using it, it requires a lot of resources.

MisterBill and poogles_uk are the 4000 experts.

[teknotoyz]

There has been reports of problems using 4 large capacity drives in raid 5 on 4000. Most have dropped back to 3 drives with 1 spare. There have been some problems reported with some of the old units on 4.0.860, but mainly on the 2000's. I know the 4.0.860 uses more ram. You may consider add more ram. Turn off jvm if you are not using it, it requires a lot of resources.

MisterBill and poogles_uk are the 4000 experts.


What are the problems that people have seen with the 4000 and 4 disk RAID5?
I've had no problems yet, but I don't want them either.
If the RAID 5 disk formats OK and works, am I in the clear?
As a complete Newb to this, what is JVM?

I appreciate the help. The snap I have came with 4.0.860 installed, I have no idea how much or what type of memory it has, but it has been running well since the new disks have been installed.

[blue68f100]

JVM is Java Machine.

Those having problems were using 250 - 300 gig drives. They were able to format but could not build the array with 4 drives, 0.1% / hour.

[soundidea]

David,

I got the Seagate 200GB HD installed in the Snap1000. I found out the linux mount command line file type switch -t auto did not work with ntfs, the file system on the c: drive, only FAT, so I copied the bin file to a usb drive and used dd to image from that. That didn't work at first until I completely deleted the partition in the new drive using disk management from W2K so it indicated the complete drive space was available and unallocated. Maybe zeros have to be written in all the drive to have the image pasted in the exact front of the drive. It then worked and the snap booted from it! I upgraded from the web console as Assist crashed during the OS upgrade. Still only 28GB, though, the size of the pasted image. I reformated and still only 28GB, but a new drive. You and Seagate reference the Snap command line, but how do you invoke it? I sure would like to have the full 200GB.

Thanks,

Nelson

Nelson

[teknotoyz]

JVM is Java Machine.

Those having problems were using 250 - 300 gig drives. They were able to format but could not build the array with 4 drives, 0.1% / hour.


Thanks David,

It looks like the 160gig drives do OK with 4 disk RAID5 on the 4000. I had no trouble with formatting (12 hrs though).

Yet another question, I am trying to connect to the Snap with an FTP program and it says "...Files ar inexistant or not sufficient access privledges..." I am using a username and password that is set for access. No troubles transfering using windows or OSX and even another FTP program, Is there something I may have turned off to allow a particular FTP program to access?

[blue68f100]

David,

I got the Seagate 200GB HD installed in the Snap1000. I found out the linux mount command line file type switch -t auto did not work with ntfs, the file system on the c: drive, only FAT, so I copied the bin file to a usb drive and used dd to image from that. That didn't work at first until I completely deleted the partition in the new drive using disk management from W2K so it indicated the complete drive space was available and unallocated. Maybe zeros have to be written in all the drive to have the image pasted in the exact front of the drive. It then worked and the snap booted from it! I upgraded from the web console as Assist crashed during the OS upgrade. Still only 28GB, though, the size of the pasted image. I reformated and still only 28GB, but a new drive. You and Seagate reference the Snap command line, but how do you invoke it? I sure would like to have the full 200GB.

Thanks,

Nelson

Nelson

You must be logged in as administrator
1. Type /debug after the address (http://snapaddress/config/debug)
2. Then type "config devices format dev 10000 /reinit" in the command line
3. It should then give you a prompt
4. restart server, it will then format
5. when finished you should have full capacity.

David

[blue68f100]

Thanks David,

It looks like the 160gig drives do OK with 4 disk RAID5 on the 4000. I had no trouble with formatting (12 hrs though).

Yet another question, I am trying to connect to the Snap with an FTP program and it says "...Files ar inexistant or not sufficient access privledges..." I am using a username and password that is set for access. No troubles transfering using windows or OSX and even another FTP program, Is there something I may have turned off to allow a particular FTP program to access?

That is a result of the software not passing userid and password info.
I had that problem when trying to connect with firefox and IE. I was not using my userid & password. WIth firefox I added an extension "fireftp" and it allowed me pass the needed info. For windows I had to delete the location in "network places" then reconnect, then I was prompted for the need info.

What software are you using that is having the problem.

David

[blue68f100]

David,

I got the Seagate 200GB HD installed in the Snap1000. I found out the linux mount command line file type switch -t auto did not work with ntfs, the file system on the c: drive, only FAT, so I copied the bin file to a usb drive and used dd to image from that. That didn't work at first until I completely deleted the partition in the new drive using disk management from W2K so it indicated the complete drive space was available and unallocated. Maybe zeros have to be written in all the drive to have the image pasted in the exact front of the drive. It then worked and the snap booted from it! I upgraded from the web console as Assist crashed during the OS upgrade. Still only 28GB, though, the size of the pasted image. I reformated and still only 28GB, but a new drive. You and Seagate reference the Snap command line, but how do you invoke it? I sure would like to have the full 200GB.

Thanks,

Nelson

Nelson

I ran into that problem too, with ntsf partitions. I need to find the command in dd for mounting them. Most of MS machines are now on ntsf. Knoppix also had a problem booting on my 915g computer with SATA drives, it would not come up at all.

David

[soundidea]

David,

How do I invoke the Snap command line utility? The Snap 1000 still has 130GB to recognize on the 200 GB drive. Only 28GB is recognized. I have the v.4 OS working. I re-formated from the snap and still only 28GB.

Do I have to remove the drive and load it on the Linux machine?

Thanks,

Nelson

[soundidea]

OK, guys. I apoligize for being lazy!

I just figured out how to bring up the debug command line in the Snap. I just had to go back through the posts; it was all there! Thanks for not telling me. I know I have to do some of the work myself.

Entering the URL Address: http://snapname/config/debug
-This brings up the Snap command line interface

I loaded Knoppix Linux v.4 onto one of my PCs running W2K Pro on NTFS and was frustrated at first because the Linux didn't recognize NTFS, even using the ntfs file system switch. So I couldn't access the image file!!

In this case I copied the snap hard disk image .bin file to a usb drive, which the Linux OS recognized and then I imaged the new Seagate drive for the Snap with that.

For those not familiar with Linux, like myself, getting the device listing of the USB devices took a little while, but typing the command: dmesg|grep usb listed the usb devices and, in my case, sda was the id of the drive.
-"mount -t auto /dev/sda /mnt" mounted the usb drive with the name of mnt.
---the -t auto, file switch automatically understood the FAT file system of the usb drive.
-typing "ls /mnt" brought up a listing of the files on the root of the usb drive for confirmation.

At first Snap didn't recognize the newly imaged drive. After playing around with a few partitioning utilities, I realized that the new Seagate must of had some info on the head of the drive and the snap image was not at the exact place the Snap expected. I couldn't get the Seagate DOS level DiskWizard to work, PartitionMagic 8 couldn't reclaim the full capacity of the drive and leave it in a "unallocated" state, so I went back to the Drive Management utility in W2K and deleted all the partitions on the drive. I think the disk utility has to "zero fill" the beginning of the drive, so no data is on the drive at all. Leave the drive "unallocated" with no partition.

I then reimaged the drive with the snap image and.....the Snap loved it and worked....but only at the 28GB of the image.

Entering the URL Address: http://snapname/config/debug
-This brings up the Snap command line interface
-Type in the command: "config devices format 10000 /reinit"
-This command configures the snap disk system to allow the full capacity of the drive
---The drive is formatted to full size on the server restart.

The new Seagate 7200 200GB drive does run a bit hotter than the original Quantum Fireball. I have ordered a new fan from Cyberguys. the Snap 1000 fan is a 40 x 40 x 10mm fan. Hopefully, that will keep it cool enough.

Thanks for all the help. These NAS boxes are sure neat!

Nelson

[blue68f100]

The image file is v3.4.805. Check you capacity it may be < 130gig.
Will have to update to v4 for large capacity drives.
Then you will have to re-issue the format dev 10000 /reinit again.

[Cubanallstar]

Can someone tell me the best way to backup data on a snapserver (4400) running version 2.x to tape on a winnt server. Spent all day attempting to configure the terrible Backup Express software with no avail. There must be another alternative surely?! Apologies if it's been mentioned on this thread. I've done a search but not been able to pull anything up.

Regards,

Cuban

[Cubanallstar]

Can anyone help me with getting hold of a version of Assist that will work with upgrading from version 2.x OS.

Many thanks

[re3dyb0y]

We may have one. Ie in our files

Drop me an email

You would need to go via v3 first. I think, but dont quote me on it


Sam

[re3dyb0y]

Hate to sound like a stuck record, but can anyone email/PM me the location of the various OS upgrades?

Snap Server 4100
S/W 3.4.803(UK)
H/W 2.2.1
BIOS 2.4.437

Thanks,
Chips.


Email Me and ill pass on the details

[re3dyb0y]

OK, guys. I apoligize for being lazy!

I just figured out how to bring up the debug command line in the Snap. I just had to go back through the posts; it was all there! Thanks for not telling me. I know I have to do some of the work myself.

Entering the URL Address: http://snapname/config/debug
-This brings up the Snap command line interface

I loaded Knoppix Linux v.4 onto one of my PCs running W2K Pro on NTFS and was frustrated at first because the Linux didn't recognize NTFS, even using the ntfs file system switch. So I couldn't access the image file!!

In this case I copied the snap hard disk image .bin file to a usb drive, which the Linux OS recognized and then I imaged the new Seagate drive for the Snap with that.

For those not familiar with Linux, like myself, getting the device listing of the USB devices took a little while, but typing the command: dmesg|grep usb listed the usb devices and, in my case, sda was the id of the drive.
-"mount -t auto /dev/sda /mnt" mounted the usb drive with the name of mnt.
---the -t auto, file switch automatically understood the FAT file system of the usb drive.
-typing "ls /mnt" brought up a listing of the files on the root of the usb drive for confirmation.

At first Snap didn't recognize the newly imaged drive. After playing around with a few partitioning utilities, I realized that the new Seagate must of had some info on the head of the drive and the snap image was not at the exact place the Snap expected. I couldn't get the Seagate DOS level DiskWizard to work, PartitionMagic 8 couldn't reclaim the full capacity of the drive and leave it in a "unallocated" state, so I went back to the Drive Management utility in W2K and deleted all the partitions on the drive. I think the disk utility has to "zero fill" the beginning of the drive, so no data is on the drive at all. Leave the drive "unallocated" with no partition.

I then reimaged the drive with the snap image and.....the Snap loved it and worked....but only at the 28GB of the image.

Entering the URL Address: http://snapname/config/debug
-This brings up the Snap command line interface
-Type in the command: "config devices format 10000 /reinit"
-This command configures the snap disk system to allow the full capacity of the drive
---The drive is formatted to full size on the server restart.

The new Seagate 7200 200GB drive does run a bit hotter than the original Quantum Fireball. I have ordered a new fan from Cyberguys. the Snap 1000 fan is a 40 x 40 x 10mm fan. Hopefully, that will keep it cool enough.

Thanks for all the help. These NAS boxes are sure neat!

Nelson


Ive used older versions, and that included NTFS support, just not write support as default without recoding/switches enabling

[blue68f100]

Since Knoppix would not boot on my WinXP machine with SATA drives, I didn't get the chance to test for NTSF support. I had to use my Win98 Computer. It worked liked a top. Besides I have docking bays on it, made it easy.

[Cubanallstar]

Can anyone help me with getting hold of a version of Assist that will work with upgrading from version 2.x OS.

Many thanks


Still no joy kids :confused:

These are my details if it helps:

Model Software Hardware Server # BIOS
4400 2.1.003 5.0.0 1111593 B25

Framework VM
1.2 1.3.1_01

[Cubanallstar]

Still no joy kids :confused:

These are my details if it helps:

Model Software Hardware Server # BIOS
4400 2.1.003 5.0.0 1111593 B25

Framework VM
1.2 1.3.1_01


Finally identified that i need Guardian 2.6 OS or version 3.2 for use with Snap Server 4400!

Thanks for those who have helped me out over the past few days. If i can just get hold of this OS i'll be :D

Cube.

[emanon1]

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.

How can I get my hands on 4_0_855. Looked google. Please somone help.

[ynodelman]

I just bought dell 705N(4100) thinking that I'll be able to update it the same way I did 4000:

Adaptec, download(snap os 4.0.8.60) -- apply -- bingo you have as much storage as big drives you want to insert in this server.

After doing all these tricks(bios unlock, set oem to none, bios lock) I still cannot apply the same update to my 705N -- it says that this firmware file is not valid

If there anyone who was able to solve this mistery? -- I will pay for this secret assuming I succeed.

Please help :shrug:

[blue68f100]

If you are upgrading from v3. You may need v4.0.830 first, it is a full set, not a patch.
Is Dell using Snap or Guardian OS. You can still download files from Dell.

[boyelectric]

I posted before, but I have still not been able to get this to work. I let the project sit for a while now, but I purchased $400 worth of drives, only to have the Snap see only HALF of the available drive space. Can any give me any advice? I have read this entire tread several times, and other threads. I swear I MUST be missing something and I want to to rip my brain out and insert fully functional model into my skull.

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

[re3dyb0y]

Its seems hardware/bios dependant generally whether you can get LBA support

The software seems to enable it if the hardware supports it

[HLouie]

To Forum

Does anyone have this problem with "Slow or No" access with Windows XP SP2. I've test all these model and looks like they have the problem. Previously with Windows XP with or without SP1 the access was quicker.

The problem is not with copying or writing to the Snap Server, it the "Network Logon".

Windows XP -> Start -> My Network Places -> Click on the SMB file share folder

I takes about 15-25sec before I get the "Net Logon Screen" "Connect to SNAPXXXXX" "Username and Password", and with some PC I get an error message of "Network Resource not accessible. See admin".

The problem only occurred after SP2. I've check the NIC, cable and swithes. Even accessing a Windows 98 PC the "Net Logon Screen" comes up faster.

After "Logon" this no problems with access, the share have the correct security right down the folder and file. HTTP and FTP have no problems.

Anyone having the same problem?

[blue68f100]

Check to see if you have installed MS KB885250 patch. It can cause this problem. There is a patch for v4 but not v3 OS. Or back out the patch and see if it straightens it out.

Adpatec Answer ID 13180

A work around may be to deselsect "Enable NT SMBs" on the snaps.

I have a tech bulitin mentioned above. I can scan and emial it to you if requested.

David

[Davesworld]

Check to see if you have installed MS KB885250 patch. It can cause this problem. There is a patch for v4 but not v3 OS. Or back out the patch and see if it straightens it out.

Adpatec Answer ID 13180

A work around may be to deselsect "Enable NT SMBs" on the snaps.

I have a tech bulitin mentioned above. I can scan and emial it to you if requested.

David

Deselecting NT SMB will have no effect on web access to the snap as the file transfers are working fine for the affected persons. Ah, the beauty of security updates.

[Davesworld]

If you are upgrading from v3. You may need v4.0.830 first, it is a full set, not a patch.
Is Dell using Snap or Guardian OS. You can still download files from Dell.

Dell is using a Snap based OS up through the 705N, They split ways as of the 715N and started using Windows Server products although the hardware looks an awful lot like the newer snaps that use Guardian. I wish Guardian was available a little less expensively since all the hardware it is installed on are basically full pc's including ps2 and vga ports. I downloaded the source for GuardianOS and you get the sources for all the programs that comprise it but no master script or makefile so you can look at the code of all the programs and kernel but not easily build it.

[Davesworld]

Finally identified that i need Guardian 2.6 OS or version 3.2 for use with Snap Server 4400!

Thanks for those who have helped me out over the past few days. If i can just get hold of this OS i'll be :D

Cube.

So you have no OS at all?

[blue68f100]

Deselecting NT SMB will have no effect on web access to the snap as the file transfers are working fine for the affected persons. Ah, the beauty of security updates.

Not according to the Tech note, it does have a impact. Apparently if you are not logging in to the server on startup.

[HoardHoard]

Hello all,

New poster here. Where I work, we have a few Snap1000's which serve up static content in remote offices. They have been setup to authenticate users on our Windows domain.

We just upgraded our PDC to Windows Server 2003 and now the Snap servers can no longer see the domain. I have done a lot of troubleshooting on this and nothing has worked to date. I found this forum when I was searching for the SnapOS v4 upgrade file. Unfortunately, it looks like the ftp server that hosted this file was taken down about a month ago.

Is there a new location for these files? Or can someone email them to me? I would very much appreciate any help you could provide.

This is my current Snap version info:
Software 2.2.393
Hardware 3.1.1
BIOS 2.1.363

My email is: hoardhoard@gmail.com
I should be able to receive large attachments at that address.

Thank you all in advance.

[FirebirdTN]

Well, after ditching all our Snap Servers except a select few due to Adaptec's crappy support, I find myself here again afterall...

I kept a Snap 1000 and a Snap 1100 because of their small size. I took all our Snap's out of mission critical service when one died and I couldn't find anyone to repair it.

I am currently "dinking" with the 1000 to try and make a "backup" of the hard drive in case its origional one dies, that way I don't have to try and find the image in desperation.

Going back over this thread for the proceedure, I saw in the initial couple replies of this thread that adding a drive was never a problem, but replacing the drive was on the 1000.

Now, I got to thinking, I know the big complaint about RAIDing a 1000 is the lack of physical space in the server. I also remember that one of the biggest performance improvements I received on my laptop upgrade was when I put a mobile 7200 rpm drive in it.

The wheels got to turning...What about the possibility of putting two E7K60 drives in the 1000? Would this work? Would the RAID be reliable as it is in the say 2000/2200 series Snaps?

Nowadays, 7200 rpm mobile drives are getting fairly common, but IIRC, Hitachi was the first to offer such drives, and they came in two flavors: 7K60 and E7K60. Although the difference between the two is hard to find in the whitepapers, I seem to remember the "E"7K60 was designated for "Enterprise" use; in other words, its perfectly fine to operate this drive 24/7.

There is definately adequate space in the 1000 for this, and would only require two adapters (to adapt the 40pin IDE to 44pin "mini IDE" (or whatever its actually called). It would also require some sort of mounting bracket, but no physical modifications would be required to the Snap server. So no cutting, drilling or anything like that to the origional case.

Thoughts?

-Alan

PS Is a 1100 as easy as the 1000 to do a drive upgrade, or are they completely different?

[blue68f100]

There is a difference depending weather you have a v1 or v2 1000. The 1000v2 and 1100 require you to copy the boot tracks (25meg) to the new drive. V1 has the os in flashram.

Use digital dolly (dd) from the knoppix CD to copy the boot tracks. After you have installed it you will be required to reinit the drive to get full capacity.

There has been a few that have converted a 1000 to a 2000 model. Remember that these models use a software raid. You may not have enough ram in the 1000. I think it only has 24 meg, where the 2000 has 32 meg.

David

[FirebirdTN]

There is a difference depending weather you have a v1 or v2 1000. The 1000v2 and 1100 require you to copy the boot tracks (25meg) to the new drive. V1 has the os in flashram.

Use digital dolly (dd) from the knoppix CD to copy the boot tracks. After you have installed it you will be required to reinit the drive to get full capacity.

There has been a few that have converted a 1000 to a 2000 model. Remember that these models use a software raid. You may not have enough ram in the 1000. I think it only has 24 meg, where the 2000 has 32 meg.

David

That last little bit went over my head; I am assuming it is some sort of app for Linux/Unix, of which I have ZERO experience...

I just successfully upgraded the 1000 I had using a clone program that was referred to back in the first few pages of this thread that operates under DOS. It was successful. I didn't really upgrade the drive that much, just went from a 40 to a 60 (all I had), but did it more for "when the hard drive fails" kind of thing.

Interesting to note on the software RAID. So, they actually implement software RAID in the 1000 series, since there isn't a hardware RAID chip in the unit? WOW, that is kind of odd, considering I have never seen a 1000 equipped with RAID, so it is interesting they they would have the feature built-in the software. -EDIT- Just re-read your reply. Are you saying the 2000/2200 also uses a software RAID solution as well? -END EDIT-

But, I guess what your telling me is it won't work? I am either going to go for a RAID 2x60, or a single 120Gig drive (don't want to fight the 137Gig barrier, which btw what determines whether you have this limitation or not? OS, BIOS version, etc?)

Thanks everyone,

-Alan

PS. In all cases I am using the newest V3 OS. Haven't seen the need for V4 in my application yet.

[blue68f100]

The 2000 uses software raid, where the 2200 uses hardware. Major difference in performance.

UNIX has had software raid avaliable for years. The snaps use a modified XPS file systems. Most clone programs have problem with it, the reason for sugesting dd. You shoud check to see if you have full capacity of you drive. Since the clone software does not know the file structure used. If it does not, let me know and I will give you the debug command to correct it.

As for as large drives, generally a bios v2 or greater with v4.0.830 os will work. There is nothing wrong with v3.4.803 if you don't have a need for large drives.

[FirebirdTN]

Thank you blue68f100, you are truly a wealth of information!

Way back early on in the thread the poster also gave the debug command to reformat the newly installed drive to its full capacity. In my case, it worked just fine, I do have full drive capacity.

Thank you also for the information on the v4 OS. So I take it that is required for drives >137Gig. Not a problem, I will just stick with 120Gig size max.

Also, the software I have is version .805; I had a hard time re-finding it again after Adaptec bought out Snap Appliance. I had that software before, but deleted it when I upgraded a couple of our other Snaps. Anyway, I ended up retrieving it again from a cached page of Snap Appliance LOL, but I don't think its there anymore.

Since the 2000 uses software RAID as well, you are really tempting me to try out the 1000 with a pair of mobile 7200rpm drives, although that is kind of an expensive experiment. I can get the single WD RE 120 Gig drive for about $90 shipped. The two mobile drives will cost probably 3 times that much.

Ahh.....decisions, decisions....But it would be kind of cool to have a RAID Snap server in such a tiny package.

As far as performance, we just used them as simple file servers. In my case I am using them in the same fashion, but with FTP capabilities, so performance isn't a major concern, but I do have to ask...

In the end, isn't the speed of the server bottlenecked but its 10/100 network connection?

Thanks again for sharing your knowledge!

-Alan

[blue68f100]

Be carefull with WD, most of their drives have a ATA133 interface. Snaps only work with ATA100. WD has a utility that allows you to manually set the ATA speed.
If its connected at 10base, I think you get a throughput of 3mbps. 100 base is in the 35mbps, I think.

[FirebirdTN]

Be carefull with WD, most of their drives have a ATA133 interface. Snaps only work with ATA100. WD has a utility that allows you to manually set the ATA speed.
If its connected at 10base, I think you get a throughput of 3mbps. 100 base is in the 35mbps, I think.
Thanks for the heads up, I'll keep note of that.

I just got finished opening up the 1100 I have (haven't tried a drive upgrade on it yet).

Its very odd...The newer 1100 I have looks like an old Pentium I computer inside; Intel P166 CPU, I belive intel TX chipset, FPRam or maybe EDO, etc.

Inside my older 1000 resembles NOTHING like the 1100. I can't even identify any PC components inside the 1000. Most all the chips are made by "ST". There is no intel chips inside that I immediately saw...no intel CPU, no intel chipset, etc...

Also, the 1000's HD used "Cable Select" on the HD, and the 1100 used "Master/Slave" settings.

Very odd, just thought I'd point that out in case anyone was wondering.

-Alan

[blue68f100]

You are right about the Intel Chip, thats the heart, slow. The ram is a edo-dimm 72 pin. If you have a ram chip the is upgradable, then you have the older model, v1.

Some of the early 1000's (v1) had the os stored in flashram like the 2000. It made it easy when the drive failed. Just install a new drive and the snap would do all the setup and installation. All you had to was setback and watch. After about 5-10 minutes you can reconnect to it and monitor the progress of the drive format.

David

[rickytim]

Hi guys. I have just got a snap server 1000. I have tried to copy the image from the snap servers 10gig hard drive to a 200 gig hard drive I have. I think I messed somthin up because now the snap server wont boot to the 10gig hard drive any more. So I am just wondering if some one might have a image of there 10gig hard drive that you could loan to me. If I could do this how abouts would I do it?

Thanks
Rick

[re3dyb0y]

How did you try to copy the image?

[rickytim]

How did you try to copy the image?

I used the ultimate boot cd..

[re3dyb0y]

I don't know of a way with the UBCD....

File hosting is down atm, but email me, and i will get back to you

The general way is by using Knoppix

[rickytim]

I don't know of a way with the UBCD....

File hosting is down atm, but email me, and i will get back to you

The general way is by using Knoppix

I just emailed You..

[rickytim]

poogles,
I got your email for the images. I have unzipped them and I do not know what I am sposed to do with the images now. Do I just copy the image to the hard drive I am going to be useing for the snap server?

Thanks
Rick

[re3dyb0y]

It is all explained in the last couple of pages.

So have a look, and if your stuck, give us a shout back, and we'll try to explain!


Sam

[rickytim]

Poogles I cant really find what I am looking for on the last couple of pages. I real do not know where even to start. I if you could please direct me some where that explanes how to put this image on to my hard drive. Also what one do you think I sould try to use? The 1000 or 2200 image?
Thanks
Rick

[re3dyb0y]

OK, guys. I apoligize for being lazy!

I just figured out how to bring up the debug command line in the Snap. I just had to go back through the posts; it was all there! Thanks for not telling me. I know I have to do some of the work myself.

Entering the URL Address: http://snapname/config/debug
-This brings up the Snap command line interface

I loaded Knoppix Linux v.4 onto one of my PCs running W2K Pro on NTFS and was frustrated at first because the Linux didn't recognize NTFS, even using the ntfs file system switch. So I couldn't access the image file!!

In this case I copied the snap hard disk image .bin file to a usb drive, which the Linux OS recognized and then I imaged the new Seagate drive for the Snap with that.

For those not familiar with Linux, like myself, getting the device listing of the USB devices took a little while, but typing the command: dmesg|grep usb listed the usb devices and, in my case, sda was the id of the drive.
-"mount -t auto /dev/sda /mnt" mounted the usb drive with the name of mnt.
---the -t auto, file switch automatically understood the FAT file system of the usb drive.
-typing "ls /mnt" brought up a listing of the files on the root of the usb drive for confirmation.

At first Snap didn't recognize the newly imaged drive. After playing around with a few partitioning utilities, I realized that the new Seagate must of had some info on the head of the drive and the snap image was not at the exact place the Snap expected. I couldn't get the Seagate DOS level DiskWizard to work, PartitionMagic 8 couldn't reclaim the full capacity of the drive and leave it in a "unallocated" state, so I went back to the Drive Management utility in W2K and deleted all the partitions on the drive. I think the disk utility has to "zero fill" the beginning of the drive, so no data is on the drive at all. Leave the drive "unallocated" with no partition.

I then reimaged the drive with the snap image and.....the Snap loved it and worked....but only at the 28GB of the image.

Entering the URL Address: http://snapname/config/debug
-This brings up the Snap command line interface
-Type in the command: "config devices format 10000 /reinit"
-This command configures the snap disk system to allow the full capacity of the drive
---The drive is formatted to full size on the server restart.

The new Seagate 7200 200GB drive does run a bit hotter than the original Quantum Fireball. I have ordered a new fan from Cyberguys. the Snap 1000 fan is a 40 x 40 x 10mm fan. Hopefully, that will keep it cool enough.

Thanks for all the help. These NAS boxes are sure neat!

Nelson

That is part of it

[rickytim]

OK, I got Knoppix 4 but I still do not know what else to do. I need like setp by step instructions on what to do in knoppix to mount the image on to the hard drive.
Some one please help.
Rick

[blue68f100]

check you email for instructions.

blue68f100

[rickytim]

ok blue68f100 I followed you directions you sent me. But when I type "ls /mnt" It said you chould see a list of windows files. I do not get that. I only get auto, cdrom, cdrom1, floppy, hda1, and hdb1. Please let me know if I have to do somthing different to get this to work.
Thanks
Rick

[rickytim]

I just saw in your email I need to use a fat32 format. I will give it a try at work tomarrow then...
Thanks
Rick

[blue68f100]

The "ls /mnt" will give you a directory listing of what you mounted @ /mnt. (The "ls" is equivlent to a "dir" command in dos.) If you copied the snap1000.bin file to root of c:/ , you should have seen it. This is just a check to make sure the files (source and target) are properly set.

I do not want you to over write the boot track on your windows hard drive.

If you have a usb pin drive. Another option would be to copy the bin file to it. Then type "dmesg|grep usb" locate your drive then mount it with "mount -t auto /dev/usb? /mnt".

Then do the "ls /mnt" again and see if you see your files.

If mounted you can continue to copy the .bin file to the hard drive.

Winndows XP, 2000, and NT default to NTSF format, which supports large hd. Fat32 is restricted to <137gig.

Make sure you have the hard drive jumpers set correct. Either CS or M/S.
Knoppix v3.8 would not boot on my computer with SATA drives. The reason for keeping Win98 with Fat32 drives.

There seams to be alot of people having problems using dd. I tried to write the instructions to make it easy to follow. After you get it to work, give me feed back so I can update my instruction to help the next person.

David

[rickytim]

OK, I followed the instructions that you gave me blue68f100 but when I go and install the hard drive into my snap server and access the snap threw a web browser I get a error that there is no devices installed. I guess it does not recognize the hard drive. I am now stuck and don’t know what to do or try next. Please let me know what else I can try.
Thanks
Rick

[blue68f100]

If you still have the org 10gig drive, see it it boots. If it does I can give the the detalis to copy it's boot tracks to the new one.

Make sure you set the hard disk to master or what ever the original was.

What are the lights doing (sys & disk) on the front of the snap? If the disk light is solid, it may be doing some disk repair.

You may need to reset the unit back to factory settings after installing.
Then use assist to do the initial setup.

Depending on which version of the 1000 you have you may need to use the 2200 img file.

David

[rickytim]

Ok, the original hard drive I have tried to copy it over to the drive I want to replace it with. When I finished copying over the original hard drive I tried the drive I just copied the image to but it didn’t work. I then tired the original hard drive and that no longer works either. So I must of messed something up when copying over the original image.

I have already reset the server back to factory settings when I tried the drive using the DD command.

When I installed the DD command hard drive into the snap and powered it up after like 1min the lights would start blinking normally like if it was working. But about 1min later when I could view the snap online the hard drive activity light would go off.

I also have an image of a 2200 snap server I will try it now and see if it works.

Thanks
Rick

[rickytim]

I have loaded the snap2200 image but I am still getting the same problem that no disks where found...

[re3dyb0y]

Is this cannot be found, in the case you cannot get to the web interface?

[rickytim]

No I can get on to the web interface with the hard drive I used the DD command to. When I go to disk management and go and try any of the options that come up I get a error saying no drives where found.

[blue68f100]

NO ? I CAN ? Double negative, OK

If I read this correctly you can login through the web interface. But the new HD is not visable.

Did you use a WD or one of the maxtor drives with a ATA133 interface? Snaps prefer ATA100. Re check the jumpers on the drive.

If you have Partition Magic pull the drive, delete any partitions found. I found a quick fat32 format works good for this.

Since the first attemp didn't work. I will send you the instructions to copy the boot tracks from your original drive.

[rickytim]

The original drive does not work. I messed it up when copying the image over to my new hard drive.. So I do not think I will be able to use it for boot tracks..

The hard drive I am useing is a WD model numberwd2000jb. I can not find if it is a ata133 or ata100. And I made sure my jumpers are set to master when hooked up to the snap server..

[blue68f100]

I checked the model, its a ATA 100.
Was your original drive set to Master or Cable Select.

Does the 10 gig drive show up, or is it missing in action like the new one. You pevious posted that the new drive was not found.

[rickytim]

The original hard drive was set to master. When I try the 10gig hard drive in the snap it does nothing I can not login to it at all. The only way I can get to the web interface is by using the DD command. I have tried formatting the hard drive with partition magic and trying it on the snap but would not work either. All that happens is the 1st and the 4th led blink at the same pace in sequence with both the original 10gig hard drive and with a fresh format to fat32.

[blue68f100]

With both lights in unison means? the os is missing? If the disk light is solid with any of the hard drives, with system blinking some what, mainly on. This ususally means it is setting up the hd. If this is happening you will have to wait 10 minutes before you can access it. I am wondering if you over wrote the image file. If you have the images files in the zip. I would un zip and try again. One thing to remember. With the XFS file system, it will not overwrite if it sees any nfs or XPS boot tracks. Do you have another ide cable to try. I know these are on there very tight and could have been damaged during removal.

Dont be afraid to reset to factory settings if nothing happens. Some times it needs a boot.

I just had a 1000 delivered to me yesterday, to try to fix. He was playing with turning a 1000 to a 2000, when the snap rebooted before he got something set. He says he has no interface, web or assist, MIA.

It want be till friday before I can do any thing else.

Have a Happy Thanksgiving.

David

[Marvin_pa]

Hi all, glad to see this thread is still going stong. It's been a long time between posts for me :D

I have obtained a couple more Snap 1000 drives and have from what I read it seems you can break through the 137gb barrier on them ?

Is there any specific requirements of the hardware ?

The one unit i have to hand has the following spec's -
h/w 3.1.2
s/w 4.0.885 (just upgraded the other day)
bios 2.1.336

Can I install a > 137gb drive in this ? Is the process much the same as a < 137gb drive ?

Thanks all,

[blue68f100]

Yes you can break the 137gig. Your Software & hardware meets the minimum requirments. The easiest way is to use dd from the knoppix cd to copy your boot tracks (and data if you want) from your existing drive to the new one. Then use debug and issue "co de format 10000 /reinit". On reboot the snap will init the drive and gain full capacity.

[jrmvt]

OK, I have a 705N which I FINALLY figured out had a bad hard drive (lights on the front were no help on this one). Replaced the Hitachi 40GB drive with an 80GB of the same line (smallest I could find). Could not get it to rebuild the RAID 5 Array :mad: , so since I had a good backup of the data, I just broke the rest of the drives apart and started from scratch.

Well, I figured this would be a good time to upgrade the OS to 4. Followed the directions to fool it into thinking its a Snap server and upgraded to 4. Appeared to go off without a hitch. All 4 drives ran through the disk check with no problems while broken apart. I built the RAID 5 array and still no problems.

Then I ran disk check on the RAID 5 disk and it blew up. I get an "FSCK fatal error = 39" and "Bad State 0 for I=237628". I did a complete reset to factory settings (all 4 options) and broke apart the RAID again and all disks checked out individually. Built RAID 5 and all OK. Ran Disk Check and it blew up again.

Anyone have any ideas? I'm afraid its something messed up in the BIOS. I don't need larger drive support as its not storing that much data, but I do need Win2003 server support. That's why I moved to OS4.

[blue68f100]

There has been some reports of the 4000 having problems with large drives. Being a dell, I was suprise you didn't use dell's down load section for the guardian file. I think v 2.6 gives you the Win2003 server support. 40 to 80 gigs should have not been a problem. Raids are can be very picky with hardrives. It is allways best to have all drives at the the same hardware and firmware versions. If you are using the JVM, you may need to increase your ram. I recall jvm requires a minimum of 24 meg. The 2003 server support is interfaced with java script.

The error is due to a parity checksum error. There have been several users that just gave up on raid5 after upgrading to hd>137gig. When you do checks like this, it also stress the ram. The 4X00 experts (misterBill & poogles_uk) may be able to shine more light on the problem.

[JPB]

I think this is a hardware limitation - probably the Promise controller and/or its BIOS.

I have a 4100 which started life as a Dell 705n. It's running 3.4.805 which is 48bitLBA compatible unlike 3.4.803 which is not. 4.0.830 is also 48bitLBA capable, but only on suitable hardware.

Which is not really true. If you "bios pci", you get the vendor and product ID's.
Devices on the PCI bus:
# 0 0 0x8086 0x7100 *430 TX Chipset memory controler
# 0 7 0x8086 0x7110 *82371AB (PIIX4) PCI-to-ISA Bridge (fcn 0)
# 0 9 0x8086 0x1209 Intel
# 0 10 0x105A 0x0D30
# 0 11 0x105A 0x0D30
The last 2 are the IDE-Controlers, which has just the same Vendor and Product-IDs as Promise FastTrak 100. Earlier FastTrack had problems with 48bit LBA, but flashing the cards with a newer BIOS resolved the problem.
This is still no answer on how to enable 48bit LBA on 4100 with to old BIOS, but I see no reason why it should not work. There are 2 ways updating a Snap-server:
1. With a newer OS - normally resides in a flashrom
2. with a newer BIOS file with either TFTP or bootp (bios Flup [T=>TFTP, B=>Broadcast])
I also get
11/29/2005 9:41:49 98 D SYS | IDE: A 48 bit LBA capable Hard Drive was detected ...
11/29/2005 9:41:49 98 D SYS | IDE: 48 bit LBA is not supported on 4100 and 12000 platforms.
on my 4100's here, but I guess that's not true by hardware, but true by Adaptec. If anyone get connection to
11/29/2005 9:41:49 98 D SYS | Executable built by KEVIN
he could tell us how to flash a newer BIOS. Another approuch is to extract the BIOS from another 4100 with working 48bit LBA. Setting up a bootp-Server is not really complicated and TFTP is a well known service. We still don't know, if the BIOS file needs to be packed or altered in any way to get flashed.
Last chance: desolder the controler-chips, put them on a FastTrack and update their BIOS in a PC... ^^
There are several hints how to hack onboard Promise chips on ASUS and other motherboards. Promise uses the same chip for standard IDE and for RAID 0/1-devices. You can extract the Promise-BIOS from the motherboard-BIOS and include the other BIOS to change the Promise into something else (the device ID will change - beware!). All we need is a 4100-BIOS with or without working 48bit-LBA and some time to find the Promise-code inside the BIOS. And a hint on how the file must be provided by TFTP or bootp.

btw.. I wonder if you can boot eg. DSL with bootp.. hmmm...:drool:
Guess I gonna play a bit with "bios Flup B"... :D

[blue68f100]

Some have turned on the 48bitLBA through debug, and have had no problems. Most of the problems were with the older 4000.

Some have used 3 drives with spare without any problems. The 4 drives in array did not work.

[Winter]

Hey all,

I'm trying to get my 4000 past the 127Gb barrier, anyone know where I can find the SnapOS v3.4.805 to download?


Great thread:D :D :D

-------------------------
Software
3.4.803
Hardware
2.2.1
BIOS
2.4.437

[jrmvt]

There has been some reports of the 4000 having problems with large drives. Being a dell, I was suprise you didn't use dell's down load section for the guardian file. I think v 2.6 gives you the Win2003 server support. 40 to 80 gigs should have not been a problem. Raids are can be very picky with hardrives. It is allways best to have all drives at the the same hardware and firmware versions. If you are using the JVM, you may need to increase your ram. I recall jvm requires a minimum of 24 meg. The 2003 server support is interfaced with java script.

The error is due to a parity checksum error. There have been several users that just gave up on raid5 after upgrading to hd>137gig. When you do checks like this, it also stress the ram. The 4X00 experts (misterBill & poogles_uk) may be able to shine more light on the problem.

OK, my mistake. I said I thought something was messed up in the BIOS but I meant OS. I did not do any upgrading to the BIOS. I was under the impression from reading here and on Dell's forum that OS 4 was the key to being able to have Server 2003 support. I didn't think Dell had updated anything for the 705N after several years ago (before the release of Server 2003). And their website says that the 705N is not compatable with Server 2003. Am I completely off base here?

OK, my drives are not larger than 137GB so that's out. Do you think my next best bet would be to replace the other three drives or increase the RAM? Or am I too concerned about this - should I just build the RAID 5 and use it and not run the disk check routine?

Thanks again!

[blue68f100]

Since you are at v4, it does support Server2003. As for as raid5, I would use 3 drives in array with 1 spare. It should test ok with this config. You will get better performace if you increase the ram. Just use drives that have the ATA100 interface, Not 133.

[AdjeH]

I've read almost all the pages but did not find an answer to my problem. I have a Snapserver 1100 with a harddiskproblem. It makes a terrible noise and is not readable. Can someone make me an image so i can use an other harddisk?
I will pay an reasonable price for it.

[FirebirdTN]

I've read almost all the pages but did not find an answer to my problem. I have a Snapserver 1100 with a harddiskproblem. It makes a terrible noise and is not readable. Can someone make me an image so i can use an other harddisk?
I will pay an reasonable price for it.
Did you ever get hooked up? I wish I could help you, and if there is ANY way that I can please let me know. Problem is I don't know how to "image", only copy from one drive to another.

I have ZERO Unix/Linux experience, so I tried a couple DOS based cloning methods mentioned EARLY on in the first few pages of this thread.

So far, I like the Norton Ghost BOOT FLOPPY method the best. When I tried that other DOS cloning software, it worked, but after slipping in the newly cloned drive the existing file shares were "X"ed out. Its not a big deal since you have to REINIT the drive to obtain full drive capacity anyway, but it did concern me a little that it obviously didn't make an EXACT copy since the file shares were Xd.

Ghost on the other hand, made a PERFECT copy, with existing file shares intact. I still had to REINIT to get full drive capacity, but I feel more comfortable with this methoed.

Which brings me to your delimna; If I knew the EXACT command with Norton to do a "raw IMAGE" instead of a "raw CLONE", I'd be willing to help you out.

Anyone else use the Ghost method and know the exact command?

-Alan

[FirebirdTN]

Ooookkkkaaaaayyyyyy.....WTF....Are there are other drive size limits besides the 137Gig barrier?

A few pages back I mentioned a successful upgrade from the stock 40gig to a 60Gig WD drive. It was all I had at the time.

Based on that success, and other posts on the 137Gig limit, I figured I'd get a 120Gig drive.

I did the EXACT same process, and now it no - workie....

Actually, the Snap 1000 WILL BOOT FINE with the new drive, however, any page I select in "Disk Utilities" (such as disk status, format, etc) says that NO DRIVES were found!!!

When I goto the debug page and try to force a REINIT of the drive, it tells me bad device ID. If I do a "devices info" command, it spews out ID's all the way down the page, on and on forever, until the Snap is no longer responsive and locks up.

I put the origional 40 Giger back in, and it works just fine, so maybe the Snap just doesn't like my new drive?

Thoughts anyone?

Origional Drive: Quantum Fireball 40Gig. Sucessful upgrade drive was a WD600BB (7200rpm, ATA100, 60Gig WD). Current attemted drive WD1200SB (7200rpm, 120Gig, *ATA100* I think-specs don't get specific, going to check that out in a second, "RE" server series drive.)

OS is 3.4.805, BIOS is 2.1.366, Hardware 3.1.2

Thanks!

-Alan

-EDIT- UPDATE: Got home and tried again with my Snap 1100. The 1100 likes the new WD "RE" server drive, but I tried EVERYTHING and couldn't get it to work in the 1000....Odd....

[AdjeH]

My Snapserver is back online again. Two forummembers send me a link to the image of an 2200. I used Knoppix to "DD" the image to a new harddisk and it worked.

[FirebirdTN]

My Snapserver is back online again. Two forummembers send me a link to the image of an 2200. I used Knoppix to "DD" the image to a new harddisk and it worked.
Glad to hear your back in business!

My saga continues:

After reading thru TONS of posts (dang this thread is huge; wish it was broken up into its respective separate discussions), I have come to the conclusion that my new WD1200SB is just not compatible with my Snap 1000. Especially helpful was the one post (#200 I believe) where one user reported he could get a 250Gig drive to work fine, but a 120Gig refused to work in his box.

The WD1200SB I have works perfectly in my Snap 1100, just not the 1000.

Just wondering if anyone has compiled a "definitive" list of compatible/incompatible drives for the Snap servers.

I now have a WD1200BB drive on its way in hope that will work.

Only difference between the two drives is 8meg cache vs 2meg cache, build constucion (the RE drive is HEAVY comparitived to the SE drives), and warranty.

It would have been nice if I could have used the "RE" in my 1000 as I wanted to RAID my 1100 with mobile drives, but what a pain in the butt to have some drives work, and others not! And just to be safe, all drives in question are ATA100, NOT ATA133.

-Alan

[blue68f100]

I believe the newer Snaps supports ATA 133 were the older 1000 do not. On large disk it is a hardware restriction if you don't see over 137 gig. Has been tied back to v2 BIOS & Firmware required.

David

[FirebirdTN]

I believe the newer Snaps supports ATA 133 were the older 1000 do not. On large disk it is a hardware restriction if you don't see over 137 gig. Has been tied back to v2 BIOS & Firmware required.

David
That is the thing though, the new drive I have IS ATA100, and still doesn't work in the 1000. Works just fine in the 1100 though.

-Alan

[mls15000]

I am so glad I found this forum. I just trading an old tape drive for a snap 4000. Did not know they could be upgraded. I have 4 120GB drives I am going to stuff into this, currently has 4 30GB drives. If anyone still has a copy of version 4 OS, I would greatly appreciate it. I run 2003 active directory and only have OS version 3.4.790 (US). Thanks! mls15000@gmail.com

[FirebirdTN]

Update on my Snap 1000 upgrade:

Evidently, there ARE compatibility issues with some drives. Reading a few posts of mine back, I could NOT get a WD1200SB drive to work in my Snap 1000. However, it worked in the Snap 1100 I had JUST FINE!

The drive in question was an ATA100, not ATA133 like some people have warned about earlier on in the forums.

I just picked up another 120 Gig drive, this time a WD1200AB, and it works perfectly in the 1000!!! I am a little miffed, as I picked up the drive on ebay, and the guy advertised it as a WD1200BB (7200rpm), but in fact he shipped an "AB" (5400 rpm). Grrrrr. But it works so I am happy. Much better than the 4500rpm 40 Gig Fireball it replaced.

The moral of my story: If you try this upgrade and follow the instructions found throughout this thread and find it doesn't work, and your positive you did everything correctly, then chances are you might just have a drive that is not compatible with your Snap.

A special "thank you" to the person who reported waaaayyyy early on in this thread that he could not get a 120Gig drive to work, but did get a 250Gig drive to work in his Snap server. And they were from the same drive family. It was his post that gave me a clue.

I hope my experience helps someone out there.

-Alan

-EDIT- 12/22

I just noticed, after the completion of the upgrade, the Snap Server's "Help" files are missing (the files that are associated with the "help" icon in the upper right hand corner of the Admin page). If you are a purist like me, you might want to restore them, even if you never really use it. All you have to do is using the "Assist" application, re-apply whatever OS upgrade your using and they will be reinstalled. In other words, I am using OS 3.4.805. Even though I already use that OS, I re-applied the 3.4.805 update and it restored the help files.

[Dino]

I have a client that has a SnapServer 1100 80GB that seems to have died. I'm new to Snap Servers, never used a working one and just have the Admin guide to go on.

I've read all the posts here and don't see anyone else having the same behavior as the one I have. I hoping the experts here can guide me in resurrecting this unit.

Here's what it's doing:

Assist cannot find the server. Tried with and without a DHCP server (without was just my laptop,a hub and the Snap.)

Performed the one, two, three and four flash resets. I even discovered an undocumented 5th and 6th flash reset (What do those do?)

Still no Assist access.

The Power is flashing once per second.
The HD light does a double flash every second.
Link is solid and Activity led flashes with network usage.


Pulled onboard battery for 2 hours and performed a 4 flash reset, No Access.

The real strange thing is that the Power button does not power the unit up or down (no 3 Power Led flash) even after holding it for 2 or 3 minutes. The only wa to power it down is to pull the power cord.

I puled the HD and ran Maxtor's disk diag on it (read only test, didn't do a low-level format) and it didn't find any problems.

If I understand the postings correctly, a portion of the 1100's O/S resides on the HD, correct?

Does the power down and the ethernet/web access portion of the O/S reside on the HD?

If so, then barring any motherboard issues, I should only need to restore the image back onto the HD, correct?

Thanks in advance for any help you can offer.

Have Happy Holiday

BTW: Adaptec wants $120 up front to open a Tech Support call (refunded and a new unit at no charge if it's a hardware problem). That would be too easy (not to mention I have a funny feeling that they would say it's not a h/w problem and keep my $120) :dome:

[blue68f100]

You are right the OS is stored on the HD. No functions work unless the unit boots. The reason for assist not finding it. It sounds like it is looking for the boot tracks. A work of caution, Snaps do not like Maxtor's ATA133 drives. Some of the newer hardware version don't seem to have the problem. The 5th blink sequence is for firmware updates. I would reload the OS from a image file using DD. The 1100 requires the 2200 image. The 1000 image is for the older models, where the OS is stored in flashram.

David

[Dino]

Thanks to all for the info, I was able to resurrect it from the dead...


Happy Holidays to all...

[evilluc]

Happy New Year everyone! I'm glad I stumbled across this thread while searching for something completely unrelated. I am getting ready to replace the drive in my Snap 1100 as it has been making some nasty noises lately. Does anyone still have Snap OS 4 laying around? Thanks all!

[boyelectric]

So, if anyone cares, I finally got it to work!!!! I had to format one drive at a time, with nothing else connected, going through the entire sequence of enabling LBA support, etc. It took forever, but it worked. Once they were all formatted, I was able to build the raid 5 array. THANK YOU everyone, and most especially blue68f100, for getting me to try it all over again, one at a time...


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

[re3dyb0y]

Am i the only person who has got an ATA-133 Maxtor drive to work

Im using Maxtor Diamond Max 9 80gbs......

[kcrossley]

Well maybe in a 1000. I have (2) 120GB Maxtor ATA/133s in a 2000.

[re3dyb0y]

These units can be pains....

Seems they are just pickey at times


Im gonna be trying some 250gbs, but they are ATA100

Some W/D's - WD2500JB

At least i know what im doing, and im only getting one drive, and if that doesnt work, i've got someone to sell it on to!

Remember - Snap OS - Email Me!

[serial]

Hello Guys,

I have an snapserver 4000 with 4 drives, we want to upgrade to an larger disk, but the OS is a limiting factor.

Is there someone who can mail me the link so we can upgrade the OS on the snapserver, the adaptec patch is not working since are running snap OS 2.x

I can recieve large e-mails on gmail, and as alternative i can provide ftp upload space.

Perhaps ik can also arrange some hosting for the product OS since i'm working for an internet company.

Thanks and please drop me an e-mail if you can help me with the OS update (v.4.0.830 i think)

Silvester

[re3dyb0y]

Check your mail

[serial]

Emailed you link for Snap OS v4

Many thanks!

I will let you know if it works tomorrow.

Greetings
Silvester

[serial]

Many thanks!
I will let you know if it works tomorrow.


I worked perfectly !

Many thanks !

Silvester

[re3dyb0y]

Good to Know




Sam

[re3dyb0y]

Is there a debug command that is used to enable lba-48 bit?

I cant remember, will look tonight

[blue68f100]

The cmd is " ide 48bitLBACounter get or reset"
Reset enables it if supported, Get reads the Statis, if = 0 = failure.

I think there are some Promise controllers on sume units that do not support LBA48. The reason for some 4100 working and some not.

[re3dyb0y]

Cheers David


Sam

[kcrossley]

The cmd is " ide 48bitLBACounter get or reset"
Reset enables it if supported, Get reads the Statis, if = 0 = failure.


How can I tell if this is already enabled?

[blue68f100]

Get to the debug page and enter "ide 48bitLBACounter get"
If the results are not 0 (zero) then it is enabled. 0 means NO

[kcrossley]

What does enabling "ide 48bitLBACounter get" do?

[re3dyb0y]

Tells you the status of the 48bit LBA

And enables you to turn it on using different instructions

[re3dyb0y]

David - Are you able to enable this without having >137gb drives in the unit?

As im trying with my 2 x 80's, and it just executes without error, but is still 0

[blue68f100]

I believe it is only valid if it is needed, drives >137gig. Other wise 24 bit is ok.
I think the "co de format ##### /reinit" will also turn it on.

[kcrossley]

Does anyone know which brands of PC100 RAM is downward compatible with the PC66 specification that a lot of the older Snap Servers are using?

[re3dyb0y]

I suppose all brands should be

Cant see why not

[kcrossley]

I just spoke with Kingston tech support and they said that the BIOS determines whether the memory is downward compatible. I read online that the chip determines this. I'll have to research it further.

[re3dyb0y]

Lol

Well, what make is in the snap at the moment?

And what have other people got?




Sam

[HLouie]

I've used all generic 256meg PC133, 128meg PC100 ram double sided with no problems with the Snap Server 2000, 4100.

What I have noticed is 512meg doesn't work, single or double sided.

Single side has problems, the Snap Server only see half of the ram and has problems booting up.

When the box reboots, I check the system logs to see how much memory has been released.
Is there any other way the check how much memory is in the unit? (config command)

The standard Snap Server 2000, 2200 come with 48-64meg, Snap Server 4100 comes with 64meg. The upgrade to 128meg had a 25% increases in performance. 256meg had very little increases.
Is there any testing software, to test the throughput via Snap Server network connection and the PC, I'm wonder if newer hard drive will make a difference in speed? (IOZone)

[kcrossley]

Great info! Thanks for the post.

[kcrossley]

Get to the debug page and enter "ide 48bitLBACounter get"
If the results are not 0 (zero) then it is enabled. 0 means NO

I just tried this and I got a 2. Does that mean that 48 bit is enabled on both drives?

[kcrossley]

Man, I'm having a GREAT night with my Snap Server 2000. Not only is it working great with the new Hitachi drives and higher CFM fan, it also seems snapier (pun intended). I've haven't checked the transfer speed yet but it seems a lot more responsive. I wonder if this has anything to do with installing the ATA100 drives as opposed to the ATA133 that were in it previously.

Plus, for years I haven't been able to get this Snap to recognize 32-character filenames with my Macs. I tried a trick someone had posted on the Internet and it worked! Woohoo! Now watch it catch fire.

You know you're old when you can get excited about small things like this. My wife just shakes her head. Thanks for your help guys!

Kelly

[kcrossley]

Okay, I just tried transferring some files. The test file is 4.44 GBs. Here are the connections I tried:

AFP: Transfer time 14 min, 5.41 mpbs (long filenames not allowed)
SMB: Transfer time 22 min, 3.44 mbps

Both of these seem really slow. How should I set this Snap up to obtain the fastest transfer speeds?

[kcrossley]

The upgrade to 128meg had a 25% increases in performance. 256meg had very little increases.(IOZone)

So the 128MB chip improved your transfer speeds by 25%? About how much extra improvement was there with the 256MB chip?

[kcrossley]

I spoke too soon. I have SMB enabled, but it's real finicky with my Mac. Sometimes if I move a folder with files to the Snap Server, the Snap won't let me delete the files I just moved because of a permissions error. Has any Mac users ever seen this? Perhaps I'll have to stay with AFP connectivity. Rats!

[re3dyb0y]

So the 128MB chip improved your transfer speeds by 25%? About how much extra improvement was there with the 256MB chip?

He said very little

I presume only a few percent.

Ie 128mb may be the maximun that the snap can utilise easily



I've found it easier on windows to set an identical named user and with the same password if one is used


And my WD ATA100 250GB 8mb Cache is due today! Can see if my snap will let me upgrade

Cheers



Sam

[gwengalon]

Hello,

I've a snapserver 2200 with no disk, i need snap2200.bin to reload software.

can anyone give me a link to download it ?
links in other thread seem to be closed.


Thank's
Gwengalon.
France

[re3dyb0y]

Will get back to you


My HD came

Got tommorow afternoon of college

Will try upgrading then!

[kcrossley]

How long should setting up a mirrored configuration on a Snap Server 2000 with (2) 250GB drives take?

[re3dyb0y]

How long should setting up a mirrored configuration on a Snap Server 2000 with (2) 250GB drives take?

IS there data on one of the hard drives?

[re3dyb0y]

I just turned my snap on to make a copy of the data before upgrading the secondary hard drive to a WD250, and it is doing disk valdation

ITs funny as it stays on 5% for ages, then jumps to 85%

Is this just a scandisk thing?

Ie the 'thorough disk check' as i know i have it to set only if there is a suspected problem

[re3dyb0y]

Drive 1
I File System : Opened FDB for device 0x10000 Disk 10000 1/18/2006 1:44:57 PM
I File System Check : Cleanup completed... Disk 10000 1/18/2006 1:44:54 PM
I File System Check : 1018 files, 7989412 used, 1581762 free (0 frags, 1581762 blocks, 0.0%% fragmentation) Disk 10000 1/18/2006 1:44:54 PM
W File System Check : Clean flag not set in superblock (Fixed) Disk 10000 1/18/2006 1:44:54 PM
W File System Check : Modified flag set in superblock (Fixed) Disk 10000 1/18/2006 1:44:54 PM
I File System Check : ** Phase 5 - Check cylinder groups Disk 10000 1/18/2006 1:42:21 PM
I File System Check : ** Phase 4b - Check backlinks Disk 10000 1/18/2006 1:42:21 PM
I File System Check : ** Phase 4 - Check reference counts Disk 10000 1/18/2006 1:42:19 PM
I File System Check : ** Phase 3 - Check connectivity Disk 10000 1/18/2006 1:42:19 PM
I File System Check : ** Phase 2 - Check pathnames Disk 10000 1/18/2006 1:42:17 PM
I File System Check : ** Phase 1b - Rescan for more duplicate blocks Disk 10000 1/18/2006 1:42:17 PM
I File System Check : ** Phase 1 - Check blocks and sizes Disk 10000 1/18/2006 1:39:34 PM
W File System Check : partition is NOT clean. Disk 10000 1/18/2006 1:39:33 PM
I File System Check : Executing fsck /dev/ride0a /fix Disk 10000 1/18/2006 1:39:33 PM


Drive 2

Message Source Date Time
I File System : Opened FDB for device 0x10010 Disk 10010 1/18/2006 1:52:03 PM
I File System Check : Cleanup completed... Disk 10010 1/18/2006 1:52:03 PM
I File System Check : 14 files, 42 used, 9806479 free (0 frags, 9806479 blocks, 0.0%% fragmentation) Disk 10010 1/18/2006 1:52:03 PM
W File System Check : Clean flag not set in superblock (Fixed) Disk 10010 1/18/2006 1:52:03 PM
W File System Check : Modified flag set in superblock (Fixed) Disk 10010 1/18/2006 1:52:03 PM
I File System Check : ** Phase 5 - Check cylinder groups Disk 10010 1/18/2006 1:49:42 PM
I File System Check : ** Phase 4b - Check backlinks Disk 10010 1/18/2006 1:49:42 PM
I File System Check : ** Phase 4 - Check reference counts Disk 10010 1/18/2006 1:49:42 PM
I File System Check : ** Phase 3 - Check connectivity Disk 10010 1/18/2006 1:49:42 PM
I File System Check : ** Phase 2 - Check pathnames Disk 10010 1/18/2006 1:49:42 PM
I File System Check : ** Phase 1b - Rescan for more duplicate blocks Disk 10010 1/18/2006 1:49:42 PM
I File System Check : ** Phase 1 - Check blocks and sizes Disk 10010 1/18/2006 1:44:57 PM
W File System Check : partition is NOT clean. Disk 10010 1/18/2006 1:44:57 PM
I File System Check : Executing fsck /dev/ride2a /fix Disk 10010 1/18/2006 1:44:57 PM


Everythings fine!

[kcrossley]

I just installed a 256MB DIMM in my Snap Server 2000. I ran the debug memory command, but I'm not quite sure how to read it. Can you tell from this is my Snap is recognizing all 256MBs?

01/18/2006 11:55:53 Command: debug memory

Total System Physical Memory: 268435456
File System Memory Allocated: 248796144
Memory To be Written: 0
Memory On Loan: 8304
Loan Count: 1
Heap Memory: 229196912
Memory In Use: 226397312
Objects Allocated: 24
Communication Memory Allocated: 2059232
Memory In Use: 466040
SDB Non-Volatile Memory Allocated: 65536
Memory In Use: 15734
Handles Allocated:4679
Handles In Use: 336
SDB Volatile Memory Allocated: 98304
Memory In Use: 278
Handles Allocated: 11705
Handles In Use: 10
System has been configured!

------------

[re3dyb0y]

268435456 (bytes?)
/1024

262144 Kbyte
/1024

= 256 MegaByte

So yes, that is fine! 100% of the space

[kcrossley]

Outstanding! When does the extra RAM really help the Snap?

[re3dyb0y]

Transferring files

Java apps and stuff, more stability

[re3dyb0y]

GET IN

I just stuck my WD 250GB in as secondary, and it automatically started formatting, showing 237,182 MB in the formatting thing

No LBA faffing, no config devices reinit and stuff

Took 5 minutes or so to format


233,938 233,704

[firestar2k3]

Hi
Im new here, have been reading much of this very long post.
I recently purchased a Dell PV 705N (Snap 4100) and would like to upgrade FW from Dell V3 to SnapOS V4 (if poss the latest version) can somone provide links and any info and tips I may require in order to upgrade my 705.

Thanks!!!

[kcrossley]

Where did you purchase your 705N? Is it new?

[dgoodrich]

Ken, can you give us a brand and part # for the 256MB ram you put in? I'd like to maximize file transfer rate since I will be using mine to host my mp3 collection.

Thanks,
Dave

[kcrossley]

That's pretty interesting. How would you set something like that up? Is it an iTunes collection?

[firestar2k3]

I purchased a second hand 705N/4100 SNAP. Ive upgraded it to the latest os from snap. 4.0.860

I have a 250GB HDD, but have the common problem of only being able to get 128GB due to 48Bit.

What can i do to make it work? Like a command or somthing to reset it.

12/07/2006 22:40:29 19 D SYS | IDE: A 48 bit LBA capable Hard Drive was detected ...
12/07/2006 22:40:29 19 D SYS | IDE: 48 bit LBA is not supported on 4100 and 12000 platforms.
12/07/2006 22:40:29 19 D SYS | IDE: Setting the hard drive size to maximum addressable by 28 bits: 131071 MBytes.

Also...

Hardware version 2.2.1
Bios Version 2.4.437

I rekon that sounds like quite a new/late version of the 4100 and i must be able to get 48bit by just being able to run a few commands, Please help!

[kcrossley]

I've heard it's a BIOS issue, but I haven't read about anyone that's been able to crack it yet. I'm very interested in the 705N as well. Does anyone know if what firestar is talking about is possible?

[blue68f100]

These have been problem childs. Some work some don't.
The best sucess has been with the unit is in JBOD (individual) drives. If an array is set it doesn't work. Even if not present. It remembers drive data.
This works best with just one drive in the server. I had one user say that was the only way it worked.
Once in JBOD. Do one reboot. clears cache
then issue the "co de format 10000 /reinit"
if it is capable of supporting 48bit this is your best bet.
Then check your log as you did before.
Changing the BIOS settings have not worked.
Then install 1 drive at a time. and issiue the format cmd if needed.
Seagates and Hitiachi have worked best.

[firestar2k3]

I have at the moment only one hitachi 250GB drive attached, no others, where shall i start from here? do you have any recommended steps and commands?

Im so desperate for 250GB!!!

[dgoodrich]

That's pretty interesting. How would you set something like that up? Is it an iTunes collection?

I've got about 40gb of .mp3s, mostly ripped from my own (and friends) CDs. I copied it all over to the Snap last night. It was all ripped using the Lame Encoder with CDex as the GUI front end.

My goal is to free up disk space on my various computers. Currently I have three copies of the music collection, because I am paranoid about losing it all. This means that every time I rip some new CDs, I have to copy the files out to the various computers to keep it all backed up. So I set up the Snap as Raid 1 to provide better data protection, and will maintain one other backup copy on an external hard drive (and I should probably burn it all to DVD-ROM too). Once I am confident that the Snap is reliably set up, I will be able to delete about 40gb each from my home machine and from my notebook.

I have recently started using iTunes because I love the interface. iTunes is a little sluggish over a wireless g connection, but not too bad. It is quite responsive over the 100mb/s LAN. iTunes maintains the music library as a XML database on the local machine. So I thought that once it had built the local database, that searching, sorting, etc. would be just as fast as a local collection. This turns out not to be true because iTunes appears to verify the actual existence of each file as it displays the tracks in its interface. If the network share isn't available, it flags the tracks as unavailable, but fortunately does not delete the database entry.

When I added the tracks to the library by browsing to the network share, I found that iTunes was unacceptably slow using wireless. If I mapped a drive to the network share, and added the tracks by browsing to the drive letter, iTunes seems to be much quicker, and is actually quite usable over a wireless g connection. I've only just started to play with this, so these conclusions are preliminary.

A third party program called "iTunes Library Updater" can update the library when tracks are added to any path you specify. Therefore, I should be able to maintain the files on the Snap (other users will have read-only access to the files), and then update the libraries on each client machine semi-automatically. I've also thought about setting the "my music" location to be on the mapped drive, and then map "M:" on all the computers to the music share. This way, the Library files would be on the Snap. All users would share the same library, and all playlists would be available to everyone. This would probably be very slow, but I plan on trying it.

I don't have an iPod (yet), so I don't know if syncing an iPod will be unreasonaby slow from the network share.

[kcrossley]

Very interesting. I know that some companies are promoting that their NAS solution can do this. One that comes to mind is the N2100P by Thecus. http://www.thecus.com/products_over.php?cid=1&pid=1&PHPSESSID=9c2859532a53fb56ece32b2cf4e032f3

Although I don't know very much about this product it seems to be getting fairly good reviews on newegg.com. What Snap Server are you using? Are you using it with a Mac?

[firestar2k3]

Hi all!
Im having a nightmare regards to getting 48bit enabled on my 4100. Please give me any ideas or tips to get this to work, I think this is a newer bios >v2 and I am getting Lba enabled drive but not being used... when i use info log t method..

please give me a shout!

cheers

[re3dyb0y]

Mine now shows
1 for ide 48bitLBACounter get

I presume that means 1 drive over 137GB?

As that is what i have

[blue68f100]

What brand drives are you using?

Check to see what config the missing drives are in. "info devices" if it has records of a drive that does not require 48bit it locks all out. I ran into this with another user, he was at the pont of giving up.

Send me a copy of the "info devices" so I can see if were over looking something.

IF individual, unmount 10000, then try the "co de format 10000 /reinit" again.

Your unit may have one of the promise controllers that has a problem with LBA48. If this is the case there is nothing We can do. One user reported this problem on " hack a snap 1000" thread. You may need to go through that thread to find the post. He gives the chip ID with the problem.

[re3dyb0y]

Call Stack :
$00105131
$002D1454
$002D8496
$002DF71A
$002B2187
$002B0957
$002BC3D6
$002BD7B6
$002B1EDF
$002B07E5
$002BC2B4
$002B0AAC
$0010413C
$001041F6
================================
System 1/19/2006 3:16:00 PM
F PANIC : Maximum yield time exceeded at $002BCEC4 System 1/19/2006 3:16:00 PM



Anyone got any ideas what it is/was?

[re3dyb0y]

Firestar

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

Logical Device: 10000 Position: 1 JBOD Size (KB): 131554128 Free (KB): 131422264 Public Mounted
Label:Drive1 Single disk
Unique Id: 0x75FEAC3C60655D39 Mount: /0 Index: 0 Order: 1
Partition: 10000 Physical: 10007 FS Size (KB): 133377984 Starting Blk: 104776 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 134217216 Fixed

[firestar2k3]

Hitachi Drive 1x 250GB Brand New.

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

Logical Device: 10000 Position: 1 JBOD Size (KB): 131554128 Free (KB): 131422296 Public Mounted
Label:Drive1 Single disk
Unique Id: 0x25C01D1E319BDA4F Mount: /0 Index: 0 Order: 1
Partition: 10000 Physical: 10007 FS Size (KB): 133377984 Starting Blk: 104776 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 134217216 Fixed


Im going to unmount then reformat..

Please give any more help if poss!

Thanks!

[blue68f100]

Call Stack :
$00105131
$002D1454
$002D8496
$002DF71A
$002B2187
$002B0957
$002BC3D6
$002BD7B6
$002B1EDF
$002B07E5
$002BC2B4
$002B0AAC
$0010413C
$001041F6
================================
System 1/19/2006 3:16:00 PM
F PANIC : Maximum yield time exceeded at $002BCEC4 System 1/19/2006 3:16:00 PM



Anyone got any ideas what it is/was?

Is this on your 2000 ?
Haven't seen this before, maybe a drive failure in mirror?

[re3dyb0y]

Its my 2200 yeah

No drive mirror, only 1 drive (the WD 250GB)

Just seems to be doing a standard drive check atm, just taking a long time, suppose its because there is a bit of data and a large drive

[re3dyb0y]

I Jrc: exiting Unknown 1/19/2006 3:41:13 PM
I Jrc.execute() starting Unknown 1/19/2006 3:41:13 PM
I Jrc created Unknown 1/19/2006 3:41:13 PM
I SnapOS.init() executed Unknown 1/19/2006 3:41:13 PM
I SnapExtension Framework 1.2 initialized Unknown 1/19/2006 3:41:13 PM
I No startup snaplets Unknown 1/19/2006 3:41:13 PM
I done Unknown 1/19/2006 3:41:13 PM
I building info for ssl.jar Unknown 1/19/2006 3:41:12 PM
I done Unknown 1/19/2006 3:41:12 PM
I building info for hello.jar Unknown 1/19/2006 3:41:12 PM
I installed security manager Unknown 1/19/2006 3:41:12 PM
I Java: Native methods linked OK Unknown 1/19/2006 3:41:11 PM
I Jrc.main() starting Unknown 1/19/2006 3:41:11 PM
I System Initialization : Initialization Complete! Memory to be released: 22304544 bytes. System 1/19/2006 3:41:06 PM
I File System : Opened FDB for device 0x10000 Disk 10000
Individual 1/19/2006 3:41:06 PM
I File System Check : Cleanup completed... Disk 10000
Individual 1/19/2006 3:41:04 PM
I File System Check : ***** File system was modified ***** Disk 10000
Individual 1/19/2006 3:41:04 PM
I File System Check : 971 files, 6545315 used, 23398862 free (0 frags, 23398862 blocks, 0.0%% fragmentation) Disk 10000
Individual 1/19/2006 3:41:04 PM
W File System Check : Clean flag not set in superblock (Fixed) Disk 10000
Individual 1/19/2006 3:41:04 PM
W File System Check : Modified flag set in superblock (Fixed) Disk 10000
Individual 1/19/2006 3:41:04 PM
W File System Check : Summary information bad (Salvaged) Disk 10000
Individual 1/19/2006 3:36:38 PM
W File System Check : Blk(s) missing in bit maps (Salvaged) Disk 10000
Individual 1/19/2006 3:36:38 PM
W File System Check : Free blk count(s) wrong in superblk (Salvaged) Disk 10000
Individual 1/19/2006 3:35:31 PM
I File System Check : ** Phase 5 - Check cylinder groups Disk 10000
Individual 1/19/2006 3:35:25 PM
I File System Check : ** Phase 4b - Check backlinks Disk 10000
Individual 1/19/2006 3:35:25 PM
I File System Check : ** Phase 4 - Check reference counts Disk 10000
Individual 1/19/2006 3:35:25 PM
I File System Check : ** Phase 3 - Check connectivity Disk 10000
Individual 1/19/2006 3:35:25 PM
I File System Check : ** Phase 2 - Check pathnames Disk 10000
Individual 1/19/2006 3:35:24 PM
I File System Check : ** Phase 1b - Rescan for more duplicate blocks Disk 10000
Individual 1/19/2006 3:35:24 PM
I File System Check : ** Phase 1 - Check blocks and sizes Disk 10000
Individual 1/19/2006 3:22:17 PM
W File System Check : partition is NOT clean. Disk 10000
Individual 1/19/2006 3:22:17 PM
I File System Check : Executing fsck /dev/ride0a /fix Disk 10000
Individual 1/19/2006 3:22:17 PM
I File System : Opened FDB for device 0x10006 Disk (Priv) 1/19/2006 3:22:17 PM
I File System Check : partition is clean. Disk (Priv) 1/19/2006 3:22:17 PM
I File System Check : Executing fsck /dev/ride0g /fix /fixfatal Disk (Priv) 1/19/2006 3:22:17 PM
I INIT: Setting IP address to 192.168.0.200 Network 1/19/2006 3:21:21 PM
S System Initialization : Server v4.0.860
Build Date: Mar 2 2005 17:50:55
Boot Count: 223 System 1/19/2006 3:21:21 PM
F Call Stack :
$00105131
$002D1454
$002D8496
$002DF71A
$002B2187
$002B0957
$002BC3D6
$002BD7B6
$002B1EDF
$002B07E5
$002BC2B4
$002B0AAC
$0010413C
$001041F6
================================
System 1/19/2006 3:16:00 PM
F PANIC : Maximum yield time exceeded at $002BCEC4 System 1/19/2006 3:16:00 PM

Drive Log

File System : Opened FDB for device 0x10000 Disk 10000 1/19/2006 3:41:06 PM
I File System Check : Cleanup completed... Disk 10000 1/19/2006 3:41:04 PM
I File System Check : ***** File system was modified ***** Disk 10000 1/19/2006 3:41:04 PM
I File System Check : 971 files, 6545315 used, 23398862 free (0 frags, 23398862 blocks, 0.0%% fragmentation) Disk 10000 1/19/2006 3:41:04 PM
W File System Check : Clean flag not set in superblock (Fixed) Disk 10000 1/19/2006 3:41:04 PM
W File System Check : Modified flag set in superblock (Fixed) Disk 10000 1/19/2006 3:41:04 PM
W File System Check : Summary information bad (Salvaged) Disk 10000 1/19/2006 3:36:38 PM
W File System Check : Blk(s) missing in bit maps (Salvaged) Disk 10000 1/19/2006 3:36:38 PM
W File System Check : Free blk count(s) wrong in superblk (Salvaged) Disk 10000 1/19/2006 3:35:31 PM
I File System Check : ** Phase 5 - Check cylinder groups Disk 10000 1/19/2006 3:35:25 PM
I File System Check : ** Phase 4b - Check backlinks Disk 10000 1/19/2006 3:35:25 PM
I File System Check : ** Phase 4 - Check reference counts Disk 10000 1/19/2006 3:35:25 PM
I File System Check : ** Phase 3 - Check connectivity Disk 10000 1/19/2006 3:35:25 PM
I File System Check : ** Phase 2 - Check pathnames Disk 10000 1/19/2006 3:35:24 PM
I File System Check : ** Phase 1b - Rescan for more duplicate blocks Disk 10000 1/19/2006 3:35:24 PM
I File System Check : ** Phase 1 - Check blocks and sizes Disk 10000 1/19/2006 3:22:17 PM
W File System Check : partition is NOT clean. Disk 10000 1/19/2006 3:22:17 PM
I File System Check : Executing fsck /dev/ride0a /fix Disk 10000 1/19/2006 3:22:17 PM
I File System : Opened FDB for device 0x10000 Disk 10000 1/19/2006 2:11:42 PM
I File System Check : partition is clean. Disk 10000 1/19/2006 2:11:42 PM
I File System Check : Executing fsck /dev/ride0a /fix Disk 10000 1/19/2006 2:11:42 PM
I File System : Closed FDB for device 0x10000 Disk 10000 1/19/2006 7:29:36 AM
I File System : Extended Rights Backup for device 0x10000 has completed successfully Disk 10000 1/19/2006 3:01:07 AM
I File System : Extended Rights Backup for device 0x10000 has begun Disk 10000 1/19/2006 3:01:05 AM
I File System : Opened FDB for device 0x10000 Disk 10000 1/18/2006 8:51:52 PM
I File System Check : partition is clean. Disk 10000 1/18/2006 8:51:52 PM
I File System Check : Executing fsck /dev/ride0a /fix Disk 10000 1/18/2006 8:51:52 PM
I File System : Closed FDB for device 0x10000 Disk 10000 1/18/2006 8:47:59 PM
I File System : Opened FDB for device 0x10000 Disk 10000 1/18/2006 8:35:12 PM
I File System Check : partition is clean. Disk 10000 1/18/2006 8:35:12 PM
I File System Check : Executing fsck /dev/ride0a /fix Disk 10000 1/18/2006 8:35:12 PM
I File System : Closed FDB for device 0x10000 Disk 10000 1/18/2006 8:32:46 PM
I File System : Opened FDB for device 0x10000 Disk 10000 1/18/2006 8:16:18 PM
I File System Check : partition is clean. Disk 10000 1/18/2006 8:16:18 PM
I File System Check : Executing fsck /dev/ride0a /fix Disk 10000 1/18/2006 8:16:18 PM
I File System : Closed FDB for device 0x10000 Disk 10000 1/18/2006 8:13:40 PM
I File System : Opened FDB for device 0x10000 Disk 10000 1/18/2006 8:10:36 PM
I File System Check : partition is clean. Disk 10000 1/18/2006 8:10:36 PM
I File System Check : Executing fsck /dev/ride0a /fix Disk 10000 1/18/2006 8:10:36 PM
I File System : Closed FDB for device 0x10000 Disk 10000 1/18/2006 7:54:19 PM
I File System : Opened FDB for device 0x10000 Disk 10000 1/18/2006 7:51:31 PM
I File System Check : partition is clean. Disk 10000 1/18/2006 7:51:31 PM
I File System Check : Executing fsck /dev/ride0a /fix Disk 10000 1/18/2006 7:51:31 PM
I File System : Closed FDB for device 0x10000 Disk 10000 1/18/2006 7:48:52 PM
I File System : Opened FDB for device 0x10000 Disk 10000 1/18/2006 7:42:48 PM
I File System Check : partition is clean. Disk 10000 1/18/2006 7:42:48 PM
I File System Check : Executing fsck /dev/ride0a /fix Disk 10000 1/18/2006 7:42:48 PM
I File System : Closed FDB for device 0x10000 Disk 10000 1/18/2006 7:27:49 PM
I File System : Opened FDB for device 0x10000 Disk 10000 1/18/2006 7:23:52 PM
I File System Check : partition is clean. Disk 10000 1/18/2006 7:23:52 PM
I File System Check : Executing fsck /dev/ride0a /fix Disk 10000 1/18/2006 7:23:52 PM
I File System : Closed FDB for device 0x10000 Disk 10000 1/18/2006 7:18:26 PM
I File System : Opened FDB for device 0x10000 Disk 10000 1/18/2006 7:13:22 PM
I File System Check : partition is clean. Disk 10000 1/18/2006 7:13:22 PM
I File System Check : Executing fsck /dev/ride0a /fix Disk 10000 1/18/2006 7:13:22 PM
I File System : Closed FDB for device 0x10000 Disk 10000 1/18/2006 7:09:46 PM
I File System : Opened FDB for device 0x10000 Disk 10000 1/18/2006 6:26:40 PM
I File System Check : partition is clean. Disk 10000 1/18/2006 6:26:40 PM
I File System Check : Executing fsck /dev/ride0a /fix Disk 10000 1/18/2006 6:26:40 PM
I File System : Closed FDB for device 0x10000 Disk 10000 1/18/2006 6:14:32 PM
I File System : Opened FDB for device 0x10000 Disk 10000 1/18/2006 1:44:57 PM
I File System Check : Cleanup completed... Disk 10000 1/18/2006 1:44:54 PM
I File System Check : 1018 files, 7989412 used, 1581762 free (0 frags, 1581762 blocks, 0.0%% fragmentation) Disk 10000 1/18/2006 1:44:54 PM
W File System Check : Clean flag not set in superblock (Fixed) Disk 10000 1/18/2006 1:44:54 PM
W File System Check : Modified flag set in superblock (Fixed) Disk 10000 1/18/2006 1:44:54 PM
I File System Check : ** Phase 5 - Check cylinder groups Disk 10000 1/18/2006 1:42:21 PM
I File System Check : ** Phase 4b - Check backlinks Disk 10000 1/18/2006 1:42:21 PM
I File System Check : ** Phase 4 - Check reference counts Disk 10000 1/18/2006 1:42:19 PM
I File System Check : ** Phase 3 - Check connectivity Disk 10000 1/18/2006 1:42:19 PM
I File System Check : ** Phase 2 - Check pathnames Disk 10000 1/18/2006 1:42:17 PM
I File System Check : ** Phase 1b - Rescan for more duplicate blocks Disk 10000 1/18/2006 1:42:17 PM
I File System Check : ** Phase 1 - Check blocks and sizes Disk 10000 1/18/2006 1:39:34 PM
W File System Check : partition is NOT clean. Disk 10000 1/18/2006 1:39:33 PM
I File System Check : Executing fsck /dev/ride0a /fix Disk 10000 1/18/2006 1:39:33 PM



I think it just mis wrote it

[re3dyb0y]

And i think it just did it again!

[firestar2k3]

I dont know if im ever going to get LBA 48Bit >137GB to work! :bawling: :bawling:

I tried unmount, then remount, then co de reinit...but still 130gb showing up!

Time to call it a day....?

[re3dyb0y]

Strange thing with mine, it was fine moving 40gb last night.....

I wonder if its just not enough ram for movign large files

[re3dyb0y]

W File System Check : Clean flag not set in superblock (Fixed) Disk 10000 1/19/2006 4:10:44 PM
W File System Check : Modified flag set in superblock (Fixed) Disk 10000 1/19/2006 4:10:44 PM
W File System Check : Free blk count(s) wrong in superblk (Salvaged) Disk 10000 1/19/2006 4:06:18 PM


W File System Check : Clean flag not set in superblock (Fixed) Disk 10000 1/19/2006 3:41:04 PM
W File System Check : Modified flag set in superblock (Fixed) Disk 10000 1/19/2006 3:41:04 PM
W File System Check : Summary information bad (Salvaged) Disk 10000 1/19/2006 3:36:38 PM
W File System Check : Blk(s) missing in bit maps (Salvaged) Disk 10000 1/19/2006 3:36:38 PM
W File System Check : Free blk count(s) wrong in superblk (Salvaged) Disk 10000 1/19/2006 3:35:31 PM


This has come up a few times

After checking, it seems it only has 22mb of ram

lol

Im gonna try moving one file at a time, see what happens

[blue68f100]

It sounds like you may have a ram failure. I thought 32 meg was the mimimun for a 2200.

As you know some units don't like WD or Maxtor drives. Try a Seagate or Hitachi drive.

How come you only have 1 drive in the 2200?

I just read a knowledge base article on the 2200 saying that it will boot from either drive. That should be true for any system running raid1.

[blue68f100]

I dont know if im ever going to get LBA 48Bit >137GB to work! :bawling: :bawling:

I tried unmount, then remount, then co de reinit...but still 130gb showing up!

Time to call it a day....?

Can you issue the format comand with it un-mounted?

[re3dyb0y]

Its done it again (3rd Time!)

Well, i can adn will try the other motherboard ive got for a 2200

I bought the WD drive, and i dont have any other larger drives. That are IDE anyway

Maybe it would be worth sticking my 2 80gb's back in and transferring some files to see if i get the same problem?

I only have one drive as i bought 1 drive to try it. A 250Gb IDE isn't much use as S-ATA is faster. And if that hadn't have worked in my snap, i had a buyer for it, who has a SAN with the WD drives in and wanted a 2nd

Also, i had Memory 22578576 bytes written down before, so i presume that is right!

Will also try copying large files from the snap and such



Strange thing is there were no problems last night

[re3dyb0y]

Seems fine just copying files from the snap server with my 250GB

[firestar2k3]

What brand drives are you using?

Check to see what config the missing drives are in. "info devices" if it has records of a drive that does not require 48bit it locks all out. I ran into this with another user, he was at the pont of giving up.

Send me a copy of the "info devices" so I can see if were over looking something.

IF individual, unmount 10000, then try the "co de format 10000 /reinit" again.

Your unit may have one of the promise controllers that has a problem with LBA48. If this is the case there is nothing We can do. One user reported this problem on " hack a snap 1000" thread. You may need to go through that thread to find the post. He gives the chip ID with the problem.

OK, Its unmounted again, but the co de format 10000 /reinit does not work...

I get the following error...

Invalid device id 10000 requested

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


what else shall I try, I have thought about giving up and calling it a day, putting 60's in and getting rid of the box... unless you think its possible to get LBA...god knows how....

[dgoodrich]

Very interesting. I know that some companies are promoting that their NAS solution can do this. One that comes to mind is the N2100P by Thecus. http://www.thecus.com/products_over.php?cid=1&pid=1&PHPSESSID=9c2859532a53fb56ece32b2cf4e032f3

Although I don't know very much about this product it seems to be getting fairly good reviews on newegg.com. What Snap Server are you using? Are you using it with a Mac?

I am using a Snap 2000 with two 80gb drives configured as Raid 1. No, I have no Macs on my network.

I saw some of the N2100P on eBay when I bought my Snap, but they were too pricy for me. That said, the iTunes server feature of that device looks pretty cool. Basically, it maintains its own database of tracks on the server, and mimics a computer on the network that is sharing its collection through the standard iTunes sharing.

So far, I am pretty happy with how the Snap works with iTunes. I played with it again last night, and I am able to browse, search and play my collection through the wireless g connection quite well. Simply create a share for your music files on the snap, map that share as a drive on the local machine, load the files into this share, and use the "File>Add folder to Library..." to import the tracks on the mapped drive into the libaray.

[re3dyb0y]

Gonna try the old drives back in, and try swapping the ide cables

Its fine transferring large amounts of files to a pc

[re3dyb0y]

I've solved one thing that was annoying me

The fan didnt come on straight away, move power cable for fan from the secondary power slot to the primary, and it comes on at inital boot

Boot time is a lot longer now for some reason

[firestar2k3]

What brand drives are you using?

Check to see what config the missing drives are in. "info devices" if it has records of a drive that does not require 48bit it locks all out. I ran into this with another user, he was at the pont of giving up.

Send me a copy of the "info devices" so I can see if were over looking something.

IF individual, unmount 10000, then try the "co de format 10000 /reinit" again.

Your unit may have one of the promise controllers that has a problem with LBA48. If this is the case there is nothing We can do. One user reported this problem on " hack a snap 1000" thread. You may need to go through that thread to find the post. He gives the chip ID with the problem.

OK, Its unmounted again, but the co de format 10000 /reinit does not work...

I get the following error...

Invalid device id 10000 requested

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


what else shall I try, I have thought about giving up and calling it a day, putting 60's in and getting rid of the box... unless you think its possible to get LBA...god knows how....

[blue68f100]

Some 4100 do not suport 48 bit due to a HW issue.

Apparently you have one of those.

[kcrossley]

Rats! That sucks. Sorry firestar.

[firestar2k3]

nothing else i can do now???

[firestar2k3]

can you give me a command so i can format whilst its unmounted as my final attempt....

[re3dyb0y]

IS there a trick to doing it then david?

Ie with it unmounted being able to format it

[blue68f100]

I guess not, It was just a shot in the dark.

I wish I had my Laptop back I would hunt for post on the promise controller chip problem.

[firestar2k3]

i assume its defo time to give up and cannot get 48bit LBA on my 4100. guess will just have to put 4x 120's in unless anyone has any ideas....

cheers

[Winter]

I'm experiencing the same problem as you poogles, but on a 4100 with new 120GB seagates...

every time I try a 'config devices fsck dev /fix /fixfatal '

it says: W File System Check : Free blk count(s) wrong in superblk (Salvaged)

if I try copy some data to it I get call stack errors.

hrrmmm, I'll try swapping IDE cables...

[kcrossley]

David,

Here's a post on the Promise 48-bit controller problem: http://hardware.mcse.ms/message46075.html

And here's the Promise download page: http://www.promise.com/support/download/download_eng.asp Do you know what Promise chip is on the 4100?

I'm not sure if this helps.

[kcrossley]

According to this web site http://www.digit-life.com/articles/quantumsnapserver/ the Snap Server 4100 uses the Promise Controller PDC20265 chip.

When you go tho this website http://www.storagedrivers.com/drivers/80/80527.htm they have a driver for that chip but the site states that it's NOT the latest driver. I tried to find the latest driver but have been unsucessful as of yet.

Here's a Promise description of that chip: http://www.promise.com/product/oem_ataasic_pdc20265_eng.htm Does the 2000 use the same Promise controller chip?

WARNING: I'm not a Snap Server expert. If you try any of these drivers you do so at your own risk. If in doubt, don't do it.

We'll solve this problem - eventually.

[kcrossley]

Okay this is getting interesting. Read this page and see what you make of it concerning enabling 48bit LBA. Perhaps it will help. http://hardware.mcse.ms/archive69-2004-7-46075.html

Kelly

[firestar2k3]

nice one! :) ill look into it all and let everyone know how i get on with my attempts...

cheers all...

[kcrossley]

David,

Is there a debug command that firestar can run to determine the firmware versions of all of the components in his 4100?

[re3dyb0y]

I'm experiencing the same problem as you poogles, but on a 4100 with new 120GB seagates...

every time I try a 'config devices fsck dev /fix /fixfatal '

it says: W File System Check : Free blk count(s) wrong in superblk (Salvaged)

if I try copy some data to it I get call stack errors.

hrrmmm, I'll try swapping IDE cables...

Well, i moved my 250gb in the second slot and put my old 80 back in

OVernight i copied 90gb of movies and data and it is still fine this morning


It seems the unit prefers to have 2 drives in


Im just going to swap the drive positions around and then try again tonight



Sam

[re3dyb0y]

Oh

It seems the 4100 have the OS on flashram

Was this worked out before

Firestar is able to boot the unit using no drives

And someone else from here was able to stick 4 new 120GB drives straight in and it booted and formatted them all off


I know for a fact that my 2200 can't boot with no drives.... Well, i couldn't get a net light, or onto the web config

Seems in some ways the larger units are more useful. But this would make sense as they are for bigger organisations, designed for more data and data transfer






Also, im fine copying data

[firestar2k3]

Tried all of last night till 2am! had no luck with the 4100 just pure aggro! need some way of making / forcing it to work. it must be possible. i cant be the unlucky one with the snap that dont to 48bit. this seems in good condition and quite newish. was orignally a dell 705n but is now a SnapOS v.4.0.860...

but still no luck at all.... tried the ? and playing with different commands but they didnt work!

[RichJ]

Hi All,

Glad I stumbled across this forum. I have a Snap 1000 whose 40 GB drive recently died. The light on the bottom of the Quantum Fireball just blinks 10 times but the drive won't spin. I keep the server in the basement so didn't notice the nasty noises it was making until too late.

I bought and installed a new drive in hopes it would reboot before finding the information here and realizing that I also need the OS that resides on the drive (now dead).

Can someone please point me to an image file for the SNAP 1000?

Rich

[re3dyb0y]

Email Me


Update on my Server being a Pain - I've had 2 drives in it for the last couple of days

250gb in 1st and 2nd

I have transferred a few hundred gigabytes to the 250gb with no problems

Seems its more stable with 2 drives. Suppose that'd make sense being a 2 drive unit

[blue68f100]

My 2200 was painless. Just turn on raid1. After the raid is built, then swap the drives one at a time.

[re3dyb0y]

Eh....

Where have half the posts gone??

I've got it working fine with an 80gb in aswell

[crapfactory]

poogles:

Thanks for your help this week. I now have two 4100s running s2s filled full of 120gb drives. Reflecting on this at the end of the week, why in the heck should a normal person have two raid5 servers mirroring each other to save a bunch of crap that should probably be deleted anyway? Anyhow, I have a line on a 4000 that I might buy and fill full of bigger drives. This is definitely a disease.

[re3dyb0y]

poogles:

Thanks for your help this week. I now have two 4100s running s2s filled full of 120gb drives. Reflecting on this at the end of the week, why in the heck should a normal person have two raid5 servers mirroring each other to save a bunch of crap that should probably be deleted anyway? Anyhow, I have a line on a 4000 that I might buy and fill full of bigger drives. This is definitely a disease.

That does seem a little OTT for data that isn't needed

[dog_guy1990]

i have a snap server 1000 how can i clean server log?

[lazarus_21]

I have a Quantum M4100 Snap server running v3.1 of SnapOS. I was wondering if anyone has an alternative ftp site from which I could download the upgrade files.

[marmfield]

[QUOTE=AdjeH]I've read almost all the pages but did not find an answer to my problem. I have a Snapserver 1100 with a harddiskproblem. It makes a terrible noise and is not readable. Can someone make me an image so i can use an other harddisk?QUOTE]


I have this issue, but have found that the drive is a Maxtor MaXLine Plus II 250GB ATA/133 HD that is still under warranty from Maxtor until 2007! I'm going to RMA the hard drive but I will need an image to put back onto my Snap 1100 when this comes back in. I would appreciate any help that can be given.

BTW, old drive is unusable and I can't get any pc to see it in BIOS.:doh:


Thanks,

Matt

[JPB]

What can i do to make it work? Like a command or somthing to reset it.



I don't think there is a simple command to get it work. The BIOS for the promise chips are located in the motherboards BIOS - like on other PC-mainboards with simular problems. Now there are 3 possible answers:
1. Quantum did some bad design and the 4100's motherboard simply lacks some address lines to use 48bit addressing
2. Adaptec is not willing to support 48bit-LBA due to some hardware bugs - though it might work in some cases
3. Adaptec is not willing to support 48bit-LBA because they don't want customers to upgrade their devices without paying a lot of money or buy newer devices from Adaptec.

So what we need is
a. an answer from Adaptec about 1. and 2.
b. a way to extract and flash a new BIOS to the 4100 with a hacked BIOS from Promise
c. if b. works, we still need a way to prevent the 4100 OS from disabling 48bit LBA just because it is a 4100 - seems to be hardcoded ("IDE: 48 bit LBA is not supported on 4100 and 12000 platforms.")

IMHO Adaptec became a "bad company" to do business with. Over the last few years they took over some good products to make them worse and to get as much money as possible from their customers. Their support for anything but Windows is a mess :mad: and didn't make any progress the last years. I doubt we will ever see an aswer to our questions. I removed about 20 4100 now just because the support is not willing to help me without paying a lot of money and I still cannot mount even single volumes in any other machines. I now try to remove every single Adaptec product here and replace it with NEC, Atto and some others. My test-4100 is took apart waiting to either reach the trash can some day or get a new life with 4x 300GB.. time will tell..
I did not make any progress booting Linux with bootp yet and without more information about "bios flup" I'm kind of stuck now. It's likely that I will replace the mobo with an EPIA and just use the 19" case.. ^^

[blue68f100]

I remember reading some ware that the File System is an Modified XFS originating from FreeBSD. If you use a hex editor and look at the .sup file you will find MOAI### markers. These are for the different version of servers. An earlier user said it was IBM Hex. (starting address then data, 16 bit). The way a 1100 is factory loaded. This MOAI300.hex is forced down to the units before the OS can be loaded. The software for doing this only runs on NT4.0. I have tried it, in hopes to recover a 1100 that is messed up from a user trying to make it work as a 2000.

You can read the OS and boot tracks from a HD with dd from knoppix.

[re3dyb0y]

XFS is what i was told by EU Snap Support


Sam

[marmfield]

So who has a link to the v4 upgrade? :)

I had v4 on my SnapServer 1100 250GB model before the drive went belly up, 2 months after the warranty expired by SnapAppliances, of course!

Matt

[JPB]

XFS is what i was told by EU Snap Support

They told me that too - but did you ever try to mount it somehow somewhere? I was not able to even determine the partition scheme..
I tried with FreeBSD, NetBSD, Linux, OSX, AIX, Windows... no luck.

[blue68f100]

I went through that. The only thing I didn't try was WINHEX in clone mode. And all it would give me would be ????. I gaveup.

[HLouie]

To Forum

I'm looking for a Snap Server 2200 image of the drive. The bin file I have works but there is a problem with the ftp on the Snap.

I've done a complete reset the 4 blinking light and a total redownload of the os but still no ftp server.

Thank-you

[blue68f100]

Sounds like a setup problem. If you reloaded or installed the OS, it should have corrected the problem.
What version of OS are you running?

[HLouie]

I'm using 4.0.860 OS.

What I've done is replace the dead hard drive with a 80GB.
-I use the Knoppix 4.0, in "failsafe" boot mode from DVD.
-Start a termial window, Super User, grep the Hard drive info
-I have the orignal image of the drive 4.0854

-Try ftp, no go, complete format of drives, complete 4 blink reset
-Try ftp, no go, Upload the 4.0.860 using Assist, upgrades no problems
-Try ftp, no go, complete format of drives, complete 4 blink reset
-Try ftp, no go, but everthing eles works.

Our server at work died, they got a new one, I get the old one before the crash ftp was working. Now I have Snap 2000, 2200. I've worked on 1000, 1100, 2000, 2200, 4100

[blue68f100]

Are you using dd to copy the image file to the 80 gig?

[HLouie]

You bet

dd if=/mnt/cdrom1/snap2200.bin of=/dev/hcd bs 1M
or
dd if=/mnt/cdrom1/snap2200.bin of=/dev/hcd bs

The only thing different is that the images are on a CD and not on a hard drive.
dd if=/dev/hda/snap2200.bin of=/dev/hdb bs=1M

Both provided the same image on the 80gb drive and both boot to 4.0.854 OS. Both work http hppts with the java, shares work, security works, local network works.

Even the firewall has been turn off for this ip. My other Snap Server work with ftp. What I might try is the snap1000.bin and try that on the 80gb drive.

[blue68f100]

You are using the correct image file. The 2200 also works on 1100 and some 1000v2 units.

You have a lot newer image than I have, mine is v3.4. I don't think the bs is required to write to disk (hd), is required to read the Mod XFS correctly.
Did you check the config menu to make sure ftp is turned on?

Were you required to use the /reinit cmd to rebuild the drive space?
Are you seeing 80 gig or just image file size?
We genneraly are required to reinit the drives after reloading the server drives.

Sorry for all the questions, but you have an Odd problem.

[HLouie]

Well, after a weekend of work on the Snap Server 2200.

To blue68f100, yes I did check if the FTP server is on. After every image and every os upgrade. Yes, I completed the Image to HD with dd. After complete I used debug to /reinit. After rebooting the drive started formatting. All 80gb no problems. But no FTP.

My procedure
Knoppix 4.0 -> failsafe -> Terminal Window -> SU -> grep -> dd -> Snap Server debug -> config device XXXXXX /reinit -> reboot -> started formatting -> check amdin screen -> No FTP

Taking your advice on FTP server is on. I turned it off. Upload the same Snap OS on the drive and 4 blink reset. Boom FTP is working.

I know what you're thinking "The idiot did not have the FTP server on". But I check after ever image and os upgrade.


Now that the Snap Server 2200 is online, I'll start on a full comparison of
1000 48meg ram (std) with - 10gb hd (std)

2000 64meg ram (std) with - 2x10gb hd (std)
2000 128meg ram (mod) with - 2x80gb 2meg cache hd (mod)
2000 256meg ram (mod) with - 2x80gb 2meg cache hd (mod)
2000 128meg ram (mod) with - 2x160 8meg cache hd (mod)
2000 256meg ram (mod) with - 2x160 8meg cache hd (mod)

2200 64meg ram (std) with - 2x80gb hd (std)
2200 64meg ram (std) with - 2x160 8meg cache hd (mod)

The software I'll be testing with is http://www.iozone.org/


I would like to thank blue68f100 for great assistance, I'll EM later.

[blue68f100]

Great news.

Sorry for all of the questions. I use to do R&D work, for 25 yrs. Was trained to ask all of the hard questions.

We both learned something from this exercise.

Snap server store some setting in flashram and some on the hd. I know the disk configuration JBOD, raids are stored in a area that is not cleared during a reset. I did not know that the supported portocall were. This finding may shead some light in why some 4100 have been able to get 48bitLBA to work.

[JBidule]

Sorry for disturb, but:

I had a snap server 1000 and tried the Joe's procedure and made THE mistake like a kid during a long night, mixed two drives during trying to copy with dd the proprietary partition to the new drive. So, the unit is like a dead one, with LED flashing indefinitely...
What I want to do first is to recover the unit (like factory) and make it run.
After, AND ONLY AFTER Cloning proptietary OS information with dd, I will play with trying to grow the hard disk size.
I am not so interested with new features of v4, but if the image comes with I will live with it.

So, if someone can give me the possibility to download the proprietary partition, this will be great.
As my unit is dead, I can't give you more details, I have seen that the latest version installed was 3.4.790.
H/W version is unknown, processor is ST.
70700034-003, S/N 103632.
Manual indicates version 1000, it was delivered with a 30GB Quantum Fireball.

You can reach me via this forum or via john.bidule <AT> gmail.com.
I know that I am maybe asking for something like a miracle, but if someone can help me, this will be so nice...

Thanks a lot! John.

[blue68f100]

Some of the 1000 will auto setup the hd. But only if there is not a partition present.
You should still be able to connect with the web interface. I think only the newer models do not allow this. Do you know what hardware and bios version you are at.

The 1000's units have used 2 different image files. One for the older models, which genreally allows you to connect with no drive installed. And the Newer model which uses the boot bios like standard pc.

I will send you instructions to help you recover.

David

[crapfactory]

Does anyone know the maximum size memory that can be installed in a 4000? If so, can you recommend a part number?
Thanks, Carl

[Matt]

Lo all,

I've been meaning to take a backup copy of the hard drive in my snap 1000 for ages and finally got around to it today. I wiped the drive and then dd the contents to another and got the new one working (same size, just wanted a backup of the OS). I've made a ghost image of this if anyone has a dead 1000 that they need an image for. Dunno if this image works for other snap servers too.

[blue68f100]

Norton's Ghost in the past have not been able to read the Modified XFS corectly. The reason dd is widely used. Only the first 25 meg of the hd contain the boot tracks needed to boot.

[blue68f100]

Does anyone know the maximum size memory that can be installed in a 4000? If so, can you recommend a part number?
Thanks, Carl

The max I have heard someone using was a 256meg.

[Matt]

Norton's Ghost in the past have not been able to read the Modified XFS corectly. The reason dd is widely used. Only the first 25 meg of the hd contain the boot tracks needed to boot.

One of the previous posts mentions using the -ir switch which tells Ghost to do a raw copy, which I did.

Because only the first few MB are needed I stopped Norton Ghost after a few minutes to keep the image size small. However I did also do a full image of a 3GB snap drive which I've bunged on DVD (this image is about 1.4GB). My original snap drive is 80GB but I wanted to make a backup of the OS onto the 3GB which I've done and is working. Can't use a 3GB drive for much else!

[re3dyb0y]

One of the previous posts mentions using the -ir switch which tells Ghost to do a raw copy, which I did.

Because only the first few MB are needed I stopped Norton Ghost after a few minutes to keep the image size small. However I did also do a full image of a 3GB snap drive which I've bunged on DVD (this image is about 1.4GB). My original snap drive is 80GB but I wanted to make a backup of the OS onto the 3GB which I've done and is working. Can't use a 3GB drive for much else!

Sounds about right

[JBidule]

To all,

I come back with upgrading the Snap Server 1000 from 30GB, dead disk to a beautiful 250GB Snap Server.

Here are my specs:
Model: 1000 series
Software: 3.4.805(US)
Hardware: 3.1.1
BIOS: 2.1.363
Original HDD Size, 30GB.
New HDD Size, 250GB.
I follows the procedure given and all works as expected.

For temperature, be aware (as I am sure you are) that a new 7200rpm disk can give too much dissipation.
I have choosen a HDD with good performance, but with "not too much peak current on 12V and with a reasonable power dissipation".
I choose the 7k250 from Hitachi/IBM.
I use the unit without the plastic cover (temparaure rise above 55°C inside with plastic cover).
Without plastic cover, temperature between HDD and mainboard doesn't rise above 45°C which is within the HDD specs (55°C).

Thanks a lot to David help, procedure and for giving me trust to buy a new 250GB.

I have now a unit which works like before, which I am able to restore in case of HDD crash.

The only warning can be if like me your unit was delivered with an international OS (french by example), the OS image given will be in english.
So, just switch codepage to Western (850) and you can work with international files and directories.
If you take the procedure to create your recovering image, it should work also with international OSes.

Cheers everybody, John.

[blue68f100]

Did you check to see if you have full capacity?
Since you are using the rare v3.4.805, I would like confirmation that you have >137gig.

David