Can I get details on "Write error"?
I am trying to backup to an external USB drive. I've done this without problems on about a dozen other systems, but this system is consistenly failing with "The last backup has failed. Write Error." This is a new ATI2017 on this Windows 7 computer so it has never yet had a successful backup. Clicking on 'Check for a solutions' yields "There is no information about this error available now."
There is no mail server on this workstation, so I can't get an emailed log of what the actual problem is. the WIN7 user can write to this drive. ATI 2017 apparently still has no logfile available from the GUI. How can I find out why ATI is having problems writing to this drive?
I've attached the complete logfile. The first several lines are below. It looks like it's trying to access a K: drive, which I don't have. Other than that, I can't tell what it's saying about the error.
2017-05-17 19:37:54:104 2116 I00640000: Writing full version to file: VBOX HARDDISK_full_b1_s1_v1.tib
2017-05-17 19:40:25:604 2116 E00040003: Error 0x40003: Error occurred while writing the file.
| trace level: error
| line: 0x1d8eab676a3f6af0
| file: k:\8053\products\imager\archive\impl\operations\archive_message_callback.cpp:1223
| function: TrueImage::Archive::ArchiveMsgWriteCallbackProcessor::ProcessWriteCallback
| line: 0x1d8eab676a3f6af0, k:\8053\products\imager\archive\impl\operations\archive_message_callback.cpp:1223,
TrueImage::Archive::ArchiveMsgWriteCallbackProcessor::ProcessWriteCallback
| Path: E:\VBOX HARDDISK_full_b1_s1_v1.tib
| $module: ti_demon_vs_8053
|
| error 0x40003: Error occurred while writing the file.
| line: 0x7ceb2cdc9fb121ae
| file: k:\8053\file\windows\win32_file.cpp:517
| function: win32_nocache_file::Write
| line: 0x7ceb2cdc9fb121ae, k:\8053\file\windows\win32_file.cpp:517, win32_nocache_file::Write
| function: WriteFileNoCache
| $module: ti_demon_vs_8053
| error 0x40003: Error occurred while writing the file.
| line: 0x7ceb2cdc9fb121ae
| file: k:\8053\file\windows\win32_file.cpp:517
| function: win32_nocache_file::Write
| line: 0x7ceb2cdc9fb121ae, k:\8053\file\windows\win32_file.cpp:517, win32_nocache_file::Write
| function: WriteFileNoCache
| $module: ti_demon_vs_8053
|
| error 0xfff0: The request could not be performed because of an I/O device error
| line: 0xbd28fdbd64edb8f1
| file: k:\8053\common\error.cpp:307
| function: Common::Error::AddWindowsError
| line: 0xbd28fdbd64edb8f1, k:\8053\common\error.cpp:307, Common::Error::AddWindowsError
| code: 0x8007045d
| $module: ti_demon_vs_8053
2017-05-17 19:40:55:604 2116 I00040003: Error 0x40003: Reattempting the operation. Error: Error occurred while
writing the file..
| trace level: information
| line: 0x1d8eab676a3f6690
| file: k:\8053\products\imager\archive\impl\operations\archive_message_callback.cpp:103
| function: `anonymous-namespace'::TraceReattemptError
| line: 0x1d8eab676a3f6690, k:\8053\products\imager\archive\impl\operations\archive_message_callback.cpp:103, `
anonymous-namespace'::TraceReattemptError
| $module: ti_demon_vs_8053
Chuck, thanks for the log file information. You can ignore the references to K:\... in the error messages, these are internal diagnostic messages referencing code that is only meaningful to the developers.
The key messages are:
Create Backup Archive From: Disk 1 To file: E:\VBOX HARDDISK.tib Writing full version to file: VBOX HARDDISK_full_b1_s1_v1.tib Error 0x40003: Error occurred while writing the file. Path: E:\VBOX HARDDISK_full_b1_s1_v1.tib error 0xfff0: The request could not be performed because of an I/O device error Error 0x40003: Reattempting the operation. Error: Error occurred while writing the file.. Error 0x13c0005: Operation has completed with errors.
There are many repeats of the above error messages, in particular for the I/O device error which suggests that you may have a problem connecting to the target backup destination drive shown as path E:\ - this could be a faulty USB connection cable or the device dropping power while connected, or a port issue.
Check what type of USB drive you are writing to, if this is a USB 3.0 drive, then it should be connected to a USB 3.0 Port on the rear of the computer or to a powered USB 3.0 Hub. USB 3.0 devices can draw up to twice the power of a similar USB 2.0 device.
Take a look for any hardware errors being logged in the Windows Event Logs that occur at the time of the errors shown in the Acronis log files.