True Image cannot find the external backup drive

Last night my laptop backup failed because the external was not seen by Acronis during the backup. The initial error message was "Backup Task is waiting for user interaction" The details are as follows:
New disk Samsung SSD 850 EVO 250GB_full_b15_s1_v1 task is waiting for user interaction. Description: Information: Error occurred while creating the file. Details: To specify another location, click Browse.
The message indicates that the backup location could not be found. I launched TI but it would not load and seemed to hang trying to find the backup location. I rebooted the machine and launched TI again. The backup location showed in the GUI with a red circle with an X between source and destination. I selected the destination in attempt to re-select it but the built in file browser did not display the disk at all. Windows file explorer could see the disk just fine. I powered the external backup drive off and then on. TI was then able to browse to the correct location. I re-selected the destination. I have a 1TB WD drive in a Wavlink dock station for my backups.
The backup eventually failed. I've attached the complete log. I experienced a similar problem a few weeks ago but he error said
The request could not be performed because of an I/O device error
In the this case Windows could not see the drive either. Turning the dock station on and off resolved the problem until last night. I've also uploaded the log file from June 1 which was the first time I saw this issue though there are two different causes. Thoughts and comments are appreciated.


- Se connecter pour poster des commentaires

Thanks for the response Steve.
1) Selective suspend was enabled. I have disabled it.
2)The dock has its own power supply.
3) I currently have no other method of connecting the drive at this time.
I'll try with the selective suspend disabled and see what happens. It was three weeks between the 2 failures so this may take a while but I will report back.
- Se connecter pour poster des commentaires

So far the error has not reoccurred with Selective Suspend disabled. I'll continue to monitor this to be sure. Thanks, for the tip Steve Smith.
- Se connecter pour poster des commentaires