Unable to recover my backups
Unable to recover my backups.
My computer is using Windows 8.0 (64 bit) and is MBR not UEFI. Ever since I built this computer I have been using Acronis True Image 2013 with Plus Pack. Recently I upgraded to Acronis True Image 2016, build 6027, in preparation for Windows 10. I have been unable to recover my Full Backups since I installed 2016.
I go through the procedures of recovering the system disk but when I click proceed I receive the message shown below.
Failed to write data to the disk.
Failed to write to sector '0' of hard disk '1'
Direct R/W operation has failed. (0x590001)
Operation not permitted (0xFFF1)
Then I am given four choices RETRY IGNORE IGNORE ALL CANCEL.
Does anyone have a clue to what the above information means? Any suggestions as to what I could do to help find out what the problem is. I have contacted Acronis Support but so far they have not provided an answer. It takes 3 days to get a reply, and then if there are more questions it takes another 2 or 4 days. I'm feeling very vulnerable at this time. I have 13 Full Backups and I can't restore any of them.
All of my Full Backups are validated when the backups are created. Below I am going to tell you what disks I have and how they are being used; they are all installed in my Desktop Computer, with the exception of the Western Digital Elements External Drive.
I am using two (02TB) Western Digital Black Caviar Disks for my system disks. Each of these disks are mounted in an Inner Tray. In one drive bay I have mounted a Caddy into a slot where a hard drive would normally be mounted. I can slide either of the drives that are mounted in an Inner Tray into this Caddy. Normally I would change out the two Inner Tray mounted hard disks every week. I'm going to call these two Inner Tray drives No. 1 and No. 2. If No. 1 is in the Caddy for a week, then I will remove it from the Caddy and replace it with hard drive No. 2. Then I would boot my computer using my Acronis Bootable Rescue CD. and recover the latest Acronis Full Backup to drive No. 2 and I would then be back up and running. In the event I could not recover my Full Backup (like I am experiencing now) then I take drive No. 2 out of the Caddy and replace it with drive No. 1. So I have two disks that are the same, but I only use one at a given period of time. Right now I have been using Inner Tray drive No. 1 and Inner Tray drive No. 2 is waiting to be placed in the Caddy when I figure out why I can't recover my Full Daily Backups. Inner Tray drive No. 2 is the destination I am trying to recovering to. I have already done a chkdsk on this destination drive, and also, using Western Digital's Data Lifeguard Diagnostics program I performed an extended examination of this destination drive. Chkdsk and Western Digital's Data Lifeguard Diagnostics program did not find anything wrong with this disk. Of course you have to realize that the destination disk could be Inner Tray disk No. 1 or No. 2, depending upon which was being used for the system disk at that time. One other thing I did with the destination drive, it had ATIH 2013 still on it and I uninstalled it and installed ATIH 2016 on it. I didn't think that should matter, but I'll try anything if I think it might help. It didn't.
In addition to what I have said above, I have 6 Full Backups stored on a (01TB) drive that is installed in a separate rack which is in my computer case. These Full Backups are created every morning at 4:00AM. When the seventh Full Backup is created, the oldest backup is deleted. So I always have 6 Daily Full Backups.
I also create a Full Backup of my System disk once a week, and these weekly Full Backups are saved to the Western Digital Elements External Drive. These backups are not scheduled, but they are configured so that no more than 7 of these weekly Full Backups are saved, when the eighth backup is created, Acronis deletes the oldest Full Backup. The reason I keep these Full Backups on this drive is that the drive is taken away from inside my house to another location, so if I was to have a fire or my computer was stolen, I would still have a Full Backup in a safe location. I also am unable to recover these Full Backups.
I noticed in the 2016 Acronis User's Manual, page 67, that " A backup that can be read during validation in Windows, may not always be readable in a Linux environment." Then it tells you how to validate backups under bootable media. I have validated the latest daily and weekly Full Backups under my bootable media, and they both validated. BUT, I still can't recover them.
Bobbo, Thanks for your reply. Here is my take on the three things you suggested.
1. I'm sorry but I don't know what "pushing back an image" means. In regards to "disconnect the original drive", I am going to elaborate on how having the two drives in a caddy and inserting them in a tray. We'll assume the Drive 1 is in the tray and it is my operating system. In order to remove it I have to shut down my computer, then I take a key and unlock the caddy (it is locked down to keep you from accidentally removing an operating hard drive), then I can remove Drive 1. Drive 2 is sitting on a shelf, so I insert it into the tray and lock it down. Then I start the computer up and insert my Acronis Bootable Rescue CD so that I can try to recover my Full Backup. The tray that the caddy slides into is connected to one of my SATA connectors inside the case, and each tray has an internal connector that makes a connection inside the tray. So in essence, whether I'm trying to recover a Full Backup, or for some reason I want to try something with the other drive, I have got to shut down the computer first.
2. In the first sentence of number 2 what you suggest is exactly what I have tried. As to the part about formatting one (or both) and then attempt a recovery, I have considered formatting what I called the destination drive, because in essence it I would be doing that when Acronis tells me that if I proceed with the recovery all data on the disk will be replaced. So far running chkdsk and then trying a recovery has not succedded, and that has been tried several times. I'll probably end up formatting the destination disk, but I can't see formatting the system disk, because then I would have nothing left to work with. If I knew absolutely, positively, that formatting the system disk would solve the problem, I would do it, but I get s__t in my neck thinking about it.
3. All backups have been created with ATIH 2016 and there are no backups created with ATIH 2013, not on any hard drive.
#1) That is all I wanted to confirm - that both drives were not in the caddy at the same time, the orignal disk with the data and the second disk where the image was pushed back to (recovered from the image). If both disks were in the caddy at the same time, the pushed back (recovered) drive and the original drive could have the same hardware ID and cause boot issues.
#2) I agree, you don't want to format both disks (original and the one for recovery) as you may end up with a non bootable system if you can't get the image to restore. Even though chkdsk is not helping and Acronis does do a format before an image is restored, others are reporting better luck when the restore disk is first formatted. Enchantech has suggested in other forum posts that he will run "Diskpart" on the recovery drive and use the /clean option first. He will then power off, boot to the recovery media and push the image (restore it) to the recovery drive and this almost always restults in a successful recovery.
#3) Good! That should help rule out some other issues. As for the images you are attempting to restore, are they fulls, incrementals or differentials? If incrementals or differentials, any luck going back to a full instead? it may not be the most recent, but maybe you get better results?
So where is the restoration failing? Does it report the restoration completed, but then you're finding that it won't boot? Or does it actually throw some kind of air during the restore process and never actually complete?
I am having similar problems with Acronis 2016. I have a 1TB WD green HDD, a 1TB WD Black HDD, and a 1TB Seagate SSHD. Here is my situation chronoligically. I had my operating system on the WD Green HDD. I used the WD Black HDD for a secondary HDD with most of my information saved on it to help ensure against loss. I had the WD version of Acronis. It was an abbreviated version. I used it to back up my HDDs. I am running Windows 10 and on the fast track for the beta versions. I have been running Windows 10 in this manner for well over a year. I used the Windows 7 version of backup and recovery to make a system image disk occasionally. I also use the Windows 10 file history option to back up specific files. All of my backups are kept on an external Seagate 4TB HDD. I have 1.023TB of free space left on the external drive. When this started, I used only the green and black HDDs. The green had the OS on it. It failed. It was still under warranty (3rd time it failed) and was replaced by WD. The support person with WD told me to use a different drive for my operating system as the grenn drives weren't that reliable. I purchased a Seagate SSHD for my primary drive. I had made a recovery thumb drive for both Acronis and Windows. Once I replaced the HDD, I tried to recover the image using Acronis (latest saved image). It failed numerous times with different problems every time. Once it couldn't find the backup, once it had the same error as mentioned above:
Failed to write data to the disk.
Failed to write to sector '0' of hard disk '1'
Direct R/W operation has failed. (0x590001)
Operation not permitted (0xFFF1)
I tried restarting the recovery and got the same error then tried hitting Ignore and the recovery ran the whole way through, but the recovered image would not boot. I tried it again beginning with adding the disk. Still would not recover the image. I also received errors telling me the image was corrupted. I had several saved images and would try a different image when I got the corrupted message. Still not able to successfully recover the image. Finally I gave up and used the Windows recovery. I was able to recover the image, but now the files I had on the second HDD were gone. I was able to find them and recover them one by one in windows explorer. I now had a spare HDD (WD Green). I wanted to clone my C:\ drive to the spare drive using Acronis. I saw an option to create a bootable media to recover to unlike devices. It was only available with the paid version. I upgraded to the paid version. I made the media, created a backup successfully of the newly recovered system, and tried to clone the C:\ drive to the spare drive as a precaution. This did not work and in fact wiped out my C:\ drive as well. I was back to square one. I tried to use the Acronis bootabel media to recover the drive again. Again I had failure after failure for various reasons. I had to recover using the Windows media to the image that I used the first time. Since then, I have updated my software to the most currnt version for the software I didn't lose in this process. I have made a more current Windows image using the Windows 7 backup and recovery option. To this point, Acronis is absolutely useless to me. I would like to find a way to get my money back so I can use it to purchase a more suitable software. How can I accomplish this?
Bobbo, I will look into Diskpart as you mentioned in #2 of your last reply.
In regards to #3, All my Backups are Full, I have never created a differential or incrmental, I agree with Grover Fulls are the only way to go. You asked "so where is the restoration failing?", using the Acronis Bootable Rescue CD I go through the whole process of finding the Full Backup that I want to recover to, and then fill in everything else, and then I get to the warning page that tells me everything will be deleted if I continue, I click OK, then I see the Summary page that shows what the backup is going to do, then I click Proceed and almost instantly I get the message shown in my original post above. It never completes a restoration.
David, have you tried creating the WinPE version of the ATIH 2016 Recovery media and using this rather than the default Linux based media?
Steve, No I have not. I assumed if it took me all the way to the proceed command that it had done what it was supposed to do.
David, I understand, however I would recommend giving the WinPE media a try as the error you are seeing is related to how the application writes to 'sector 0 of disk 1' which may very well be handled very differently between the Linux and WinPE media, especially given that the latter will include all drivers needed to fully interact with your drive hardware.
I would assume that there are differences even in the Linux recovery media from ATIH 2013 to 2016 - this in turn assuming from your initial post that this was working without problem when you were using the 2013 media?
This comment is for James Mason...
James, sounds like you have had a lot of problems. It is normally best to start your own thread, rather than asking questions in the middle of another thread, even if your problem is similar. So, if you want to attempt to get ATI 2016 up and running, please start a new thread in this section. If you want a refund, you need to contact Acronis directly...to their credit, they have an excellent refund policy.
Regards,
FtrPilot
Thank you ftrpilot. Being new to this product, it was difficult just to find the forum. I didn't see how t start a new chain, so I went into the one that most resembled my issue. I'll try to figure out how to use this blog. Thanks agian.
James,
There are a lot of experts on this blog willing to help, but sometimes, requests imbedded in other threads get overlooked. You are more than welcome to start your own thread. I hope you do, and I hope we can get your problem resolved. If you still can't start your own thread, send me a PM and I will try to help.
Regards,
FtrPilot
Steve Smith,
I've been involved with other matters the last two days. Today I tried to create a WinPe media and it failed. I don't know if it's something I did or did not do, put it failed and didn't give any information as why it failed. I'm going to go back and look at the procedure to create the WinPE media and see if there is something I missed. I've never done this before and I did a lot of researching how to do this, and it's very disappointing to fail.
I had to create a wim file, downloaded the Windows Assessment and Development Kit for Windows 8, and downloaded the Acronis Media Add-on. Is there anything I have missed.
David,
See if this post helps. I think that many are getting confused thinking they need to work with the defaault WinPE from Windows ADK. This is not the case as Acronis is creating the WINPE environment for you already. The key is to make sure you're working with the Acronis boot.wim, mounting that and injecting drivers there.
http://forum.acronis.com/forum/111208#comment-332581
Hi David, I am sorry to hear that you have had problems trying to create the WinPE media, I have done this myself but mainly on Windows 10 rather than Windows 8.1, but the process should be much the same.
The one point that stands out for me is your statement that you 'had to create a wim file'?
The process when I followed it was to launch the Acronis Rescue Media Builder, then select the option for WinPE based media with the Acronis plug-in (Note: you should have downloaded & installed the AcronisTrueImage2016_6027addons.exe application - this is available in your Acronis Account).
At this point, if you do not have the necessary Windows ADK, it would give you a link to download & install the same.
The next choice is the media on which you want the WinPE Rescue Media to be created, i.e. an ISO file, a WIM file or directly written to a DVD or CD drive with blank media inserted?
The ISO file can be used to burn a CD or DVD later or can be used to boot from for MBR based BIOS systems.
The WIM file can be used to boot for both MBR or UEFI BIOS systems.
Depending on your choice of media you will next be asked where to store the image files, what folder / drive etc.
Next a Summary panel is shown to confirm your choices for this WinPE Rescue Media, and you click the Proceed button.
The build process will copy a source WIM file, mount that WIM file, make any changes then save the WIM file which will take a few minutes and should result in a media created successfully message.
If you want to boot from either the ISO or WIM image you will need to use a BCD editor such as the free EasyBCD program which allows ISO or WIM files to be added as menu options on the Windows Start Menu.
I also am having a problem restoring a prior backup and when trying to restore to a clean drive I get the following error message:
Failed to deploy task. Restart your computer and try again. If the error persists, check your Antivirus settings
I am using a MacPro with OSX El Capitan 10.11.3. I have a 4 bay USB 3 JBOD. Disc 4 contiains the backup file that was created with Acronis True Image. The drive that was getting backed up died and I am trying to some folders from the backup to a separate clean drive that is in the MacPro. I have rebooted the MacPro. I am not running antivirus software. I have tried rebooting several times and have tried to restore to different drives.
Is there something I can do to recover from this backup? I use Time Machine to backup my boot drive, but the particular drive that failed was excluded from the Time Machine backup. I have several drives that were not included in the Time Machine backup which is why I was using the Acronis software. I had these drives backing up to the 4 bay JBOD, drive for drive.
I also am having a problem restoring a prior backup and when trying to restore to a clean drive I get the following error message:
Failed to deploy task. Restart your computer and try again. If the error persists, check your Antivirus settings
I am using a MacPro with OSX El Capitan 10.11.3. I have a 4 bay USB 3 JBOD. Disc 4 contiains the backup file that was created with Acronis True Image. The drive that was getting backed up died and I am trying to some folders from the backup to a separate clean drive that is in the MacPro. I have rebooted the MacPro. I am not running antivirus software. I have tried rebooting several times and have tried to restore to different drives.
Is there something I can do to recover from this backup? I use Time Machine to backup my boot drive, but the particular drive that failed was excluded from the Time Machine backup. I have several drives that were not included in the Time Machine backup which is why I was using the Acronis software. I had these drives backing up to the 4 bay JBOD, drive for drive.
Petabyte. Be happy to help, but please open your own forum topic so as not to hijack the OP's original post. These issue are not one in the same.
Steve Smith,
Steve, your statement "The one point that stands out for me is your statement that you 'had to create a wim file?' makes me think that you probably feel that something is not quite right with what I did. If you, are anyone else on this forum thinks I have done something wrong, or unwise, please feel free to just say so. I appreciate everyone's help and if that somtimes requires a critical comment, then so be it. Do not hold back saying what you think because you feel I might be offended.
The reason I did that was because of something I found while trying to find out how to create a WinPE media. This was an item I found entitled "Create a USB recovery drive". I found this in Microsoft Help and Support, there was no URL. In this article it had me check for a recovery partition, which I did, and found out I did not have one so I followed the instructions and I wound up with a file C:\RefreshImage\CustomRefresh.wim. Then it went on to tell me how to create a USB recovery drive, which I haven't created at this time. After I did this I realized that there wasn't anything mentioned as to how I would use this with Acronis. The .wim is what caused me to say that I had created a .wim file.
Now I am asking what you think I should do next, delete the file created above "C:\RefreshImage\CustomRefresh.wim" or just start all over. I'm open to any suggestions.
Hello David, thank you for your further update and information. My statement was simply that the fact that you had to create a wim file caught my eye as I know from my own experience in creating the Acronis WinPE recovery media that I did not need to do this as a separate step.
The steps that you followed to "Create a USB recovery drive" may well be valid for the context in which they were offered, but these steps are not needed to create an Acronis WinPE Recovery drive.
The process I outlined in my post above http://forum.acronis.com/forum/112885#comment-332588 are all you need to follow - Acronis Rescue Media Builder will perform all the tasks needed to create the required wim file for you.
My recommendation for your next step would be to reformat the USB drive (assuming you have nothing else on it that you want to move or save), and then use the Acronis Rescue Media Builder to create the USB recovery drive.
See https://kb.acronis.com/content/46170 for known issues with doing this.
See http://www.acronis.com/en-us/support/documentation/ATI2016/index.html#26974.html for the ATIH 2016 User Guide pages on doing this.
Hi David,
It sounds like you created s Windows Specific recovery PE .wim. Use Acronis media builder to create a bootable Windows PE recoverable bootable USB flash drive. Once you have that, the PE is already built. Test it and if it is not finding things like your hard drive or NIC (if your backups are on a network location), we only need to update that particular .WIM. You can do that using my suggestions HERE or perhaps this one HERE. Alternatively, try out DISMGUI as it is GUI based and does not rely on command line so it may be easier to use. If you use DISMGUI, copy the boot.wim file from your default Acronis WinPE bootable USB drive and paste it somewhere easy to access (recommend on teh root of your C: drive to keep it simple). Then create a folder in the same place (again, suggest the root of your C: drive for simplicity - make sure all users have "full access" to the .wim and the new folder - call the folderwhatever you want but "Mount" would make sense or PEMount, or something like that). In DISMGui, you point to the acronis version of the boot.wim and then tell it to mount the wim in the folder you made. Once mounted, the second tab is for injecting drivers. Point it to the driver(s) and let it inject them for you. When done, go back to the first tab and unmount the .WIM and be sure to COMMIT the changes. Then copy your modified boot.wim back to the original location of the bootable USB drive that you previously created in Acronis and you now have updated WinPE with the drivers you injected into it.
Steve Smith and Boobo,
SUCCESS. I was able to finally recover my latest Full Backup, which was on my Western Digital Elements external drive. I was very happy it was from this drive because I had never tried recovering a backup from it before, I always recovered from an internal drive that was only used to store my daily backups.
In regards to my creating the Acronis WinPE Bootable Rescue Media all I can say is that I made a mountain out of a molehill. My advise to anyone wanting to do this is just trust that the Acronis Rescue Media Builder will create what you ask it to.
A funny thing that happened is that when I created the Rescue Media I placed it on a USB Flash drive, never giving any consideration as to whether I could boot from a USB device. When I went to my BIOS to configure it to boot from the USB, I discovered that my BIOS did not offer this, so I placed it on a CD-R, and it works just fine.
I cannot thank the two of you enough for all the information you provided me, the hand-holding you provided, and your infinite patience while trying to help me. THANK YOU SO MUCH.
Nice! Sometimes it's simpler than it seems :).
In most cases, the default offline bootable recovery (Linux version) is sufficient. When it's not, often times, the default bootable WinPE media will be enough without needing to do anything except for downloading an installing the latest compatible Windows ADK and letting Acronis create it.
In more complicated systems (those with the latest hardware such as NVME PCIE hard drives, custom RAID controllers, and apparently even some of the newest Intel Ethernet adapters) then you have to do some of your own advanced ADK modifications to slip the correct drivers in to the Acronis created WinPE.
It can seem like a lot of work if you've never actually done it and/or don't have a strong technical PC background. However, after the 1st or second time it's not really that hard. That said, I am hoping that Acronis will soon relelase updated Linux versions with the most current drivers which should really help most people and alleviate the need for WinPE other than those rare circumstances with new hardware. Also, in the future, I'm hoping the WinPE driver customization will become more user friendly as well within the Acronis products and I've been passing this information through the MVP program so I hope it gets some traction.
Until we actually see these changes in future releases though (here's to hoping), happy to help out and always suggest that users read the WinPE sticky from Mustang as he is probably the most knowledgeable person on the matter and has spent a great deal of time writing up the processes and explaining his findings and recomendations too.
did u solve this problem or still searching for an answer?
it's too easy solution in just 1 step just tell me if u still searching
I'll tell you anyways..
Just turn off (fast startup) option from the power option and then restart and boot from Acronis it gonna work.