Home Storage General Discussion

Backupper GPT errors

I am a new user to Backupper, and have not been able to find an answer to this question in the forums yet.

After a successful system backup, I attempt to Explore the image, but keep getting GPT type of errors. "Failed

to init GPT style table."

The destination disk is an 8tb NAS device, so pleanty of room.

This error occurs on both a Windows 10, and 7 system. Backups indicate no errors.

The mount process creates a drive letter, but when attempting to access it, get "device not ready" message.

Any help would be appreciated.


Comments

  • Sorry for the inconvenience.

    You may try to use the Administrator Account to log in your computer and reinstall the software then try again to see if it works.

  • I've got the same problem!


    Windows 10

    Backupper installed as Administrator

    Launched Backupper as Administrator

    When I try to access the newly mounted drive -> "device not ready" error


    ???


  • "When I try to access the newly mounted drive -> "device not ready" error"

    Would you tell us more details of this problem?

  • imageaomei-error.jpg


    Well, that's very easy to explain ...


    I go and mount the image through aomei backupper (X-Drive).

    Then I open windows explorer, click on the X-Drive and then I get this "device not ready" message!


    I also looked into the windows event log for some related message ... nothing there!

  • Would you give us the screenshot of the problem?

    Looking forward your reply.

  • edited January 2016

    It's attached with the previous comment (aomei-error.jpg)!

  • Again, here is the screenshot ...


    imageaomei-error.jpg


  • edited January 2016

    OK, we got it.There is a small problem with the explore functionality. We will fix it ASAP.

    Sorry for the inconvenience.

  • No Promblem, glad you know about the error and how to fix it already!

    Thanks!

  • On January 26th was a reply about a small problem with functionality. This problem still exists. This occured in thr 3.2 version. Is ther a planned fix date please?

  • Maybe we will fix it in the next vesion in the next month.

Sign In or Register to comment.