dEad Snap 2000

[gmcdermott]

We have 2 Snap 2000 servers.
Hardware version 2.0.0 (2ea 30 gig disks)
Software 2.4.441
Until now they have given us great service. One has for the past 6 months been dropping off line. Reset (power off and back on) and it would come back.
It now will not reset regardless of number of tries or time. At first I thought it was a bad disk so I physically swapped HDs between the two servers. Problem remains with the appliance itself (disks work in other unit).
You can see the snap on network but not the disks.

I have tried manually resetting per the snap manual – no luck.

LED codes are as follows”
Sys – 1 blink every second
Link – Solid green
Net – 2 rapid blinks, pause, 2 rapid blinks, etc
Disk – nothing

Checking via the web program (disk check) I get a FSCK Error 39.

Any help or suggestions would be appreciated.

[Hallis]

See if you can reload the OS. the older 2000's were really picky about jumper settings, i believe they need to be set as master/slave.

Make sure the jumper settings of the drives you put in match the ones you took out.

Shane

[gmcdermott]

We have not rplaced any hard drives. They are the originals and have worked for 3 years. I suspect we have lost a MB but thought someone might have a different idea.

[blue68f100]

Snap-tech has a list of what the error codes means and may be able to give more detail. Are there any more error codes beside the FSCK?

You say you can still access the interface without seeing the drives, this is std with the 2000, since OS is in flashram. Are both using the same version of OS? And are both units the v2 2000, DIMM PC100/133 ram. Verify that the HD settings were the same, some were shipped with CS other M/S.

Try swaping the whole unit with the other snap you have to eliminate the net hardware. Were both of your units using the same mfg of drives? Hitachi/IBM, Maxtors or WD seam to be the most common. The 2000 does not require hd to boot.

What drive setup are you using JBOD, RAID 0 or 1 ???

http://www.northwesttechnical.com/ Has replacement motherboards if you decide to repair.

[gmcdermott]

Both of our Snap 2000 are the same. 2 - 30 GiG Quantum Fireball drives configured into one 60 Gig.
They are all jumpered CS.

I have swapped HDs and the all are fine in the one snap (let's call it Snap 1). None of them show up in the other (call it Snap 2).
I believe there was a error message 190 but not sure. I have pulled the unit.

[blue68f100]

Setup as spanning (Raid0) does not offer any data protection. You say it work for a short period of time the shuts down. With the unit open, verify that the CPU and Case fans are operating. I think the cpu fan is temp controlled, so you may have to watch it.

[gmcdermott]

I had the case open - fan works, hDs spin up.
Latest - After beign shut down for a couple days I plugged the bad snap back in and it came up. Was able to pull data off. Going into admin the snap shows up, changed name, also IP address. Went to check disk and after 5% get message "cannot access disks". Back to windows and the files show and can be opened. Running software 2.4

[blue68f100]

You have determined that it's not the drives. So that only leaves the MB or PS. It apears that it is overheating and shutting down. Did you check on the fans when the error showed up. I've seen many fans run for a short period, then stop. Since you have 2 models you can confirm which one. You don't have very many options since you confirmed the HD worked in the other unit. Unless you did not run it long enough to confirm the HD's were not acting up. In raid 0 only one drive needs to actup to kill the complete set.