TeraByte Unlimited

Received popup during incremental backup:
"Insert media 2 containing file i:-\2015-08-05-0005-Win10(SSD64)-(I)-.#1"

6 hours later I replied "CANCEL" to the popup. The backup completed normally with return code 0. The .#1 file did not exist, however #0 did. There are no .#1 files in the backup chain of files. Validation is fine. What went wrong? Or did it ? Here are my logs.

What will happen tonight?
EDIT: The Next Day: Incremental backup to the newer existing set worked perfectly without a glitch.

=============================================================================
=================== New Operation Starting ===========================
=================== Date: 2015-08-06 12:05:24 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-05-0005-Win10(SSD64)-(I)-.TBI
Comments : Using existing Increment as Base
Run Command : IMAGEw.EXE /ue /b /base:1@0x2:"\2015-08-05-0005-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-06 12:05:27 AM] F:\Program Files\TeraByte Unlimited\TeraByte OSD Tool Suite Pro for BootIt\win\IMAGEw.EXE /ue /b /base:1@0x2:\2015-08-05-0005-Win10(SSD64)-(I)-.TBI /f:1@0x2:\$~YYYY$-$~MM$-$~DD$-$~HHMM$-Win10(SSD64)-(I)-
[2015-08-06 12:05:28 AM] Image for Windows 2.97c
[2015-08-06 12:05:28 AM] Starting ...
IMAGEw.EXE /b /uy /u /sch:"I:\" /base:"I:\2015-08-05-0005-Win10(SSD64)-(I)-" /f:"I:\$~YYYY$-$~MM$-$~DD$-$~HHMM$-Win10(SSD64)-(I)-" /max:4GiB /v /comp:13 /hash
[2015-08-06 12:05:29 AM] PHYLock is waiting for drive writing to stop ...
[2015-08-06 12:05:34 AM] PHYLock Started
[2015-08-06 12:05:34 AM] PHYLock Using RAM
[2015-08-06 12:05:34 AM] PHYLock version 11
[2015-08-06 12:05:36 AM] Backup: Drive 3 Win10(SSD64) Partition (5E) 60000 MiB HPFS/NTFS
[2015-08-06 12:05:36 AM] To: I:\2015-08-06-0005-Win10(SSD64)-(I)-.TBI
[2015-08-06 06:59:25 AM] Are you sure you want to cancel?
[2015-08-06 06:59:27 AM] Cannot open "I:\2015-08-05-0005-Win10(SSD64)-(I)-.#1".
[2015-08-06 06:59:34 AM] INFO: Total Sectors:122880000 Total Allocated:51276904
[2015-08-06 06:59:34 AM] INFO: 2451406 Sector(s) backed up
[2015-08-06 06:59:35 AM] Validating: Win10(SSD64) Partition (5E) 60000 MiB HPFS/NTFS
[2015-08-06 06:59:35 AM] From: I:\2015-08-06-0005-Win10(SSD64)-(I)-.TBI
[2015-08-06 06:59:43 AM] Operation Completed with Error Code 0
[2015-08-06 06:59:43 AM] Stop
[2015-08-06 06:59:44 AM] -***-INCR Win10(SSD64) to I_DRIVE-Image processing completed with RC=0

******************* Resulting File Chain **********************
************************ "Win10(SSD64)" **************************
********************************************************************
2015-08-02-0017-Win10(SSD64)-.TBI-
2015-08-02-0800-Win10(SSD64)-(I)-.TBI
2015-08-04-0010-Win10(SSD64)-(I)-.TBI
2015-08-05-0005-Win10(SSD64)-(I)-.TBI
2015-08-06-0005-Win10(SSD64)-(I)-.TBI
------------------------------------------------------------------------------
Directory of I:\ (for the file that was missing)

2015-08-05 12:07 AM 147,607,288 2015-08-05-0005-Win10(SSD64)-(I)-.#0
2015-08-05 12:07 AM 2,818,048 2015-08-05-0005-Win10(SSD64)-(I)-.TBI
2 File(s) 150,425,336 bytes

It is now 08-08-2015, while yesterdays increment was successful, todays increment experienced the same notice error but for yesterdays file:
"Insert media 2 containing file i:-\2015-08-07-0005-Win10(SSD64)-(I)-.#1"
Entering cancel, imagew reported the same error and then completed normally with return code 0.
That file does not and has never existed. Why is it asking for it, and stopping the automated backup?

One thing that I do notice that is odd, is that this win10 partition is the third physical primary partition on the disk, yet it's partition address is 3@0x5E
All of my other primary partition numbers end in a single number 1,2,3,or 4. Why is this one showing as 5E. 5 is normally an extended logical partition whos numbers normally end in 0x###. Could this be a reason why things are goofy?

This issue is being looked into. When this showed up the first time was the base image for the backup created by v2.97c?

Regarding the partition ID, is that drive EMBR? It's normal for those types of ID values to be used. I don't think it has anything to do with it asking for the .#1 file. I assume it's used that ID for a long time.

Does it ask for it with 2.97a ?

The c change would change the way it looks for the next file when it hits
the end to cover a condition. But It's possible that prompt problem is part
of that fix, clicking ok would then just continue as normal as your
experiencing.

It would help if you can send (or make available) the #0 file zipped up and
use the grab utility (at the ftp site ftp://www.terabyteunlimited.com) to
grab the first 64K of the associated .tbi file and send it along as well.
Send an email with the link to download otherwise email to get a link you
can upload to.

There is no data in the #0 file, it's just a hash.


"tas3086" wrote in message news:[email protected]...

It is now 08-08-2015, while yesterdays increment was successful, todays
increment experienced the same notice error but for yesterdays file:
"Insert media 2 containing file i:-\2015-08-07-0005-Win10(SSD64)-(I)-.#1"
Entering cancel, imagew reported the same error and then completed normally
with return code 0.
That file does not and has never existed. Why is it asking for it, and
stopping the automated backup?

One thing that I do notice that is odd, is that this win10 partition is the
third physical primary partition on the disk, yet it's partition address is
3@0x5E
All of my other primary partition numbers end in a single number 1,2,3,or 4.
Why is this one showing as 5E. 5 is normally an extended logical partition
whos numbers normally end in 0x###. Could this be a reason why things are
goofy?

I will see if I can recreate the problem with the a and c versions and get back to you later. In the meantime .....
I would be very happy to help. Could you give me an indication of which of the #0 files you would want, and which .tbi files to grab?
All #0 files together amount to 3.5 GB and compression does not help much. It might be better to send this stuff by DVD/Mail if you need a lot of files.
Let me know.

Here is a current directory listing of the chain that is having problems:

2015-08-02 12:29 AM 4,294,966,784 2015-08-02-0017-Win10(SSD64)-.1
2015-08-02 12:30 AM 995,931,136 2015-08-02-0017-Win10(SSD64)-.2
2015-08-02 12:30 AM 4,294,966,784 2015-08-02-0017-Win10(SSD64)-.TBI
2015-08-02 12:30 AM 154,986,808 2015-08-02-0017-Win10(SSD64)-.#0
2015-08-02 08:02 AM 154,986,808 2015-08-02-0800-Win10(SSD64)-(I)-.#0
2015-08-02 08:02 AM 479,232 2015-08-02-0800-Win10(SSD64)-(I)-.TBI
2015-08-04 12:13 AM 147,613,656 2015-08-04-0010-Win10(SSD64)-(I)-.#0
2015-08-04 12:13 AM 847,257,600 2015-08-04-0010-Win10(SSD64)-(I)-.TBI
2015-08-05 12:07 AM 147,607,288 2015-08-05-0005-Win10(SSD64)-(I)-.#0
2015-08-05 12:07 AM 2,818,048 2015-08-05-0005-Win10(SSD64)-(I)-.TBI
2015-08-06 06:59 AM 149,795,400 2015-08-06-0005-Win10(SSD64)-(I)-.#0
2015-08-06 06:59 AM 440,872,960 2015-08-06-0005-Win10(SSD64)-(I)-.TBI
2015-08-07 12:06 AM 16,916,480 2015-08-07-0005-Win10(SSD64)-(I)-.TBI
2015-08-07 12:06 AM 149,599,744 2015-08-07-0005-Win10(SSD64)-(I)-.#0
2015-08-08 10:15 AM 154,130,448 2015-08-08-0137-Win10(SSD64)-(I)-.#0
2015-08-08 10:15 AM 866,922,496 2015-08-08-0137-Win10(SSD64)-(I)-.TBI
2015-08-09 12:06 AM 154,130,448 2015-08-09-0005-Win10(SSD64)-(I)-.#0
2015-08-09 12:06 AM 380,928 2015-08-09-0005-Win10(SSD64)-(I)-.TBI

Just the one given you trouble:

2015-08-09 12:15 AM 422,035,528 2015-08-09-0011-Win7(SSD32)-(I)-.#0
2015-08-09 12:15 AM 461,094,912 2015-08-09-0011-Win7(SSD32)-(I)-.TBI

But after thinking about it more, I'm sure it was the change in 2.97c that
causes that prompt. It worked around another problem where it needs to look
for the next file, but while doing that there was some other logic removed
which would prevent what you're seeing. Need to add that logic back.




"tas3086" wrote in message news:[email protected]...

I would be very happy to help. Could you give me an indication of which of
the #0 files you would want, and which .tbi files to grab?
All #0 files together amount to 3.5 GB and compression does not help much.
It might be better to send this stuff by DVD/Mail if you need a lot of
files.
Let me know.

Here is a current directory listing of the chain that is having problems:

2015-08-01 02:47 AM 4,294,963,200 2015-08-01-0237-Win7(SSD32)-.1
2015-08-01 02:52 AM 4,294,963,200 2015-08-01-0237-Win7(SSD32)-.2
2015-08-01 02:57 AM 4,294,963,200 2015-08-01-0237-Win7(SSD32)-.3
2015-08-01 03:01 AM 4,294,963,200 2015-08-01-0237-Win7(SSD32)-.4
2015-08-01 03:05 AM 4,294,963,200 2015-08-01-0237-Win7(SSD32)-.5
2015-08-01 03:08 AM 421,228,696 2015-08-01-0237-Win7(SSD32)-.#0
2015-08-01 03:08 AM 3,400,409,088 2015-08-01-0237-Win7(SSD32)-.6
2015-08-01 03:08 AM 4,294,963,200 2015-08-01-0237-Win7(SSD32)-.TBI
2015-08-02 12:09 AM 412,468,968 2015-08-02-0005-Win7(SSD32)-(I)-.#0
2015-08-02 12:09 AM 521,469,952 2015-08-02-0005-Win7(SSD32)-(I)-.TBI
2015-08-03 04:47 PM 425,307,552 2015-08-03-1643-Win7(SSD32)-(I)-.#0
2015-08-03 04:47 PM 1,010,008,064 2015-08-03-1643-Win7(SSD32)-(I)-.TBI
2015-08-04 12:20 AM 428,744,840 2015-08-04-0017-Win7(SSD32)-(I)-.#0
2015-08-04 12:20 AM 393,490,432 2015-08-04-0017-Win7(SSD32)-(I)-.TBI
2015-08-05 12:16 AM 430,749,040 2015-08-05-0013-Win7(SSD32)-(I)-.#0
2015-08-05 12:16 AM 434,819,072 2015-08-05-0013-Win7(SSD32)-(I)-.TBI
2015-08-06 07:07 AM 418,228,176 2015-08-06-0703-Win7(SSD32)-(I)-.#0
2015-08-06 07:07 AM 380,518,400 2015-08-06-0703-Win7(SSD32)-(I)-.TBI
2015-08-07 12:14 AM 421,755,320 2015-08-07-0010-Win7(SSD32)-(I)-.#0
2015-08-07 12:14 AM 303,976,448 2015-08-07-0010-Win7(SSD32)-(I)-.TBI
2015-08-08 01:34 AM 417,506,856 2015-08-08-0130-Win7(SSD32)-(I)-.#0
2015-08-08 01:34 AM 380,424,192 2015-08-08-0130-Win7(SSD32)-(I)-.TBI
2015-08-09 12:15 AM 422,035,528 2015-08-09-0011-Win7(SSD32)-(I)-.#0
2015-08-09 12:15 AM 461,094,912 2015-08-09-0011-Win7(SSD32)-(I)-.TBI

I'm uploading both the 5th and the 7th set of files now to my server. Will take about 45 minutes.
How do I send you an email to give you instructions to retrieve?
(sorry the previous directory listing was in error, but has been corrected, and I understood what you wanted. )

Does not happen with the A version, but can be recreated with the c version.

Do you still need the files? They are still slowly uploading.

it be nice to have it. email support@


"tas3086" wrote in message news:[email protected]...

Does not happen with the A version, but can be recreated with the c version.

Do you still need the files? They are still slowly uploading.