Snap 4100 Orphan Issue

GrAfiX · 10-11-2007, 08:42 AM

Here's the story...

I have a Snap 4100 in a Raid 5 configuration.

The other day one of the hard drives failed... No big deal, replaced the drive, rebuilt everything working fine.

Seeing as though I figured this thing was gonna crap out any day I started to backup all the data... Using RoboCopy to sync another server it hit some Open or busy files... Damn people just don't understand stay off the File server... So I rebooted the server to kick those people off this was done through SnapOS. Well the drives never came back up... Not getting an IP address. Rebooted many times it had a network link...Soooo

Well I unplugged all the drive and reset the CMOS.. Great now it's booting into snap OS with a differen't IP. I'm on the phone with Adaptec support by this time I was fiddling with it on the phone. I tell the guy I don't need him but he did give me a tip to unplug one drive at a time and see if it would boot that way... Hung up the phone, plugged the drives back in... It booted, however the Raid container was broken and in degraded mode, however I couldn't access anything. So I shut it down and to follow the directions of adaptec I unplugged Disk position 2... (1 was the replaced drive) boots back up and now I have 3 orpaned drives...

Shut it down plugged 2 back in and have 1 raid container (drive 2) and 3 individual drives that are orphaned...

What can I do... Adaptec support said I'm FUBAR howeve they would push it to higher techs...

The Drives aren't bad or at least I don't believe. So how can I get these back into a Raid Set??? I read some stuff about "config devices config raid" Can I manual put the raid back together with this???

Can I throw these drives into another machine and use a Raid Recovery tool???

Let me know how I should procede as I don't want to jack it up any more than it already is.

Thanks
Mike

GrAfiX · 10-11-2007, 08:45 AM

Logical Device: 10000 Position: 1 ORPHAN Size (KB): 133377984 Free (KB): 0 Public Unmounted
Label

rive1 Large data protection disk
Unique Id: 0x1FB0210B3EEF683D
Partition: 10000 Physical: 10007 ORPHAN Size (KB): 133377984 Starting Blk: 104776 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 134217216 Fixed

Logical Device: 10006 Position: 0 JBOD Size (KB): 32296 Free (KB): 32120 Private Mounted
Label:Private Contains system files only
Unique Id: 0x0179338F3644A532 Mount: /priv Index: 0 Order: 0
Partition: 10006 Physical: 10007 FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 10007 Drive Slot: 0 IDE Size (KB): 134217216 Fixed

Logical Device: 10010 Position: 2 ORPHAN Size (KB): 97028944 Free (KB): 0 Public Unmounted
Label

rive3 Orphan from SNAP509437 - RAID5
Unique Id: 0x1FB0210B3EEF683D
Partition: 10010 Physical: 10017 ORPHAN Size (KB): 97028944 Starting Blk: 81942 Public
Physical: 10017 Drive Slot: 2 IDE Size (KB): 97685504 Fixed

Logical Device: 10018 Position: 3 ORPHAN Size (KB): 97028944 Free (KB): 0 Public Unmounted
Label

rive4 Orphan from SNAP509437 - RAID5
Unique Id: 0x1FB0210B3EEF683D
Partition: 10018 Physical: 1001F ORPHAN Size (KB): 97028944 Starting Blk: 81942 Public
Physical: 1001F Drive Slot: 3 IDE Size (KB): 97685504 Fixed

Logical Device: 60000 Position: 4 RAID_BROKEN Size (KB): 0 Free (KB): 0 Public Unmounted
Label

Unknown) Unable to access the information for this disk.
Unique Id: 0x1FB0210B3EEF683D
Partition: 10008 Physical: 1000F R 60000 Size (KB): 97028944 Starting Blk: 81942 Public
Physical: 1000F Drive Slot: 1 IDE Size (KB): 97685504 Fixed

blue68f100 · 10-11-2007, 11:55 AM

Well you did something you should never do, that is disconnect a HD that had not failed after already having a failed drive that had not completed the resync. Normally when this happens you must use a recovery service to recover your data.

You also have a larger HD in drive 1 position. This is a NO NO on snaps.

They use this drive to determine the size af the raid5 array. All starting blocks must be the same.

Having 2 drives failed on a 4 drive raid5 you do not have enough parity data on 2 drives to recover from. This applys to ALL RAID5 units. Your only choice is a recovery service.

You would have been a lot better off by pulling the cat5 cable from the 4100 dropping off all users. Then give the snap time to do the resysnc. Then connect using a crossover cable if the snap has a static IP. Or use a managed switch to kick the users off by creating a virtual lan, with the 4100, your pc and backup server/drive. At times it takes a snap several hrs to come on line. This happens when it is doing a check/resync on the drives.

Also check to make sure your units has been repaired to handle larger drives. Sticky on top of thread. Not all 4100 were repaired. Snap only contacted 4100 240gig owners that had registered with them. So units upgraded were not repaired.

Sorry being the bearer of BAD NEWS.

Being impacient (panic) caused you to destroy the raind5 array.

My recommendation right now is for you to contact a recovery service. You should have 3 drives that contain all of your data. Your original failed HD may not be complete. This will be expensive, but if you must have the data, it's your best chance. Under NO Circumstances move your drives to a PC and try to read the drives. The file structure is a Highly Modified XFS on BSD, so nothing but a snap or special recovery software can read the drives.

Phoenix32 · 10-11-2007, 12:29 PM

Well, my answer will be shorter. You're screwed, unless you want to use a recovery service.

The Adaptec tech who told you to unplug drives in a failing array was an idiot!

You needed to figure out which drive was the problem and replace it, not any others. When you unplugged a good drive from the degraded arrary, you killed the array. No way to get it back without software that will rebuild your array for you (i.e. what a recovery service will do).

GrAfiX · 10-11-2007, 12:36 PM

The Raid was fine 4 working drives yesterday after it rebuilt the array.. All was in good working order, no orphans nothing...

Then restarted the server... wouldn't reboot... Disconnected all drives, booted up reconnected wouldn't boot up. Disconnected Drive 2 it booted up with 3 orphaned drives. shut down, plugged all drives in.. Drive 2 was showing raid 5 the other 3 were orphaned.

Not that 2 drives were failed at the same time.

And yes I feel the Adaptec technition did F me by telling me to do that.

Doesn't make sense why the thing wouldn't boot back up and get an IP.... I put on a ping trace on it and pinged 4 times right after start up and then lost the connection and never would come back. all lights seemed fine too.

10-11-2007, 08:42 AM	#1
GrAfiX Cooling Neophyte Join Date: Oct 2007 Location: NJ Posts: 4	Snap 4100 Orphan Issue Here's the story... I have a Snap 4100 in a Raid 5 configuration. The other day one of the hard drives failed... No big deal, replaced the drive, rebuilt everything working fine. Seeing as though I figured this thing was gonna crap out any day I started to backup all the data... Using RoboCopy to sync another server it hit some Open or busy files... Damn people just don't understand stay off the File server... So I rebooted the server to kick those people off this was done through SnapOS. Well the drives never came back up... Not getting an IP address. Rebooted many times it had a network link...Soooo Well I unplugged all the drive and reset the CMOS.. Great now it's booting into snap OS with a differen't IP. I'm on the phone with Adaptec support by this time I was fiddling with it on the phone. I tell the guy I don't need him but he did give me a tip to unplug one drive at a time and see if it would boot that way... Hung up the phone, plugged the drives back in... It booted, however the Raid container was broken and in degraded mode, however I couldn't access anything. So I shut it down and to follow the directions of adaptec I unplugged Disk position 2... (1 was the replaced drive) boots back up and now I have 3 orpaned drives... Shut it down plugged 2 back in and have 1 raid container (drive 2) and 3 individual drives that are orphaned... What can I do... Adaptec support said I'm FUBAR howeve they would push it to higher techs... The Drives aren't bad or at least I don't believe. So how can I get these back into a Raid Set??? I read some stuff about "config devices config raid" Can I manual put the raid back together with this??? Can I throw these drives into another machine and use a Raid Recovery tool??? Let me know how I should procede as I don't want to jack it up any more than it already is. Thanks Mike

10-11-2007, 08:45 AM	#2
GrAfiX Cooling Neophyte Join Date: Oct 2007 Location: NJ Posts: 4	Re: Snap 4100 Orphan Issue Logical Device: 10000 Position: 1 ORPHAN Size (KB): 133377984 Free (KB): 0 Public Unmounted Labelrive1 Large data protection disk Unique Id: 0x1FB0210B3EEF683D Partition: 10000 Physical: 10007 ORPHAN Size (KB): 133377984 Starting Blk: 104776 Public Physical: 10007 Drive Slot: 0 IDE Size (KB): 134217216 Fixed Logical Device: 10006 Position: 0 JBOD Size (KB): 32296 Free (KB): 32120 Private Mounted Label:Private Contains system files only Unique Id: 0x0179338F3644A532 Mount: /priv Index: 0 Order: 0 Partition: 10006 Physical: 10007 FS Size (KB): 32768 Starting Blk: 515 Private Physical: 10007 Drive Slot: 0 IDE Size (KB): 134217216 Fixed Logical Device: 10010 Position: 2 ORPHAN Size (KB): 97028944 Free (KB): 0 Public Unmounted Labelrive3 Orphan from SNAP509437 - RAID5 Unique Id: 0x1FB0210B3EEF683D Partition: 10010 Physical: 10017 ORPHAN Size (KB): 97028944 Starting Blk: 81942 Public Physical: 10017 Drive Slot: 2 IDE Size (KB): 97685504 Fixed Logical Device: 10018 Position: 3 ORPHAN Size (KB): 97028944 Free (KB): 0 Public Unmounted Labelrive4 Orphan from SNAP509437 - RAID5 Unique Id: 0x1FB0210B3EEF683D Partition: 10018 Physical: 1001F ORPHAN Size (KB): 97028944 Starting Blk: 81942 Public Physical: 1001F Drive Slot: 3 IDE Size (KB): 97685504 Fixed Logical Device: 60000 Position: 4 RAID_BROKEN Size (KB): 0 Free (KB): 0 Public Unmounted LabelUnknown) Unable to access the information for this disk. Unique Id: 0x1FB0210B3EEF683D Partition: 10008 Physical: 1000F R 60000 Size (KB): 97028944 Starting Blk: 81942 Public Physical: 1000F Drive Slot: 1 IDE Size (KB): 97685504 Fixed

10-11-2007, 11:55 AM	#3
blue68f100 Thermophile Join Date: Jul 2005 Location: Plano, TX Posts: 3,135	Re: Snap 4100 Orphan Issue Well you did something you should never do, that is disconnect a HD that had not failed after already having a failed drive that had not completed the resync. Normally when this happens you must use a recovery service to recover your data. You also have a larger HD in drive 1 position. This is a NO NO on snaps. They use this drive to determine the size af the raid5 array. All starting blocks must be the same. Having 2 drives failed on a 4 drive raid5 you do not have enough parity data on 2 drives to recover from. This applys to ALL RAID5 units. Your only choice is a recovery service. You would have been a lot better off by pulling the cat5 cable from the 4100 dropping off all users. Then give the snap time to do the resysnc. Then connect using a crossover cable if the snap has a static IP. Or use a managed switch to kick the users off by creating a virtual lan, with the 4100, your pc and backup server/drive. At times it takes a snap several hrs to come on line. This happens when it is doing a check/resync on the drives. Also check to make sure your units has been repaired to handle larger drives. Sticky on top of thread. Not all 4100 were repaired. Snap only contacted 4100 240gig owners that had registered with them. So units upgraded were not repaired. Sorry being the bearer of BAD NEWS. Being impacient (panic) caused you to destroy the raind5 array. My recommendation right now is for you to contact a recovery service. You should have 3 drives that contain all of your data. Your original failed HD may not be complete. This will be expensive, but if you must have the data, it's your best chance. Under NO Circumstances move your drives to a PC and try to read the drives. The file structure is a Highly Modified XFS on BSD, so nothing but a snap or special recovery software can read the drives. __________________ 1 Snap 4500 - 1.0T (4 x 250gig WD2500SB RE), Raid5, 1 Snap 4500 - 1.6T (4 x 400gig Seagates), Raid5, 1 Snap 4200 - 4.0T (4 x 2gig Seagates), Raid5, Using SATA converts from Andy Link to SnapOS FAQ's http://forums.procooling.com/vbb/showthread.php?t=13820

10-11-2007, 12:29 PM	#4
Phoenix32 Thermophile Join Date: May 2006 Location: Yakima, WA Posts: 1,282	Re: Snap 4100 Orphan Issue Well, my answer will be shorter. You're screwed, unless you want to use a recovery service. The Adaptec tech who told you to unplug drives in a failing array was an idiot! You needed to figure out which drive was the problem and replace it, not any others. When you unplugged a good drive from the degraded arrary, you killed the array. No way to get it back without software that will rebuild your array for you (i.e. what a recovery service will do). __________________ ~ 6 x Snap 4400 (SATA Converted) 2 x Snap 4500 (SATA Converted) 1 x Snap 110 5 x Snap 410 3 x Snap 520 2 x Sanbloc S50 Drives from 250GB to 2TB (PATA, SATA, and SAS) GOS v5.2.067 All subject to change, day by day......

10-11-2007, 12:36 PM	#5
GrAfiX Cooling Neophyte Join Date: Oct 2007 Location: NJ Posts: 4	Re: Snap 4100 Orphan Issue The Raid was fine 4 working drives yesterday after it rebuilt the array.. All was in good working order, no orphans nothing... Then restarted the server... wouldn't reboot... Disconnected all drives, booted up reconnected wouldn't boot up. Disconnected Drive 2 it booted up with 3 orphaned drives. shut down, plugged all drives in.. Drive 2 was showing raid 5 the other 3 were orphaned. Not that 2 drives were failed at the same time. And yes I feel the Adaptec technition did F me by telling me to do that. Doesn't make sense why the thing wouldn't boot back up and get an IP.... I put on a ping trace on it and pinged 4 times right after start up and then lost the connection and never would come back. all lights seemed fine too. Last edited by GrAfiX; 10-11-2007 at 12:41 PM.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)