Thank you for the reply, Simon. It prompted me to investigate CloneZilla and consequently, cloning versus copying. I will definitely take the cloning route, but I'm planning to do it via Seagate's DiscWizard which I understand is a simple version of Acronis.
I have not received the new HDDs as yet, so I'll report back after my "adventure".
I'm back, but unfortunately I don't have a report for my original question. I've tried so many things and gone around in so many circles that I would not be able to give a clear answer to my own question.
Instead I have a new question.
I am trying to rebuild my RAID 1 using the Intel Matrix Storage Console (MSC) by building from a 250GB to a 500GB. Every time I try to "Create RAID Volume" I get an error message: "Not enough space to create a volume".
I get this error whether the target drive is:
- Completely wiped clean (I used DBAN) --OR--
- Simply Initialized --OR--
- Formatted with a basic partition and the remainder unallocated
Can anyone PLEASE tell me what must be done to avoid this bloody error message?
This is being posted as both a wrap up of this thread and as an aid to any fellow PCer who may find himself with a similar problem.
My most recent headache evolved from what should have been a straightforward exercise in RAID re-building. Unfortunately, it resulted in a series of “blind alleys”, frustration and some cussing (OK, a lot of cussing). It also consumed three weeks.
I set out to replace a failed 250GB RAID1 array with a similar 500GB RAID1 array. My first error was to directly substitute a new 500GB HDD for the failed 250GB drive. The array rebuilt itself as an exact image of the remaining 250GB drive and there was no way to access the remainder of the 500GB.
This should have been a simple “data migration” using Intel’s Matrix Storage Console (MSC), as my chipset contains Intel’s ICH9R. Unfortunately, somewhere early in the process my MSC disappeared and despite numerous attempts, I was never able to re-install it because “The computer does not meet the minimum requirements for installing the software” despite evidence to the contrary and positive advice from the Intel community.
I was left with Intel’s Matrix Storage Manager (MSM) which stubbornly insisted that there was "Not enough space to create a volume". In the end, I have not discovered why Intel’s software dislikes me, and at this point the matter is moot.
- I took my 500GB HDDs with their assortment of partitions and WinXP installs and wiped them clean using Darik’s Boot & Nuke (DBAN), a 2½-hour process using the “QUICK” tool. This returned the drives to their out-of-the-box state.
- With both 500GB HDDs connected, SATA configured as RAID in the BIOS and the optical drive as # 1 in boot priority, the Matrix Storage Manager (MSM) was used to create a RAID1 array, a process which occurred in the blink of an eye.
- Next, used Windows Setup and F6 to install the ICH9R RAID drivers, partition the drive and install WinXP SP2. All told, about a 40-minute process.
- After completing the Windows install I used EaseUS’ Partition Master – a marvelously useful and intuitive tool that should reside on every “advanced” desktop – to further partition and adjust the disk the way I wanted, a process which took exactly 49 seconds. Unbelievable!
- The last step was to transfer files from the restore I had made when the original array failed. That process required 3½- hours.
Lessons learned “along-the-way”
* Create RAID arrays using “raw” (unformatted) disks
* If you are replacing a failed disk with one of the same size, simply substitute it for the failed disk
* If you are replacing a failed disk with a larger one, use Intel’s data migration procedure [link] »
* Install the O/S AFTER the array is created; the creation process will erase everything on the disks
Johnyik here- I understand this is an old post but I'm hoping a veteran Raid aficionado will offer a solution to my dilemma. Have XPS 420 w/ Intel matrix storage manger. Option ROM v22.214.171.1241 ICH9R that I would simply like to revert to pre-raid A06 Bios firmware or remove so both attached drives can be seen in what's now Windows 7. Both currently appear as one C: drive. I'm hopeful someone here can direct me or provide link to safe removal procedure. Have a previous related question posted here: Matrix Storage Manager XPS 420