- ACRONIS TRUE IMAGE 2015 STARTS CLONE THEN RESTARTS SERIAL
- ACRONIS TRUE IMAGE 2015 STARTS CLONE THEN RESTARTS UPDATE
- ACRONIS TRUE IMAGE 2015 STARTS CLONE THEN RESTARTS PC
- ACRONIS TRUE IMAGE 2015 STARTS CLONE THEN RESTARTS PLUS
- ACRONIS TRUE IMAGE 2015 STARTS CLONE THEN RESTARTS WINDOWS
ACRONIS TRUE IMAGE 2015 STARTS CLONE THEN RESTARTS UPDATE
(But if you are keeping the drive in your system, it seems you would want to periodically update the cloned image drive. It would be better to remove it to a safe place.) (If you are making the clone as a "one-time" thing - i.e., sort of a "Factory Restore" drive, which you would use to return the system back to its original, "factory" state - then I cannot see why you would leave that clone drive in the system. Question 2: If a user does experience the problem you describe, it seems that s/he would have to change Volume IDs EVERY TIME s/he makes a clone (onto a drive that remains in/attached to the system). I do not understand why he has not had the problem you describe. He periodically clones his main (1st) drive onto the other two drives, for a backup.
ACRONIS TRUE IMAGE 2015 STARTS CLONE THEN RESTARTS PLUS
He has a 2nd internal hard drive, plus a USB drive (that remains attached always). Question 1: Why does my customer not experience this problem? Moral of the story: Changing the volume IDs is like a rejuvenating fix for Windows, because it resets its current drive letter assignments and starts from scratch, thereby eliminating all troublesome drive letter and volume ID conflicts and ambiguities. Now everything works just fine again, including Acronis True Image. So you may not want to use this method on more than one drive, otherwise you end up with duplicate volume IDs again.Īnyways, I cloned my drive and had lots of problems until I changed the diskid of both drives (just to be safe) with volumeid.exe. Same effect, except you can't choose the volume ID freely - instead, you get a default value.
This re-writes the Master Boot Record, but it also happens to overwrite the volume ID, as initially discovered by Michal Kawecki.
ACRONIS TRUE IMAGE 2015 STARTS CLONE THEN RESTARTS WINDOWS
If you don't have windows access, boot with a Windows 98 or Windows ME floppy disk and type at the command prompt FDISK /mbr
Windows may hang momentarily, but after the next reboot it will re-assign its drive letters from scratch, eliminating all conflicts. Open a command window and use the utility and use this to create new volume IDs. If you still have Windows access, this can be done with a small Microsoft Sysinternals utility from Mark Russinovich called volumeid.exe. The solution is to alter the volume ID of either the original or the clone HDD to a different value.
ACRONIS TRUE IMAGE 2015 STARTS CLONE THEN RESTARTS PC
More details about it here.Īnyways, if any two drives in your PC have the same volume ID, then you're likely to have problems, ranging from Acronis hangs to Windows boot failures.
ACRONIS TRUE IMAGE 2015 STARTS CLONE THEN RESTARTS SERIAL
It is also know as DiskID "Disk ID", "NT serial number", or "Partition Signature". In the DOS prompt it is apparently called "Volume Serial Number". You can most easily see the volume ID by opening a command prompt window and saying DIR C: /p. Note that I am talking about the volume ID, not about the volume name. The solution in all of these cases is to alter the volume ID of one HDD, so that no two logical drives share the same volume ID. In a less severe case of volume ID conflicts, other applications such as Acronis True Image may hang or crash. The typical Windows failure mode after such a SNAFU is that you get the login window, but when you log in, you are immediately logged out again. Once such a thing has happened, neither HDD might be able to boot on its own, since drive letters are now cross-assigned. Since Windows uses these volume ID bytes to assign drive letters etc., bad stuff can happen if you hook up the original HDD and its exact clone to a windows machine at the same time.įor example, if you boot up Windows with two such HDDs attached (one original, one clone), then Windows may boot with its left leg on the original HDD, and with the right leg on the clone HDD, figuratively speaking. This means that these two HDDs also have the exact same volume ID bytes in the MBR. The issue seemed to be that I had multiple physical hard disk drives, and one of those was an exact clone of the other. This was under Windows XP, but it may also apply to other windows versions. However, recently it would often hang or crash altogether - for example, when I clicked "backup", it would display a progress bar and the message "Analyzing Partition C:", but it would simply hang there and never complete. I used Acronis True Image in the past with good success.