Skip to main content

Acronis True Image Home 2012, Update 2 (build 7119) - Backup stuck in "calculating", never starts.

Thread needs solution

I recently formatted a new 3 TB hard drive for use as a backup drive via USB. Tried setting up a backup job to that drive, but when I start the backup it seems to be stuck in "calculating" backup size mode and doesn't proceed.

Any suggestions, please?

0 Users found this helpful

Try creating a small file-task just to ensure that ati can properly address the hdisk. If it can, then try recreating the task.

No joy, tried starting a backup of a single file, it remained calculating for 30+ minutes until I ended the job.

Is backup on same drive as whenyou created the backup? did you run chkdsk /f on the drive?

I did run chkdsk /f and no errors were found. This is a brand new drive, no backups have yet been created on it.

It's been formatted as NTFS with I think 16K cluster size.

Can you validate the archive?

Alan,
Run the "chkdsk /f" command on your source drive. There may be issues with the source, not the destination.

Ahh, James F, sorry I misunderstood; I did run chkdsk /f on the source drive (C:, an Intel SSD), no errors.

Scott Hieber, there's no archive to validate, I'm trying to create a backup archive. Did you mean something else?

Was the backup working before to another disk?

What if you "add new disk" using ATI and targeting the new disk? Does this solve the issue?

Ok folks I think the problem is now resolved. Part of the problem appears to be some weirdness with my system, for some reason it sees the single USB external drive as two separate disks in Disk Management:

Disk 4, with its partition Z: named BACKUP I created via Add Disk in Acronis. The mysterious Disk 3 is some strange doppelganger my system sees for some reason, and that was the disk I first tried and failed running the backup with in Acronis.

I tried going into Device Manager and removing both of the entries for the 3 TB USB drives, then rebooted, but after plugging the external drive in after Windows finished booting, both it and its mystery partner were detected again.

Currently the backup seems to be running properly to drive Z: with around 9 minutes remaining, so assuming it validates all should be good. For what it's worth, here's an outline of my system specs:

  • Intel DP965LT motherboard with latest drivers and BIOS
  • 4 GB RAM
  • Rosewill RX35-AT-SU BLK external USB hard drive enclosure
  • Windows 7 Ultimate 32-bit with latest updates
  • eVGA nVidia GTX 470-based graphics card
  • Intel 82566DC Gigabit network adapter
  • Sound Blaster X-Fi Xtreme sound card
  • QSoft RAMDrive Enterprise x86 (set up with drive letter R: on my system, using PAE memory)
  • Intel SSDA2CW080G3 SSD drive (boot)
  • Western Digital WD30EURS-63R8UY0 ATA Device (another 3 TB drive I have in a SATA hot swap tray)
  • Western Digital WD5001AALS-00L3B2 ATA Device (500 GB drive also SATA hot swap)
  • Western Digital WD 30 EURS-63R8UY0 USB Device (the mystery "doppelganger" Disk 3)
  • Western Digital WD 30 EURS-63R8UY0LUN1 USB Device (Disk 4, the one Acronis is using now)

EDIT: The backup has completed and validated successfully. Thanks again for the help! :)

Alan,
The disk controller built in to the external USB enclosure is presenting the drive as two disks to your system, The Z: drive and the unallocated space as Disk 3.
If you want to have your system see the entire drive as one disk, you could use the Windows diskpart command line tool to clean the 3TB external drive. Then use Windows Disk Management to initialize the drive as GPT, create a partition and format the drive. This would be accessible under Windows 7 as a full 3TB drive. You would not be able to use the 3TB drive under Windows XP or earlier if converted to GPT.
Also the USB enclosure you are using may not properly support 3TB drives.

James I tried using DiskPart to clean the 3 TB external drive but no joy, when I reconnected the drive Disk Management still showed Disk 3 and Disk 4, not just a single disk. I've decided to stick my old 500 GB drive in the enclosure, as I couldn't find any firmware updates for the enclosure that might address what seems to be a problem it's having with drives of this size.