• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

How Do I copy RAID 0 drive to a single IDE drive?

Triggerhappy007

Golden Member
I don't want to use RAID anymore and going to get a quieter Barracuda IV.
How do I copy everything to the new single HD and use that to boot? I have Notron Ghost 2002(not installed yet), but if there's a easier way, LMK. Thanks.
 
Since a RAID setup is viewed as a single drive, maybe PowerQuests' Drive copy would be able to do it..I have never tried it with a RAID setup, but the program works wonders on single drive to single drive..
 
I have Drive Copy 2.0 I think, it's a DOS version, I doubt it will work.

Also I don't want to spend any more money for software just to copy once.
 
Is it a hardware raid controller or software? If it's hardware ghost should be able to use it as the source volume and then you just do a drive clone to the new drive.
Bill
 
It's a promise lite controller. The thing I'm worried about is that if I clone it and use it as my boot drive, then WinXP will use the Promise RAID drivers for a non-RAID drive. Will XP find my primary controller and use the default driver? I've already activated XP, do you think the will be any problems?
 
> Will XP find my primary controller and use the default driver?

Is this your MB controller or an add in controller? Either way you should try and add the controller (if it isn't already in the system) so XP has the right drivers before the clone. That done, XP should just continuing loading from the new controller/drive no problem.
Bill
 


<< It's a promise lite controller. The thing I'm worried about is that if I clone it and use it as my boot drive, then WinXP will use the Promise RAID drivers for a non-RAID drive. Will XP find my primary controller and use the default driver? I've already activated XP, do you think the will be any problems? >>


Triggerhappy,

You're right that this is a concern. WinXP will attempt to load the Promise disk controller driver and won't find a drive with an OS out there, and you'll get a STOP 0x0000007B Inaccessible Boot Device blue screen.

I can think of two ideas:

1) Back up your drive, including the system state, to a file. Then, install Windows XP to your non-RAID hard drive, and do a restore from the backup file. All should be well.

2) If you're going to move the drive to a regular IDE channel, set the ATAPI device driver to boot start. HKLM\System\CCS\Services\ATAPI\Start=0. That will cause ntldr to load the atapi driver so that the kernel can find the drive with the OS.

-Noggin
 
> Promise disk controller driver and won't find a drive with an OS out there

Huh? The bootable disk will be on the IDE controller, not the promise controller. Windows will load the promise driver, see their are no disks attached, and continue on it's merry way. The default IDE driver should continue functioning.

Bill
 


<< > Promise disk controller driver and won't find a drive with an OS out there

Huh? The bootable disk will be on the IDE controller, not the promise controller. Windows will load the promise driver, see their are no disks attached, and continue on it's merry way. The default IDE driver should continue functioning.

Bill
>>



My guess is that the default IDE driver is not set as a boot-start device driver. That's the whole point of setting the start value of the atapi driver to 0. (This is the same as setting it to boot start through devices control panel.)

Or from the recovery console you could do a ENABLE ATAPI SERVICE_BOOT_START command. Also sets that registry value.

You see, ntldr only loads the boot-start device drivers when the system starts. The kernel is invoked by ntldr and cannot access the disk. The kernel must start the device drivers that ntldr has preloaded into RAM to gain access to the disk drive. If ntldr doesn't load the disk device driver that's needed for the physical disk controller, you get a STOP 7B blue screen.

So, it seems that Triggerhappy's OS does not have the disk driver for the new motherboard set to boot start.

-Noggin
 
> You see, ntldr only loads the boot-start device drivers when the system starts

I understand this quite well, but the ATAPI device is usually always enabled. My system is on a Promise raid controller also, but my ATAPI device is set to start. This is on a clean install of XP to the raid controller.

> So, it seems that Triggerhappy's OS does not have the disk driver for the new motherboard set to boot start.

Based on what in the thread? So far he's only asked how to copy the data over. He hasn't actually done that or ran into a problem yet. Your techincal description was very good, but I think your making this more complicated than it likely needs to be (I'm preparing to eat crow later if TriggerHappy does have a problem 😉)

Bill
 


<< > Your techincal description was very good, but I think your making this more complicated than it likely needs to be (I'm preparing to eat crow later if TriggerHappy does have a problem 😉)

Bill
>>



Ya know-- you're right.

I'll shut up now.

Triggerhappy, Bill and I say go for it. If it doesn't work, THEN read all of my gobbledygook above.
 
Thanks for the help. I think I'll try to clone it with ghost and try to run a single drive. Hopefully I don't have to do a clean install. My windows xp won't activate again will it?
Could some explain to me how to use ghost?
 
My windows xp won't activate again will it? . Yes, It will..Although you "may" have to call MS. I believe that if you haven't changed any major hardware, you should be able to just do it online just fine. Just go for it..If it should for some reason not work, as long as you haven't wiped the RAID drives clean, you can just hook them back up the way you took them off and be back to where you started.
 
Sorry if I'm too late but...

I'm trying out Win 2k right now and have Ghosted both 2k and 98se back and forth between a single drive connected to the primary master and a raid array on a Promise Lite controller. You just have to change the boot device in the bios. I've done it several times in the past week with no problems whatsoever.
 
Uh, you don't even have to turn off the Promise, and actually you don't have to change the boot order either. If it doesn't find an active array, it asks what device I want to boot from and lists all drives in the system as options.
 
Back
Top