Skip to main content

Backup of SD card stalls indefinitely without fail error when destination drive not plugged in

Thread needs solution
Forum Member
Posts: 9
Comments: 27

Not sure if this is linked to the previous scheduling problem or not (which somehow doesn't happen now), but I have observed over several days that when the SD card backup scheme kicks in schedule, it will get stuck at 0% forever if the external destination hard disk just so happen to not be connected at that time. It is configured not to re-attempt the backup at all on error.

Using the ATI UI to cancel the backup has no effect. An entire system restart is necessary to "snap it back to its senses", which in reality is forcing the ATI process to terminate.

Thing is, the backup scheme for the main SSD also points to the same destination drive and folder, and that knows how to fail the backup procedure if the destination is not present.

What should I be looking at between the two backup schemes that determines this difference in behaviour?

0 Users found this helpful
Legend
Posts: 80
Comments: 17191

#1

Aaron, what does ATI write in the SD card backup task log files for this situation?

Forum Member
Posts: 9
Comments: 27

#2

The log file reads

log uuid=E22EAA0D-E96F-4DD6-8A9D-FD89D5F14FBF;  product=True Image;  version=18.0;  build=6613;  task=95415547-1547-4CFB-8E25-D625080C788C;  task_name=SanDisk128
Start= 17/5/2018 23:19:13
id=1;  date/time=17/5/2018 23:19:13;  message=Backup reserve copy attributes: format tib; need_reserve_backup_copy false
id=2;  date/time=17/5/2018 23:19:13;  message=Operation SanDisk128 started by schedule.
id=3;  date/time=17/5/2018 23:19:13;  message=Operation description: Stage Description.
id=4;  date/time=17/5/2018 23:19:13;  message=AcronisLRPCConnect::BEGIN id=9,224
id=5;  date/time=17/5/2018 23:19:15;  message=Retreiving Fdisk ver1 disk set to Fdisk ver2c disk set...
id=6;  date/time=17/5/2018 23:19:15;  message=Fdisk2: Use Disk 1 host= 0 bus = 0 target = 0
id=7;  date/time=17/5/2018 23:19:15;  message=Fdisk2: Use Disk 2 host= 0 bus = 0 target = 0
id=8;  date/time=17/5/2018 23:19:15;  message=Refreshing Drivers...
id=9;  date/time=17/5/2018 23:19:15;  message=Enter to process disks in Mbr Driver (id = 9)
id=10;  date/time=17/5/2018 23:19:15;  message=Exit from process disks in Mbr Driver (id = 9)
id=11;  date/time=17/5/2018 23:19:15;  message=Enter to process disks in Gpt Driver (id = 10)
id=12;  date/time=17/5/2018 23:19:15;  message=Try to load Alternate Header from 1000215215
id=13;  date/time=17/5/2018 23:19:15;  message=Gpt Disk 9E253870-2326-4E32-8BBE-7E476385298C LBA=1000215215 ALBA=1
id=14;  date/time=17/5/2018 23:19:15;  message=try to loading Header from 1
id=15;  date/time=17/5/2018 23:19:15;  message=Gpt Disk 9E253870-2326-4E32-8BBE-7E476385298C LBA=1 ALBA=1000215215
id=16;  date/time=17/5/2018 23:19:15;  message=Exit from process disks in Gpt Driver (id = 10)
id=17;  date/time=17/5/2018 23:19:15;  message=LDM: New ProcessDisks(rawLayer, headLayer)
id=18;  date/time=17/5/2018 23:19:15;  message=ProcessDisks: One more disk to check
id=19;  date/time=17/5/2018 23:19:15;  message=ProcessDisks: One more disk to check
id=20;  date/time=17/5/2018 23:19:15;  message=Mark All groups as Root Like Dgs
id=21;  date/time=17/5/2018 23:19:15;  message=------ Volumes Objects ------
id=22;  date/time=17/5/2018 23:19:15;  message=LDM initialization complete
id=23;  date/time=17/5/2018 23:19:15;  message=Analyzing partition '0-0'...
id=24;  date/time=17/5/2018 23:19:16;  message=Analyzing partition '1-1'...
id=25;  date/time=17/5/2018 23:19:16;  message=Analyzing partition 'C:'...
id=26;  date/time=17/5/2018 23:19:16;  message=Analyzing partition '1-4'...
id=27;  date/time=17/5/2018 23:19:16;  message=Analyzing partition '0-0'...
id=28;  date/time=17/5/2018 23:19:16;  message=Analyzing partition 'A:'...
id=29;  date/time=17/5/2018 23:19:16;  message=Backup reserve copy attributes: format tib; need_reserve_backup_copy false
id=30;  date/time=17/5/2018 23:19:16;  message=Operation: backup
id=31;  date/time=17/5/2018 23:19:16;  message=Priority changed to Low.
id=32;  date/time=17/5/2018 23:19:16;  message=Cannot access the path: E:\Acronis Backups\SanDisk128_full_b3_s1_v1.tib;  line_tag=0x4D3F22948E29F1C0
Error_Code=ASMA5QHA8SmOlCI/TUNhbm5vdCBhY2Nlc3MgdGhlIHBhdGg6IEU6XEFjcm9uaXMgQmFja3Vwc1xTYW5EaXNrMTI4X2Z1bGxfYjNfczFfdjEudGliACRtb2R1bGUAV0M6XFByb2dyYW0gRmlsZXMgKHg4NilcQ29tbW9uIEZpbGVzXEFjcm9uaXNcVHJ1ZUltYWdlSG9tZVxUcnVlSW1hZ2VIb21lU2VydmljZS5leGUAAH8ACwBFcUgLqkBeBlRoZSBpbml0aWFsIGZ1bGwgYmFja3VwIHZlcnNpb24gaXMgbm90IGFjY2Vzc2libGUgYXQgdGhlIG1vbWVudC4AAC0ABAAG/CE7e3Rf81RoZSBzcGVjaWZpZWQgZmlsZSBwYXRoIGRvZXMgbm90IGV4aXN0LgBmdW5jdGlvbgBBRmluZEZpcnN0RmlsZVcAcGF0aABXXFw/XEU6XEFjcm9uaXMgQmFja3Vwc1xTYW5EaXNrMTI4X2Z1bGxfYjNfczFfdjEudGliACRtb2R1bGUATgAAAAAAAAAAAPD/AADDuO1kvf0ovVRoZSBzeXN0ZW0gY2Fubm90IGZpbmQgdGhlIHBhdGggc3BlY2lmaWVkAGNvZGUATgMAB4AAAAAAAA==
id=33;  date/time=17/5/2018 23:19:16;  message=The initial full backup version is not accessible at the moment.;  line_tag=0x65E40AA0B487145;  hide=1
id=34;  date/time=17/5/2018 23:19:16;  message=The specified file path does not exist.;  line_tag=0xF35F747B3B21FC06;  hide=1
id=35;  date/time=17/5/2018 23:19:16;  message=The system cannot find the path specified;  line_tag=0xBD28FDBD64EDB8C3;  hide=1
id=36;  date/time=17/5/2018 23:19:16;  message=The specified file path does not exist.;  line_tag=0xF35F747B3B21F8E2
Error_Code=AS0ABADi+CE7e3Rf81RoZSBzcGVjaWZpZWQgZmlsZSBwYXRoIGRvZXMgbm90IGV4aXN0LgBmdW5jdGlvbgBBT3BlbkZpbGVXAHBhdGgAV1xcP1xFOlxBY3JvbmlzIEJhY2t1cHNcU2FuRGlzazEyOF9pbmNfYjNfczNfdjEudGliACRtb2R1bGUATgAAAAAAAAAAAPD/AADDuO1kvf0ovVRoZSBzeXN0ZW0gY2Fubm90IGZpbmQgdGhlIHBhdGggc3BlY2lmaWVkAGNvZGUATgMAB4AAAAAAAA==
id=37;  date/time=17/5/2018 23:19:16;  message=The system cannot find the path specified;  line_tag=0xBD28FDBD64EDB8C3;  hide=1
id=38;  date/time=18/5/2018 00:06:52;  message=The operations have been canceled due to the system shutdown.
id=39;  date/time=18/5/2018 00:07:52;  message=The operation has been terminated due to time out.
Start= 17/5/2018 23:19:13
Finish= 18/5/2018 00:07:52
Total Time= 00:48:39

 

As you can see, the last moments were user intervention (me) to restart the system and terminate the process. Otherwise, it would have been stuck at the error condition of non-existent destination (without proceeding to fail the procedure).

Legend
Posts: 80
Comments: 17191

#3

Aaron, thanks for the log file details, this clearly shows that the task should have terminated by itself without you needing to forcibly end it.  Unfortunately if this is an issue with your ATI 2015 product then there will be no fix coming from Acronis as it is long out of support.

All I can suggest would be to setup a Pre Command to test for the presence of the backup drive and post an error message if it is not connected.  The Pre Command could be something as simple as the lines below put into a .BAT or .CMD file

echo off
if not exist e:\BackupDrive.txt {
msg * Please connect the Acronis backup drive
}

You would need to create a simple text file in the root of your E: backup drive to test for if using the above.

Forum Member
Posts: 9
Comments: 27

#4

Well the (yet again) strange thing is last night ATI didn't even kick in the backup procedure on scheduled time (external destination drive was unplugged). Tonight, with destination drive unplugged again, it actually knew how to fail and stop the procedure on its own!

id=22;  date/time=22/5/2018 23:00:04;  message=------ Volumes Objects ------
id=23;  date/time=22/5/2018 23:00:04;  message=LDM initialization complete
id=24;  date/time=22/5/2018 23:00:04;  message=Analyzing partition '0-0'...
id=25;  date/time=22/5/2018 23:00:04;  message=Analyzing partition '1-1'...
id=26;  date/time=22/5/2018 23:00:04;  message=Analyzing partition 'C:'...
id=27;  date/time=22/5/2018 23:00:04;  message=Analyzing partition '1-4'...
id=28;  date/time=22/5/2018 23:00:04;  message=Analyzing partition '0-0'...
id=29;  date/time=22/5/2018 23:00:05;  message=Analyzing partition 'A:'...
id=30;  date/time=22/5/2018 23:00:05;  message=Backup reserve copy attributes: format tib; need_reserve_backup_copy false
id=31;  date/time=22/5/2018 23:00:05;  message=Operation: backup
id=32;  date/time=22/5/2018 23:00:05;  message=Priority changed to Low.
id=33;  date/time=22/5/2018 23:00:05;  message=Cannot access the path: E:\Acronis Backups\SanDisk128_full_b4_s1_v1.tib;  line_tag=0x4D3F22948E29F1C0
Error_Code=ASMA5QHA8SmOlCI/TUNhbm5vdCBhY2Nlc3MgdGhlIHBhdGg6IEU6XEFjcm9uaXMgQmFja3Vwc1xTYW5EaXNrMTI4X2Z1bGxfYjRfczFfdjEudGliACRtb2R1bGUAV0M6XFByb2dyYW0gRmlsZXMgKHg4NilcQ29tbW9uIEZpbGVzXEFjcm9uaXNcVHJ1ZUltYWdlSG9tZVxUcnVlSW1hZ2VIb21lU2VydmljZS5leGUAAH8ACwBFcUgLqkBeBlRoZSBpbml0aWFsIGZ1bGwgYmFja3VwIHZlcnNpb24gaXMgbm90IGFjY2Vzc2libGUgYXQgdGhlIG1vbWVudC4AAC0ABAAG/CE7e3Rf81RoZSBzcGVjaWZpZWQgZmlsZSBwYXRoIGRvZXMgbm90IGV4aXN0LgBmdW5jdGlvbgBBRmluZEZpcnN0RmlsZVcAcGF0aABXXFw/XEU6XEFjcm9uaXMgQmFja3Vwc1xTYW5EaXNrMTI4X2Z1bGxfYjRfczFfdjEudGliACRtb2R1bGUATgAAAAAAAAAAAPD/AADDuO1kvf0ovVRoZSBzeXN0ZW0gY2Fubm90IGZpbmQgdGhlIHBhdGggc3BlY2lmaWVkAGNvZGUATgMAB4AAAAAAAA==
id=34;  date/time=22/5/2018 23:00:05;  message=The initial full backup version is not accessible at the moment.;  line_tag=0x65E40AA0B487145;  hide=1
id=35;  date/time=22/5/2018 23:00:05;  message=The specified file path does not exist.;  line_tag=0xF35F747B3B21FC06;  hide=1
id=36;  date/time=22/5/2018 23:00:05;  message=The system cannot find the path specified;  line_tag=0xBD28FDBD64EDB8C3;  hide=1
id=37;  date/time=22/5/2018 23:00:05;  message=The specified file path does not exist.;  line_tag=0xF35F747B3B21F8E2
Error_Code=AS0ABADi+CE7e3Rf81RoZSBzcGVjaWZpZWQgZmlsZSBwYXRoIGRvZXMgbm90IGV4aXN0LgBmdW5jdGlvbgBBT3BlbkZpbGVXAHBhdGgAV1xcP1xFOlxBY3JvbmlzIEJhY2t1cHNcU2FuRGlzazEyOF9mdWxsX2I0X3MxX3YxLnRpYgAkbW9kdWxlAE4AAAAAAAAAAADw/wAAw7jtZL39KL1UaGUgc3lzdGVtIGNhbm5vdCBmaW5kIHRoZSBwYXRoIHNwZWNpZmllZABjb2RlAE4DAAeAAAAAAAA=
id=38;  date/time=22/5/2018 23:00:05;  message=The system cannot find the path specified;  line_tag=0xBD28FDBD64EDB8C3;  hide=1
id=39;  date/time=22/5/2018 23:05:04;  message=AcronisLRPCConnect::BEGIN id=4,044
id=40;  date/time=22/5/2018 23:10:06;  message=Cannot access the path: E:\Acronis Backups\SanDisk128_full_b4_s1_v1.tib;  line_tag=0x4D3F22948E29F1C0
Error_Code=ASMA5QHA8SmOlCI/TUNhbm5vdCBhY2Nlc3MgdGhlIHBhdGg6IEU6XEFjcm9uaXMgQmFja3Vwc1xTYW5EaXNrMTI4X2Z1bGxfYjRfczFfdjEudGliACRtb2R1bGUAV0M6XFByb2dyYW0gRmlsZXMgKHg4NilcQ29tbW9uIEZpbGVzXEFjcm9uaXNcVHJ1ZUltYWdlSG9tZVxUcnVlSW1hZ2VIb21lU2VydmljZS5leGUAAOkDCwBKb0gLqkBeBkNoZWNrIHdoZXRoZXIgdGhlIHNvdXJjZSBhbmQgZGVzdGluYXRpb24gcGFydGl0aW9ucyBleGlzdC4AAA8ABABJaT9qZ6uOHUNhbmNlbGVkLgAALQAEAOL4ITt7dF/zVGhlIHNwZWNpZmllZCBmaWxlIHBhdGggZG9lcyBub3QgZXhpc3QuAGZ1bmN0aW9uAEFPcGVuRmlsZVcAcGF0aABXXFw/XEU6XEFjcm9uaXMgQmFja3Vwc1xTYW5EaXNrMTI4X2Z1bGxfYjRfczFfdjEudGliACRtb2R1bGUATgAAAAAAAAAAAPD/AADDuO1kvf0ovVRoZSBzeXN0ZW0gY2Fubm90IGZpbmQgdGhlIHBhdGggc3BlY2lmaWVkAGNvZGUATgMAB4AAAAAAAA==
id=41;  date/time=22/5/2018 23:10:06;  message=Check whether the source and destination partitions exist.;  line_tag=0x65E40AA0B486F4A;  hide=1
id=42;  date/time=22/5/2018 23:10:06;  message=Canceled.;  line_tag=0x1D8EAB676A3F6949;  hide=1
id=43;  date/time=22/5/2018 23:10:06;  message=The specified file path does not exist.;  line_tag=0xF35F747B3B21F8E2;  hide=1
id=44;  date/time=22/5/2018 23:10:06;  message=The system cannot find the path specified;  line_tag=0xBD28FDBD64EDB8C3;  hide=1
 

I'm just confused what the software will or will not do.

Forum Member
Posts: 9
Comments: 27

#5

Took quite a fair amount of time, but I think I figured out what's really happening.

Many days back working on my unplugged laptop, I just so happened to have the ATI UI open when the schedule for the SD card backup kicked in; that UI instance popped up an error dialog box (since the backup storage device ain't present) asking for user decision for further action. I was thus able to cancel it and ATI went back to usable, responsive state.

I thus guessed even though the scheduled operation's supposed to kick start and run without any UI, it still deferred the error to a non-existent UI waiting forever for user feedback will that never return. Any new UI launched after the fact is unaware of that "dialog box" thus unable to rescue the situation, necessitating an entire OS restart.

By setting the Error handling section - Do not show messages and dialogs while processing (silent mode), the backup operation is now able to fail immediately (as it should) and I get a workable UI once I've plugged back in my backup drive.

It seems to me there's some UI programming naivete in this design that makes the backup operation expect an always-open UI to display error dialog boxes. Hopefully the newer versions don't carry such tightly-coupled behaviour.

Legend
Posts: 80
Comments: 17191

#6

Aaron, thanks for the update and explanation of the issue you have discovered.  Personally, I always turn off all of the Error Handling options for my backup tasks, as I prefer that if an issue arises that I get to know about it when it happens, and not after ATI has exhausted all its error retries etc.