Direkt zum Inhalt

True Image 2021 Error 0xb042e: Destination is unavailable.

Thread needs solution

I know this is for 2020 but I didn't see a separate one for 2021

I've seen this error on several machines, but then I noticed that this one has a secondary error of 

error 0xfff0: Invalid access to memory location.

The main error - The target drive is available, this error seems bogus.  When I look in explorer after receiving the message the drive and folder are always there.  I've moved the drive to a new connection on the controller to rule that out and still receive the message also the drive has been replaced.  I'm currently running memtest,12 hrs. so far and no errors.  Chkdsk /r has been run on both the disk being backed up and the on being written to.

I've begun to wonder if I'm reading the error message wrong and the tibx file is not available and not the drive, the contents of the error in the email is in the email.log file and the Acronis error log is Backup worker.log.  

 

Your help is appreciated

 

 

 

Anhang Größe
email.log 2.63 KB
email_0.log 2.63 KB
Backup Worker.log 187.97 KB
0 Users found this helpful

Gary, there looks to be some issues with the backup worker log that is causing the log to give errors in the MVP Assistant tool and not be formatted correctly, making it more difficult to read!  This is one reason for asking users to always zip these log files from the source folder so as to preserve both the original log file name plus also avoid any changes to the content.

Your email logs are actually condensed versions of the TI_Demon logs that accompany the Backup worker ones but without all the extra detailed information.

The errors in the demon logs are slightly different to those in the backup worker log and may offer a clue to what is happening here.

The first error:  Error 0xb042e: Destination is unavailable. is quickly followed by the further error: error 0x29b138d: Input/output error, which is then further clarified by the next error line: error 0xfff0: Invalid access to memory location.

The backup worker log shows normal processing for an extended period up to the point where Acronis was trying to close out the backup file on the destination drive as shown by:

3/24/2022 08:07:54:293 PM message=ar#1: slices=5 user=5861429MB data=3305494MB meta=1644MB unused=10656MB/0.32% deallocated=1929MB/0.06%;
3/24/2022 08:07:56:335 PM message=pcs_errno_to_err: Failed to convert errno 998 to pcs error. Return PCS_ERR_UNKNOWN value.;
3/24/2022 08:07:56:335 PM message=pcs_co_file_readv(\\?\N:\F Drive\F Drive-0001.tibx) failed: 998 (pcs_err=4095);

The above lines are repeated multiple times over in the log then followed by further errors in trying to close the backup file before the log ends with the following lines:

3/24/2022 08:07:57:338 PM message=ar#1: slices=5 user=5861655MB data=3305494MB meta=1644MB unused=10656MB/0.32% deallocated=1929MB/0.06%;
3/24/2022 08:07:57:338 PM message=ar#1: archive close (commit=238/238, file_size=3480984518656, uuid=85b2c61ab2fb6dea5b461739ff4b7438, user read=0MB write=463423MB) rc=-5005 (Input/output error);
3/24/2022 08:07:57:353 PM message=image backup: failed to close archive: 0x29b138d;

From all of the above, there are several possible reasons for this failure:

If the destination drive is connected via USB, then check the Power options for whether USB selective suspend is enabled, that could cause the drive to sleep when Acronis is busy processing data in memory and not actively writing or reading the drive?

Check the backup task Scheduler > Advanced options have the option to prevent the PC from going to sleep or hibernating is enabled.

The invalid access to memory location can be an indication that overclocking of CPU or memory is involved, otherwise may indicate other integrity issues either in Acronis or with the Windows OS.

I thought I had replied to this, guess not

The backup drive is internal, not USB.  The prevent machine from hibernating option is checked.  I'll reinstall Acronis to see if that helps.