TeraByte Unlimited

See error 80 log report below:
It should be noted that there were no errors in the backup or validation on 11/30, no errors on the weekly iterative backups and validations during the month of December, and no errors reported when a validation is done on the 12/28 last iteration. And no error when I do a manual validation of the 12/28 file. Yet, an error occurs when I try to consolidate the base and all the iterations back together. This same error happened on another partition as well (error2). This has process has worked without problem since combine operation was introduced, and it is my first combine since installing IFD 2.86. Any ideas of suggestions?

I am concerned that all verify and validate operations all completed without error, yet now the combine shows an error. A Manual validation after the error showed no error.
Chkdsk /f on partition d3@0x2 shows no errors.
Combine operations were run again and same error occurred.
If I needed to do a restore, would it have worked?

--------------------------------------------------error1 ------------------------
[ 1/01/2014 7:45:17 am] C:\.\IMAGE.EXE /ue /combine /base:d3@0x2:\2013-12-28-2010-F_DRIVE-(I)-.TBI /f:d3@0x2:\2013-12-28-9999-F_DRIVE-
[ 1/01/2014 7:45:19 am] Image for DOS 2.86
[ 1/01/2014 7:45:19 am] Starting ...
[ 1/01/2014 7:45:21 am] Processing: F_DRIVE Volume (31B) 102407 MiB FAT-32
[ 1/01/2014 7:45:21 am] From: b3@0x2:\2013-12-28-2010-F_DRIVE-(I)-.TBI
[ 1/01/2014 7:45:21 am] To: b3@0x2:\2013-12-28-9999-F_DRIVE-.TBI
[ 1/01/2014 9:04:04 am] Error 80 occured while processing file \2013-11-30-9999-F_DRIVE-.14
[ 1/01/2014 9:04:04 am] INFO: Total Sectors:209728512 Total Allocated:166429144
[ 1/01/2014 9:04:04 am] Deleting incomplete or failed backup.
[ 1/01/2014 9:04:05 am] Deleting \2013-12-28-9999-F_DRIVE-.#0
[ 1/01/2014 9:04:05 am] Deleting \2013-12-28-9999-F_DRIVE-.1
[ 1/01/2014 9:04:05 am] Deleting \2013-12-28-9999-F_DRIVE-.10
[ 1/01/2014 9:04:05 am] Deleting \2013-12-28-9999-F_DRIVE-.11
[ 1/01/2014 9:04:05 am] Deleting \2013-12-28-9999-F_DRIVE-.12
[ 1/01/2014 9:04:05 am] Deleting \2013-12-28-9999-F_DRIVE-.13
[ 1/01/2014 9:04:05 am] Deleting \2013-12-28-9999-F_DRIVE-.2
[ 1/01/2014 9:04:06 am] Deleting \2013-12-28-9999-F_DRIVE-.3
[ 1/01/2014 9:04:06 am] Deleting \2013-12-28-9999-F_DRIVE-.4
[ 1/01/2014 9:04:06 am] Deleting \2013-12-28-9999-F_DRIVE-.5
[ 1/01/2014 9:04:06 am] Deleting \2013-12-28-9999-F_DRIVE-.6
[ 1/01/2014 9:04:06 am] Deleting \2013-12-28-9999-F_DRIVE-.7
[ 1/01/2014 9:04:06 am] Deleting \2013-12-28-9999-F_DRIVE-.8
[ 1/01/2014 9:04:06 am] Deleting \2013-12-28-9999-F_DRIVE-.9
[ 1/01/2014 9:04:07 am] Deleting \2013-12-28-9999-F_DRIVE-.TBI
[ 1/01/2014 9:04:07 am] Operation Completed with Error Code 80
[ 1/01/2014 9:04:07 am] The image stream is corrupt. Please reboot!
[ 1/01/2014 10:05:21 am] Stop
-------------------------------------------error2-------------------------------
[ 1/01/2014 7:23:57 am] C:\.\IMAGE.EXE /ue /combine /base:d3@0x2:\2013-12-28-0742-Win7(SSD32)-(I)-.TBI /f:d3@0x2:\2013-12-28-9999-Win7(SSD32)-
[ 1/01/2014 7:23:58 am] Image for DOS 2.86
[ 1/01/2014 7:23:58 am] Starting ...
[ 1/01/2014 7:24:00 am] Processing: Win7(SSD32) Partition (01) 60000 MiB Hidden HPFS/NTFS
[ 1/01/2014 7:24:00 am] From: b3@0x2:\2013-12-28-0742-Win7(SSD32)-(I)-.TBI
[ 1/01/2014 7:24:00 am] To: b3@0x2:\2013-12-28-9999-Win7(SSD32)-.TBI
[ 1/01/2014 7:26:40 am] Error 80 occured while processing file \2013-12-21-0246-Win7(SSD32)-(I)-.TBI
[ 1/01/2014 7:26:40 am] INFO: Total Sectors:122880384 Total Allocated:99353424
[ 1/01/2014 7:26:40 am] Deleting incomplete or failed backup.
[ 1/01/2014 7:26:40 am] Deleting \2013-12-28-9999-Win7(SSD32)-.#0
[ 1/01/2014 7:26:40 am] Deleting \2013-12-28-9999-Win7(SSD32)-.TBI
[ 1/01/2014 7:26:40 am] Operation Completed with Error Code 80
[ 1/01/2014 7:26:40 am] The image stream is corrupt. Please reboot!
[ 1/01/2014 7:27:06 am] Stop

Have you tried it from Windows or Linux?

Did you use Enhanced Size A, B or C compression in any of them?

Are some from prior versions?


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

See error 80 log report below:
It should be noted that there were no errors in the backup or validation on
11/30, no errors on the weekly iterative backups and validations during the
month of December, and no errors reported when a validation is done on the
12/28 last iteration. And no error when I do a manual validation of the
12/28 file. Yet, an error occurs when I try to consolidate the base and
all the iterations back together. This same error happened on another
partition as well (error2). This has process has worked without problem
since combine operation was introduced, and it is my first combine since
installing IFD 2.86. Any ideas of suggestions?

I am concerned that all verify and validate operations all completed without
error, yet now the combine shows an error. A Manual validation after the
error showed no error.
Chkdsk /f on partition d3@0x2 shows no errors.
Combine operations were run again and same error occurred.
If I needed to do a restore, would it have worked?

--------------------------------------------------error1 ------------------------
[ 1/01/2014 7:45:17 am] C:\.\IMAGE.EXE /ue /combine
/base:d3@0x2:\2013-12-28-2010-F_DRIVE-(I)-.TBI
/f:d3@0x2:\2013-12-28-9999-F_DRIVE-
[ 1/01/2014 7:45:19 am] Image for DOS 2.86
[ 1/01/2014 7:45:19 am] Starting ...
[ 1/01/2014 7:45:21 am] Processing: F_DRIVE Volume (31B) 102407 MiB FAT-32
[ 1/01/2014 7:45:21 am] From: b3@0x2:\2013-12-28-2010-F_DRIVE-(I)-.TBI
[ 1/01/2014 7:45:21 am] To: b3@0x2:\2013-12-28-9999-F_DRIVE-.TBI
[ 1/01/2014 9:04:04 am] Error 80 occured while processing file
\2013-11-30-9999-F_DRIVE-.14
[ 1/01/2014 9:04:04 am] INFO: Total Sectors:209728512 Total
Allocated:166429144
[ 1/01/2014 9:04:04 am] Deleting incomplete or failed backup.
[ 1/01/2014 9:04:05 am] Deleting \2013-12-28-9999-F_DRIVE-.#0
[ 1/01/2014 9:04:05 am] Deleting \2013-12-28-9999-F_DRIVE-.1
[ 1/01/2014 9:04:05 am] Deleting \2013-12-28-9999-F_DRIVE-.10
[ 1/01/2014 9:04:05 am] Deleting \2013-12-28-9999-F_DRIVE-.11
[ 1/01/2014 9:04:05 am] Deleting \2013-12-28-9999-F_DRIVE-.12
[ 1/01/2014 9:04:05 am] Deleting \2013-12-28-9999-F_DRIVE-.13
[ 1/01/2014 9:04:05 am] Deleting \2013-12-28-9999-F_DRIVE-.2
[ 1/01/2014 9:04:06 am] Deleting \2013-12-28-9999-F_DRIVE-.3
[ 1/01/2014 9:04:06 am] Deleting \2013-12-28-9999-F_DRIVE-.4
[ 1/01/2014 9:04:06 am] Deleting \2013-12-28-9999-F_DRIVE-.5
[ 1/01/2014 9:04:06 am] Deleting \2013-12-28-9999-F_DRIVE-.6
[ 1/01/2014 9:04:06 am] Deleting \2013-12-28-9999-F_DRIVE-.7
[ 1/01/2014 9:04:06 am] Deleting \2013-12-28-9999-F_DRIVE-.8
[ 1/01/2014 9:04:06 am] Deleting \2013-12-28-9999-F_DRIVE-.9
[ 1/01/2014 9:04:07 am] Deleting \2013-12-28-9999-F_DRIVE-.TBI
[ 1/01/2014 9:04:07 am] Operation Completed with Error Code 80
[ 1/01/2014 9:04:07 am] The image stream is corrupt. Please reboot!
[ 1/01/2014 10:05:21 am] Stop
-------------------------------------------error2-------------------------------
[ 1/01/2014 7:23:57 am] C:\.\IMAGE.EXE /ue /combine
/base:d3@0x2:\2013-12-28-0742-Win7(SSD32)-(I)-.TBI
/f:d3@0x2:\2013-12-28-9999-Win7(SSD32)-
[ 1/01/2014 7:23:58 am] Image for DOS 2.86
[ 1/01/2014 7:23:58 am] Starting ...
[ 1/01/2014 7:24:00 am] Processing: Win7(SSD32) Partition (01) 60000 MiB
Hidden HPFS/NTFS
[ 1/01/2014 7:24:00 am] From: b3@0x2:\2013-12-28-0742-Win7(SSD32)-(I)-.TBI
[ 1/01/2014 7:24:00 am] To: b3@0x2:\2013-12-28-9999-Win7(SSD32)-.TBI
[ 1/01/2014 7:26:40 am] Error 80 occured while processing file
\2013-12-21-0246-Win7(SSD32)-(I)-.TBI
[ 1/01/2014 7:26:40 am] INFO: Total Sectors:122880384 Total
Allocated:99353424
[ 1/01/2014 7:26:40 am] Deleting incomplete or failed backup.
[ 1/01/2014 7:26:40 am] Deleting \2013-12-28-9999-Win7(SSD32)-.#0
[ 1/01/2014 7:26:40 am] Deleting \2013-12-28-9999-Win7(SSD32)-.TBI
[ 1/01/2014 7:26:40 am] Operation Completed with Error Code 80
[ 1/01/2014 7:26:40 am] The image stream is corrupt. Please reboot!
[ 1/01/2014 7:27:06 am] Stop

All base and iterations were compressed using level : 13

The end of November base was created by a COMBINE of weekly iterations made in November, and Octobers Base.
The end of December base that failed to be created was a COMBINE of the November base and weekly iteration items in December.

I update my software as soon as your releases come out, so Novembers batch would have been made up of 3 of your releases (2.83,2.84, and 2.85), and the December batch was mostly 2.85 with the last iterative update being done under 2.86, and the COMBINE failed with error code 80 while running 2.86.

(iterations are run on Saturday , and the COMBINES, creating a new monthly base, are run on the 1st of each month ( with a name of the last iteration).

It should be noted that there are 8 partitions that go through this process during the backup cycle, only 2 of them failed with the same 80 error.

Just to be sure, I started the new year with a complete new base build of all my partitions.

Let me know if you need any more documentation, or if I can help in any way.

what's in your environment variable? (re: /ue) ?

Have you tried in IFL or IFW ?


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

All base and iterations were compressed using level : 13

The end of November base was created by a COMBINE of weekly iterations made
in November, and Octobers Base.
The end of December base that failed to be created was a COMBINE of the
November base and weekly iteration items in December.

I update my software as soon as your releases come out, so Novembers batch
would have been made up of 3 of your releases (2.83,2.84, and 2.85), and the
December batch was mostly 2.85 with the last iterative update being done
under 2.86, and the COMBINE failed with error code 80 while running 2.86.

(iterations are run on Saturday , and the COMBINES, creating a new monthly
base, are run on the 1st of each month ( with a name of the last iteration).

It should be noted that there are 8 partitions that go through this process
during the backup cycle, only 2 of them failed with the same 80 error.

Just to be sure, I started the new year with a complete new base build of
all my partitions.

Let me know if you need any more documentation, or if I can help in any way.

DOS Environmental:
;u;hash;comp:13;max:4GiB;logl:3;logmode:1000000;logfile:\IFD.LOG;sch:3@0x2:"\;v

I have tried IFL and IFW. Both work with my script.
I prefer IFD, as it runs nicely under bootitBM. I do not trust creating a backup under IFW, while IFW is active, and you need to use IFD anyway for restore. IFL is nice because it adds networking capability, but I do not need that just yet.

A windows timer event wakes up my system, runs bootnow to run a bootitbm selection item script, invokes a backup script, and bootndos to get back to bootitBM and start the windows partition again. I could do the same totally within windows, but not knowing the windows state when the run is done, makes me hesitant.

if you could email a link to download the files - I can see if it will
reproduce here...

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

;u;hash;comp:13;max:4GiB;logl:3;logmode:1000000;logfile:\IFD.LOG;sch:3@0x2:"\;v

How about logl: 9 or 10, would that help?

tas3086 wrote:
> I do not trust creating a
> backup under IFW, while IFW is active,

tas3086, why not? I think most of us create hot images with IFW. I've never had a hot image issue and I don't know anyone who has either.



>and you need to use IFD anyway for
> restore.

Not really. You can use IFW offline to restore. And you can use IFW offline to create images if you can't bring yourself to create hot images.

I have a great deal of confidence in backing/restoring any operating system disk that is not operating, and less confidence in doing the same to a system that changing under my feet as it is backed up.

In addition, on my hardware, Windows/BootitBM has the nasty habit of changing disk hardware mapping and id numbers. This makes doing a restore from non-windows real mode bios based environment, a little more difficult. Backing/restoring from the same environment adds some consistency.

That is a great part of BootitBM, as it adds not only a multi-boot selection capability, but it is also its own OS that can run independently with a good and very simple scripting language.

But let's take this discussion to another thread as I'd rather spend time here trying to isolate my Error Code 80 problem.

So TERABYTE: How about logl: 9 or 10, would that help?

tas3086 wrote:
> In addition, on my hardware, Windows/BootitBM has the nasty habit of
> changing disk hardware mapping and id numbers.

That happens in one of my computers too. You can get around this issue by using Disk Signatures instead of drive numbers in your scripts. See page 111 in the IFD manual.