Mount Corrupt and Unreadable & others errors

User discussion and information resource forum for Image products.

Mount Corrupt and Unreadable & others errors

Postby tas3086 » Tue Sep 27, 2016 2:20 pm

I take daily incremental backups of my operatins system 'C' drive. The base backup was made on 9/11. tried to find a file in todays incremental but was unable to find it. There are 16 incremental files in the chain.
9/12 and 9/13 incrementals are mountable and viewable. File structure is correct.
9/14 and 9/15 incremental mounts are corrupt and unreadable, but views show a single c:\S-1-5-18 directory with lots of directx 2005 dated subdirectories.
9/16 thru 9/24 incrementals are mountable and viewable, but many subdirectories are missing ... like c:\windows\system32\* all the * directories do not exist.
9/25 thr6 9/27 mounts are corrupt and unreadable, but are viewable, and many subdirectories are missing like above.

Attached below are the image logs of the days when things seem to change. Note all backups and validations completed without error. A manual validation of all 17 individual files completed without error.

Somewhere an error should have been generated, or a validation failed. Having to find out that a backup chain is broken is not tolerable, especially when you need it. How can I trust any future backup? How can I help you find the cause of the problem?

Logs follow:
=============================================================================
=================== New Operation Starting ===========================
=================== Date: 2016-09-13 12:14:28 AM ===========================
=============================================================================
Script Name : E:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TeraByte OSD Tool Suite Pro\win\bui9.tbs
script Ver : 2016-08-10 v10.20
TBOSDT Ver : 1.63 - B
Environment : WINDOWS - Option Locking: 0
Log Location: E:\IFD.LOG
Backup From : 3@0x4: Win10(SSD64)(C)
Backup TO : 1@0x2: I_DRIVE(I)
Backup Type : INCR
Basename : 2016-09-11-1021-Win10(SSD64)-.TBI
Incremental : 2016-09-12-0014-Win10(SSD64)-(I)-.TBI
Comments : Using existing Increment as Base
Run Command : imagew64.EXE /ue /b /base:1@0x2:"\2016-09-12-0014-Win10(SSD64)-(I)-.TBI" /f:1@0x2:"\$~YYYY$-$~MM$-$~DD$-$~HHMM$-Win10(SSD64)-(I)-"
Options : EXEC,INCR,,,,
Bios Option : d (DOS Only)
EnvironmentD:
EnvironmentW: u;uy;hash;comp:11;max:4GiB;logl:4;logmax:1MiB;logfile:E:\IFD.LOG;sch:1@0x2:\;;v;wco
EnvironmentL:
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
--------------------------------------------------------------------------
[2016-09-13 12:14:28 AM] E:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TeraByte OSD Tool Suite Pro\win\imagew64.EXE /ue /b /base:1@0x2:\2016-09-12-0014-Win10(SSD64)-(I)-.TBI /f:1@0x2:\$~YYYY$-$~MM$-$~DD$-$~HHMM$-Win10(SSD64)-(I)-
[2016-09-13 12:14:29 AM] Image for Windows (x64) 3.02
[2016-09-13 12:14:29 AM] Starting ...
imagew64.EXE /b /uy /u /sch:"I:\" /base:"I:\2016-09-12-0014-Win10(SSD64)-(I)-" /f:"I:\$~YYYY$-$~MM$-$~DD$-$~HHMM$-Win10(SSD64)-(I)-" /max:4GiB /v /comp:11 /hash
[2016-09-13 12:14:30 AM] PHYLock is waiting for drive writing to stop ...
[2016-09-13 12:14:36 AM] PHYLock using drive C:
[2016-09-13 12:14:36 AM] PHYLock Started
[2016-09-13 12:14:36 AM] PHYLock Using Disk
[2016-09-13 12:14:36 AM] PHYLock version 12
[2016-09-13 12:14:36 AM] Backup: Drive 3 (C:) Win10(SSD64) Partition (04) 60000 MiB NTFS
[2016-09-13 12:14:36 AM] To: I:\2016-09-13-0014-Win10(SSD64)-(I)-.TBI
[2016-09-13 12:16:24 AM] INFO: Total Sectors:122880000 Total Allocated:62665320
[2016-09-13 12:16:24 AM] INFO: 1771963 Sector(s) backed up
[2016-09-13 12:16:25 AM] Validating: Win10(SSD64) Partition (04) 60000 MiB NTFS
[2016-09-13 12:16:25 AM] From: I:\2016-09-13-0014-Win10(SSD64)-(I)-.TBI
[2016-09-13 12:16:33 AM] Operation Completed with Error Code 0
[2016-09-13 12:16:33 AM] Stop
[2016-09-13 12:16:33 AM] -***-INCR Win10(SSD64) to I_DRIVE -Image processing completed with RC=0
=============================================================================
=================== New Operation Starting ===========================
=================== Date: 2016-09-14 12:15:20 AM ===========================
=============================================================================
Script Name : E:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TeraByte OSD Tool Suite Pro\win\bui9.tbs
script Ver : 2016-08-10 v10.20
TBOSDT Ver : 1.63 - B
Environment : WINDOWS - Option Locking: 0
Log Location: E:\IFD.LOG
Backup From : 3@0x4: Win10(SSD64)(C)
Backup TO : 1@0x2: I_DRIVE(I)
Backup Type : INCR
Basename : 2016-09-11-1021-Win10(SSD64)-.TBI
Incremental : 2016-09-13-0014-Win10(SSD64)-(I)-.TBI
Comments : Using existing Increment as Base
Run Command : imagew64.EXE /ue /b /base:1@0x2:"\2016-09-13-0014-Win10(SSD64)-(I)-.TBI" /f:1@0x2:"\$~YYYY$-$~MM$-$~DD$-$~HHMM$-Win10(SSD64)-(I)-"
Options : EXEC,INCR,,,,
Bios Option : d (DOS Only)
EnvironmentD:
EnvironmentW: u;uy;hash;comp:11;max:4GiB;logl:4;logmax:1MiB;logfile:E:\IFD.LOG;sch:1@0x2:\;;v;wco
EnvironmentL:
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
--------------------------------------------------------------------------
[2016-09-14 12:15:20 AM] E:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TeraByte OSD Tool Suite Pro\win\imagew64.EXE /ue /b /base:1@0x2:\2016-09-13-0014-Win10(SSD64)-(I)-.TBI /f:1@0x2:\$~YYYY$-$~MM$-$~DD$-$~HHMM$-Win10(SSD64)-(I)-
[2016-09-14 12:15:20 AM] Image for Windows (x64) 3.02
[2016-09-14 12:15:20 AM] Starting ...
imagew64.EXE /b /uy /u /sch:"I:\" /base:"I:\2016-09-13-0014-Win10(SSD64)-(I)-" /f:"I:\$~YYYY$-$~MM$-$~DD$-$~HHMM$-Win10(SSD64)-(I)-" /max:4GiB /v /comp:11 /hash
[2016-09-14 12:15:22 AM] PHYLock is waiting for drive writing to stop ...
[2016-09-14 12:15:26 AM] PHYLock using drive C:
[2016-09-14 12:15:26 AM] PHYLock Started
[2016-09-14 12:15:26 AM] PHYLock Using Disk
[2016-09-14 12:15:26 AM] PHYLock version 12
[2016-09-14 12:15:27 AM] Backup: Drive 3 (C:) Win10(SSD64) Partition (04) 60000 MiB NTFS
[2016-09-14 12:15:27 AM] To: I:\2016-09-14-0015-Win10(SSD64)-(I)-.TBI
[2016-09-14 12:17:35 AM] INFO: Total Sectors:122880000 Total Allocated:66251824
[2016-09-14 12:17:35 AM] INFO: 6322772 Sector(s) backed up
[2016-09-14 12:17:38 AM] Validating: Win10(SSD64) Partition (04) 60000 MiB NTFS
[2016-09-14 12:17:38 AM] From: I:\2016-09-14-0015-Win10(SSD64)-(I)-.TBI
[2016-09-14 12:17:59 AM] Operation Completed with Error Code 0
[2016-09-14 12:17:59 AM] Stop
[2016-09-14 12:17:59 AM] -***-INCR Win10(SSD64) to I_DRIVE -Image processing completed with RC=0

=============================================================================
=================== New Operation Starting ===========================
=================== Date: 2016-09-15 12:14:45 AM ===========================
=============================================================================
Script Name : E:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TeraByte OSD Tool Suite Pro\win\bui9.tbs
script Ver : 2016-08-10 v10.20
TBOSDT Ver : 1.63 - B
Environment : WINDOWS - Option Locking: 0
Log Location: E:\IFD.LOG
Backup From : 3@0x4: Win10(SSD64)(C)
Backup TO : 1@0x2: I_DRIVE(I)
Backup Type : INCR
Basename : 2016-09-11-1021-Win10(SSD64)-.TBI
Incremental : 2016-09-14-0015-Win10(SSD64)-(I)-.TBI
Comments : Using existing Increment as Base
Run Command : imagew64.EXE /ue /b /base:1@0x2:"\2016-09-14-0015-Win10(SSD64)-(I)-.TBI" /f:1@0x2:"\$~YYYY$-$~MM$-$~DD$-$~HHMM$-Win10(SSD64)-(I)-"
Options : EXEC,INCR,,,,
Bios Option : d (DOS Only)
EnvironmentD:
EnvironmentW: u;uy;hash;comp:11;max:4GiB;logl:4;logmax:1MiB;logfile:E:\IFD.LOG;sch:1@0x2:\;;v;wco
EnvironmentL:
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
--------------------------------------------------------------------------
[2016-09-15 12:14:45 AM] E:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TeraByte OSD Tool Suite Pro\win\imagew64.EXE /ue /b /base:1@0x2:\2016-09-14-0015-Win10(SSD64)-(I)-.TBI /f:1@0x2:\$~YYYY$-$~MM$-$~DD$-$~HHMM$-Win10(SSD64)-(I)-
[2016-09-15 12:14:45 AM] Image for Windows (x64) 3.02
[2016-09-15 12:14:45 AM] Starting ...
imagew64.EXE /b /uy /u /sch:"I:\" /base:"I:\2016-09-14-0015-Win10(SSD64)-(I)-" /f:"I:\$~YYYY$-$~MM$-$~DD$-$~HHMM$-Win10(SSD64)-(I)-" /max:4GiB /v /comp:11 /hash
[2016-09-15 12:14:47 AM] PHYLock is waiting for drive writing to stop ...
[2016-09-15 12:14:58 AM] PHYLock using drive C:
[2016-09-15 12:14:58 AM] PHYLock Started
[2016-09-15 12:14:58 AM] PHYLock Using Disk
[2016-09-15 12:14:58 AM] PHYLock version 12
[2016-09-15 12:14:58 AM] Backup: Drive 3 (C:) Win10(SSD64) Partition (04) 60000 MiB NTFS
[2016-09-15 12:14:58 AM] To: I:\2016-09-15-0014-Win10(SSD64)-(I)-.TBI
[2016-09-15 12:16:59 AM] INFO: Total Sectors:122880000 Total Allocated:65912528
[2016-09-15 12:16:59 AM] INFO: 6569774 Sector(s) backed up
[2016-09-15 12:17:01 AM] Validating: Win10(SSD64) Partition (04) 60000 MiB NTFS
[2016-09-15 12:17:01 AM] From: I:\2016-09-15-0014-Win10(SSD64)-(I)-.TBI
[2016-09-15 12:17:23 AM] Operation Completed with Error Code 0
[2016-09-15 12:17:23 AM] Stop
[2016-09-15 12:17:23 AM] -***-INCR Win10(SSD64) to I_DRIVE -Image processing completed with RC=0
=============================================================================
=============================================================================
=================== New Operation Starting ===========================
=================== Date: 2016-09-16 12:17:48 AM ===========================
=============================================================================
Script Name : E:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TeraByte OSD Tool Suite Pro\win\bui9.tbs
script Ver : 2016-08-10 v10.20
TBOSDT Ver : 1.63 - B
Environment : WINDOWS - Option Locking: 0
Log Location: E:\IFD.LOG
Backup From : 3@0x4: Win10(SSD64)(C)
Backup TO : 1@0x2: I_DRIVE(I)
Backup Type : INCR
Basename : 2016-09-11-1021-Win10(SSD64)-.TBI
Incremental : 2016-09-15-0014-Win10(SSD64)-(I)-.TBI
Comments : Using existing Increment as Base
Run Command : imagew64.EXE /ue /b /base:1@0x2:"\2016-09-15-0014-Win10(SSD64)-(I)-.TBI" /f:1@0x2:"\$~YYYY$-$~MM$-$~DD$-$~HHMM$-Win10(SSD64)-(I)-"
Options : EXEC,INCR,,,,
Bios Option : d (DOS Only)
EnvironmentD:
EnvironmentW: u;uy;hash;comp:11;max:4GiB;logl:4;logmax:1MiB;logfile:E:\IFD.LOG;sch:1@0x2:\;;v;wco
EnvironmentL:
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
--------------------------------------------------------------------------
[2016-09-16 12:17:48 AM] E:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TeraByte OSD Tool Suite Pro\win\imagew64.EXE /ue /b /base:1@0x2:\2016-09-15-0014-Win10(SSD64)-(I)-.TBI /f:1@0x2:\$~YYYY$-$~MM$-$~DD$-$~HHMM$-Win10(SSD64)-(I)-
[2016-09-16 12:17:48 AM] Image for Windows (x64) 3.02
[2016-09-16 12:17:48 AM] Starting ...
imagew64.EXE /b /uy /u /sch:"I:\" /base:"I:\2016-09-15-0014-Win10(SSD64)-(I)-" /f:"I:\$~YYYY$-$~MM$-$~DD$-$~HHMM$-Win10(SSD64)-(I)-" /max:4GiB /v /comp:11 /hash
[2016-09-16 12:17:50 AM] PHYLock is waiting for drive writing to stop ...
[2016-09-16 12:17:56 AM] PHYLock using drive C:
[2016-09-16 12:17:56 AM] PHYLock Started
[2016-09-16 12:17:56 AM] PHYLock Using Disk
[2016-09-16 12:17:56 AM] PHYLock version 12
[2016-09-16 12:17:56 AM] Backup: Drive 3 (C:) Win10(SSD64) Partition (04) 60000 MiB NTFS
[2016-09-16 12:17:56 AM] To: I:\2016-09-16-0017-Win10(SSD64)-(I)-.TBI
[2016-09-16 12:19:52 AM] INFO: Total Sectors:122880000 Total Allocated:62410696
[2016-09-16 12:19:52 AM] INFO: 12226664 Sector(s) backed up
[2016-09-16 12:19:56 AM] Validating: Win10(SSD64) Partition (04) 60000 MiB NTFS
[2016-09-16 12:19:56 AM] From: I:\2016-09-16-0017-Win10(SSD64)-(I)-.TBI
[2016-09-16 12:20:31 AM] Operation Completed with Error Code 0
[2016-09-16 12:20:31 AM] Stop
[2016-09-16 12:20:31 AM] -***-INCR Win10(SSD64) to I_DRIVE -Image processing completed with RC=0
=============================================================================
=================== New Operation Starting ===========================
=================== Date: 2016-09-24 1:33:29 AM ===========================
=============================================================================
Script Name : E:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TeraByte OSD Tool Suite Pro\win\bui9.tbs
script Ver : 2016-08-10 v10.20
TBOSDT Ver : 1.63 - B
Environment : WINDOWS - Option Locking: 0
Log Location: E:\IFD.LOG
Backup From : 3@0x4: Win10(SSD64)(C)
Backup TO : 1@0x2: I_DRIVE(I)
Backup Type : INCR
Basename : 2016-09-11-1021-Win10(SSD64)-.TBI
Incremental : 2016-09-23-0014-Win10(SSD64)-(I)-.TBI
Comments : Using existing Increment as Base
Run Command : imagew64.EXE /ue /b /base:1@0x2:"\2016-09-23-0014-Win10(SSD64)-(I)-.TBI" /f:1@0x2:"\$~YYYY$-$~MM$-$~DD$-$~HHMM$-Win10(SSD64)-(I)-"
Options : EXEC,comp,11,/B,,INCR
Bios Option : b (DOS Only)
EnvironmentD:
EnvironmentW: u;uy;hash;comp:11;max:4GiB;logl:4;logmax:1MiB;logfile:E:\IFD.LOG;sch:1@0x2:\;;v;wco
EnvironmentL:
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
--------------------------------------------------------------------------
[2016-09-24 1:33:29 AM] E:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TeraByte OSD Tool Suite Pro\win\imagew64.EXE /ue /b /base:1@0x2:\2016-09-23-0014-Win10(SSD64)-(I)-.TBI /f:1@0x2:\$~YYYY$-$~MM$-$~DD$-$~HHMM$-Win10(SSD64)-(I)-
[2016-09-24 1:33:30 AM] Image for Windows (x64) 3.02
[2016-09-24 1:33:30 AM] Starting ...
imagew64.EXE /b /uy /u /sch:"I:\" /base:"I:\2016-09-23-0014-Win10(SSD64)-(I)-" /f:"I:\$~YYYY$-$~MM$-$~DD$-$~HHMM$-Win10(SSD64)-(I)-" /max:4GiB /v /comp:11 /hash
[2016-09-24 1:33:30 AM] PHYLock is waiting for drive writing to stop ...
[2016-09-24 1:34:14 AM] PHYLock using drive C:
[2016-09-24 1:34:14 AM] PHYLock Started
[2016-09-24 1:34:14 AM] PHYLock Using Disk
[2016-09-24 1:34:14 AM] PHYLock version 12
[2016-09-24 1:34:14 AM] Backup: Drive 3 (C:) Win10(SSD64) Partition (04) 60000 MiB NTFS
[2016-09-24 1:34:14 AM] To: I:\2016-09-24-0133-Win10(SSD64)-(I)-.TBI
[2016-09-24 1:36:03 AM] INFO: Total Sectors:122880000 Total Allocated:63723768
[2016-09-24 1:36:03 AM] INFO: 3134757 Sector(s) backed up
[2016-09-24 1:36:04 AM] Validating: Win10(SSD64) Partition (04) 60000 MiB NTFS
[2016-09-24 1:36:04 AM] From: I:\2016-09-24-0133-Win10(SSD64)-(I)-.TBI
[2016-09-24 1:36:11 AM] Operation Completed with Error Code 0
[2016-09-24 1:36:11 AM] Stop
[2016-09-24 1:36:11 AM ] -***-INCR Win10(SSD64) to I_DRIVE -Image processing completed with RC=0
=============================================================================
=================== New Operation Starting ===========================
=================== Date: 2016-09-25 12:14:18 AM ===========================
=============================================================================
Script Name : E:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TeraByte OSD Tool Suite Pro\win\bui9.tbs
script Ver : 2016-08-10 v10.20
TBOSDT Ver : 1.63 - B
Environment : WINDOWS - Option Locking: 0
Log Location: E:\IFD.LOG
Backup From : 3@0x4: Win10(SSD64)(C)
Backup TO : 1@0x2: I_DRIVE(I)
Backup Type : INCR
Basename : 2016-09-11-1021-Win10(SSD64)-.TBI
Incremental : 2016-09-24-0133-Win10(SSD64)-(I)-.TBI
Comments : Using existing Increment as Base
Run Command : imagew64.EXE /ue /b /base:1@0x2:"\2016-09-24-0133-Win10(SSD64)-(I)-.TBI" /f:1@0x2:"\$~YYYY$-$~MM$-$~DD$-$~HHMM$-Win10(SSD64)-(I)-"
Options : EXEC,INCR,,,,
Bios Option : d (DOS Only)
EnvironmentD:
EnvironmentW: u;uy;hash;comp:11;max:4GiB;logl:4;logmax:1MiB;logfile:E:\IFD.LOG;sch:1@0x2:\;;v;wco
EnvironmentL:
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
--------------------------------------------------------------------------
[2016-09-25 12:14:18 AM] E:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TeraByte OSD Tool Suite Pro\win\imagew64.EXE /ue /b /base:1@0x2:\2016-09-24-0133-Win10(SSD64)-(I)-.TBI /f:1@0x2:\$~YYYY$-$~MM$-$~DD$-$~HHMM$-Win10(SSD64)-(I)-
[2016-09-25 12:14:18 AM] Image for Windows (x64) 3.02
[2016-09-25 12:14:18 AM] Starting ...
imagew64.EXE /b /uy /u /sch:"I:\" /base:"I:\2016-09-24-0133-Win10(SSD64)-(I)-" /f:"I:\$~YYYY$-$~MM$-$~DD$-$~HHMM$-Win10(SSD64)-(I)-" /max:4GiB /v /comp:11 /hash
[2016-09-25 12:14:19 AM] PHYLock is waiting for drive writing to stop ...
[2016-09-25 12:14:32 AM] PHYLock using drive C:
[2016-09-25 12:14:32 AM] PHYLock Started
[2016-09-25 12:14:32 AM] PHYLock Using Disk
[2016-09-25 12:14:32 AM] PHYLock version 12
[2016-09-25 12:14:32 AM] Backup: Drive 3 (C:) Win10(SSD64) Partition (04) 60000 MiB NTFS
[2016-09-25 12:14:32 AM] To: I:\2016-09-25-0014-Win10(SSD64)-(I)-.TBI
[2016-09-25 12:16:20 AM] INFO: Total Sectors:122880000 Total Allocated:64015288
[2016-09-25 12:16:20 AM] INFO: 1339117 Sector(s) backed up
[2016-09-25 12:16:21 AM] Validating: Win10(SSD64) Partition (04) 60000 MiB NTFS
[2016-09-25 12:16:21 AM] From: I:\2016-09-25-0014-Win10(SSD64)-(I)-.TBI
[2016-09-25 12:16:23 AM] Operation Completed with Error Code 0
[2016-09-25 12:16:23 AM] Stop
[2016-09-25 12:16:23 AM] -***-INCR Win10(SSD64) to I_DRIVE -Image processing completed with RC=0
tas3086
 
Posts: 208
Joined: Mon Mar 19, 2012 11:15 am

Re: Mount Corrupt and Unreadable & others errors

Postby Bob Coleman » Wed Sep 28, 2016 11:42 am

Since you talk about things being "mountable and viewable', I assume you are using TBIMount. Could this possibly just be an error in TBIMount? See viewtopic.php?f=4&t=2353. Not the same type of error, but a couple of incrementals that couldn't be handled by TBIMount, but could be restored OK.
Bob Coleman
 
Posts: 394
Joined: Fri Aug 12, 2011 10:58 am

Re: Mount Corrupt and Unreadable & others errors

Postby tas3086 » Wed Sep 28, 2016 6:44 pm

I ran a memtest86 for 24 hours without errors.

I will try a restore to another test location and see what happens. I will let you know.
tas3086
 
Posts: 208
Joined: Mon Mar 19, 2012 11:15 am

Re: Mount Corrupt and Unreadable & others errors

Postby tas3086 » Wed Sep 28, 2016 8:04 pm

I restored the partition, and I am currently running on it. All appears fine, there are no missing subdirectories that I can see. :D

Bob, thank you for restoring my faith in Terabytes backup, validate, and restore processes. Especially validation. All of these appear to be working fine.

Terabyte: Please let me know if there is anything that I can do to help resolve the Mount and View problems that I have documented.
tas3086
 
Posts: 208
Joined: Mon Mar 19, 2012 11:15 am

Re: Mount Corrupt and Unreadable & others errors

Postby TeraByte Support » Wed Sep 28, 2016 11:54 pm

what about tbiview? If okay, in tbiview but issue in tbimount, may want to
try mounting with simulated writes.

"tas3086" wrote in message news:12577@public.image...

I restored the partition, and I am currently running on it. All appears
fine, there are no missing subdirectories that I can see.

![:D]({SMILIES_PATH}/icon_e_biggrin.gif)

Bob, thank you for restoring my faith in Terabytes backup, validate, and
restore processes. Especially validation. All of these appear to be working
fine.

Terabyte: Please let me know if there is anything that I can do to help
resolve the Mount and View problems that I have documented.

TeraByte Support
 
Posts: 2273
Joined: Thu May 05, 2011 3:37 pm

Re: Mount Corrupt and Unreadable & others errors

Postby TAC109 » Thu Sep 29, 2016 6:59 pm

Could you explain 'mount with simulated writes' in more detail, please. I've checked the 3.02 manual and can't find any reference to this.
TAC109
 
Posts: 214
Joined: Tue Sep 06, 2011 3:41 pm

Re: Mount Corrupt and Unreadable & others errors

Postby TeraByte Support(PP) » Thu Sep 29, 2016 9:35 pm

It's an option in TBIMount you can enable when mounting a partition image. It allows changes to be written to the mounted drive (changes are not saved). This allows things like fixing file system errors, adjusting permissions, etc. -- the drive isn't seen as write protected/read-only.
Paul Purviance
TeraByte Support
TeraByte Support(PP)
 
Posts: 1087
Joined: Thu Aug 11, 2011 5:51 pm

Re: Mount Corrupt and Unreadable & others errors

Postby tas3086 » Sat Oct 01, 2016 9:38 am

Tbiview showed things when tbimount errored with corrupt message. Otherwise tbiview and tbimount show the same missing subdirectories, but a restore and validate worked perfectly. CHKDSK run after restore showed no errors either.

TBIview and Tbimount possibly not handling multiple levels of iterations correctly.

I will retain all the files for a while, just in case you need me to try something.
tas3086
 
Posts: 208
Joined: Mon Mar 19, 2012 11:15 am

Re: Mount Corrupt and Unreadable & others errors

Postby Bob Coleman » Sat Oct 01, 2016 1:35 pm

tas3086 wrote:

>
> TBIview and Tbimount possibly not handling multiple levels of iterations
> correctly.
>

That seems like a reasonable hypothesis though TBIMount, at least, does handle them most of the time
Bob Coleman
 
Posts: 394
Joined: Fri Aug 12, 2011 10:58 am

Re: Mount Corrupt and Unreadable & others errors

Postby TeraByte Support » Sat Oct 01, 2016 4:18 pm

suggest mounting with simulated writes.


"tas3086" wrote in message news:12602@public.image...

Tbiview showed things when tbimount errored with corrupt message. Otherwise
tbiview and tbimount show the same missing subdirectories, but a restore and
validate worked perfectly. CHKDSK run after restore showed no errors
either.

TBIview and Tbimount possibly not handling multiple levels of iterations
correctly.

I will retain all the files for a while, just in case you need me to try
something.

TeraByte Support
 
Posts: 2273
Joined: Thu May 05, 2011 3:37 pm

Next

Return to Image for DOS/Linux/Windows