Go Back   Pro/Forums > ProCooling Technical Discussions > Snap Server / NAS / Storage Technical Goodies
Password
Register FAQ Members List Calendar JavaChat Mark Forums Read

Snap Server / NAS / Storage Technical Goodies The Home for Snap Server Hacking, Storage and NAS info. And NAS / Snap Classifides

Reply
Thread Tools
Unread 12-22-2006, 08:30 AM   #1
jt99
Cooling Neophyte
 
Join Date: Mar 2006
Location: Jupiter, FL
Posts: 4
Default Yet another set of orphans

4x30GB Quantum Fireball lct RAID5

One drive dropped (orphaned), replaced it with the exact make/model and converted it to a spare. Snap complained the drive was like 60MB too small and refused to use it. Replaced that with a 40GB Quantum Fireball Plus AS, detected it as a 6.2GB...grrr. Then it dropped a second drive. I've since cloned all 4 original drives to 4 identical Quantum 30GB drives with zero errors. Drives 0 and 1 are both labeled as orphans. Here is what info devices looks like. I also have an identical working unit purchased from eBay and putting the drives in that makes no difference, so it isn't cables/connectors/mobo. I know dropping 2 drives from a RAID5 is craptacular, but there's nothing wrong with the drives (physically) and SNAP won't let me force them online.

Ideas?

Code:
Logical Device: 10000      Position: 1  ORPHAN   Size (KB): 29132303  Free (KB):        0  Public   Unmounted
  Label:Drive1  Orphan from STORAGE01 - RAID5
     Unique Id: 0x2A76ABDA00223F7B
     Partition: 10000  Physical: 10007  ORPHAN   Size (KB): 29132303  Starting Blk: 22910  Public 
      Physical: 10007    Drive Slot: 0  IDE      Size (KB): 29316608  Fixed    

Logical Device: 10006      Position: 0  JBOD     Size (KB):    32296  Free (KB):    30856  Private  Mounted
  Label:Private  Contains system files only
     Unique Id: 0x17AA3AAA65BA336F    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): 29316608  Fixed    

Logical Device: 10008      Position: 2  ORPHAN   Size (KB): 29132303  Free (KB):        0  Public   Unmounted
  Label:Drive2  Orphan from STORAGE01 - RAID5
     Unique Id: 0x2A76ABDA00223F7B
     Partition: 10008  Physical: 1000F  ORPHAN   Size (KB): 29132303  Starting Blk: 22910  Public 
      Physical: 1000F    Drive Slot: 1  IDE      Size (KB): 29316608  Fixed    

Logical Device: 60000      Position: 3  RAID_BROKEN Size (KB):        0  Free (KB):        0  Public   Unmounted
  Label:(Unknown)  Unable to access the information for this disk.
     Unique Id: 0x2A76ABDA00223F7B
     Partition: 10010  Physical: 10017  R 60000  Size (KB): 29132303  Starting Blk: 22910  Public 
      Physical: 10017    Drive Slot: 2  IDE      Size (KB): 29316608  Fixed    
     Partition: 10018  Physical: 1001F  R 60000  Size (KB): 29132303  Starting Blk: 22910  Public 
      Physical: 1001F    Drive Slot: 3  IDE      Size (KB): 29316608  Fixed
jt99 is offline   Reply With Quote
Unread 12-22-2006, 10:58 AM   #2
blue68f100
Thermophile
 
blue68f100's Avatar
 
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
Default Re: Yet another set of orphans

I am assuming this is a 4000. Quantium made 2 drives that had the same name but different in size, by a very small amount. There was another problem that was posted in a earlier thread on units that were upgraded had a different starting point.

To put a long story short. Your starting point is different on one of the drives. The way around it, is to have drive formated in a unit that is running the same OS version as the original hd were formated to.

Need to know the vitals on the snap. Click on the snap logo from the admin page, a popup will display the vitals. Also need to know your model # from the name plate, the -003 will be which hardware version you have. There is a problem with v1 & 2, but can easly be fixed.

Your 40gig drive has a jumper to make it apear small, should be removed.

Try formating the drive with the "/nocore" option. Then re-check the starting point. Data is not lost, it just a bug in the way snap calculated the starting points between OS version. If the drive is reporting to big Quantium has abtility to adjust the drive capacity size.
__________________
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
blue68f100 is offline   Reply With Quote
Unread 12-22-2006, 11:13 AM   #3
jt99
Cooling Neophyte
 
Join Date: Mar 2006
Location: Jupiter, FL
Posts: 4
Default Re: Yet another set of orphans

I have two -001 models both with 4 x Quantum 30GB Fireball lct. One is for parts/etc and the other contains a RAID5 with about 30GB of data.

The 40GB drive I tried to set as a spare did not have a jumper clipping it, it was master on the IDE chain (the other drive, which fell later, was jumpered slave [PK on Quantum]).

My problem right this minute is that I have two orphans from the RAID5 but the disks haven't physically failed, just dropped out. Many systems have a 'force online' feature which will re-introduce the offline disk(s) and fix the problem.

info version
Code:
Product: 2 - "Spinnaker: 4 drive IDE" - Platform Bytes "2.0.1"
Quantum Snap! Server-2.2.393, Build Date: Feb  4 2000 18:59:00
jt99 is offline   Reply With Quote
Unread 12-22-2006, 12:10 PM   #4
Phoenix32
Thermophile
 
Phoenix32's Avatar
 
Join Date: May 2006
Location: Yakima, WA
Posts: 1,282
Default Re: Yet another set of orphans

You can't force both Orphans back into the array. The array has to be rebuilt (all data gone). Or, if you are trying to save your data, then the drives will have to be put into a PC and some recovery software used (there is another thread here somewhere where someone else did this and explained how to do it etc). I strongly suggest cloning the original drives and using the clones for recovery, keeping the old drives as is, just in case...
Phoenix32 is offline   Reply With Quote
Unread 12-22-2006, 12:17 PM   #5
jt99
Cooling Neophyte
 
Join Date: Mar 2006
Location: Jupiter, FL
Posts: 4
Default Re: Yet another set of orphans

I already cloned all 4 drives and have been working with those. I have tried RAID Reconstructor on PC and it found 'results insignificant'.

The server itself has been tested good, I used another 4 drives and created another RAID5 which worked fine.

You mean to say there isn't simply a button that says "Hey Snap, these two drives belong to that RAID5, please let them back in"?

I think the CPU fan failed, perhaps causing some data corruption on the first orphan, then it was just coincidence that the second failed before I could successfully replace the first with a spare. The end-user let it run in degraded mode for some time while trying to pull data off. By the time I received it, the shares weren't accessible any more.
jt99 is offline   Reply With Quote
Unread 12-22-2006, 01:16 PM   #6
blue68f100
Thermophile
 
blue68f100's Avatar
 
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
Default Re: Yet another set of orphans

Sound like you nee to contact Snap-tech (Douglas), he has a recovery service and is well adept to snaps. You need to run "co de info" from debug and see if the starting points are correct. All must be the same. If not one of the drives was replaced earlier after an OS update. This is what caused the starting point error. An easy fix was to reformat the drives after the update. There was also a bug in the firmware. You need to replace the IDE cables to the cable select type, requires cutting 1 lead in the ribbon. Phoenix32 did this. Found the bug when he started testing his throughly. He just happen to have a v4 that had the CS ide cables in it.

There was another thred that went the the same problems with in the last couple of months. I will try to locate the thread.

http://forums.procooling.com/vbb/showthread.php?t=13573

Here's the thread with the different size identical drives.
http://forums.procooling.com/vbb/showthread.php?t=13581
__________________
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

Last edited by blue68f100; 12-22-2006 at 03:27 PM.
blue68f100 is offline   Reply With Quote
Unread 12-22-2006, 02:49 PM   #7
blue68f100
Thermophile
 
blue68f100's Avatar
 
Join Date: Jul 2005
Location: Plano, TX
Posts: 3,135
Default Re: Yet another set of orphans

Need "co de info" its the same as "in de"

This will give you the starting points of the drives. These must start at the same point. Before you can issue a cmd to attempt to join/resync 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
blue68f100 is offline   Reply With Quote
Unread 12-22-2006, 06:46 PM   #8
Phoenix32
Thermophile
 
Phoenix32's Avatar
 
Join Date: May 2006
Location: Yakima, WA
Posts: 1,282
Default Re: Yet another set of orphans

Quote:
Originally Posted by jt99

You mean to say there isn't simply a button that says "Hey Snap, these two drives belong to that RAID5, please let them back in"?
Nope, not gonna happen... It's gone friend... It's gone bye bye... If you cannot reconstruct the RAID from a PC with some reconstruction software, then you are down to letting it go or paying bucks to have someone do it for you.
Phoenix32 is offline   Reply With Quote
Reply


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

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 11:01 AM.


Powered by vBulletin® Version 3.7.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
(C) 2005 ProCooling.com
If we in some way offend you, insult you or your people, screw your mom, beat up your dad, or poop on your porch... we're sorry... we were probably really drunk...
Oh and dont steal our content bitches! Don't give us a reason to pee in your open car window this summer...