I cannot believe this is happening...
Asus X99-A mobo - Intel i7-5820K - Samsung Pro 850 OS drive, Latest Insider Build Windows 10 - ATI 2016
All had been working well until a few days ago - I was in File Explorer, cliked on the drive ATI was backing up to at that time - File Explore froze - the little busy hour glass started spinning and would not stop. Rebooted and have not been able to do a back up since. it shows it backed up a few MBs and is calculating remaining time.
Uninstalled/reinstalled 2016 - same results - Installed 2015 - same results
Put a new SSD in - clean install of Win 10 RTM - installed 2016 - same results (this aboslutley baffles me) Having changed OSes, drives, ATI versions, The only thing I see that has not been changed is the motherboard - If anybody has any idea how the mobo could cause this situation, I'd be glad to hear it.
I am no expert, but have built a few machines, messed with everyone of them, but never seen anything like this.
All else works fine exept ATI...


- Se connecter pour poster des commentaires

Steve,
I have tried to back up to 3 different drives. NEVER The drives with an OS on them. I will have to check the Windows Event logs.
- Se connecter pour poster des commentaires

One further question, have you checked for any clues in the Acronis Logs folder - you will find this at:
C:\ProgramData\Acronis\TrueImageHome\Logs.
It may be worth cleaning the old logs out (copy into a temporary folder) then try running a new backup and check for any information that might be present to indicate what the problem is - if you have a second system where ATI is working correctly, you could compare the logs from a good backup with the failing one.
- Se connecter pour poster des commentaires

I think I found the cilprit - one of the back up drives, which had 2 back ups on it, appears to have been damaged in some way during my initial "clicking on the drive" scenario - OR - the backs ups on the drive were messed up - or both.
Using DISKPART, at boot up with a Windows 10 Instrall USB, I cleaned, made a new partition, formatted the patrition and now 1 of the drives works fine. The other seems to be damaged beyond reapir at this point, if I try to back up to it I am back at "square one".
So I'm pretty sure I caused this nonsense by not leaving things alone...like I've never done this before ;-)
- Se connecter pour poster des commentaires

I am not 100% certain here but given your descriptions I would say that what occured to your drives was corruption to the MFT and to Partiton Table information on the drives in question. Most likely your assessment as to cause is correct.
You might be able to salvage your drive which you say is beyond repair by again using DISKPART and running a CLEAN ALL command. Since the drive is not a system disk you could do this from an admin command prompt from within Windows if you are comfortable with doing so. The clean all command will remove all formatting and partitioning information from the drive and return it to a RAW state. You can at that point initialize the drive and format it which would bring it back to use for you.
- Se connecter pour poster des commentaires

@Enchantech - tried your idea at the Admin Command Prompt, and booting from a Win 10 Install USB - same results:
"The request could not be performed because of an I/O device error".
At least I have made progress since this am, thanks for ideas. I may just get rid of this drive and chalk if up to the "cost of messing with computers" :-).
I'm afraid if I keep trying to fix it I may break other things in the process.
- Se connecter pour poster des commentaires

It may be worth trying a low-level disk check utility to see if your failed drive is recoverable.
I have used Hiren's Boot CD which has a DOS tool called HDAT2 that I have used to successfully recover bad sectors on drives when these have been connected to the machine I use to boot the CD. Depending on the drive maker, there are other low-level format tools that can completely format problem drives, assuming that the hardware mechanisms are still good and the disk surface is recoverable without head crashes etc.
- Se connecter pour poster des commentaires

@ Steve - I'll check that out - THANKS
- Se connecter pour poster des commentaires

Boot to your Windows install USB and run the diskpart clean all command again. That should work with your I/O error.
- Se connecter pour poster des commentaires

Enchantech wrote:Boot to your Windows install USB and run the diskpart clean all command again. That should work with your I/O error.
It did - you saved a Samsung Pro 850 512 GB SSD - BRAVO! :-)
- Se connecter pour poster des commentaires

I would suggest downloading the diagnostic program from the maker of you problem drive. Western Digital offers Data Lifeguard Diagnostics for Windows and Seagate offers SeaTools for Windows. If it is a WD drive, write all zeros to the drive. That will either fix the problem or tell you the drive has failed and needs to be replaced. If it is a Seagate drive, enable Advanced Tests and select Overwrite Erase. Again, that will either fix the problem or tell you the drive has failed. After the drive has been fixed, you will need to initialize and repartition it.
EDIT:
Missed you post by 6 sec.
- Se connecter pour poster des commentaires

Thanks Mustang - it is the thought that counts, not the timing ;-)
- Se connecter pour poster des commentaires