So, besides the 63 MB difference between the two drives, something has changed between saving the full disk backup and then loading it onto the new drive. Switching to Disk Management is where it gets interesting-ĭisk 0 (C:\) shows the following three partitions-Ģ32.27 GB NTFS Healthy (Boot, Page File, Crash Dump, Primary Partition)ĭisk 2 (F:\) shows the following four partitions-ġ02 MB Healthy (Active, EFI System Partition) So, after putting C: & blank: SATA cables back in place the computer starts as it should, to C:\, and in Windows Explorer I see blank: is no longer blank but has the proper folders. The application or operating system couldn't be loaded because a required file is missing or contains errors. You'll need the recovery tools on your installation media etc. Upon reboot, with SATA cable still attached to blank: and C: still unplugged, here is what I get-Ī required device isn't connected or can't be accessed While pretty much the same process, neither one works. I've tried the standard Acronis procedure as well as GroverH's tih2012-disk-option-restore.pdf. I'm testing out this plan in advance by using Acronis True Image 2014 to back up the current C:\ drive to an external USB3 drive and simply swapping the SATA cable from C: to blank: and proceeding to use the Acronis 2014 boot CD to load the inage onto blank:īut.no dice. Just load the image onto the new 250GB RAID array.
No partition changes, both drives are same capacity. Now I'd like to set up RAID 1 for the 250GB OS drive, using the 2nd 250GB one for RAID creation.Īs all data is destroyed during RAID setup, I want to create the OS image to reload once RAID is running. I currently have RAID 1 set up on D:\ drive, a pair of 1TB drives and all is well there.
Project: Create disk image in preparation for C:\ drive RAID creationĭrives: A pair of WD 250GB SATA, 1st one operational (C:\ on Dell) - and 2nd one blank, in place