Re: Need to migrate system drive from Raid 0 to Raid 1 - HP Smart Array 6400 ML-370 Ghost?



I apologize - you are correct - I am looking to go from Raid 0 to
Raid 1. I am actually using Windows Server 2003 Standard Edition -
maybe I should repost in another forum. I was suprised at the BSOD -
when it starting loading the OS I thought we were home free.
So you don't think any raid info from the 0 array would be on the
Ghost image and casue trouble on the new raid 1 array? I think I am
going to try to put the image on a single drive in an attempt to
isolate the issue. If it works in that format I will simply add a 2nd
formatted drive and creat a raid 1 array with the ACU.
ANy other thoughts - my ears are open!

Thanks for the reply,

Chris.

SuperGumby [SBS MVP] wrote:
there's a couple of things questionable with your description. We should
clear it up.

You suggest:
2 other logical drives corrected to be Raid 0+1 for the mail store and logs
drive

and then go on to say:
install two new drives of the same size configured as Raid 0+1

For RAID0+1 you need four physical HDD's and from your description I don't
_think_ this is what you have, but it could be, maybe the confusion is mine.
The four HDD's would appear as one physical drive to the OS and may then be
divided into logical drives.

I'm surprised you're getting the BSOD with the change of array type. As
suggested by Rob I'd expect the same driver to be used accessing either RAID
type. I do know of controllers which use one driver to access nonRAID drives
and another to access RAID drives but don't expect this to be relevent in
the circumstances.

just check whether your description needs rewording.

RAID0 = 2 HDD's appear as one drive to the OS, twice the capacity of one
HDD, no redundancy.
RAID1 = 2 HDD's appear as one drive to the OS, capacity equals one HDD, full
redundancy.
RAID0+1 = 4 HDD's appear as one drive to the OS, twice the capacity of one
HDD, full redundancy.

also, you don't mention Small Business Server anywhere and this group is
SBS. I'm not overly concerned if you're in the wrong group but with the
problems you are experiencing you may be better off going to a more general
group or simply doing a fresh install to drives configured in the manner you
wish.

"Chris" <chris_campbell@xxxxxxxxxxxxxxxx> wrote in message
news:1168705185.451940.126720@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Our exchange 2003 mail server was incorrectly configured a couple
years ago to have 3 logical drives all Raid 0. We were able to move
the logs and mail store to other drives, rebuild the array correctly
and then more the data back. No problem. The problem we are having is
in correcting the system drive. Below is the current config.

HP ML-370 G3 Server
HP Smart Array 6400 RAID card
(2) 18 GB SCSI drives setup for raid 0 creating 1 36 GB logical drive
2 other logical drives corrected to be Raid 0+1 for the mail store and
logs drive
10 Gigs of info on the system drive
Using Ghost Cast Server 8.0

We have tried creating an image of the system drive as it is
currently, install two new drives of the same size configured as Raid
0+1, use the smart start CD to make the new array bootable, throw the
ghost image on the new array and reboot. All looked well until the
BSOD occurred while booting. Tried safe mode - no luck. We then tried
to do a restore install of Windows to hopefully fix the BSOD, but when
running the Windows Server 2003 setup it does not recognize the current
install of Windows 2003 Server, so the repair option is not there.

Any ideas here? We also tried a full backup of the C drive with
Veritas using the client agent software. When we installed the new
copy of Server 2003, the backup agent and then restored from tape - we
could not boot into windows again this way either.

This mail server is also an active directory member and DNS server.
I liked the idea of Ghost because all the config should make it and
there would be very little if any further work to do. I am perplexed
as to why the BSOD occurs. Could it be because Ghost picks up some
info about the Raid 0 and that causes the image to not work properly
when put back on a Raid 0+1 array? Would a newer version of Ghost
possibly yield better results?

Thanks for ANY help! I need to get this mail server system drive
fault tolerant, and I would prefer not to rebuild the entire server
from scratch. If you have an outside the box idea - I would love to
hear.


.



Relevant Pages

  • Re: Problems with software RAID on SATA
    ... Connected to this are two 320GB drives ... >>which I want to turn into a RAID1 array. ... >>I'm almost certain it's a problem with initting the RAID arrays at boot. ...
    (Debian-User)
  • Re: RAID newbie...can I have several partitions on a RAID 1 array?
    ... You haven't expounded upon why you think you need raid. ... better backup device rather than buy 2 cheap RAID HBAs. ... RAID array then I would have to replace the mobo with the same one or at ... Lets say, for example, you buy 2 identical model drives, from ...
    (comp.sys.ibm.pc.hardware.storage)
  • Re: [PATCH 000 of 5] md: Introduction
    ... "why linux raid isn't Raid really, why it can be worse than plain disk") ... After this, the array ... error is in the filesystem, due to the complex layout of raid5. ... hundreds or 1000s of drives, you've quite high probability that some of them will fail sometimes, or will develop a bad sector etc). ...
    (Linux-Kernel)
  • Re: HP proliant ML115 G5 on debian lenny
    ... dardrives to do RAID 1 backup for several other servers. ... simple backup server, any drive over 1 GB will hold all the ... system onto a 6 GB partition on one of the drives. ...
    (Debian-User)
  • Re: Moving SCSI RAID array to new server
    ... Install the now blank array into the SBS2003, create the RAID volume, etc... ... I'd also probably lose the shirty SATA drives and eventually swing the whole ... > migrate the settings from the old server I just want to move the old RAID5 ...
    (microsoft.public.windows.server.sbs)

Loading