cloning doesn't work
Have tried every conceivable configuration, turned off all "open" programs, and can't get it to clone my 840 EVO 120gb SSD to my Intel 120GB SSD, or any other drive for that matter. I have both the Intel and Samsung cloning software successfully before, but the Samsung will only clone TO a Samsung drive, and the Intel does NOT recognize the Samsung drive, only the Raid cards. So I BOUGHT your software hoping that that would be the solution. NO JOY so far. Please find attached the SystemReport you requested, a screen shot from disk mgmt showing SSD setup, and ten(ten) photos taken from the last failed attempt. As a note, the time sequence between photo 09 and the reboot screen (photo 10) is approximately 15 sec.
I appreciate your reply and read the documentation you referenced. Nowhere in this documentation does it say a "backup/boot disk" is "required", just "recommended". I never would have purchased this software if it had been. I purchased it because the site "sales pitch" said it would clone any SSD to any SSD and to any HDD and vice versa. If I had wanted the time consuming and inconvenient "boot disk-backup-restore" scenario, I would have used the the B/U feature in Windows. I want a cloned drive sitting next to me so if the boot drive fails, I can remove it, install the clone, and be back on line in less than 2 minutes. My operating systems rarely change and when they do, I simply clone the drive again. But the Samsung provided software will only clone to Samsung drives, and the Intel provided software only to Intel drives. There are faster and more convenient "backup" procedures for files other than "operating" systems. Mine is setup to copy any newly created files to one of the raid 5 arrays every 60 seconds and I'm not concerned with "power outages". This computer is on a 2.5KW zero sequence UPS and the house is on a 22KW Genset/auto xfer.
Simply put, I want it to "clone" as advertised, and it ain't work'n.
That's fine. I did indicate that my response was for the recommended procedure. Whether you chose to follow that or not is your choice. Obviously the way you have attempted to do it is a failure.
Is the way I attempted wrong ?? That's why I posted the photos. I was hoping that by looking thru the sequence, someone could identify what I WAS doing wrong.
Thanks again..
If you haven't done so, I would detach the cables on the old SSD
and connect the new SSD to the same sata connetor used by the original and then try to boot.
In other word, have the new disk use the same sata connection as when the computer did boot.
and the old ssd not connected.
Windows is known to get confused when it sees two identical drives.
It is always best that both old and new not both be connected on first foot following the cloning.
The problem is that I cannot get the 120gb Samsung SSD "C" (boot) drive to clone the 120gb Intel SSD. If you look at photo 9 it looks likes it's ready to, and then about 15 sec later it boots back into the C drive. There is nothing on the Intel SSD. It's been formatted and checked for errors. See the photo entitled disk_mgmt.
Thanks for the try...
Another option would be to create a disk image backup of the original SSD,
Boot into the TI Recovery CD
and then restore the backup onto the new SSD,
with only the new SSD attached following first boot after restore.
New disk to be attahed in same location as old ssd.
http://www.acronis.com/en-us/support/documentation/ATI2015/index.html#2…
====================================
This link may also be applicable.
https://kb.acronis.com/content/45437
Appreciate your reply, but I can do that with multiple programs I already have. I bought this software because it was advertised to work exactly like the cloning software furnished w/ the SSD's. From my original post "...but the Samsung will only clone TO a Samsung drive, and the Intel does NOT recognize the Samsung drive" Those programs were written by Acronis. They are simple, fast, and foolproof. This program is supposed to be just like them WITHOUT the restrictions. If it can't do it as advertised, I want my money back.
Why don't you retry the cloning except choose Manual rather than automatic.
Chose the Move method to be "as is"
AFter cloning,'
boot with only the new disk connected.
-------------------------------------------------
HavE you tried using the "Windows Install disk to do a startup repair?
Only the new disk can be attached.
Double check the bios setting before bootup to make sure the correct disk is being selected--even if only one disk attached.
Hey, its volunteers trying to help you. If you want help from Aconis, then register your serial and contact them via live chat.
I am not here to argue with you.
http://www.acronis.com/en-us/support/contact-us.html
Here is the link to contact support directly once you have registered your serial number, but I'm sure they are going to tell you the same thing Groverh and Enchantech have stated. Non-system disks can be cloned from the Windows application. System disks will require the bootable rescue media 99.99% of the time. You get thirty days of standard support from the date of purchase. This forum is not the primary support channel and is rarely visited by Acronis representatives. I recommend using the live chat option when contacting support.
http://www.cleverbridge.com/?scope=cuseco
If you purchased your product from the Acronis website, you may submit a refund request to Cleverbridge with the link above. It is usually processed within a few hours during business hours. You have thirty days from the date of purchase to submit a refund request.
Glancing at your SystemReport disk.txt file I see a couple of concerns. One, it is showing MFT bitmap corruption on both drives. It most likely exists on the source disk and is being copied to the target disk. At this point the clone fails and the reboot occurs. Have you run check disk on the source disk recently? Second your source and target disk have different physical sector sizes. Since the logical sector sizes are the same this shouldn't present an issue, but sometimes this does require a backup and recovery operation to successfully transfer the system.
Nice post Joey.
There is also a problem with the starting offset of the intel drive.
The starting offset of the samsung is correct at 1,048,576
The starting ofset for the intel is wrong at 32,256
Once the disk corruption is corrected
Use Win7, 8, or 10 and create a partiton of any size on the intel drive to correct the starting offset.
Then clone manual, using the "as is" option
and the clone will probably boot (clone only disk connected)
Kudus to you and GroverH !! First off, I hope I wasn't coming across as confrontational. Sometimes us really old retired guys can get pretty frustrated (EE/ME).
Your mention of disk corruption really set off some flags. Haven't done a chkdsk /f on any of the drives in a long time. Ran it on the C:\ SSD system/boot disk and the SSD target disk(s). Then re-ran the "clone" program and it worked as advertised. Plugged the target disk in in place of the source disk and it booted right up. No bootable rescue disks required. Just for the hell of it, I cloned the boot/system disk to a really old sata1 300gb velociraptor and an 750gb 2 1/2" HDD from a laptop. They all worked perfectly as system/boot disks. Happy camper now. Will purchase another copy for my laptop :-)
Again, thanks to both of you.
Just to make sure the first partition is aligned correctly, do take the time to confirm that the starting offset is 1,048,576
YOur attachment showed the samsung. Wasn't the Intel the target disk?
Yes, here is the Intel SSD. Just plugged it back into an external usb drive to get the info.
Hi Chief,
I , too, am one of those "really old retired guys" as well. As you look forward to your next computer purchase, be aware of these changes.
Prior to Windows 8, most disk configurations were MBR partitioning. Starting a little in some later versions of Win7, but mostly starting with Win 8,
the pre-built systems sold by manufacturers almost all had GPT style partitioning. This change to GPT added complexity and several new partitions such as the Microsoft Reserved partitions--which is not displayed via Windows Disk management, but visible via Windows Diskpart & various disk utilities.
Some vendors vary the placement of this pre-installed Reserved partition so the user needs to be aware in advance how their specific disk is configured so they can tell whether any new replacement disk that they create has the partitions correctly created. Whether the new replacement disk is cloned or a backup restored, the possibility of mis-located partitions exist.
The user that does their own fresh install of Win 8-10 (rather than "Windows pre-installed) usually don't have the Microsoft Reserved partition placement issues that accompany a vendor pre-installed Windows as the Microsoft Reserved is "usually" always first
My purpose in mentioning this now is to encourage you to
1. know the placment of your partitions before doing any cloning or restoring, and
2. be sure and take the time to make a full disk image backups BEFORE you do any cloning of your future GPT systems, so you are not faced with the possibility of doing a fresh install of "Windows (without a backup) because of the cloning screwed up your original master host disk. Some backup software handle restoring this partition placement better than others. Having backups can help to provide options.
Good luck.
To comply with UEFI standards, the MSR partition should always immediately precede the Windows operating system partition. I have yet to see an OEM partitioning scheme that does not follow that guideline. If the disk is initialized to GPT with another utility such as True Image or Disk director which results in the creation of an MSR partition prior to beginning a Windows installation, the MSR partition will be left where it was created. Performing a clean installation of Windows to an uninitialized disk always places the MSR directly before the Windows partition.
Thank you Joey for the additional clarification. The link below is an example of a TI restore of a GPT system.
Any change of GPT partition location via a TI restore or TI cloning may cause the computer not to boot or disable the Windows or OEM recovery functions.
https://forum.acronis.com/system/files/mvp/user285/misc/show-final.jpg
Sorry to revive an old thread but i had this exact problem as well with a message in "disk.txt" of "File record corrupted". The OS drive is a Samsung EVO 850 (cloned recently from an EVO 840) and I am trying to clone it to a number of different Intel SSDs (520, 535, 710) all of which failed to get past the "Proceed" stage of the cloning process with an error message. The cloning neither works for the 850 or 840. I have moved these disks to different machines that can clone other Samsungs and Intel drives, and the error message still comes up - so likely problem is in the drives themselves.
After running CHKDSK and fixing some initial problem, it still fails to clone. Subsequent scans show no problem. I have even imaged the OS disk using Windows backup and reinstalled, and then tried to clone but still no luck. I can use Samsung disk migration or Macrium succesfully to clone, but not Acronis. Despite all this, when I run the Acronis diagnostics I still see the "File record corrupted".
Is there another CHKDSK type program I could use to correct this? Sometime ago I had extended the Reserve Partition using mini-tool Partition on the drive - may this be causing some kind of mismatch problem? For example I see the "Before" and "After" sizes on the target disk info as different by 100MB when they should be the same just before I click on "Proceed" and then error message? I have tried messing around with the manual vs automatic mode but not sure what I am doing there.
Thanks in advance for any tips!
this thread shows me that Acronis really need to field this feature in the next update or release.
imho it is a too tiny change to pend it for a new release: https://forum.acronis.com/de/node/102309
thanks for upvotes.