Problems with failure on a 2000 model in mirror mode

[dunkz]

Hey all,

I bought a used 2000 v2 model (quantum) a few years ago and it's been great for me. Last week I had a failure and I"m having a hard time figuring out if any of this is recoverable. The disk has two 190 db drives in it in a mirror setup. I did this precisely to have a safe place to keep things should a disk fail.

Here is a copy of the status page from the admin ui:

From what it looks like, one of the disks failed but I was having a hard time figuring out which one it was. I got a replacement drive, same make/model/everything. I replaced what I thought was the bad drive and on boot it seems likt the unit is in a continual reboot state. I can only connect to the admin UI very briefly and then the machine stops responding to pings entirely.

After a bit I decided that maybe I replaced the wrong disk. So I put the one I took out in place of the one I left in. This time the unit came up and showed my new (empty) disk and one disk that had "unknown disk operation" errors. This made me think I had the wrong disk so I went back to the other one only this time I changed which drive was connected to which IDE channel. I get the same continual reboot problem.

I'm a bit lost at this point and was hoping one of you could shed some light on the issue. Here's the machine's current specs:

Model Software Hardware BIOS
2000 series 4.0.860 (US) 2.0.0 2.0.282

Here is a link to a copy of the server log before I removed the faulty disk.

THanks for any help you can offer!

[blue68f100]

It apears the smart tech is reporting 10002 is failed, this is the master drive (10000, drive 0). It is also reporting a problem loading the os, too.
Make sure you set the jumpers correctly on your replacement drives. Some are M/S while others are CS, you can not mix. Master is usually the end of the cable.

The error you are getting may be due to the starrting point is not correct. This can happens if the snap has been upgraded or the existing HD are reporting a different capacity. HD with the same model number can have different capacity, due to a different firmware revision.

Has this unit been through update, starting with 1 or v2?

Run these cmd from debug, to get to debug:
ipaddress/config/debug and press enter. Ipaddress is the address of your Snap Server.

Enter in lo p -1 and press enter

Save the information as HTML only and email it to me.

and
"co de info"

[dunkz]

Well currently I can't get to the UI because it is stuck in a permanent reboot state. Which drive configuration should I go back to? The original where it failed or new drive with the failure drive configuration? Both allowed the system to remain responsive.

The one causing the reboots is the new drive + the old one that didn't fail as far as I can tell.

The drives are all the same capacity, and none have any master/slave settings on the jumpers set.

I did not do the firmware updates myself it was purchased with this done already.

Thanks!
-Greg

[blue68f100]

Install the original drives back in. In there original positions.

[Phoenix32]

I am going to stay out of this one with it being a 2000, but David is already on the track I would be, so listen to him...

[blue68f100]

What I'm loosing backup ...

[Phoenix32]

Originally Posted by blue68f100

What I'm loosing backup ...

Uh no. I am just going to shut up unless I see an obvious glitch...

[dunkz]

Well I put the original drives in , in the original configuration. The device powers on but gets no further. I can't connect to the admin server at all :/ The system and link LEDs are on and not flashing.

My main concern here is to save the data on the drives. Is there some way I can get it off by putting the drives in a PC? Maybe boot a linux liveCD or something?

[blue68f100]

No, DON'T DO that or you will loose all. You can only read it with another snap.

Verify the jumpers are set correctly. If so try again. If no go, reset the snap to factory settings. Will not change the drive config, but will reset password and network settings. So you will need assist to set the IP address for your network.

[dunkz]

Hi blue,

Thanks for the help so far I really do appreciate it.

Here's the latest update. Nothing seems to be getting its attention, I can't even get the reset to take. Something wrong with the unit atm but I"m not sure what. THe only symptom of note is that once it's powered up I don't even have to flip the power switch to get it to turn off. The slightest touch of the switch makes it power down. It's acting quite weird :/

[blue68f100]

It has ESP power now, that must be a new feature.

Are you doing the reset correctly as posted in the FAQ and WIKI?

Sounds like a loose connection.

On my 2000 I had problem with the power connections to the HD's. The sockets had discolored which indicates heat. I used a pic to tighten the sockets. Also be careful with the shield, I had mine cut through the insulation and blew the fuse.

The 2000 will boot with out HD installed. Disconnect the HD and see if you gain access. Then try connecting 1 drive at a time. You can do all of this with the case open. If both drives are set to master or slave it want boot to.

Does yours have the 2032 battery? It has been proven that some models will not boot without a good battery.

[dunkz]

Hey Blue,

Sorry for the long time between responses, I finally had time to sit down with this. When I disconnect all drives and try to boot same thing. THe lights are on but no one is home.

I noticed that the fan on the mainboard isn't spinning. That made me think either the board isn't getting power or the fan only goes on as needed. I looked at the connections and nothing was loose as far as I could tell.

[blue68f100]

The fan is temp controlled on v2's.

Have you tried a reset to factory? Then assist to do the basic setup.

If you have a spare drive any size Install it as master and see if the snap will setup a new drive. If not you have a HW problem.

[dunkz]

Yeah I tried using a spare drive, reset to factory, etc. It's just not responding.

What are my options at this point for getting my data off of the disk?

[blue68f100]

You can try swapping drive positions. If you have hardware a failure in the snap the only option is another 2000v2, with the same OS version installed in flash. It must be the same OS version, v2 and v3 use a different disk structure. In all of the 2000 I have worked around at least one of the HD would boot the snap. Double check your jumpers, it's the most common mistake. Try with only 1 drive at a time.

OR

If you do not have one, contact Snap-tech for recovery. He should be able to help you.

[dunkz]

Well it seems the HW is really giving out. Now it won't even power on despite my not really doing anything to it other than removing the drives.

I need to find some other way to retrieve my data if at all possible. Who/What is Snap-Tech?

[blue68f100]

Snap-tech is a X SnapAppliance (Quantium) employee that has started his own recovery service, Front Line Recovery Service. Since you have a MB failure, it should not be much for data recovery. You can reach Douglas at 1-866-279-2985. I talked to him last night, he has just finished up on a couple of big jobs. So he should beable to give you a quick turn around.

It's bad that you went to the precaution to preserve you data, then you loose hardware that hosted it. I too, got caught in that circle. This is why no matter what you use, backups are still required. Even if to another NAS. Though I prefer to backup up to some other media than hard drives. That way I do not require anything special hardware.

[dunkz]

Hi all, I'm drudging up this post as I just got my hands on a new replacement unit since the HW was the problem (at least).

What I'd like to know is what's the best way to recover my data with a new unit? Remember that I'm not entirely sure that one of the drives died or not. The new unit is the same hw (2.0) and OS rev. What are the steps to getting the old drive into the unit to recover my data?

Thanks!

[blue68f100]

If your unit was in RAID1, just move the drives over. Or if you want to use the new drives in the new unit. Just move 1 drive, then copy the data over to the new one. Once complete remove your org data drive and reinstall the new drive. If the drive you copied the data over to was in the master position, you can just re-configure the unit for RAID1. It will then mirror the HD.

[Phoenix32]

Make sure the new unit is using the same OS as before if at all possible...

[dunkz]

Thanks for the replies guys,

Yes it is the same rev of the OS. My main concern was if I pop the drives in I didn't want it reformatting the disks and wiping them.

Does it recognize it as a RAID1 pair already and just operate as such? Or if I put one old and one new disk in will the old one be accessible? I'm just not sure of the exact steps.