The image stream is corrupt. Please reboot!

User discussion and information resource forum for Image products.
Post Reply
rseiler
Posts: 70
Joined: Sat May 05, 2012 10:29 pm

The image stream is corrupt. Please reboot!

Post by rseiler »

I did find a KB about this here:
http://www.terabyteunlimited.com/kb/article.php?id=350

It's happened two days in a row here for the backup of a system volume (haven't been able to reboot yet), but interestingly, IFW is still working for the backup of a data volume. The KB says "Such an error message indicates that a problem occurred somewhere between the system memory and the target drive," but if that's the case, how can it be that the backup of the data volume isn't throwing the same error--in all cases, I'm using the same target drive? Also, there's a very long history of backups on this system, and this is the first week this error has ever happened.

Anyway, I'll reboot, and also upgrade from 2.75 to 2.76 (maybe one of the "misc" fixes was this?).

[11/08/2012 5:15:16 am] PHYLock is waiting for drive writing to stop ...
[11/08/2012 5:16:07 am] PHYLock using drive C:
[11/08/2012 5:16:10 am] PHYLock Started
[11/08/2012 5:16:10 am] PHYLock Using Disk
[11/08/2012 5:16:10 am] PHYLock version 9
[11/08/2012 5:18:14 am] Deleting incomplete or failed backup.
...
[11/08/2012 5:18:14 am] Operation Completed with Error Code 94
[11/08/2012 5:18:14 am] The image stream is corrupt. Please reboot!
[11/08/2012 5:18:14 am] Stop
TeraByte Support
Posts: 3598
Joined: Thu May 05, 2011 10:37 pm

Re: The image stream is corrupt. Please reboot!

Post by TeraByte Support »

if you're doing a differential, it can be the base file.

in general, you can't predict what's going to happen with bad/flakey memory
or hardware.

"rseiler" wrote in message news:3718@public.image...

I did find a KB about this here:

[
http://www.terabyteunlimited.com/kb/article.php?id=350
](http://www.terabyteunlimited.com/kb/article.php?id=350)

It's happened two days in a row here for the backup of a system volume
(haven't been able to reboot yet), but interestingly, IFW is still working
for the backup of a data volume. The KB says "Such an error message
indicates that a problem occurred somewhere between the system memory and
the target drive," but if that's the case, how can it be that the backup of
the data volume isn't throwing the same error--in all cases, I'm using the
same target drive? Also, there's a very long history of backups on this
system, and this is the first week this error has ever happened.

Anyway, I'll reboot, and also upgrade from 2.75 to 2.76 (maybe one of the
"misc" fixes was this?).

[11/08/2012 5:15:16 am] PHYLock is waiting for drive writing to stop ...
[11/08/2012 5:16:07 am] PHYLock using drive C:
[11/08/2012 5:16:10 am] PHYLock Started
[11/08/2012 5:16:10 am] PHYLock Using Disk
[11/08/2012 5:16:10 am] PHYLock version 9
[11/08/2012 5:18:14 am] Deleting incomplete or failed backup.
....
[11/08/2012 5:18:14 am] Operation Completed with Error Code 94
[11/08/2012 5:18:14 am] The image stream is corrupt. Please reboot!
[11/08/2012 5:18:14 am] Stop

rseiler
Posts: 70
Joined: Sat May 05, 2012 10:29 pm

Re: The image stream is corrupt. Please reboot!

Post by rseiler »

TeraByte Support wrote:
> if you're doing a differential, it can be the base file.
>
> in general, you can't predict what's going to happen with bad/flakey memory or hardware.

Yes, it was a differential, and I had created a new full backup last weekend, but the day before the first failure I had made a successful differential, so I don't know how it could be the base file. Plus, since upgrading to 2.76 and rebooting, I've made another against the same base file.

If it was a hardware issue, then I'm still confused why the second backup never showed the problem. It's the same machine (i.e. same memory), same source drive (just a different partition), and the exact same destination.

The only anomaly that I noticed on the C partition (i.e. the partition in question) was a fairly common "discovered free space marked as allocated" message seen with chkdsk, so I scheduled that be fixed with the reboot.
DrTeeth
Posts: 1289
Joined: Fri Aug 12, 2011 6:58 pm

Re: The image stream is corrupt. Please reboot!

Post by DrTeeth »

On Sat, 10 Nov 2012 08:05:59 PST, just as I was about to take a herb,
rseiler disturbed my reverie and wrote:

>If it was a hardware issue, then I'm still confused why the second backup never showed the problem.
That's bloody computers for you, they mess with your brain until you
doubt your own sanity. Don't get me started on SATA connections .
--

Cheers

DrT
______________________________
We may not be able to prevent the stormy times in
our lives; but we can always choose whether or not
to dance in the puddles (Jewish proverb).
TeraByte Support
Posts: 3598
Joined: Thu May 05, 2011 10:37 pm

Re: The image stream is corrupt. Please reboot!

Post by TeraByte Support »

run a validation on the base file.

"rseiler" wrote in message news:3730@public.image...

TeraByte Support wrote:
> if you're doing a differential, it can be the base file.
>
> in general, you can't predict what's going to happen with bad/flakey
> memory or hardware.

Yes, it was a differential, and I had created a new full backup last
weekend, but the day before the first failure I had made a successful
differential, so I don't know how it could be the base file. Plus, since
upgrading to 2.76 and rebooting, I've made another against the same base
file.

If it was a hardware issue, then I'm still confused why the second backup
never showed the problem. It's the same machine (i.e. same memory), same
source drive (just a different partition), and the exact same destination.

The only anomaly that I noticed on the C partition (i.e. the partition in
question) was a fairly common "discovered free space marked as allocated"
message seen with chkdsk, so I scheduled that be fixed with the reboot.

rseiler
Posts: 70
Joined: Sat May 05, 2012 10:29 pm

Re: The image stream is corrupt. Please reboot!

Post by rseiler »

I didn't get notice of your post, or I would have, though when it was created a validation was done.

Unfortunately, it's too late now! In what may or may not be a coincidence, the target drive died late last week, but IFW had been working perfectly for several days since the reboot and against the same base file.

There was a power event of some sort, and the UPS shut the system down. When it came back up, the drive was dead. Sounds normal, spins, no sign of a problem on either site of the circuit board, but this 3.5 year-old 1TB WD Green drive died.

Was IFW some kind of early warning? I guess we'll never know.

TeraByte Support wrote:
> run a validation on the base file.
>
> "rseiler" wrote in message news:3730@public.image...
>
> TeraByte Support wrote:
> > if you're doing a differential, it can be the base file.
> >
> > in general, you can't predict what's going to happen with bad/flakey
> > memory or hardware.
>
> Yes, it was a differential, and I had created a new full backup last
> weekend, but the day before the first failure I had made a successful
> differential, so I don't know how it could be the base file. Plus, since
> upgrading to 2.76 and rebooting, I've made another against the same base
> file.
>
> If it was a hardware issue, then I'm still confused why the second backup
> never showed the problem. It's the same machine (i.e. same memory), same
> source drive (just a different partition), and the exact same destination.
>
> The only anomaly that I noticed on the C partition (i.e. the partition in
> question) was a fairly common "discovered free space marked as allocated"
> message seen with chkdsk, so I scheduled that be fixed with the reboot.
Post Reply