View Single Post
Unread 05-26-2006, 06:53 PM   #8
blue68f100
Thermophile
 
blue68f100's Avatar
 
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
Default Re: uh-oh, pulled the battery out.

That is a update responce. Waiting for down load.

Some times it is related to a missing OS. Do you get the same patern with out a HD?

Bad or missing os generally kicks out "sys/dsk once then dsk twice" which is waiting for IP if it was being updated.

If so try reloading the image file. The 1100's have been a mixed bag. Some uses the 1000 image where other use the 2200. At one time I thought I had them figured out. I was only right about 1/2 the time. There had to be a firmware change some where along the line.

There are several reset procedures to kick these out of loops.
Here is the reset instructions for SnapOS.

a) Power off the Snap! Server.
b) Press in and hold the reset button at the back of the Snap! Server.
c) Power on the Snap! Server while holding in the reset button.
d) Verify that the System and Disk LED are blinking in unison.
e) Release the reset button.
f) Press and release the reset button 4 times. If you press to many times you can continue pressing/releasing the reset button until the 5 flash pattern repeats itself
g) Verify that the Disk LED blinks 4 times, pauses and then blinks 4 times, and continues repeating this pattern. THIS IS RESET TO FACTORY
h) If the pattern was not present, restart at step a.
i) Press in and hold the reset button until the System and Disk led are not lit or blinking.
j) Release the reset button. The server will begin to reboot
__________________
1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5,
1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5,
1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy

Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820
blue68f100 is offline   Reply With Quote