Good thought Pat, and it will work to a degree.
You can "fail" one drive on the array on purpose and replace it with the larger drive, and remirror to the larger drive. This can be repeated for the other drive as well.
I have had the best luck in "failing a drive" by shutting down, removing one drive, installing the new drive, and then power up with the power on the new drive off. Once the system has powered up completely then apply the power on the new drive. The Promise controller should remirror automatically when it sees a "blank new drive". (I use removeable drive carriers so the power thing is likely easier for me.) At times when I boot with a good drive and a blank drive the Promise controllers have gotten confused and locked up so that is why I generally avoid that.
Now, data will be on the larger drives.
The "paritions", however; will still be the same size as before. If don't want to change the size of the boot parition then this may work for you. (For the non-boot partition you can copy the data onto your 100gb drive, and then delete and recreate that parition under a larger size then copy the data back onto it.)
The last factor is "does Promise" store the size of the logical drive, the array, to present to Windows in the array data on the drive or is that determined based on the "smallest drive in the array at boot time"?
If it is stored in the array data on the drive, then it won't see the extra capacity. If it does what some RAID controllers do and determine the logical drive size to present to Windows based on the "smallest drive in the array at boot" then Windows will see a larger drive with a bunch of unpartitioned space. (Which is what I suspect is the case.)
So it may be worth a try.
If you are going to use Ghost, which I use often, be aware that under some configurations Ghost will not be able to Ghost drives on a Promise controller.
Sometimes you will need to use the "onboard controllers" in order to Ghost the drives. (Since it doesn't always work, I always use the onboard controllers.)
If you don't have any onboard controllers then you will need to try to use Ghost with the drives on the Promise controller.
To use Ghost on the "onboard controllers" you will need to make sure the BIOS is treating those SATA controllers in IDE mode and not RAID mode.
One original drive, and one large drive and Ghost away. Ghost will allow you to change the parition sizes during the Ghosting process. (Although sometimes if you make the sizes smaller, it doesn't work properly. Larger paritions always seems to work properly.)
If you are going to try to use the drives on the Promise controller at the very least you will need to remove your RAID 1 configuration and create two RAID 0 arrays. One array will have one of your original drives, the other will have one of the larger drives. (NOTE: Each array will consist ONLY of 1 drive.)
Try to Ghost!
If Ghost works boot up the first time with just the larger drive on the array in RAID 0 and then see if it comes up.
If all seems good add the other larger drive and recreate your RAID 1 array. Remirror and you should be all SET!
Facebook
Twitter
Instagram