• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Areca 1680 IX Failed Migration

R

Rhogorn

n00b
Joined
Apr 29, 2013
Messages
6
So during a migration from 13 to 14 drives in a raid 6 array, I inserted 2 new drives into the computer (to be used later). About some time later I noticed my file server rebooting about every 5 minutes. I plugged up a monitor to see what was going on and noticed the raid firmware timing out and restarting it. A suggestion I found was to reset the onboard cache...probably the stupidest thing I could have done. But unfortunately I had taken the advice and did it without thinking about migration cache.

Areca web console showed that one of the new drives had failed, and that drive 7 of the array had failed and that drive 8 had gone missing. Removing the doa drive allowed the firmware to boot but the raid is now in the failed migration state.


This is a personal system; most of the data on here is backed up elsewhere, however there are certain things on here that I would like to recover.

I was curious as how to to about this as I'm now trying to research all my options before I try anything destructive (more so x.x).

What's the RESCUE command do? would i have to delete the set first and hope it finds it? since it was migrating (it was at 30%, just fyi) would it even see all the data? What about the LeVeL2ReScUe i read about in another post (shame it didn't say what it did)

I might even be okay if i have to use recovery software (r-studio comes to mind) even if i had to let it scan 14 drives to pull the first 30%, and then again on 13 drives for the remainder, minus the probably destroyed data that it was currently processing. I don't even know if that's possible, as I'm not experienced in recovering raids.


snippet of event log

Code: 
2013-04-21 22:29:23 	010.001.000.050 	HTTP Log In 	  	 
2013-04-21 22:26:49 	Incomplete RAID 	Discovered 	  	 
2013-04-21 22:26:49 	H/W Monitor 	Raid Powered On 	  	 
2013-04-21 22:25:06 	RS232 Terminal 	VT100 Log In 	  	 
2013-04-21 22:24:23 	H/W Monitor 	Raid Powered On 	  	 
2013-04-21 22:24:22 	Enc#2 SLOT 17 	Device Removed 	  	 
2013-04-21 22:24:20 	Enc#2 SLOT 18 	Device Removed 	  	 
2013-04-21 22:21:57 	010.001.000.050 	HTTP Log In 	  	 
2013-04-20 19:03:02 	010.001.000.050 	HTTP Log In 	  	 
2013-04-20 18:43:02 	010.001.000.050 	HTTP Log In 	  	 
2013-04-20 18:37:16 	000:0004C1001000 	Lost Rebuilding/Migration LBA 	  	 
2013-04-20 18:37:16 	Incomplete RAID 	Discovered 	  	 
2013-04-20 18:37:15 	H/W Monitor 	Raid Powered On 	  	 
2013-04-20 18:36:24 	ARC-1680-VOL#000 	Start Migrating 	  	 
2013-04-20 18:36:22 	Raid #1 	Rebuild RaidSet 	  	 
2013-04-20 18:36:22 	ARC-1680-VOL#000 	Failed Volume Revived 	  	 
2013-04-20 18:36:22 	Enc#2 SLOT 12 	Device Inserted 	  	 
2013-04-20 18:36:18 	Enc#2 SLOT 07 	Device Removed 	  	 
2013-04-20 18:36:18 	Raid #1 	RaidSet Degraded 	  	 
2013-04-20 18:36:17 	Enc#2 SLOT 12 	Device Removed 	  	 
2013-04-20 18:36:17 	Raid #1 	RaidSet Degraded 	  	 
2013-04-20 18:36:16 	ARC-1680-VOL#000 	Volume Failed 	  	 
2013-04-20 18:36:15 	ARC-1680-VOL#000 	Stop Migration 	000:00:05 	 
2013-04-20 18:36:15 	ARC-1680-VOL#000 	Volume Failed 	  	 
2013-04-20 18:36:10 	ARC-1680-VOL#000 	Start Migrating 	  	 
2013-04-20 18:36:09 	Raid #1 	Rebuild RaidSet 	  	 
2013-04-20 18:36:09 	Enc#2 SLOT 07 	Device Inserted 	  	 
2013-04-20 18:36:08 	Raid #1 	Rebuild RaidSet 	  	 
2013-04-20 18:36:08 	ARC-1680-VOL#000 	Failed Volume Revived 	  	 
2013-04-20 18:36:08 	Enc#2 SLOT 08 	Device Inserted 	  	 
2013-04-20 18:36:07 	Raid #1 	Rebuild RaidSet 	  	 
2013-04-20 18:36:07 	Enc#2 SLOT 12 	Device Inserted 	  	 
2013-04-20 18:36:04 	Enc#2 SLOT 08 	Device Removed 	  	 
2013-04-20 18:36:04 	Enc#2 SLOT 07 	Device Removed 	  	 
2013-04-20 18:36:03 	Raid #1 	RaidSet Degraded 	  	 
2013-04-20 18:36:03 	Raid #1 	RaidSet Degraded 	  	 
2013-04-20 18:36:03 	Enc#2 SLOT 12 	Device Removed 	  	 
2013-04-20 18:36:03 	Raid #1 	RaidSet Degraded 	  	 
2013-04-20 18:36:01 	ARC-1680-VOL#000 	Volume Failed 	  	 
2013-04-20 18:36:01 	ARC-1680-VOL#000 	Volume Failed 	  	 
2013-04-20 18:36:01 	ARC-1680-VOL#000 	Volume Failed 	  	 
2013-04-20 18:36:00 	Raid #1 	Rebuild RaidSet 	  	 
2013-04-20 18:36:00 	Enc#2 SLOT 08 	Device Inserted 	  	 
2013-04-20 18:35:59 	Raid #1 	Rebuild RaidSet 	  	 
2013-04-20 18:35:59 	ARC-1680-VOL#000 	Failed Volume Revived 	  	 
2013-04-20 18:35:59 	Enc#2 SLOT 07 	Device Inserted 	  	 
2013-04-20 18:35:56 	Enc#2 SLOT 08 	Device Removed 	  	 
2013-04-20 18:35:55 	Raid #1 	RaidSet Degraded 	  	 
2013-04-20 18:35:55 	Enc#2 SLOT 07 	Device Removed 	  	 
2013-04-20 18:35:54 	Raid #1 	RaidSet Degraded 	  	 
2013-04-20 18:35:53 	ARC-1680-VOL#000 	Volume Failed 	  	 
2013-04-20 18:35:52 	ARC-1680-VOL#000 	Stop Migration 	000:00:04
 
Don't run those commands. You might make it worse.

Have you contacted Areca? Start there.
Do you have 13 spare disks to image to using R-studio?
 
I contacted areca the 21st and I've yet to get a response. I do not have 13 spare discs, sadly. I do have enough spare storage laying around to store the data from the raid if i was able to access it, though
 
Well the card recognizes your raidset, which is a start, but im hesitant to tell you the next step because its in a failed migration state, with no backups. Do you have a friend that would let you borrow 13 drives to do uncompressed images? Who did you contact at Areca? Kevin wang? support@areca.com.tw
 
unfortunately no; no one i know in close proximity even has 1 3tb drives
if it comes down to it i may hold off recovery to acquire some drives to mirror the current setup, but it's definitely not in the budget atm

i did not address anyone specifically as i didn't know whom to request but that is the email i sent my situation to.

in the past, i have recovered data from a somewhat failed raid 0, but with raid 6 i'm new to recovery methods x.x
 
Yea Raid6 presents some additional challenges. Even R-Studio does not recognize the Areca Raid6 Striping, so you would have to do it manually.

I hate to say this, but until you can get some drives, I would hold off on recovery, chances are you are going to need a second chance.
 
Okay, I've started acquiring more drives, what's the best method of mirroring the drives? Is r-studio's image tool acceptable? I'm assuming I'll have to mirror them in a different computer so the areca card doesn't flip out?
 
Yea R-Studio is what I used in the past. Do not do compressed images, it will take longer, wont net you much space saving and most importantly, you will need uncompressed images for the recovery.
 
I meant to ask, the 14th drive (the one that was being migrated into the array), that one isn't important and I can use it to mirror another drive, yes? I thought I would need 14 drives...just wanted to confirm.
 
In lieu of mirroring all the drives, I recorded the raid configuration and drive order then deleted the raidset. I recreated it with no-init in read only mode in the drive order listed and now using r-studio to full scan the array for all files and plan on pulling the ones i need to the new drives i bought. i'm not concerned with the former raid and will be replacing it with a raid 60 when all former vital data recovered.

when i first started scanning the drives i'd pause at about 50GB and see the files recovered to check for corruption (bad raid creation parameters, etc.) some files were okay but some were not; is there any way to confirm the drives are in the correct order? i believe the raid controller listed the drive order based on initial creation but if u moved drives around (had a bad backplane x.x) the order could not be linear

my reported order was 1,2,x,4,x,8,6,7,9,10,11,12,13,14
drives 3 and 5 were kicked out for whatever reason and labeled as 'free'
i repositioned the drives in the 'expected' 1-14 order and recreated hoping it would all line up

the longer i run the scan, the more files seem to come out better so i've been letting that take it's course (take about a week)

i wanted to know if i'm on the right track and if there are any ways to confirm or help find the proper drive order in case the drives were switched and i'd never know about it

also, what about the migration process? how does that effect the raid? will it be necessary to scan the first 30% with one configuration (14 drives) and 30%-100% with the other (13 drives)?

so far i have recovered some important data off of the raid, so at least there's some progress...but there's one file in particular that is 1TB in size (it's a container for other files) that i need...so i need to make sure everything is aligned properly (stars, too ;) )

i appreciate the help so far, sorry if it seems like i'm ignoring advice to mirror, a read-only scan seemed safe enough and i knew i wouldn't be able to recover the raid w/o deleting it first....i tried setting all drives as pass-through and using r-studio, but i believe i'd need to know more about areca's raid 6 methods before i could configure that properly
 
Last edited:
You must log in or register to reply here.
Back
Top