That is the second error after failing to create a Primary Partition on the new RAID volume.

Try loading the drivers for the RAID controller into the Recovery Environment, and we get a "Path not found" error when trying to Load from floppy or USB flash drive.

Image was taken from the same machine with the intent of upgrading the existing hard drive pair.

Setup:

Intel DQ35JOE + E6850, 4GB RAM with current BIOS.

2 x 500GB setup as RAID 1 volume (via on board controller).

The new drives are replacing a pair of 200GB drive pairs where one of the drive pairs is failing.

What next?

Philip

It seems that I have discovered the answer to my own question.

When booting into the SRE, one must head right into Disk Map tab, right click on the unallocated space, and set the partition size there.

A reboot later, and we are in business.

We had the USB HDD with the images on it on and taking a drive letter, C:, while trying to do the restore. We had it off during the boot specific to creating the new partition. Would the USB HDD taking C: be a problem?

Anyway, for now we know that we are not able to create the partition from within the Restore Wizard. Why? Not too sure about that one yet.

Philip

There is an issue in the 3.0 recovery environment relating to un-initialized disks.  If you initialize the disk in the Disk Map (which will occur if you create a new partition on it for the first time ever) then you will need to reboot before you can use it.  This is actually an issue with Windows itself (legacy, I think, but I must go back and refer to my notes to know for sure).  At any rate, we have added a reboot dialog to the 3.1 recovery environment to deal with this scenario (it will prompt for a reboot if if has just initialized a disk).