AND Another "cannot open *.#1" issue.

User discussion and information resource forum for Image products.
Post Reply
tas3086
Posts: 321
Joined: Mon Mar 19, 2012 6:15 pm

AND Another "cannot open *.#1" issue.

Post by tas3086 »

What documentation do you need? Exactly which files? Pick from the list below.
Was able to recreate the error running the sequence a 2nd time using the same command.
(Sorry was in hospital last time after last error)


=============================================================================
=================== New Operation Starting ===========================
=================== Date: 2015-08-23 12:05:01 AM ===========================
=============================================================================
Script Name : F:\Program Files\TeraByte Unlimited\TeraByte OSD Tool Suite Pro for BootIt\win\bui9.tbs 2015-09-05 v10.06
Environment : WINDOWS - Option Locking: 0
Backup From : 3@0x5E: Win10(SSD64)()
Backup TO : 1@0x2: I_DRIVE(I)
Backup Type : INCR
Basename : 2015-08-02-0017-Win10(SSD64)-.TBI
Incremental : 2015-08-22-0235-Win10(SSD64)-(I)-.TBI
Comments : Using existing Increment as Base
Run Command : IMAGEw.EXE /ue /b /base:1@0x2:"\2015-08-22-0235-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:13;max:4GiB;logl:4;logmax:1MiB;logfile:\IFD.LOG;sch:1@0x2:\;;v;wco
EnvironmentL:
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
--------------------------------------------------------------------------
[2015-08-23 12:05:03 AM] F:\Program Files\TeraByte Unlimited\TeraByte OSD Tool Suite Pro for BootIt\win\IMAGEw.EXE /ue /b /base:1@0x2:\2015-08-22-0235-Win10(SSD64)-(I)-.TBI /f:1@0x2:\$~YYYY$-$~MM$-$~DD$-$~HHMM$-Win10(SSD64)-(I)-
[2015-08-23 12:05:05 AM] Image for Windows 2.97d
[2015-08-23 12:05:05 AM] Starting ...
IMAGEw.EXE /b /uy /u /sch:"I:\" /base:"I:\2015-08-22-0235-Win10(SSD64)-(I)-" /f:"I:\$~YYYY$-$~MM$-$~DD$-$~HHMM$-Win10(SSD64)-(I)-" /max:4GiB /v /comp:13 /hash
[2015-08-23 12:05:05 AM] PHYLock is waiting for drive writing to stop ...
[2015-08-23 12:05:09 AM] PHYLock Started
[2015-08-23 12:05:09 AM] PHYLock Using RAM
[2015-08-23 12:05:09 AM] PHYLock version 11
[2015-08-23 12:05:10 AM] Backup: Drive 3 Win10(SSD64) Partition (5E) 60000 MiB HPFS/NTFS
[2015-08-23 12:05:10 AM] To: I:\2015-08-23-0005-Win10(SSD64)-(I)-.TBI
[2015-08-23 08:38:23 AM] Are you sure you want to cancel?
[2015-08-23 08:38:25 AM] Cannot open "I:\2015-08-22-0235-Win10(SSD64)-(I)-.#1".
[2015-08-23 08:38:29 AM] INFO: Total Sectors:122880000 Total Allocated:52940168
[2015-08-23 08:38:29 AM] INFO: 1514924 Sector(s) backed up
[2015-08-23 08:38:29 AM] Validating: Win10(SSD64) Partition (5E) 60000 MiB HPFS/NTFS
[2015-08-23 08:38:29 AM] From: I:\2015-08-23-0005-Win10(SSD64)-(I)-.TBI
[2015-08-23 08:38:33 AM] Operation Completed with Error Code 0
[2015-08-23 08:38:33 AM] Stop
[2015-08-23 08:38:34 AM] -***-INCR Win10(SSD64) to I_DRIVE-Image processing completed with RC=0
***************************************************************************************************
File Chain:
2015-08-02-0017-Win10(SSD64)-.#0
2015-08-02-0017-Win10(SSD64)-.1
2015-08-02-0017-Win10(SSD64)-.2
2015-08-02-0017-Win10(SSD64)-.TBI
2015-08-02-0800-Win10(SSD64)-(I)-.#0
2015-08-02-0800-Win10(SSD64)-(I)-.TBI
2015-08-04-0010-Win10(SSD64)-(I)-.#0
2015-08-04-0010-Win10(SSD64)-(I)-.TBI
2015-08-05-0005-Win10(SSD64)-(I)-.#0
2015-08-05-0005-Win10(SSD64)-(I)-.TBI
2015-08-06-0005-Win10(SSD64)-(I)-.#0
2015-08-06-0005-Win10(SSD64)-(I)-.TBI
2015-08-07-0005-Win10(SSD64)-(I)-.#0
2015-08-07-0005-Win10(SSD64)-(I)-.TBI
2015-08-08-0137-Win10(SSD64)-(I)-.#0
2015-08-08-0137-Win10(SSD64)-(I)-.TBI
2015-08-09-0005-Win10(SSD64)-(I)-.#0
2015-08-09-0005-Win10(SSD64)-(I)-.TBI
2015-08-10-0005-Win10(SSD64)-(I)-.#0
2015-08-10-0005-Win10(SSD64)-(I)-.TBI
2015-08-11-0005-Win10(SSD64)-(I)-.#0
2015-08-11-0005-Win10(SSD64)-(I)-.1
2015-08-11-0005-Win10(SSD64)-(I)-.TBI
2015-08-12-0838-Win10(SSD64)-(I)-.#0
2015-08-12-0838-Win10(SSD64)-(I)-.TBI
2015-08-13-0005-Win10(SSD64)-(I)-.#0
2015-08-13-0005-Win10(SSD64)-(I)-.TBI
2015-08-14-0005-Win10(SSD64)-(I)-.#0
2015-08-14-0005-Win10(SSD64)-(I)-.TBI
2015-08-15-0255-Win10(SSD64)-(I)-.#0
2015-08-15-0255-Win10(SSD64)-(I)-.TBI
2015-08-16-0005-Win10(SSD64)-(I)-.#0
2015-08-16-0005-Win10(SSD64)-(I)-.TBI
2015-08-17-0005-Win10(SSD64)-(I)-.#0
2015-08-17-0005-Win10(SSD64)-(I)-.TBI
2015-08-18-0005-Win10(SSD64)-(I)-.#0
2015-08-18-0005-Win10(SSD64)-(I)-.TBI
2015-08-19-0005-Win10(SSD64)-(I)-.#0
2015-08-19-0005-Win10(SSD64)-(I)-.TBI
2015-08-20-0005-Win10(SSD64)-(I)-.#0
2015-08-20-0005-Win10(SSD64)-(I)-.TBI
2015-08-22-0235-Win10(SSD64)-(I)-.#0
2015-08-22-0235-Win10(SSD64)-(I)-.TBI
2015-08-23-0005-Win10(SSD64)-(I)-.#0
2015-08-23-0005-Win10(SSD64)-(I)-.TBI
TeraByte Support
Posts: 3615
Joined: Thu May 05, 2011 10:37 pm

Re: AND Another "cannot open *.#1" issue.

Post by TeraByte Support »

I need all .tbi files grabbed from the base to the one that was the base of
the incremental (not the result but the base). Plus only the #0 file of
that base of the incremental.

So in this case all base .tbi files (grab 64K from the start) up to and
including I:\2015-08-22-0235-Win10(SSD64)-(I)-.tbi plus the
I:\2015-08-22-0235-Win10(SSD64)-(I)-.#0 file

If you have any earlier in the chain that would be less files...


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

What documentation do you need? Exactly which files? Pick from the list
below.
Was able to recreate the error running the sequence a 2nd time using the
same command.
(Sorry was in hospital last time after last error)


=============================================================================
=================== New Operation Starting
===========================
=================== Date: 2015-08-23 12:05:01 AM
===========================
=============================================================================
Script Name : F:\Program Files\TeraByte Unlimited\TeraByte OSD Tool Suite
Pro for BootIt\win\bui9.tbs 2015-09-05 v10.06
Environment : WINDOWS - Option Locking: 0
Backup From : 3@0x5E: Win10(SSD64)()
Backup TO : 1@0x2: I_DRIVE(I)
Backup Type : INCR
Basename : 2015-08-02-0017-Win10(SSD64)-.TBI
Incremental : 2015-08-22-0235-Win10(SSD64)-(I)-.TBI
Comments : Using existing Increment as Base
Run Command : IMAGEw.EXE /ue /b
/base:1@0x2:"\2015-08-22-0235-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:13;max:4GiB;logl:4;logmax:1MiB;logfile:\IFD.LOG;sch:1@0x2:\;;v;wco
EnvironmentL:
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
=
--------------------------------------------------------------------------
[2015-08-23 12:05:03 AM] F:\Program Files\TeraByte Unlimited\TeraByte OSD
Tool Suite Pro for BootIt\win\IMAGEw.EXE /ue /b
/base:1@0x2:\2015-08-22-0235-Win10(SSD64)-(I)-.TBI
/f:1@0x2:\$~YYYY$-$~MM$-$~DD$-$~HHMM$-Win10(SSD64)-(I)-
[2015-08-23 12:05:05 AM] Image for Windows 2.97d
[2015-08-23 12:05:05 AM] Starting ...
IMAGEw.EXE /b /uy /u /sch:"I:\" /base:"I:\2015-08-22-0235-Win10(SSD64)-(I)-"
/f:"I:\$~YYYY$-$~MM$-$~DD$-$~HHMM$-Win10(SSD64)-(I)-" /max:4GiB /v /comp:13
/hash
[2015-08-23 12:05:05 AM] PHYLock is waiting for drive writing to stop ...
[2015-08-23 12:05:09 AM] PHYLock Started
[2015-08-23 12:05:09 AM] PHYLock Using RAM
[2015-08-23 12:05:09 AM] PHYLock version 11
[2015-08-23 12:05:10 AM] Backup: Drive 3 Win10(SSD64) Partition (5E) 60000
MiB HPFS/NTFS
[2015-08-23 12:05:10 AM] To: I:\2015-08-23-0005-Win10(SSD64)-(I)-.TBI
[2015-08-23 08:38:23 AM] Are you sure you want to cancel?
[2015-08-23 08:38:25 AM] Cannot open
"I:\2015-08-22-0235-Win10(SSD64)-(I)-.#1".
[2015-08-23 08:38:29 AM] INFO: Total Sectors:122880000 Total
Allocated:52940168
[2015-08-23 08:38:29 AM] INFO: 1514924 Sector(s) backed up
[2015-08-23 08:38:29 AM] Validating: Win10(SSD64) Partition (5E) 60000 MiB
HPFS/NTFS
[2015-08-23 08:38:29 AM] From: I:\2015-08-23-0005-Win10(SSD64)-(I)-.TBI
[2015-08-23 08:38:33 AM] Operation Completed with Error Code 0
[2015-08-23 08:38:33 AM] Stop
[2015-08-23 08:38:34 AM] -***-INCR Win10(SSD64) to I_DRIVE-Image processing
completed with RC=0
***************************************************************************************************
File Chain:
2015-08-02-0017-Win10(SSD64)-.#0
2015-08-02-0017-Win10(SSD64)-.1
2015-08-02-0017-Win10(SSD64)-.2
2015-08-02-0017-Win10(SSD64)-.TBI
2015-08-02-0800-Win10(SSD64)-(I)-.#0
2015-08-02-0800-Win10(SSD64)-(I)-.TBI
2015-08-04-0010-Win10(SSD64)-(I)-.#0
2015-08-04-0010-Win10(SSD64)-(I)-.TBI
2015-08-05-0005-Win10(SSD64)-(I)-.#0
2015-08-05-0005-Win10(SSD64)-(I)-.TBI
2015-08-06-0005-Win10(SSD64)-(I)-.#0
2015-08-06-0005-Win10(SSD64)-(I)-.TBI
2015-08-07-0005-Win10(SSD64)-(I)-.#0
2015-08-07-0005-Win10(SSD64)-(I)-.TBI
2015-08-08-0137-Win10(SSD64)-(I)-.#0
2015-08-08-0137-Win10(SSD64)-(I)-.TBI
2015-08-09-0005-Win10(SSD64)-(I)-.#0
2015-08-09-0005-Win10(SSD64)-(I)-.TBI
2015-08-10-0005-Win10(SSD64)-(I)-.#0
2015-08-10-0005-Win10(SSD64)-(I)-.TBI
2015-08-11-0005-Win10(SSD64)-(I)-.#0
2015-08-11-0005-Win10(SSD64)-(I)-.1
2015-08-11-0005-Win10(SSD64)-(I)-.TBI
2015-08-12-0838-Win10(SSD64)-(I)-.#0
2015-08-12-0838-Win10(SSD64)-(I)-.TBI
2015-08-13-0005-Win10(SSD64)-(I)-.#0
2015-08-13-0005-Win10(SSD64)-(I)-.TBI
2015-08-14-0005-Win10(SSD64)-(I)-.#0
2015-08-14-0005-Win10(SSD64)-(I)-.TBI
2015-08-15-0255-Win10(SSD64)-(I)-.#0
2015-08-15-0255-Win10(SSD64)-(I)-.TBI
2015-08-16-0005-Win10(SSD64)-(I)-.#0
2015-08-16-0005-Win10(SSD64)-(I)-.TBI
2015-08-17-0005-Win10(SSD64)-(I)-.#0
2015-08-17-0005-Win10(SSD64)-(I)-.TBI
2015-08-18-0005-Win10(SSD64)-(I)-.#0
2015-08-18-0005-Win10(SSD64)-(I)-.TBI
2015-08-19-0005-Win10(SSD64)-(I)-.#0
2015-08-19-0005-Win10(SSD64)-(I)-.TBI
2015-08-20-0005-Win10(SSD64)-(I)-.#0
2015-08-20-0005-Win10(SSD64)-(I)-.TBI
2015-08-22-0235-Win10(SSD64)-(I)-.#0
2015-08-22-0235-Win10(SSD64)-(I)-.TBI
2015-08-23-0005-Win10(SSD64)-(I)-.#0
2015-08-23-0005-Win10(SSD64)-(I)-.TBI

tas3086
Posts: 321
Joined: Mon Mar 19, 2012 6:15 pm

Re: AND Another "cannot open *.#1" issue.

Post by tas3086 »

File is being uploaded now, will take 30 minutes or so to complete. UPDATE: It is completed.
It is in the same location and name as documented in: Ticket ID: PUZ-678-12931

I included grab of all .tbi files. I think you want to ignore the last one. It was the one created during the error.
hope it helps.

As I can recreate, I can test and verify any fix.
Let me know when I can delete the upload.
TeraByte Support
Posts: 3615
Joined: Thu May 05, 2011 10:37 pm

Re: AND Another "cannot open *.#1" issue.

Post by TeraByte Support »

thanks but the #0 file was from that last file too .. would need the
2015-08-22-0235-Win10(SSD64)-(I)-.#0 file


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

File is being uploaded now, will take 30 minutes or so to complete. UPDATE:
It is completed.
It is in the same location and name as documented in: Ticket ID:
PUZ-678-12931

I included grab of all .tbi files. I think you want to ignore the last one.
It was the one created during the error.
hope it helps.

As I can recreate, I can test and verify any fix.
Let me know when I can delete the upload.

tas3086
Posts: 321
Joined: Mon Mar 19, 2012 6:15 pm

Re: AND Another "cannot open *.#1" issue.

Post by tas3086 »

Sorry,
Same location as last, but filename is doc1.zip and only contains the #0 file
Let me know when you are done with files.
TeraByte Support
Posts: 3615
Joined: Thu May 05, 2011 10:37 pm

Re: AND Another "cannot open *.#1" issue.

Post by TeraByte Support »

You have an email on the ticket.

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

Post Reply