Backups Failing Due to GPT Name
Hopefully this may help others who run into the same issue that just cost me a day of troubleshooting and searching...
I spent a lot of time between last night and tonight trying to get Acronis True Image to back up my laptop drives. The back ups would never progress beyond "Preparing data" and a number of VSS writers would fail almost immediately after the back up began. I read through many knowledge base articles on the Acronis site as well as elsewhere.
One obscure hint, which turned out to be critical was an error having to do with an invalid character in an XML file. I finally found someone who mentioned that at some point they had used a tool from EaseUS which had written an invalid GPT name to the disk, and this invalid name resulted in the ASR Writer failing and bringing down back ups.
I too had used a utility from EaseUS once. I figured this was a long shot, but decided to pursue it.
Windows does not allow you to change the name of a GPT partition (as far as I could determine). Using a utility called Rufus, I created a bootable USB image of gparted, a GNOME Partition Editor. gparted allows you to rename a GPT Partition Name (keep in mind that the GPT partition name is not the same thing as the label you see in Windows).
Once I loaded gparted and viewed the GPT Name, I could see that one of the GPT partition names was a smiley face. I blanked out the name, applied the changes, rebooted, reinstalled Acronis True Image... and wallah... it worked without issue.


- Se connecter pour poster des commentaires

Thank you for your post! I had the exact same issue, and I wish it had only taken a day to run into this.
I used EaseUS Partition Master to Migrate my OS to a new drive, and found it had created GptNames that were made up of invalid characters. This was causing the exact same VSS XML parsing issue.
Even though this isn't an issue with the Acronis software, it would be really helpful if it could detect an invalid GptName and report it to the user. In my case, the backup sat "Preparing Data..." for hours and then failed without a reason.
I eventually stumbled onto the Acronis VSS Doctor, which, while helping to narrow it down, also just left me with a giant XML to parse with no idea where to start looking. In addition, when I tried to save the results of the scan, the program crashed because of the invalid characters in the XML.
Here is a user on another forum who also had this issue: https://superuser.com/questions/1212894/how-to-clean-a-working-ssd-repa…
Fichier attaché | Taille |
---|---|
545936-188064.jpg | 86.87 Ko |
- Se connecter pour poster des commentaires