Aller au contenu principal

Acronis True Image 2017 (giving erros) vs Intel Data Migration (all good)

Thread needs solution

I have an Intel SSD as my main drive. Lately I have been getting startup errors (Windows 8.1 Blue Screen errors) so I decided to buy a new Intel SSD. I have a working Back Up (Clone through Acronis) Hard Drive which I use to clone new drives. When I clone this drive to my NEW SSD I get a Blue Screen errors (Header) and just won't boot. If I do the same process using the INTEL SSD MIGRATION software everything works fine.

Why is this happening?

Note: I tried cloning 3 times with ACRONIS to no avail. By the way I was using ACRONIS through the BOOT DISK

 

0 Users found this helpful

Rene,

Hard to say without a log - when you use the boot disk you can capture the log and a system report and provide it here for a set of eyes.

My best guesses are:

1) the disk is corrupted (hence the errors).  Cloning in Acronis is not sector-by-sector and may be faulting at a bad sector.  To circumvent this, the best method is to do a sector-by-sector backup and then restore the backup.  In this case, you would need to ensure the new disk is as large (or larger) than the original.

2) The method the recovery media is being booted may be incorrect.  Although, you're cloning, you need to ensure that the rescue media is being booted to match the OS install (same applies for a restore).  If you have a legacy / MBR OS install, you want to boot in legacy mode.  If you have a UEFI / GPT install, you want to boot the rescue media in UEFI mode.  This same limitation of Legacy vs UEFI booting also applies to things like the Windows installation disk too.  How you boot, determines the outcome of the recovery in Acronis, or the type of OS install in Windows.

You can verify the boot mode by using your system one time boot menu (differs from system to system but I have an example linked below as a reference).  Also, Acronis menus look different... in legacy mode, the original options are a colorful blue graphical interface to choose between True Image, Universal Restore, etc.  in UEFI mode, it's a black screen with numbered text for the options. 

I'm also assuming you're using the default Acronis boot disk, which is Linux based.  In 2017, there isn't a good option for building winpe (not really).  However, if you try the MVP tool (download the .zip and extract to the root of a drive - not your user profile) and just follow the prompts, it will build some nice WinPE rescue media for you using your local system WinRE (recovery environment), or you can download and install the Windows 10 ADK from Microsoft and use that instead.

These are all linked in my signature below.

Thanks for a very good explanation. Yes I was "cloning" with the BOOT DISK in UEFI mode. I will use your sector to sector Back Up in the Future.

 

Thanks again!

 

Cheers

Rene,

Normally, sector by sector is not necessary, unless there is some disk corruption (bad sectors).  I'd suggest running chkdsk /R on the source drive to see if it finds and/or repairs corruption. If it does, then a regular clone, or a non sector by sector backup and recovery should be fine.  Sector-by-sector is much slower (and larger) since it backs up the entire disk and not just the currently used portion.

 

chkdsk /?
Checks a disk and displays a status report.

CHKDSK [volume[[path]filename]]] [/F] [/V] [/R] [/X] [/I] [/C] [/L[:size]] [/B] [/scan] [/spotfix]

  volume              Specifies the drive letter (followed by a colon),
                      mount point, or volume name.
  filename            FAT/FAT32 only: Specifies the files to check for
                      fragmentation.
  /F                  Fixes errors on the disk.
  /V                  On FAT/FAT32: Displays the full path and name of every
                      file on the disk.
                      On NTFS: Displays cleanup messages if any.
  /R                  Locates bad sectors and recovers readable information
                      (implies /F, when /scan not specified).