Skip to main content

ATI 2019 becomes unresponsive whenever a 10TB hdd is involved

Thread needs solution

I have ATI 2019 on a Win10 1809 (17763.195) machine, with an external 10TB hdd over usb 3.0. I set up a backup scheme from my machine to this external hdd in ATI 2019, but as soon as it's set to go, ATI becomes unresponsive. Other functions involving this 10TB hdd result in unresponsiveness, as well; e.g. attempting to save a Universal-Media .iso file on this disk. My ATI 2019 is typically responsive when backing up to smaller disks/media. Is there some kind of size limit there, one that I'm unaware of?

0 Users found this helpful

I am not aware of any particular size limitations or issues with ATI 2019 (or earlier versions).

When you say "Other functions involving this 10TB hdd result in unresponsiveness, as well; e.g. attempting to save a Universal-Media .iso file on this disk." does this include using Windows Explorer or other non-Acronis applications?

If yes, then I would recommend checking the disk drive via CHKDSK or other tools, trying it on a different computer etc.

10TB is a very large disk.  Being attached via USB even a 3.0 connection will not be a fast performer. 

True Image scans disks before use to verify the integrity of the disk.  I would be patient and wait it out, what you are seeing is probably normal behavior.

Thank you for the responses, my friends.

Steve, I meant Acronis-related operations; other actions work okay. I'm attaching the chkdsk result, though, in any case. And the chkdsk function took a few seconds to conclude (this hdd is literally empty).

Now, there's been a development in my case: I set a back-up scheme in ATI for my 256 GB ssd where this machine's OS resides, and told ATI to perform it. Well, this time there was no unresponsiveness (so, unresponsiveness might be connected to sizes, as before that attempt my source was the entire pc), but I got a 'Queued' message on ATI that has been staying there for the last eight hours and utterly nothing has happened in the meantime.

Do you think I'd better open a ticket with Acronis?

Attachment Size
484443-162309.png 45.21 KB

I wonder if CHKDSK did actually fix an issue here in Stage 2 of its action?

No, this was the result that ATI's Active Protection was triggered; I had to select 'Allow chkdsk.exe' and then repeat the process.

OK, the next question is: can you still reproduce the original issue?  If yes, then you could open a support ticket to have Acronis investigate further with you.

The issue right now is that the Backup process shows as 'Queued' for more than 8 hrs. I don't think this is normal, is it?

Steve is correct.  Looks like chkdsk fixed some errors in the MFT on your disk.  True Image encountered those in its scan of the drive and was attempting to deal with which caused your issue.

A backup set to backup an entire PC will take awhile to run and can take a long time if several disks are involved.  If you have multiple disks installed on or in your system you should run backups for each drive independently and avoid the default Entire PC option.  Leave that to those whom have laptops with a single drive.

 

But now I've selected just a 256 GB disk, this is by not means large or difficult to manage for ATI.

Did you run chkdsk on that disk as well?  You should as it can have errors as well.

You might want to review the link in my signature below (Fix Disk Corruption) for a complete rundown on disk errors and correcting them using chkdsk.

Well, first of all a very happy New Year to you all!

Regarding the issue: Yes, I've run chkdsk on all mounted storage disks. Moreover, I've rechecked and reverified that all power settings for usb etc do not allow for the pc, the connection or the device to enter any power state other than fully on. But, alas, nothing changed; when the designated time for the backup task comes, ATI shows that it is either preparing (for ever and ever) or shows a 2-3% progress that remains frozen for all eternity. At the same time, the external HDD is not accessible by File Explorer or by Command Prompt or PowerShell. After some hours of nothing-happening-ness, I'll have to manually stop everything. The result will be a .tib file of either 0 KB or of just a few KB.

So far I've devised a quick-and-dirty workaround just for me to be able to keep working: I'm attaching the external HDD a few minutes before the scheduled backup time, and in such a scenario things work out smoothly. But obviously ATI cannot do the same when the HDD has been on for more than some mere minutes.