True Image hang when trying to clone source drive sector 0
I've tried 4 times and the app hangs at the same place. When it starts to clone source drive, it says it can't read sector 0 and to test disk. The disk is fine and passes Win8.1 64 disc check. Selecting the source drive is confusing on this system. In windows, the C drive shows it is the boot drive, but the bios shows another drive. When I change the bios to boot the C drive, it cannot find the op sys. Could this system use the boot from one drive, but use another drive for "C"? I would think that would screw up the cloning. Is there a way to remedy this?
I have tried EaseUS as a check/test and it doesn't give any error messages, but the SSD will not boot when the cloning is finished, stating it cannot find the system.
The Boot (H) is the new SSD.
The Boot (C) is not the drive that I think is being booted.
The Archives(E) is the boot drive as per the BIOS.
If I backup the E drive and restore it to the H drive, It won't have the boot files needed from the E drive.
Assigning letters to the hidden partition, which I assume is the boot area on the E drive will allow it to be selected for testing?
Thank you.
Correction:
If I backup the C drive and restore it to the H drive, It won't have the boot files needed from the E drive.
I believe your issue is the procedure you used in your attempt to clone the disk. Please review the link provided and follow the recommended steps to clone your disk.
http://www.acronis.com/en-us/support/documentation/ATIH2014/index.html#…
Can you be a little more specific? I've been working on/with computers since 1970, but I'm 66 now and there seem to be quite a few variables. I really do appreciate the help.
Thank you.
It is better if you point out what you do not understand in the instructions so that specifics can be discussed. We MVP's have no idea where ones knowledge level is and if you do not have a solid knowledge base then cloning is not for you. You are better off performing a full Disk Mode backup and restore of a disk.
On the right hand column of this page is a link to Grover's guides which give specifics to all of this and more. Do some reading then ask some questions, it is much easier that way for all of us.
I started by cloning my "C" drive to my SSD drive. The SSD drive would not boot. I looked further and it appears that while my "C" drive holds the "system", the "D" is the boot drive. I would like to know how I can make the SSD drive bootable and contain all of the files that are now on my "C" drive.
So far, I have been directed to perform a backup and not clone, told that I don't have enough knowledge to clone, and to read. I have read and there is no mention of performing what I have described. I have followed the instructions and cannot boot the SSD drive.
I agree that this isn't rocket science, but I don't seem able to get there from here.
Let step back for a moment and confirm what we have.
1. If the disk being copied is Win 8.1 and IF the disk is GPT type partitiioning, then TrueImage Home does NOT support the clone process of GPT disks..
a. GPT disks can be replicated via the backup and restore method but you may still need to run the Windows Recovery CD Repair function in order to make it bootable.
2. If the currenet 8.1 disk being copied is MBR, then yes, both the cloning process or the backup and restore process is possible.
but you may still need the Windows Repair.
3. Whether cloning or restoring, the process should be performed when booted from the TI Recovery CD.
On first boot following the clone or the restore, the original source disk must not be attached.
4. For instruction on creating the required backup, click on my signature lnk 2-A below and the first few screens shows how to create a disk mode backup which will include ALL partitons on the disk.
5. For instructions on performing the restore, signature link 3 below has it. The item 2 or item 1 will work--whichever is applicable to target disk size.
6. If the source disk is GPT, this could ge a major stumbling block and Windows Repair needed to get the disk to boot and even then, the partitions on the new disk may not be in the same sequence as the original.
7. As you can see, there is much we do not know here about your system.
8. Age is not an issue here as I am 17 years older than your 66.
Thanks "old man". I had no idea it would be this complicated. I appreciate your time and effort to get me rolling here. I have an 8.1 MBR so cloning still looks like the way to go.
Would you post a screen capture of the source disk when viewed in Windows disk management graphical view.
Just to make sure we are all talking the same language. When the term cloning is used, on THIS forum we are talking about a specific function offered by the TrueImage software tools menu. We are NOT talking about restoring a backup as that is its own function and not part of the TI clone function.
So.. when you write "so cloning is the way to go", that tells me you are NOT doing a backup and restore but you are performing the TI clone function. We are talking about the "process" and not about the "results".
Is the TI cloning function (process) what you are doing?
Most of us regulars do NOT use the clone function due to the risk factor. Or, if we do, we make a full and complete backup (all partitions) before performiing the clone so if things go wrong (which it often does), the restore of the backup will get us back functioning again. As the net result of the cloning operation or the restore from bacikup will not differ--either process should produce a bootsable disk.
If you are performing the clone, which method are you using? Is it the automatic? or is it the Manual with manual partition sizing move method ? or is the Manual mode with "AS IS" move method.
What size and type is your disk source and what size and type is your target disk being duplicated.
Have you created the Windows Recovery CD? If no, that is a necessary chore.
Was your checking for disk errors a disk check on ALL partitions of the source disk including checking the non-lettered partitions?
It is not usually this complicated but you are having problems so troubleshooting invoves so much more.