Re: RAID 10 recovery question


"RAIDwoes" <sbraudrick@xxxxxxxxx> wrote in message
news:1181573788.308477.38620@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I'm hoping someone will see this and set my mind at ease.

I have a Dell PE 2600 with 6 73GB 15k SCSI drives on a PERC 4/Di
controller arranged as follows:

Physical Disks:
Disks 0 & 1 = RAID 1 (OS partition, Server2003)
Disks 2 & 3 = RAID 0 (Array 1)
Disks 4 & 5 = RAID 0 (Array 2)

Logical Drives:
0 = OS partition
1 = RAID 1 (Array1 & Array 2)

Here's what happened and the issue I am having:

When moving the server from one rack to another the BIOS lost its
settings, evidently the battery was dead.

The BIOS showed the Integrated controller in SCSI mode instead of RAID
mode.

To ensure I didn't lose any of the data on physical disks 2 - 5, I
numbered and removed them from the server.

Then I replaced the battery and checked to make sure the BIOS was
holding the settings even in a no-power situation. After I confirmed
that I changed the mode to RAID and the machine restarted.

When I booted into the RAID configuration, disk 1 showed as "FAILED",
so I rebuilt it and then rebooted.

This time the machine booted into Server 2003 without a hitch, so I
shut it down and then re-inserted disks 2 - 5 and powered the machine
back on. Server 2003 started with no problems but could not see the
logical drive 1.

I rebooted into the RAID configuration. Disks 2 & 3 show "FAILED" and
disks 4 & 5 show "ONLINE". The RAID controller will not allow me to
rebuild disks 2 or 3.

If my understanding is correct, disks 4 & 5 should be a striped set
that contain all information of the mirrored set of disks 2 & 3. In
theory at least, this should be a recoverable state, but I don't want
to monkey around and end up losing the data on logical drive 1 since
it contains newly installed software that (as you may have guessed)
has not been backed up yet.

Any ideas, thoughts, or resources that you may offer will be greatly
appreciated.


Cut and paste your post here and I bet you'll receive more responses with
more first-hand knowledge:

http://www.dellcommunity.com/supportforums/board?board.id=pes_hardrive

You may have to register, but it will be worth it.

Good luck -

Stew

Stew


.

Relevant Pages

  • Re: [SLE] Machine Building - Nightmare Alley - Compatibility and Upgrade
    ... On the other side I've been using Gigabyte boards with SuSE for years no ... graphic cards as the server terminal stays in text mode anyway. ... > department) that I will have to install their SuSe 9.1 distribution from ... Disks have a limited life time... ...
    (SuSE)
  • Re: Unix runs faster, maybe (was: Re: Educating potential VMS users)
    ... That's what I just suggested, Kerry: they're limited by disk I/O, not CPU, and hence CPU utilization *will* be low, even if the disks are working their little tails off. ... A server with very low CPU utilization is a *good* candidate for virtualization, since it's got lots of horsepower left over for other tasks that admins might be reluctant to run on the same OS instance: just hook up some more disks to service the added applicationand let 'er rip. ...
    (comp.os.vms)
  • Re: panic after removing usb flash disk
    ... are only interested in it for its use as a server or embedded OS. ... they 1) stopped using single disks in their multi-thousand-dollar ... ATA disks with no hotswap capability. ... I have no idea whether Juniper is a contributor to FreeBSD. ...
    (freebsd-stable)
  • Re: Exchange Disks
    ... I was looking at using a cheaper alternative with 7,200 RPM Server SATA ... Logs raid 1 mirror ... consider single drives for the OS and or Logs instead of mirrors. ... Is there some sort of rule-of-thumb for setting up disks based on a number ...
    (microsoft.public.exchange.setup)
  • Re: PowerEdge 1800 Spontaneous Reboots
    ... you're seeing the server crashing? ... I thought it could be the raid controller, but no HDD are attached to ... RAID 1 Mirror array spanning the whole of the 160GB. ... rebuilding the MBR or BOOT record with both disks plugged into the ...
    (microsoft.public.windows.server.sbs)