4100 recover from degraded mode?

crystallake · 12-03-2008, 10:52 AM

Can anyone tell me if it is possible to get the RAID back up so I can pull the data off?

Model Software Hardware BIOS
4000 series 4.0.860 (US) 2.2.1 2.4.437
4 120gb seagates
raid over 123 with 4 as hot spare

12/03/2008 10:46:10 Command: in dev pa

Current HDD State: 01 02 03 04
In In In In

Physical: 10007 Drive Slot: 0 IDE Size (KB): 117220352 Fixed
Partition: 10000 Physical: 10007 R 60000 Size (KB): 116466112 Starting Blk: 94152 Public
Partition: 10002 Physical: 10007 NOFS Size (KB): 4096 Starting Blk: 3 Private
Partition: 10003 Physical: 10007 NOFS Size (KB): 585248 Starting Blk: 20996 Private
Partition: 10004 Physical: 10007 NOFS Size (KB): 131080 Starting Blk: 4611 Private
Partition: 10007 Physical: 10007 NOFS Size (KB): 117220352 Starting Blk: 0 Private

Physical: 1000F Drive Slot: 1 IDE Size (KB): 117220352 Fixed
Partition: 10008 Physical: 1000F ORPHAN Size (KB): 116466112 Starting Blk: 94152 Public
Partition: 1000A Physical: 1000F NOFS Size (KB): 4096 Starting Blk: 3 Private
Partition: 1000B Physical: 1000F NOFS Size (KB): 585248 Starting Blk: 20996 Private
Partition: 1000C Physical: 1000F NOFS Size (KB): 131080 Starting Blk: 4611 Private
Partition: 1000E Physical: 1000F FS Size (KB): 32768 Starting Blk: 515 Private
Partition: 1000F Physical: 1000F NOFS Size (KB): 117220352 Starting Blk: 0 Private

Physical: 10017 Drive Slot: 2 IDE Size (KB): 117220352 Fixed
Partition: 10010 Physical: 10017 R 60000 Size (KB): 116466112 Starting Blk: 94152 Public
Partition: 10012 Physical: 10017 NOFS Size (KB): 4096 Starting Blk: 3 Private
Partition: 10013 Physical: 10017 NOFS Size (KB): 585248 Starting Blk: 20996 Private
Partition: 10014 Physical: 10017 NOFS Size (KB): 131080 Starting Blk: 4611 Private
Partition: 10016 Physical: 10017 NOFS Size (KB): 32768 Starting Blk: 515 Private
Partition: 10017 Physical: 10017 NOFS Size (KB): 117220352 Starting Blk: 0 Private

Physical: 1001F Drive Slot: 3 IDE Size (KB): 117220352 Fixed
Partition: 10018 Physical: 1001F SPARE Size (KB): 116466112 Starting Blk: 94152 Public
Partition: 1001A Physical: 1001F NOFS Size (KB): 4096 Starting Blk: 3 Private
Partition: 1001B Physical: 1001F NOFS Size (KB): 585248 Starting Blk: 20996 Private
Partition: 1001C Physical: 1001F NOFS Size (KB): 131080 Starting Blk: 4611 Private
Partition: 1001E Physical: 1001F NOFS Size (KB): 32768 Starting Blk: 515 Private
Partition: 1001F Physical: 1001F NOFS Size (KB): 117220352 Starting Blk: 0 Private

------------
Command executed without error.

12/03/2008 10:51:04 Command: co de info

Logical Device: 10006 Position: 0 JBOD Size (KB): 32768 Free (KB): 0 Private Unmounted
Label:Private Contains system files only
Unique Id: 0x3BA787FD22DD1FBC Mount: /priv Index: 12 Order: 255
Partition: 10006 Physical: 10007 FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 10007 Drive Slot: 0 IDE Size (KB): 117220352 Fixed

Logical Device: 1000E Position: 0 JBOD Size (KB): 32296 Free (KB): 23960 Private Mounted
Label:Private Contains system files only
Unique Id: 0x2DAD87385FD11FC5 Mount: /pri2 Index: 13 Order: 0
Partition: 1000E Physical: 1000F FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 1000F Drive Slot: 1 IDE Size (KB): 117220352 Fixed

Logical Device: 10008 Position: 1 ORPHAN Size (KB): 116466112 Free (KB): 0 Public Unmounted
Label:Drive2 Orphan from SNAP_DATA_VAULT - RAID5
Unique Id: 0x66504C7A71F15DF0
Partition: 10008 Physical: 1000F ORPHAN Size (KB): 116466112 Starting Blk: 94152 Public
Physical: 1000F Drive Slot: 1 IDE Size (KB): 117220352 Fixed

Logical Device: 60000 Position: 2 RAID_CRACKED Size (KB): 232932224 Free (KB): 0 Public Unmounted
Label:RAID5 Large data protection disk
Unique Id: 0x66504C7A71F15DF0 Mount: /0 Index: 0 Order: 255
Partition: 10000 Physical: 10007 R 60000 Size (KB): 116466112 Starting Blk: 94152 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 117220352 Fixed
Partition: 10010 Physical: 10017 R 60000 Size (KB): 116466112 Starting Blk: 94152 Public
Physical: 10017 Drive Slot: 2 IDE Size (KB): 117220352 Fixed

Logical Device: 10018 Position: 3 SPARE Size (KB): 116466112 Free (KB): 0 Public Unmounted
Label:Spare4 Reserved for data protection
Unique Id: 0x5D28D4F333128C8B
Partition: 10018 Physical: 1001F SPARE Size (KB): 116466112 Starting Blk: 94152 Public
Physical: 1001F Drive Slot: 3 IDE Size (KB): 117220352 Fixed

------------
Command executed without error.

12/03/2008 10:51:38 Command: info device

Logical Device: 10006 Position: 0 JBOD Size (KB): 32768 Free (KB): 0 Private Unmounted
Label:Private Contains system files only
Unique Id: 0x3BA787FD22DD1FBC Mount: /priv Index: 12 Order: 255
Partition: 10006 Physical: 10007 FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 10007 Drive Slot: 0 IDE Size (KB): 117220352 Fixed

Logical Device: 1000E Position: 0 JBOD Size (KB): 32296 Free (KB): 23960 Private Mounted
Label:Private Contains system files only
Unique Id: 0x2DAD87385FD11FC5 Mount: /pri2 Index: 13 Order: 0
Partition: 1000E Physical: 1000F FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 1000F Drive Slot: 1 IDE Size (KB): 117220352 Fixed

Logical Device: 10008 Position: 1 ORPHAN Size (KB): 116466112 Free (KB): 0 Public Unmounted
Label:Drive2 Orphan from SNAP_DATA_VAULT - RAID5
Unique Id: 0x66504C7A71F15DF0
Partition: 10008 Physical: 1000F ORPHAN Size (KB): 116466112 Starting Blk: 94152 Public
Physical: 1000F Drive Slot: 1 IDE Size (KB): 117220352 Fixed

Logical Device: 60000 Position: 2 RAID_CRACKED Size (KB): 232932224 Free (KB): 0 Public Unmounted
Label:RAID5 Large data protection disk
Unique Id: 0x66504C7A71F15DF0 Mount: /0 Index: 0 Order: 255
Partition: 10000 Physical: 10007 R 60000 Size (KB): 116466112 Starting Blk: 94152 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 117220352 Fixed
Partition: 10010 Physical: 10017 R 60000 Size (KB): 116466112 Starting Blk: 94152 Public
Physical: 10017 Drive Slot: 2 IDE Size (KB): 117220352 Fixed

Logical Device: 10018 Position: 3 SPARE Size (KB): 116466112 Free (KB): 0 Public Unmounted
Label:Spare4 Reserved for data protection
Unique Id: 0x5D28D4F333128C8B
Partition: 10018 Physical: 1001F SPARE Size (KB): 116466112 Starting Blk: 94152 Public
Physical: 1001F Drive Slot: 3 IDE Size (KB): 117220352 Fixed

------------
Command executed without error.

crystallake · 12-03-2008, 12:49 PM

disks
1 2 3 4

raid was 1 2 3
spare is 4

If I simply pull the cables from bad disk 2 (Drive slot 1) and reboot will my 3 disk array automatically rebuild using spare 4?

Or do I need to issue some command?

any ideas? It looks like I should be in good shape as array was across three disks and two report online but it is not autobuilding upon boot and the raid is offline.

crystallake · 12-03-2008, 04:56 PM

on the GUI interface it reports disks configured as...

The server's disks are configured as follows:
Drive2
(Individual)

RAID5
(RAID 5)

Spare4
(Spare)

Select an operation below and we'll guide you through it. Note that only individual disks can be used to create a disk configuration.

Create a Disk Configuration Create a Disk Configuration
Create a Data Protected Disk (RAID 5 or disk mirroring), One Large Disk (disk striping), or a Spare Disk.
Remove a Disk Configuration Remove a Disk Configuration
Change a Data Protected Disk, One Large Disk, or a Spare Disk back to individual disks.

>>should I remove the Drive 2 orphan from this menu?

Not touching anything until someone can advise me .
Thanks

blue68f100 · 12-03-2008, 05:20 PM

You do not want to do any thing to break the array if you want your data back.

You may remove the failed HD if you like. Just make sure you get the right one, other wise all is lost. 2 outs and your out.

If you already had a hot spare normally it only takes a reboot of the snap to start the process. If not change it to Hot Spare.

Power down and replace the failed HD.
Boot the snap
Once up wait about 5 min
Migrate to the drive configuration page.
Select the newly installed HD, set it as a Hot Spare.
Then walk away. It my take the snap many hours to init the drive and start the array rebuild. Be Patient.
If it hangs in the 5% area, this is the area where the snap stores all of it tables. NOT GOOD.
If it does it may indicate another HD is having problem.

crystallake · 12-03-2008, 07:04 PM

This is how it sits right now.... I am happy to leave the bad drive in if I can rebuild the raid using the spare.

Leaving the bad drive in, how do I get it to rebuild the raid?

Currently the raid is offline

12/03/2008 19:05:10 Command: info device

Logical Device: 10006 Position: 0 JBOD Size (KB): 32768 Free (KB): 0 Private Unmounted
Label:Private Contains system files only
Unique Id: 0x3BA787FD22DD1FBC Mount: /priv Index: 12 Order: 255
Partition: 10006 Physical: 10007 FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 10007 Drive Slot: 0 IDE Size (KB): 117220352 Fixed

Logical Device: 1000E Position: 0 JBOD Size (KB): 32296 Free (KB): 23960 Private Mounted
Label:Private Contains system files only
Unique Id: 0x2DAD87385FD11FC5 Mount: /pri2 Index: 13 Order: 0
Partition: 1000E Physical: 1000F FS Size (KB): 32768 Starting Blk: 515 Private
Physical: 1000F Drive Slot: 1 IDE Size (KB): 117220352 Fixed

Logical Device: 10008 Position: 1 ORPHAN Size (KB): 116466112 Free (KB): 0 Public Unmounted
Label

rive2 Orphan from SNAP_DATA_VAULT - RAID5
Unique Id: 0x66504C7A71F15DF0
Partition: 10008 Physical: 1000F ORPHAN Size (KB): 116466112 Starting Blk: 94152 Public
Physical: 1000F Drive Slot: 1 IDE Size (KB): 117220352 Fixed

Logical Device: 60000 Position: 2 RAID_CRACKED Size (KB): 232932224 Free (KB): 0 Public Unmounted
Label:RAID5 Large data protection disk
Unique Id: 0x66504C7A71F15DF0 Mount: /0 Index: 0 Order: 255
Partition: 10000 Physical: 10007 R 60000 Size (KB): 116466112 Starting Blk: 94152 Public
Physical: 10007 Drive Slot: 0 IDE Size (KB): 117220352 Fixed
Partition: 10010 Physical: 10017 R 60000 Size (KB): 116466112 Starting Blk: 94152 Public
Physical: 10017 Drive Slot: 2 IDE Size (KB): 117220352 Fixed

Logical Device: 10018 Position: 3 SPARE Size (KB): 116466112 Free (KB): 0 Public Unmounted
Label:Spare4 Reserved for data protection
Unique Id: 0x5D28D4F333128C8B
Partition: 10018 Physical: 1001F SPARE Size (KB): 116466112 Starting Blk: 94152 Public
Physical: 1001F Drive Slot: 3 IDE Size (KB): 117220352 Fixed

------------
Command executed without error.

crystallake · 12-03-2008, 07:12 PM

"If you already had a hot spare normally it only takes a reboot of the snap to start the process. If not change it to Hot Spare."

Sorry, it already had disk 4 as a hot spare, I have rebooted and it comes back up exactly as posted this thread. The spare is in there now, how do I make it use the spare?

blue68f100 · 12-03-2008, 08:14 PM

Just set it as Spare.

crystallake · 12-04-2008, 07:43 AM

I apologize for my ignorance, but is it not already set as spare?

On the View Disk Status page is clearly says Spare4
Does that not mean it is already set as spare?

Disk Status Page
-Red Image- Drive 2 Orphan
-Grey Image- RAID5 Data protection disabled. One RAID 5 member has failed. Operating in degraded mode.
-Green Image- Spare 4 - Reserved for data protection OK

blue68f100 · 12-04-2008, 08:17 AM

If id did not use the spare, power down and remove the HD (spare). Use any utility you want to do a quick format. Any format except linux/unix. The reinstall, once the unit comes up, set it as a spare and see if it will use it. This will not happen very quick. It take around 10 min for the init to happen some times. One it it is inited, it will then start the resysnc, this can take 24hrs at time.

Just out of curisity, how full is the array/drive. If more than 90% it may have a problem.

Also have you checked to see if your unit has the updated or patched MB. The sticky at the top of the threads will show you what to look for.

crystallake · 12-04-2008, 08:21 AM

I will check for the patch, I checked when I updated the drives two years ago but cannot remember. I think it was about 35%-45% full, so mostly empty as the hopes and dreams of a ten year old milk cow at the slaughter house.

I can format the drive using XP? Just format as NTFS?

again, I apologize if this has been answered a million times elsewhere.

12-03-2008, 10:52 AM	#1
crystallake Cooling Neophyte Join Date: Sep 2006 Location: alabama Posts: 20	4100 recover from degraded mode? Can anyone tell me if it is possible to get the RAID back up so I can pull the data off? Model Software Hardware BIOS 4000 series 4.0.860 (US) 2.2.1 2.4.437 4 120gb seagates raid over 123 with 4 as hot spare 12/03/2008 10:46:10 Command: in dev pa Current HDD State: 01 02 03 04 In In In In Physical: 10007 Drive Slot: 0 IDE Size (KB): 117220352 Fixed Partition: 10000 Physical: 10007 R 60000 Size (KB): 116466112 Starting Blk: 94152 Public Partition: 10002 Physical: 10007 NOFS Size (KB): 4096 Starting Blk: 3 Private Partition: 10003 Physical: 10007 NOFS Size (KB): 585248 Starting Blk: 20996 Private Partition: 10004 Physical: 10007 NOFS Size (KB): 131080 Starting Blk: 4611 Private Partition: 10007 Physical: 10007 NOFS Size (KB): 117220352 Starting Blk: 0 Private Physical: 1000F Drive Slot: 1 IDE Size (KB): 117220352 Fixed Partition: 10008 Physical: 1000F ORPHAN Size (KB): 116466112 Starting Blk: 94152 Public Partition: 1000A Physical: 1000F NOFS Size (KB): 4096 Starting Blk: 3 Private Partition: 1000B Physical: 1000F NOFS Size (KB): 585248 Starting Blk: 20996 Private Partition: 1000C Physical: 1000F NOFS Size (KB): 131080 Starting Blk: 4611 Private Partition: 1000E Physical: 1000F FS Size (KB): 32768 Starting Blk: 515 Private Partition: 1000F Physical: 1000F NOFS Size (KB): 117220352 Starting Blk: 0 Private Physical: 10017 Drive Slot: 2 IDE Size (KB): 117220352 Fixed Partition: 10010 Physical: 10017 R 60000 Size (KB): 116466112 Starting Blk: 94152 Public Partition: 10012 Physical: 10017 NOFS Size (KB): 4096 Starting Blk: 3 Private Partition: 10013 Physical: 10017 NOFS Size (KB): 585248 Starting Blk: 20996 Private Partition: 10014 Physical: 10017 NOFS Size (KB): 131080 Starting Blk: 4611 Private Partition: 10016 Physical: 10017 NOFS Size (KB): 32768 Starting Blk: 515 Private Partition: 10017 Physical: 10017 NOFS Size (KB): 117220352 Starting Blk: 0 Private Physical: 1001F Drive Slot: 3 IDE Size (KB): 117220352 Fixed Partition: 10018 Physical: 1001F SPARE Size (KB): 116466112 Starting Blk: 94152 Public Partition: 1001A Physical: 1001F NOFS Size (KB): 4096 Starting Blk: 3 Private Partition: 1001B Physical: 1001F NOFS Size (KB): 585248 Starting Blk: 20996 Private Partition: 1001C Physical: 1001F NOFS Size (KB): 131080 Starting Blk: 4611 Private Partition: 1001E Physical: 1001F NOFS Size (KB): 32768 Starting Blk: 515 Private Partition: 1001F Physical: 1001F NOFS Size (KB): 117220352 Starting Blk: 0 Private ------------ Command executed without error. 12/03/2008 10:51:04 Command: co de info Logical Device: 10006 Position: 0 JBOD Size (KB): 32768 Free (KB): 0 Private Unmounted Label:Private Contains system files only Unique Id: 0x3BA787FD22DD1FBC Mount: /priv Index: 12 Order: 255 Partition: 10006 Physical: 10007 FS Size (KB): 32768 Starting Blk: 515 Private Physical: 10007 Drive Slot: 0 IDE Size (KB): 117220352 Fixed Logical Device: 1000E Position: 0 JBOD Size (KB): 32296 Free (KB): 23960 Private Mounted Label:Private Contains system files only Unique Id: 0x2DAD87385FD11FC5 Mount: /pri2 Index: 13 Order: 0 Partition: 1000E Physical: 1000F FS Size (KB): 32768 Starting Blk: 515 Private Physical: 1000F Drive Slot: 1 IDE Size (KB): 117220352 Fixed Logical Device: 10008 Position: 1 ORPHAN Size (KB): 116466112 Free (KB): 0 Public Unmounted Label:Drive2 Orphan from SNAP_DATA_VAULT - RAID5 Unique Id: 0x66504C7A71F15DF0 Partition: 10008 Physical: 1000F ORPHAN Size (KB): 116466112 Starting Blk: 94152 Public Physical: 1000F Drive Slot: 1 IDE Size (KB): 117220352 Fixed Logical Device: 60000 Position: 2 RAID_CRACKED Size (KB): 232932224 Free (KB): 0 Public Unmounted Label:RAID5 Large data protection disk Unique Id: 0x66504C7A71F15DF0 Mount: /0 Index: 0 Order: 255 Partition: 10000 Physical: 10007 R 60000 Size (KB): 116466112 Starting Blk: 94152 Public Physical: 10007 Drive Slot: 0 IDE Size (KB): 117220352 Fixed Partition: 10010 Physical: 10017 R 60000 Size (KB): 116466112 Starting Blk: 94152 Public Physical: 10017 Drive Slot: 2 IDE Size (KB): 117220352 Fixed Logical Device: 10018 Position: 3 SPARE Size (KB): 116466112 Free (KB): 0 Public Unmounted Label:Spare4 Reserved for data protection Unique Id: 0x5D28D4F333128C8B Partition: 10018 Physical: 1001F SPARE Size (KB): 116466112 Starting Blk: 94152 Public Physical: 1001F Drive Slot: 3 IDE Size (KB): 117220352 Fixed ------------ Command executed without error. 12/03/2008 10:51:38 Command: info device Logical Device: 10006 Position: 0 JBOD Size (KB): 32768 Free (KB): 0 Private Unmounted Label:Private Contains system files only Unique Id: 0x3BA787FD22DD1FBC Mount: /priv Index: 12 Order: 255 Partition: 10006 Physical: 10007 FS Size (KB): 32768 Starting Blk: 515 Private Physical: 10007 Drive Slot: 0 IDE Size (KB): 117220352 Fixed Logical Device: 1000E Position: 0 JBOD Size (KB): 32296 Free (KB): 23960 Private Mounted Label:Private Contains system files only Unique Id: 0x2DAD87385FD11FC5 Mount: /pri2 Index: 13 Order: 0 Partition: 1000E Physical: 1000F FS Size (KB): 32768 Starting Blk: 515 Private Physical: 1000F Drive Slot: 1 IDE Size (KB): 117220352 Fixed Logical Device: 10008 Position: 1 ORPHAN Size (KB): 116466112 Free (KB): 0 Public Unmounted Label:Drive2 Orphan from SNAP_DATA_VAULT - RAID5 Unique Id: 0x66504C7A71F15DF0 Partition: 10008 Physical: 1000F ORPHAN Size (KB): 116466112 Starting Blk: 94152 Public Physical: 1000F Drive Slot: 1 IDE Size (KB): 117220352 Fixed Logical Device: 60000 Position: 2 RAID_CRACKED Size (KB): 232932224 Free (KB): 0 Public Unmounted Label:RAID5 Large data protection disk Unique Id: 0x66504C7A71F15DF0 Mount: /0 Index: 0 Order: 255 Partition: 10000 Physical: 10007 R 60000 Size (KB): 116466112 Starting Blk: 94152 Public Physical: 10007 Drive Slot: 0 IDE Size (KB): 117220352 Fixed Partition: 10010 Physical: 10017 R 60000 Size (KB): 116466112 Starting Blk: 94152 Public Physical: 10017 Drive Slot: 2 IDE Size (KB): 117220352 Fixed Logical Device: 10018 Position: 3 SPARE Size (KB): 116466112 Free (KB): 0 Public Unmounted Label:Spare4 Reserved for data protection Unique Id: 0x5D28D4F333128C8B Partition: 10018 Physical: 1001F SPARE Size (KB): 116466112 Starting Blk: 94152 Public Physical: 1001F Drive Slot: 3 IDE Size (KB): 117220352 Fixed ------------ Command executed without error.

12-03-2008, 12:49 PM	#2
crystallake Cooling Neophyte Join Date: Sep 2006 Location: alabama Posts: 20	Re: 4100 recover from degraded mode? disks 1 2 3 4 raid was 1 2 3 spare is 4 If I simply pull the cables from bad disk 2 (Drive slot 1) and reboot will my 3 disk array automatically rebuild using spare 4? Or do I need to issue some command? any ideas? It looks like I should be in good shape as array was across three disks and two report online but it is not autobuilding upon boot and the raid is offline.

12-03-2008, 04:56 PM	#3
crystallake Cooling Neophyte Join Date: Sep 2006 Location: alabama Posts: 20	Re: 4100 recover from degraded mode? on the GUI interface it reports disks configured as... The server's disks are configured as follows: Drive2 (Individual) RAID5 (RAID 5) Spare4 (Spare) Select an operation below and we'll guide you through it. Note that only individual disks can be used to create a disk configuration. Create a Disk Configuration Create a Disk Configuration Create a Data Protected Disk (RAID 5 or disk mirroring), One Large Disk (disk striping), or a Spare Disk. Remove a Disk Configuration Remove a Disk Configuration Change a Data Protected Disk, One Large Disk, or a Spare Disk back to individual disks. >>should I remove the Drive 2 orphan from this menu? Not touching anything until someone can advise me . Thanks

12-03-2008, 05:20 PM	#4
blue68f100 Thermophile Join Date: Jul 2005 Location: Plano, TX Posts: 3,135	Re: 4100 recover from degraded mode? You do not want to do any thing to break the array if you want your data back. You may remove the failed HD if you like. Just make sure you get the right one, other wise all is lost. 2 outs and your out. If you already had a hot spare normally it only takes a reboot of the snap to start the process. If not change it to Hot Spare. Power down and replace the failed HD. Boot the snap Once up wait about 5 min Migrate to the drive configuration page. Select the newly installed HD, set it as a Hot Spare. Then walk away. It my take the snap many hours to init the drive and start the array rebuild. Be Patient. If it hangs in the 5% area, this is the area where the snap stores all of it tables. NOT GOOD. If it does it may indicate another HD is having problem. __________________ 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-03-2008 at 05:26 PM.

12-03-2008, 07:04 PM	#5
crystallake Cooling Neophyte Join Date: Sep 2006 Location: alabama Posts: 20	Re: 4100 recover from degraded mode? This is how it sits right now.... I am happy to leave the bad drive in if I can rebuild the raid using the spare. Leaving the bad drive in, how do I get it to rebuild the raid? Currently the raid is offline 12/03/2008 19:05:10 Command: info device Logical Device: 10006 Position: 0 JBOD Size (KB): 32768 Free (KB): 0 Private Unmounted Label:Private Contains system files only Unique Id: 0x3BA787FD22DD1FBC Mount: /priv Index: 12 Order: 255 Partition: 10006 Physical: 10007 FS Size (KB): 32768 Starting Blk: 515 Private Physical: 10007 Drive Slot: 0 IDE Size (KB): 117220352 Fixed Logical Device: 1000E Position: 0 JBOD Size (KB): 32296 Free (KB): 23960 Private Mounted Label:Private Contains system files only Unique Id: 0x2DAD87385FD11FC5 Mount: /pri2 Index: 13 Order: 0 Partition: 1000E Physical: 1000F FS Size (KB): 32768 Starting Blk: 515 Private Physical: 1000F Drive Slot: 1 IDE Size (KB): 117220352 Fixed Logical Device: 10008 Position: 1 ORPHAN Size (KB): 116466112 Free (KB): 0 Public Unmounted Labelrive2 Orphan from SNAP_DATA_VAULT - RAID5 Unique Id: 0x66504C7A71F15DF0 Partition: 10008 Physical: 1000F ORPHAN Size (KB): 116466112 Starting Blk: 94152 Public Physical: 1000F Drive Slot: 1 IDE Size (KB): 117220352 Fixed Logical Device: 60000 Position: 2 RAID_CRACKED Size (KB): 232932224 Free (KB): 0 Public Unmounted Label:RAID5 Large data protection disk Unique Id: 0x66504C7A71F15DF0 Mount: /0 Index: 0 Order: 255 Partition: 10000 Physical: 10007 R 60000 Size (KB): 116466112 Starting Blk: 94152 Public Physical: 10007 Drive Slot: 0 IDE Size (KB): 117220352 Fixed Partition: 10010 Physical: 10017 R 60000 Size (KB): 116466112 Starting Blk: 94152 Public Physical: 10017 Drive Slot: 2 IDE Size (KB): 117220352 Fixed Logical Device: 10018 Position: 3 SPARE Size (KB): 116466112 Free (KB): 0 Public Unmounted Label:Spare4 Reserved for data protection Unique Id: 0x5D28D4F333128C8B Partition: 10018 Physical: 1001F SPARE Size (KB): 116466112 Starting Blk: 94152 Public Physical: 1001F Drive Slot: 3 IDE Size (KB): 117220352 Fixed ------------ Command executed without error.

12-03-2008, 07:12 PM	#6
crystallake Cooling Neophyte Join Date: Sep 2006 Location: alabama Posts: 20	Re: 4100 recover from degraded mode? "If you already had a hot spare normally it only takes a reboot of the snap to start the process. If not change it to Hot Spare." Sorry, it already had disk 4 as a hot spare, I have rebooted and it comes back up exactly as posted this thread. The spare is in there now, how do I make it use the spare?

12-03-2008, 08:14 PM	#7
blue68f100 Thermophile Join Date: Jul 2005 Location: Plano, TX Posts: 3,135	Re: 4100 recover from degraded mode? Just set it as Spare. __________________ 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

12-04-2008, 07:43 AM	#8
crystallake Cooling Neophyte Join Date: Sep 2006 Location: alabama Posts: 20	Re: 4100 recover from degraded mode? I apologize for my ignorance, but is it not already set as spare? On the View Disk Status page is clearly says Spare4 Does that not mean it is already set as spare? Disk Status Page -Red Image- Drive 2 Orphan -Grey Image- RAID5 Data protection disabled. One RAID 5 member has failed. Operating in degraded mode. -Green Image- Spare 4 - Reserved for data protection OK

12-04-2008, 08:17 AM	#9
blue68f100 Thermophile Join Date: Jul 2005 Location: Plano, TX Posts: 3,135	Re: 4100 recover from degraded mode? If id did not use the spare, power down and remove the HD (spare). Use any utility you want to do a quick format. Any format except linux/unix. The reinstall, once the unit comes up, set it as a spare and see if it will use it. This will not happen very quick. It take around 10 min for the init to happen some times. One it it is inited, it will then start the resysnc, this can take 24hrs at time. Just out of curisity, how full is the array/drive. If more than 90% it may have a problem. Also have you checked to see if your unit has the updated or patched MB. The sticky at the top of the threads will show you what to look for. __________________ 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

12-04-2008, 08:21 AM	#10
crystallake Cooling Neophyte Join Date: Sep 2006 Location: alabama Posts: 20	Re: 4100 recover from degraded mode? I will check for the patch, I checked when I updated the drives two years ago but cannot remember. I think it was about 35%-45% full, so mostly empty as the hopes and dreams of a ten year old milk cow at the slaughter house. I can format the drive using XP? Just format as NTFS? again, I apologize if this has been answered a million times elsewhere.

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