which drive had read error during Validate?
During validation I got read error, but it seems my Log is saying the read error was not on either the drive being backed up (F:), or on the backup target drive (H:). It seems my error was on my OS (C:) drive. Can anyone confirm for me which drive is at fault?
I'd re-run the backup but it's big so it takes overnight. I think first I'll run HDD diagnostics and CHKDSK on the three drives (which is gonna take days).
Here's the log (I aborted the backup when I found the message this morning):
| 2/15/2018 2:02:39 PM: -08:00 5356 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false; 2/15/2018 2:02:39 PM: -08:00 5356 I00640002: Operation F started by schedule. 2/15/2018 2:03:07 PM: -08:00 5356 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false; 2/15/2018 2:03:07 PM: -08:00 5356 I013C0000: Operation: Backup 2/15/2018 2:03:07 PM: -08:00 5356 I0064000B: Priority changed to Low. 2/15/2018 2:03:07 PM: -08:00 5356 I000B03F0: Create Backup Archive Password Protected From: Disk 3 To file: H:\ati\F.tib Compression: Normal Exclude: Files matching mask Match criterion: hiberfil.sys, pagefile.sys, $Recycle.Bin, swapfile.sys, System Volume Information, *.tib, *.tib.metadata, *.~, *.tmp, C:\Users\Bill\AppData\Local\Temp, C:\Users\UpdatusUser\AppData\Local\Temp, C:\Users\Administrator\AppData\Local\Temp, C:\Users\Bill\AppData\Local\Microsoft\Windows\INetCache, C:\Users\UpdatusUser\AppData\Local\Microsoft\Windows\INetCache, C:\Users\Administrator\AppData\Local\Microsoft\Windows\INetCache, C:\Users\Bill\AppData\Local\Google\Chrome\User Data\Default\Cache, C:\Users\Bill\AppData\Local\Opera Software, C:\Users\Bill\AppData\Local\Mozilla\Firefox\Profiles, C:\Users\Bill\AppData\Local\Google\Chrome\User Data\Default\Cache, C:\Users\Bill\AppData\Local\Opera Software, C:\Users\Bill\AppData\Local\Mozilla\Firefox\Profiles, C:\Users\Bill\AppData\Local\Google\Chrome\User Data\Default\Cache, C:\Users\Bill\AppData\Local\Opera Software, C:\Users\Bill\AppData\Local\Mozilla\Firefox\Profiles, C:\WINDOWS\CSC, F:\Newsbin, C:\Users\Bill\AppData\Local\Mozilla\Firefox\Profiles\*\cache2, C:\Users\Bill\AppData\Local\Mozilla\Firefox\Profiles\*\OfflineCache, C:\Users\Bill\AppData\Local\Opera Software\Opera Stable\Cache, C:\Users\Bill\AppData\Local\Opera Software\Opera Stable\Media Cache, C:\Users\UpdatusUser\AppData\Local\Mozilla\Firefox\Profiles\*\cache2, C:\Users\UpdatusUser\AppData\Local\Mozilla\Firefox\Profiles\*\OfflineCache, C:\Users\UpdatusUser\AppData\Local\Opera Software\Opera Stable\Cache, C:\Users\UpdatusUser\AppData\Local\Opera Software\Opera Stable\Media Cache, C:\Users\UpdatusUser\AppData\Local\Google\Chrome\User Data\Default\Cache, C:\Users\Administrator\AppData\Local\Mozilla\Firefox\Profiles\*\cache2, C:\Users\Administrator\AppData\Local\Mozilla\Firefox\Profiles\*\OfflineCache, C:\Users\Administrator\AppData\Local\Opera Software\Opera Stable\Cache, C:\Users\Administrator\AppData\Local\Opera Software\Opera Stable\Media Cache, C:\Users\Administrator\AppData\Local\Google\Chrome\User Data\Default\Cache 2/15/2018 2:03:08 PM: -08:00 5356 I000101F8: Pending operation 173 started: 'Creating partition image'. 2/15/2018 2:03:57 PM: -08:00 1492 I00640000: Writing full version to file: F_full_b2_s1_v1.tib 2/15/2018 8:30:11 PM: -08:00 5356 I000101F8: Pending operation 173 started: 'Creating partition image'. 2/15/2018 8:30:12 PM: -08:00 5356 I00640000: The following backups have been successfully created: H:\ati\F_full_b2_s1_v1.tib 2/15/2018 8:30:12 PM: -08:00 5356 I000B0402: Validate Backup Archive Location: H:\ati\F_full_b2_s1_v1.tib 2/15/2018 8:30:12 PM: -08:00 5356 I000101F8: Pending operation 4 started: 'Validate Backup Archive'. 2/16/2018 12:13:50 AM: -08:00 5356 I00040001: Error 0x40001: Error occurred while reading the file. | trace level: information | line: 0x1d8eab676a3f695f | file: c:\bs_hudson\workspace\245\products\imager\archive\impl\operations\archive_message_callback.cpp:822 | function: TrueImage::Archive::ArchiveMsgReadCallbackProcessor::ProcessReadCallback | line: 0x1d8eab676a3f695f, c:\bs_hudson\workspace\245\products\imager\archive\impl\operations\archive_message_callback.cpp:822, TrueImage::Archive::ArchiveMsgReadCallbackProcessor::ProcessReadCallback | Path: | $module: ti_demon_vs_10640 | | error 0x40001: Error occurred while reading the file. | line: 0x7ceb2cdc9fb1203c | file: c:\bs_hudson\workspace\245\core\file\windows\win32_file.cpp:147 | function: win32_file::Read | line: 0x7ceb2cdc9fb1203c, c:\bs_hudson\workspace\245\core\file\windows\win32_file.cpp:147, win32_file::Read | function: ReadFile | $module: ti_demon_vs_10640 | | error 0xfff0: The semaphore timeout period has expired | line: 0xbd28fdbd64edb8f1 | file: c:\bs_hudson\workspace\245\core\common\error.cpp:307 | function: Common::Error::AddWindowsError | line: 0xbd28fdbd64edb8f1, c:\bs_hudson\workspace\245\core\common\error.cpp:307, Common::Error::AddWindowsError | code: 0x80070079 | $module: ti_demon_vs_10640 2/16/2018 5:02:44 AM: -08:00 5356 I013C0006: Operation has succeeded. Start: 2/15/2018 2:02:39 PM |
Thank you very much for the billionth time, Steve! I had a hunch I didn't understand the log.
Since on H I only have room for 1+1, and since I didn't 'trust' the unvalidated +1....I unfortunately already deleted the new 850GB backup.
I figured H (ca. 6 years old) was the more likely culprit simply because C & F are both about a year old.
Right now HD Tune (in Hirens MiniXP) has nearly completed checking C. Next I'll do HD Tune on H; if it passes I'll do CHKDSK /f on H.
(Tangentially, here's a tip somebody might like:) I like to thusly do physical and filesystem error checking separately and in that order because in my and others' experience, CHKDSK /f can occasionally totally hose one's data files, making it impossible to back them up. (The only exception is that I sometimes with a brand new HDD do redundant error checking, i.e. HDD diagnostics then also CHKDSK /r. I lacked the patience to do this when I bought HDDs of 8TB and 10TB though.)
Steve called it. All testing passed except physical testing of H (HDD Tune diagnostics failed; it showed just one red box).
H passed it's 5-year warranty 15 months ago, so no surprise. Replacement ordered.