HELP - Snap 2000 - going into PANIC!
 

Hi,

I have been experiencing a problem with my Snap 2000 recently. I bought some new drives to upgrade but before I installed them, I backed up all the data (or was trying) using FTP to another external PC and USB drive.

I was only able to get about half way through before the Snap would got into PANIC, drop off the network and require pulling the plug to get it to restart. When it did, it would run a check of the drives and begin a mirror resysc. Obviously, this slowed my backup but I persisted and got the data off.

I have now replaced the drives with WD 320Gb (WD3200AAJB) but the Snap continues to go into PANIC while trying to sync the mirror. It seems to run for just under 6 hours each time before failing and locking up.

I have checked all fans and are operating fine, I've tried 2 different RAM modules with no change.

I have persisted with this since Saturday and seem to be getting nowhere, I would appreciate any help.

Thanks.

Here is a copy of the log from 1 instance -

System Details -

Re: HELP - Snap 2000 - going into PANIC!
 

Check your cooling fans and make sure they are working. The 2000v2 are temp controlled by the cpu, most users have set them up to run 24/7. The cpu controls allow the cpu to get real hot before kicking in. Re-seat the ram chip too.

When you swapped HD's, did you break the raid 1 or just installed them (both at the same time) ?

Re: HELP - Snap 2000 - going into PANIC!
 

Thanks for your reply.

I have reseated RAM several times, including trying 2 different modules (original 64Mb and 256Mb).

I did break the Raid 1 before removing the original drives as that was the only way I could complete a full data backup. Drives seem to run fine in JBOD config, the problem only appears either while original 80Gb drives were in Raid 1 or while trying to sync new drives to Raid 1.

Both fans are working. The main fan I have replaced with an uprated CFM fan but the CPU fan is still the temp controlled original setup. I've checked and the CPU fan is cycling on and off but I will try rewiring it to run full time.

Any further ideas would be great.

Cheers,
Kris.

Re: HELP - Snap 2000 - going into PANIC!
 

BTW, I did search this error and although a couple of people have experienced this same log error, no one seemed to come up with a solution. :(

Thanks again.

Re: HELP - Snap 2000 - going into PANIC!
 

David, drives have a different start point (init in different OS)?

my 2 cents

Re: HELP - Snap 2000 - going into PANIC!
 

To find that out we need the resutls of "co de info" from debug

Re: HELP - Snap 2000 - going into PANIC!
 

Pre-Mirror "co de info"

Re: HELP - Snap 2000 - going into PANIC!
 

Hmmm .. The drives appear to be different sizes even though they are identical and purchased at the same time.

Using the Western Digital Diag tool, I ran a sector scan on the drives to detect bad sectors but it came up passed with no errors. Could it have marked some sectors bad without telling me? ... I'm sure they were reporting the same size earlier.

What have I done wrong? :confused:

Re: HELP - Snap 2000 - going into PANIC!
 

I tried reformatting a couple of times to see what happened.

The log shows a few warning about cyl counts, etc ... are these something to be worried about?

Re: HELP - Snap 2000 - going into PANIC!
 

OK, I've hard wired the CPU fan and started the mirror sync again, we'll see what happens ... ;)

Re: HELP - Snap 2000 - going into PANIC!
 

Well that's that, 3 minutes and 36 seconds shy of 6 hours, PANIC. Seems to be a time limited thing to me.

:mad:

Re: HELP - Snap 2000 - going into PANIC!
 

If you formatted under v3 then upgraded to v4, then installed the second drive, you must /reinit both drives. The 2 versions calculate the starting point dfferently. Then re check the starting points. Must be the same.

You may need to use the drive utility by WD and set the drive capacity so they match.

Then re-format the drives using the /init cmd. Drives should not be in raid. the SNAP OS does not like drives that are different capacty.

This is a MAJOR problem on 4x00 units. Don't see it very often on 2000.

Re: HELP - Snap 2000 - going into PANIC!
 

OK, ran a low level format on both drives using an XP machine.

I have got both drives to match all the important numbers now so I'm going to give it one more try, if it doesn't work this time, I think the lot will be going on ebay!!! :doh:

Re: HELP - Snap 2000 - going into PANIC!
 

Starting blocks are now the same and you have the smaller drive in the correct position 10000. See what happens, should work now.

Re: HELP - Snap 2000 - going into PANIC!
 

Grrrrr ... same thing. Just on 6 hours, PANIC!

I reckon it's software/OS problem. Can I downgrade the OS to an erlier version without bricking the unit?

I think the version I have around here somwhere is 3.4.805.

Re: HELP - Snap 2000 - going into PANIC!
 

Have you tried re-loading the OS? (use Assist)

The 2000 has the OS in flashram and not be reversed.

Normally this is a hardware problem.

Do you have a different set of drives you can try? (250 or smaller)

Re: HELP - Snap 2000 - going into PANIC!
 

Nup, reloaded OS from Assist. Resync, 6 hours later, PANIC!

I don't have any other drives to test, other than the original 80Gb drives I bought it with. I think because of the whole 6 hour thing, it must be a setting or software bug/"feature" that no one is aware of.

Me thinks I've had enough O' this shiat ... :mad:

Re: HELP - Snap 2000 - going into PANIC!
 

It's a hardware problem. Software is not the problem. How do you have the drives setup as Both Master or CS?

Should be set to Master for a 2000v2. But if its not working try CS and see what happens.

Re: HELP - Snap 2000 - going into PANIC!
 

I did a full rollback of the OS to 4.0.830.

The unit no longer goes into panic but still fails the sync on the 80Gb drives after about 1 hour 15 mins. At least the unit doesn't lock up and drop off the network.

Not sure I've got any further though, really.

I've changed to CS and restarted the sync. Only thing left to try is change the IDE cables to see if they are a problem, then it becomes a missle through a window ... lol