Aller au contenu principal

Recovery fails on multiple validated backups with format/resize error

Thread needs solution

I upgraded my computer at the end of April, shifting to a PCIe M2 Samsung EVO C: drive (computer specs below).  I had problems installing a program a few days ago (message that this program is not compatible with your computer) and I knew that I had done some registry edits a week earlier, so I thought that I would go back to a version from 2 weeks previous to be sure.  When I tried to recover the backup, Acronis wiped my M2 C: drive (might have left the Fat 32 boot volume). 

Luckily I had saved the Sata SSD from just before I upgraded so I had something to fall back on. 

I have 2 full and 13 differential backups since I upgraded and given the number of changes I made since the upgrade I would be happy to get any of them to work rather than having to start at the Sata SSD again.  I tried to recover from multiple backup versions the first day, all with same result:

Recovery to the original location failed due to an error: A format/resize error. 

I then validated the 4-5 backups that I most wanted to work -- all were successfully validated and they all failed with the same error. 

I tried the recoveries with a created a newly created Rescue drive with the same result. 

The method at https://kb.acronis.com/content/59416 does not work likely because it is a different program.  I was able to follow a similar procedure with the new Rescue drive and add the kernel option DISABLE_VOLUMES_RESIZE=1.  This recovery made it much further that any of the others (which usually fail in <30 sec or so) but still failed.

These failed recoveries usually leave a Fat 32 boot volume, so I did a file copy of all the C: drive files from the same backup version and then did a manual repair on the EFI Bootloader using DISKPART.  This recovered drive booted to Windows once and failed on re-boot. 

Today I tried a separate recovery of the Fat 32 boot portion and all the windows files to to two separate drives (the M2 EVO drive and an old HDD).  Neither will boot to windows.

This seems to be a new problem, but I hope that someone can suggest a fix. 

If not I am going to give up on Acronis (despite years of successful backups).  I need to have backups that I can rely on.

Mark

Windows 10 Pro 1709.  Intel Core i7-8700K, Maximus X Hero MB, 32 CB Ram

Acronis True Image 2018

0 Users found this helpful

A number of Acronis users, including me, have PCIe M2 Samsung EVO for system drives. Am I correct in assuming it is an NVMe drive and not a SATA drive?

If it is a SATA drive is it configured as Raid, if so it may be a driver problem. This is getting beyond my expertise so it may be best to wait for someone more knowledgeable.

What recovery media are you using, is it Linux, or MS RM (Microsoft Recovery Media) based? Did you select simple version. When booting the recovery media are us selecting the UEIF mode for the recovery media (I assume given the high end board that you did not select BIOS rather than UEFI when building the system).

Ian

Hi Ian,

I did not get an e-mail saying that there was a reply to my post.  

The C: drive is a Samsung 960 EVO NVMe drive in the primary PCIe M.2 slot.  This is the drive that Acronis wiped. The SATA drive was my C: drive in the previous system.  This is what I booted to to recover the system.  The new system is all UEFI and the recovery media is the default for creating a rescue drive (I think it is Linux).  

The SATA mode is Intel RST (I have a couple of Raid 1 drive attached to the SATA ports) and the Samsung M.2 PCIe drive is handled by the IRST storage system.  (The M.2 drive is not in a Raid though.)

I upgraded my Windows 10 Install USB drive to the latest version (18/03) and tried startup repair again on the M.2 EVO drive (the one where the Fat 32 boot portion and all the windows files were recovered separately).  This time it worked and I was able to boot to Windows using the PCIe M.2 drive.  (The Windows 10 version on the USB was a couple of years old.  It never occurred to me that this would make a difference for repair.)

I then ran the System File Checker (no problems) and then upgraded to Windows 10 18/03.  (This also has the effect of doing a system repair: https://www.tenforums.com/tutorials/16397-repair-install-windows-10-pla….)

The system has now been stable for a couple of days.

I still would like to know what happened, and how to prevent this from happening again.  

Mark

Ian,

I forgot to mention that I also tried to recover the backup of the Samsung 960 EVO NVMe M.2 drive to an old Western Digital SATA hard disk drive and the recovery failed with the format/resize error.

This rules out a driver problem with the PCIe M.2 drive (at least as the primary problem for recovery failures).

Mark

Glad to hear that you have managed to get things to work correctly. If you used the Linux recovery media, this could explain why things went wrong as it does not support IRST. However, my recollection is that the default media created from within ATI was Windows based. If you downloaded it from you Acronis account then it would, as I understand it, be Linux based version.

My only system with M.2 drive is AMD not Intel, so my understanding of how it works on Intel System that support IRST. You may wish to investigate if using the M.2 drive with IRST driver is optimal; it may operate better with the Samsung Driver - you would need to change the settings in the UEFI for the drive so that it is not managed by IRST.

Ian

OK I will check out the Windows based Rescue drive.  Remember though that the recovery failed using Acronis in Windows as well.

I switched the M.2 drive to Raid as a way of handling all the drives in one place in the Intel RST module.  When this proved to be not much of an advantage for a single M.2 drive and the Samsung Magician did not detect the drive I tried to change it back to AHCI but the system does not boot.  As part of the recovery process I did re-format the drive and tried restoring with the M.2 raid switched off.  This did not work and I needed to go back into Raid mode to boot.

Before I do anything else with this I need to make sure that this recovery problem is solved.  

Mark

 

I suspect the failure to boot when using AHCI could be driver related. (I am sure I have seen a main board with three options, Raid, AHIC and NVMe, but I could be mistaken.) As I mentioned before I have limited knowledge of newer Intel main boards. I am sure someone who has may be able to help understand what is going on.

Mark, please understand that performing a recovery from within Windows of an OS drive will still use the Linux version of recovery media to perform the required boot to the standalone ATI application.  As Ian has mentioned, the Linux rescue media is lacking in support for such as Intel RST /RAID and may have limited support for NVMe M.2 drives.

With ATI 2018, Acronis has started the move away from using Linux for recovery media other than when no other alternative is possible.  The new default rescue media, when created from within the ATI application in Windows is to use Windows PE (based on the Windows Recovery Environment), then if this is not available / in the correct state etc, to look for the Windows ADK for WinPE files, before falling back to using Linux.

See KB documents: 

KB 60091: Acronis True Image 2018: how Simple bootable media creation mode works

KB 60820: Acronis True Image 2018: how to create bootable media

Another tool which is recommended is the MVP Custom ATIPE Builder script which can be found via the Useful Links section in the forum in the MVP User Tools and Tutorials repository.  This provides a way to create customised WinPE rescue media with RAID support etc.

Ian and Steve, Thank you.

This gives me a starting point.  I first thing that I will try is to build a Win PE rescue disk and see if I can copy the MVMe M.2 drive to another drive.  I am away for the next two weeks so I will pick this up again after I return.

The failure to boot when using AHCI is likely due to a registry setting, since the AHCI driver for the Samsung NMVe M.2 drive was present before I shifted control to Intel RST.  Shifting a Windows C: drive from AHCI SATA to Raid SATA without reinstalling Windows required editing the registry (which I successfully did a few years ago).  I suspect that something similar is happening with NMVe M.2 and I will do a search when I return.  (I will not try the fix until I am sure that I have working backups.)

Mark