Aller au contenu principal

Acronis causing freeze

Thread needs solution

W7, True Image 2016

TI is backing up an internal drive with images successfully. During the scheduled bu of a raid 1 C drive (Intel Rapid Storage Technology) it causes a lockup at about 3/4 complete. This started yesterday and then repeated today. 1. Any ideas? 2. How do I generate a failure report? 

0 Users found this helpful

I would recommend starting by downloading a copy of the Log File Viewer app from this forum and checking for any messages in the log(s) for the backup task where you are seeing the lockup.

When you say it causes a lockup at about 3/4 complete, how is this displayed, i.e. is it just the backup that is locked up or is the whole system locked up?

Is this a new backup task or has this been run successfully without lockup for a longer period?

If the backup task has been successful in the past but now gives this lockup, has anything changed on your system in the intervening period?

You state that backups of internal drive are successful, but not this Raid 1 C drive - does that mean that this is an external drive, and if so, is this in a NAS device?

You can generate a System Report from within the ATIH 2016 application in the Tools & Utilities section, or using the Feedback tool.

Is the entire system locked up or just Acronis?  

Dirty/back sectors/blocks can cause a backup to slowdown or fail.  You may want to do a disk/RAID integrity check.  Alternatively, you can configure backups to ignore bad sectors with the Error Handling options in you backup task

Network shares can be an issue if connectivity is lost during the process as well.  Guessing this is not the issue if it's a local internal RAID, but the RAID controller could be disconnecting too which would have a similar effect. What do your Windows System logs show?  Any signs of a failing drive or RAID issue?

What if you create a new backup task in Windows and run it - same issue or does that one complete?  Sometimes, backup tasks can get corrupted (usually due to modifying them after they've been configured and backups have already run, but can also occur during unexpcted shutdowns during backup tasks, or other sytsem issues).  In some cases, just creating a new backup task and letting it run to completion is all you need and then discontinue using the old one (you can keep the old backups for posterity though - if you do though, make sure your new job has a unique name so it does NOT match the existing backup job name).

What happens if you try to boot to the offline bootable recovery media and take a backup instead of via Windows?  If it also fails, it could be a dirty drive.