Help with an 1100

[Geek_Ed]

Hi all,

I have a Snap 1100, and I can't seem to get it to boot correctly. I get the LED code for the server being in software update mode and not getting an IP (one Sytem LED flash, 2 Disk LED flashes "Snap! Server does not have IP Address; Waiting for a download in broadcast mode ")

I have read through all the posts, and someone (blue68f100 I believe) had said that this LED pattern could also mean a corrupted OS load or a bad hard drive. I have replaced the drive in the unit with known good ones running both ver 3.x and ver 4.x of the OS with the same results (known good meaning they both work in a 1000 unit flawlessly). I have tried resetting to factory defaults numerous times, and even removed the CMOS battery and let it sit overnight to clear the BIOS. I am stumped.

Do I have a nice paperweight on my hands?? Any suggestions would be greatly appreciated.

[blue68f100]

The 1100 and 1000 have a different OS loads. Even thought they use the the same OS. Your 1100 may be the v2 with uses the image from a 2200.

To complicate things there are 2 version of the 1000, 2 version of the 1100, 2 version of the 2000, 2 version of the 2200, 4 rev of the 4000, .....

So just because its a single drive unit dosen't necessary mean it will work.

The led pater you refer to is NO OS found in your case. If you were doing a OS upgrade it would indicate it was waiting for IP address from server.

[Geek_Ed]

So, a version 2 1100 uses the same image as a 2200, and a version 1 1100 uses a version 2 1000 image?

I think I have it now. Just need to get my hands on a version 2 1100 or a 2200 and get an image of any OS.

Thanks for the help!

[blue68f100]

This is general, if one doesn't work try the other.

[Geek_Ed]

I would like to take this minute to thank Quantum (and ultimately Snap Appliance) for trying to stretch "proprietary" as far as they possibly could!!

[Geek_Ed]

So, got my hands on an 1100 image, but I'm having strange problems. Wondering if it's a HW ver. 1 image, my HW is ver. 2.

Load image to HD, machine boots, I can access it, go to debug, issue format command successfully, try to reset machine through web interface, it hangs shutting down. Pull the plug to power cycle it, hard drive formats to correct size, have to do factory reset to clear corrupted administrator password. Boots normally, everything looks good until I try to update the OS. I've tried the web interface, Assist, and the command-line tool, everytime after the SUP file uploads, the server loses connectivity, and I have to pull the power, can't power it off even using the power button. Even if I don't try to update the OS, it loses connectivity within 10 minutes.

Any ideas??

[Geek_Ed]

Does anyone know if there are BIOS / OS compatability issues? I noticed my unit has a version 4.1.x BIOS (never seen version 4 BIOS), maybe I need a version 4.x OS.

I got the unit very cheap because the original 160GB drive in it died, and discovered the drive (Maxtor) was still under warranty until sometime in 2008, so it must be a fairly new unit.

I can test my "theory" this weekend, I bought another 1100, so I'll upgrade it to 4.0.860, take an image, and go from there, just wanted to see if anyone had some insight for me.

FYI - And if anyone is reading this, the AC adapter listed here in the forums from Mouser does not fit my 1100, the center hole on the plug is too small (compared it to a 1000, and the posts in the jacks are a different size). Nothing a small round file didn't fix though.

[Hallis]

It very well might be a BIOS/OS compatability issue. Keep us posted on your progress.

Shane

[snap-tech]

In response to your post Geek_ED from today;

Do you have the ability to give snap an external ip address. As in one that I could access. I would like to gain access to the debug section while the unit is accessible. Then I would like for you to put unit into what called flup mode and I will install the basic os on unit. then you can do the full os install using the sup file. after that all should be ok.

if you agree and need detailed instructions, on how to put unit into flup let me know.

[blue68f100]

Geek Ed, Since you are having problems it may be the img file is not compatable with your version. Snap has so may hw versions of every model I quit keeping count. If you have access to the debug page. Type "bios model" and "bios oem" lets chack to see if something is set wrong.

The 1000 and 1100 img files are not compatable with each other. You need a 2200 img file.

[Hallis]

Geek_Ed, Rather than upgrading the newer drive to OS 4. Upgrade it to 3.4.805 or 3.4.807 if you have either of those files. I think it'll have more of a liklihood of working. My 1100 came with 3.4.803 which wouldnt support >137gb drives.

Shane

[Geek_Ed]

Let me clarify a couple things. First, this unit HAD to come with at least 3.4.805 since it was a 160GB box from the factory. My hardware is ver 2.02, and the image I am using is OS 3.4.805 from a hardware version 2 1100 unit.

Here is the output from the various debug bios commands, I found the "locked BIOS" interesting:

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

OEM Type currently is NOT an OEM box.
Only Quantum resources allowed on this non-OEM box.

Failsafe Bios Exists
Failsafe 4.0.855.FS Sat Sep 25 16:29:10 2004

Bios stamp 4.0.855 Sat Sep 25 16:29:08 2004

Plat Bytes 2.0.2

Model Byte 1

Failsafe: LLLLLLLLLL-LL-L-LLLLLLLLLL-LL-L-
Flash sector locked that shouldn't be (0)
Flash sector locked that shouldn't be (1)
Flash sector locked that shouldn't be (2)
Flash sector locked that shouldn't be (3)
Flash sector locked that shouldn't be (4)
Flash sector locked that shouldn't be (5)
Flash sector locked that shouldn't be (6)
Flash sector locked that shouldn't be (7)
Flash sector locked that shouldn't be (8)
Flash sector locked that shouldn't be (9)
Flash sector locked that shouldn't be (11)
Flash sector locked that shouldn't be (12)
Flash sector locked that shouldn't be (14)
Flash sector locked that shouldn't be (16)
Flash sector locked that shouldn't be (17)
Flash sector locked that shouldn't be (18)
Flash sector locked that shouldn't be (19)
Flash sector locked that shouldn't be (20)
Flash sector locked that shouldn't be (21)
Flash sector locked that shouldn't be (22)
Flash sector locked that shouldn't be (23)
Flash sector locked that shouldn't be (24)
Flash sector locked that shouldn't be (25)
Flash sector locked that shouldn't be (27)
Flash sector locked that shouldn't be (28)
Flash failsafe sector not locked(31)

[Geek_Ed]

OK, so the locked BIOS is normal. And I found in the "hacking a 1000" thread this exact same issue, and the guy decided it was a bad board because the drive worked in a different 1100, but I don't think so. I still think it is BIOS/OS version related, this is a newer SnapAppliance model (not a Quantum). I suspect that the version 4.x BIOS requies version 4.x OS.

I will test this theory when the other unit I bought arrives, and post the result (hopefully I don't need another SnapAppliance model 1100)

[Hallis]

Good thing about the 1100 is that, depending on the size of drive that comes in it, they can be had for not too much money off of ebay.

Shane

[blue68f100]

Geek ED the BIOS should be locked, and the OEM should be NON-OEM as reporded, settings are correct.


I think the OS needs to be reinstalled, or at least use a 2200 image file. Mainly because of the hardware differences.

[Geek_Ed]

Well, the new unit came today, and it was one of the ewer "SnapAppliance" models (the graphics on the front of both of mine say SanpAppliance on the front). I check it, and it is the same HW and BIOS version as the unit I am having issues with, i.e. HW 2.0.2 and BIOS 4.0.855.

Imaged the drive, which had the factory loaded OS on it, 4.0.855 (interestingly enough, it matches the BIOS). I loaded that image on the original unit, and all the weird problems went away, no disconnects, I was able to update the OS, no problems at all.

To verify my theory that there is a BIOS/OS version dependency, I put a drive loaded with 3.4.805 on it in the new unit, and it started acting just like the old one, exact same symptoms (could not update it, disconnects from the network after a few minutes, etc.)

So it's my conclusion that with newer 1100 units, the OS must be => the BIOS on the SNAP. A good thing to keep in mind as the "newer" SNAPs are becoming more and more available.

[Hallis]

This might be good info to add to the Wiki.

Good work Ed. Now youve got 2 good working 1100's

Shane