Snap 4500 - Snap Disk 10 - Raid Array Issue!

[tryptal]

Hey All-

Hoping someone can help me out with this-
This morning one of my drives had a failure on my second volume that resides on the extension Snap Disk 10- I tried to re-seat the drive and re-sync- The drive failed again during the re-synch-
I then brought the box down to swap another new drive in. (Stupid mistake)-
I didn't have any other drive fail, but when it came back up the raid set was in FAILED status- with all drives showing up as unassigned in that set now. I tried to put the original drive back in and reboot- Same thing.

So now all the drives on that Snap Disk 10 box show green lights, but none are assinged and the volume mount says ERROR under it's status. and FAILED under the Raid sets Status- The green 'WRENCH' LED on the Snap Disk 10 keeps blinking green once per second.

Anyone have any idea what may have happened and how I can get the volume to mount again? It's a 4 drive raid5 array that came stock with the unit.

I've tried re-seating all drives in that array, several reboots, nothing I do will get the machine to recognize that raid set anymore.

Been racking my brain and searching for a solution for the past 10 hours with no progress-

Any help would be GREATLY appreciated!

Thanks!
Rich

[blue68f100]

I think I'm about the only one here who has a S10 unit. I have not used mine in some time, because of another problem.

What version of GOS are you using?

Did you have the disaster recovery active when you powered down?

Did you power up the 4500 without the S10 powered up?

If I recall I did this without any issues, but do not recall if I had the disaster recovery active.

I do know if you bridge or expand your main share on the 4500 the S10 can crash the raid5, all will be lost.

[tryptal]

Thanks for the reply! I have a separate array on the main then on the s10- When it powered down it did a clean shut down so the main 4500 shut down with the S10.. The main array on the 4500 is fine- and I can access the volume. It's just the volume on the s10 won't mount and all the drives say UNASSIGNED - So it seems the volume won't mount- Perhaps it flagged another drive with an error during one of my reboots while it was only running on 3 drives is what I was thinking..
I'm running: GuardianOS 3.2.019
Not sure if there are any commands in the dubug I can run to check out the status of the disks or run a fsck-
I had disaster recovery setup for the primary volume that of course was not the one I lost. (Murphy's Law)- I guess when I added the S10 I forgot to setup disaster recovery for the second volume.
I'm confused because now the system isn't flagging the drive as failed anymore it says they are all OK, but it just won't mount the volume or start the raid array...

[blue68f100]

If I recall the earlier versions of the OS may have had some issues with the S10, but don't hold me to it ( I slept since then). There are some recovery programs that work with the linux/unix file system. You will have to move the HD over to a PC based system so you could run the utility. I have not used an of them. But most allow you to define what drive position there in. I have a habit of labeling HD's with a Sharpy marker as of position and date installed. This way I have no chance of getting the driver order messed up.

The problem I have with my S10 is related with a bad connection on the Controller card. If you bump/touch the cable or any thing to causes vibration I get a communication error, or 5 days which happens first. I tried to resolder the connection but my iron was to low in heat (18 watt) and have not tried it with my hotter iron or different tip (larger).

You did not mention what mfg of drives you were using. I have seen Maxtors fail within days and hrs of each other. So I will not use Maxtors in anything. So if maxtor its has a high probability of another HD failed.

Take a close look at the log files and see it another HD showed up as having a problem.