Hack a Snap Sever 1000?

[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]

Originally Posted by 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.

Email Me and ill pass on the details

[re3dyb0y]

Originally Posted by 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

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]

Originally Posted by 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

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]

Originally Posted by Cubanallstar

Still no joy kids

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

Cube.

[emanon1]

Originally Posted by upstech

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]

Originally Posted by 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

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]

Originally Posted by 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.

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]

Originally Posted by Cubanallstar

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

Cube.

So you have no OS at all?

[blue68f100]

Originally Posted by Davesworld

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