Unable to boot from cloned or restored disk and related issue
Hi, I have Windows 7x64 Ultimate SP1 installed in a RAID0 configuration of 2 SSD's. Everything is working fine. I cloned the Windows installation using Acronis True Image Home 2014 (using boot CD) to a single SSD drive and Disk Clone operation was successful (according to TIH).I physically removed the two SSD's and replaced them with the cloned SSD, went to BIOS to set SATA to AHCI (it was previously set to RAID), then rebooted and get the following message (I get the same message if instead of cloning the system I do a backup/restore.) (see "screen1" attachment).
I did a Windows Repair as suggested with the Windows 7 installation DVD and the OS boots perfectly now. But a new related issue appeared which is preventing me from doing some operations like full drive encryption as I describe below.
So now I have two physical drives, an SSD drive where Windows 7x64 is installed listed as "C" drive (Disk 0), and a 2nd internal HDD, listed as "E" drive (Disk 1). When I go to Disk Management in Control Panel/Administrative Tools/Computer Management I find what seems to be the culprit preventing Truecrypt from continuing encryption. The C drive is listed as "Boot" drive but not "System" drive, instead drive E is listed as "System" (see "system" attachment)
So how can I make the boot drive C also be the System drive?
| Fichier attaché | Taille |
|---|---|
| screen1.jpg | 313.19 Ko |
| system.jpg | 202.49 Ko |
- Se connecter pour poster des commentaires
Thanks Pat, I thought about doing that, in fact I just noticed too that "bootmgr" is located in the E drive and not in the C drive. I will do what you suggest right now and report back, thanks.
- Se connecter pour poster des commentaires
Ok., so after doing it now the C drive is the boot and system drive. Now, why couldn't TIH2014 make the clone so that none of all these workarounds would've been necessary? Also, the E drive still has the bootmgr file in the root directory, can I safely delete it? Thanks
- Se connecter pour poster des commentaires
Hi Marcus, just a suggestion here: Are you using the Premium version of ATI 2014? Because I am under the impression that only the Premium version supports cloning to a different PC configuration, such as what you described.
- Se connecter pour poster des commentaires
Marcus,
There is a registry trick you can do so that Windows doesn't complain if you change between RAID, AHCI or IDE type disk access. By default Windows only enables the one driver that you set it up with.
If the drive that became 'E:' was in the PC when you rebooted, Windows and the PC may have become confused as there should be only one drive marked as active (assuming no hidden OSs) and only one drive with a unique disk signature, a clone would have attempted to copy both of those items across.
The answer is to perform first boot with only the new/destination drive connected, after first boot, the source/older drive can be connected and have its drive letters changed as wanted within a disk management utility.
Does your system have a 100MB system partition?
- Se connecter pour poster des commentaires
Pako wrote:Hi Marcus, just a suggestion here: Are you using the Premium version of ATI 2014? Because I am under the impression that only the Premium version supports cloning to a different PC configuration, such as what you described.
Hi Pako, yes, I'm using the Premium version of ATI2014
Colin B wrote:Marcus,
There is a registry trick you can do so that Windows doesn't complain if you change between RAID, AHCI or IDE type disk access. By default Windows only enables the one driver that you set it up with.
If the drive that became 'E:' was in the PC when you rebooted, Windows and the PC may have become confused as there should be only one drive marked as active (assuming no hidden OSs) and only one drive with a unique disk signature, a clone would have attempted to copy both of those items across.
The answer is to perform first boot with only the new/destination drive connected, after first boot, the source/older drive can be connected and have its drive letters changed as wanted within a disk management utility.
Does your system have a 100MB system partition?
Hi Colin, thanks for your reply.My system does not have a 100MB partition. So what is the registry trick? Also, when I cloned both the C and E drives (each physically distinct drives) where present (the C drive being the two SSD's in RAID0 and the E drive a WD BLACK 2TB HDD), but I indicated to Acronis TIH to only clone the C drive (the OS drive). For some reason which I ignore, the system drive was originally marked as active and boot but not system, and the E drive was marked as active and system. Originally, the C drive did not have the bootmgr file in the root directory, but it was present in the E drive's root.
- Se connecter pour poster des commentaires
Marcus,
First make sure you have either imaged your complete drive or have a copy of the current registry.
Second find the following registry entries and change the '3' to a '0' . Depending on your RAID driver you may not have the IORSTORV entry unless your hardware RAID chip is an Intel one.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\pciide
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\msahci
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStorV
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\iaStor
Close registry, on first reboot you may get an error message or even a BSOD, a further cold reboot in my experience clears that.
I've not tried cloning a RAID setup, but I suspect if you only clone one physical disk you need to break the RAID before doing this.
- Se connecter pour poster des commentaires
Colin B wrote:>I've not tried cloning a RAID setup, but I suspect if you only clone one physical disk you need to break the RAID before doing this.
Hi Colin, maybe you misunderstood, I cloned BOTH SSD's which were acting as a single logical drive under RAID0. In the Acronis TIH2014 these two SSD's showed as a single Disk (Disk C), which I marked for cloning.
- Se connecter pour poster des commentaires
As Colin Says, Windows requires different drivers for raid and non-raid configuration (assuming you are using Intel Chipset to configure the raid). However, if you are using a third-pary raid controller then you may not have this difficulty. This would explain why Windows is refusing to boot. Rather than clone you should have migrated (my recollection is that ATI Premium supports migration).
Ian
- Se connecter pour poster des commentaires