TeraByte Unlimited

Versions older than 2.86 wouldn't be able to restore a .TBI file created by
2.86 or later (you'd get a message telling you the version required) unless
you backed up using the backwards compatible option.

??


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

I don't know the location of the grab utility to which you are referring,
can you specify?

Of note, I still had an old copy of IFW 2.83, so I reinstalled my version of
IFW to 2.83 and then ran imagew64 /recover and was able to now select the
image file for restore, then got the restore options screen, then asked to
confirm overwriting the destination, but then it fails with the error:
Image Stream is Corrupt. Please Reboot. Rebooted, but still get same Image
Stream is Corrupt Error. Also, it will not mount in TBView or TBMount while
under IFW 2.83.

Yes, I always and did in this case use the backwards compatibility option during backup. Since the /recover command is functioning in the older version and I am getting this Stream is Corrupt error, is that the end of the issue I will be unable to restore?

That is a strange option to have enabled?

But getting ISC message would be consistent with the backup not completing.
Perhaps you were thinking of a different image that said it was completed?
The description in the file doesn't mean that is the completion message
you're thinking about.

You'd have to create a partition that is the same location as the original
(you can look at properties to find it - starting lba is the most
important). Then you restore single partition over the top of it, at the
ISC message you do not answer it, instead,reboot the system. Whatever
point it was at before the system rebooted or powered off during the backup
is what data will be there (I presume the restore is taking a while or is it right away).
Some file names may appear but the data not there (depending on how far it was
backing up, If it's about the same size as the amount of data, then you probably
have just about everything there). How long ago was the Image created vs when
it was overwritten? What overwrote it? Depending on what it is, the data may
still be on the drive. What size is the .tbi file?

Are you in China? I noticed the posts are coming from various China servers
in different cities? Can you email support the following:

The system make/model you're using.
The first 64K of that .tbi file using the grab utility.
Include the name and email you used when purchasing the product.

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

Yes, I always and did in this case use the backwards compatibility option
during backup. Since the /recover command is functioning in the older
version and I am getting this Stream is Corrupt error, is that the end of
the issue I will be unable to restore?

I'll have to confirm if the newly re-created partition is as the same starting block or not. I get the Image Stream error immediately after telling it to begin the restore - no delay at all. I'm not confusing the backups as I did it all the same day and it's the first backup since the summer, so no mistakes here on that. The original source disk was used for another manual backup process, so the entire disk was overwritten with new data, so there is no recovery going to happen there - I simply did the backup, had no errors, it did the backup and said it was successful, so I "trusted" it as it were. The TBI is 398 GB. I'll consider retrying the restore with the 2.83 version of IFW via the bootdisk and in-Windows and do the reboot as you suggest, but I'm guessing that there will be nothing coming out of this backup file. It's unfortunate, but not critical, but it's a lot of data, that's why I'm trying to solve it if possible. Yes, I am in China, but I am American - I have lived in China for nearly 10 years - not from different cities, it's just the ridiculous internet - the companies route their logins through servers in other cities, so I may appear to be in one city then suddenly I'm 300 miles away the next time I get a new IP. China is hardly the ideal standard for anything.

If the ISC message is right away, it won't do any good. It's possible it is
related to the newer version creating it with that version of /recover.
You'll need to wait for the updated /recover option. If you send that first
64K of the file, it may be possible to try fixing it to the point of at
least work similar to /recover even though the progress bars will be way off
during the restore of that file (can still get ICS but would be farther
towards the end at whatever point the system restarted). Don't run chkdsk
/f on your drive until attempting to recover from it if there is an issue
with it, it may end up changing the file.

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

I'll have to confirm if the newly re-created partition is as the same
starting block or not. I get the Image Stream error immediately after
telling it to begin the restore - no delay at all. I'm not confusing the
backups as I did it all the same day and it's the first backup since the
summer, so no mistakes here on that. The original source disk was used for
another manual backup process, so the entire disk was overwritten with new
data, so there is no recovery going to happen there - I simply did the
backup, had no errors, it did the backup and said it was successful, so I
"trusted" it as it were. The TBI is 398 GB. I'll consider retrying the
restore with the 2.83 version of IFW via the bootdisk and in-Windows and do
the reboot as you suggest, but I'm guessing that there will be nothing
coming out of this backup file. It's unfortunate, but not critical, but
it's a lot of data, that's why I'm trying to solve it if possible. Yes, I
am in China, but I am American - I have lived in China for nearly 10 years -
not from different cities, it's just the ridiculous internet - the companies
route their logins through servers in other cities, so I may appear to be in
one city then suddenly I'm 300 miles away the next time I get a new IP.
China is hardly the ideal standard for anything.

Alright, here is the current status - VERY GOOD news, not perfect as would be most hoped, but great - and in advance, thank you very very much to TB support folks:

- I created the grab file from my TBI backup and e-mailed it to support and they e-mail back a modified version of the 2.93 IFW program
- I ran imagew64 /recover and chose my backup file that gave me issues
- The restore then proceeded nearly perfectly
- After 3 and 1/2 hours of IFW /recover restoration it then gave an error message that it asked for me to Insert Disk 2 of the backup with a file extension of .1 ... it was expecting a second part of the backup file - which doesn't exist of course
- I then chose to reboot instead of "cancel"
- This error/failure message came 3 1/2 hours into the restore with only 35 MB remaining to restore of the 379,837 MB (or so, I can't recall at the moment) .... so, it was nearly 100% finished when it failed.
- After rebooting, the disk/partition structure did not exist - there was no visible partition created in Windows or any other means
- I then used Undelete to evaluate the partition
- There was no partition information, but the data from the backup WAS WRITTEN to the disk ... so my files were rewritten to the disk
- I was able to use Undelete to recover the data from the disk that was written from the restore process to another location]

So, that is where it is - while of course I would have hoped that the restore would create the disk/partition information and leave me with a browsable-in-Windows disk structure - I have had to take the extra step of running data recovery on the restored data - then copy it to the disk I want it to be at (the restore location - to another backup disk - verify the data is real - the copy to the disk where I want it (the restore/recovered location).

In the end, the result is the same ............... the data was recovered/restored out of the TBI file to the disk I want - but was not visible except with data recovery tools -- I just had to to extra steps to actually get/see it

I'm sure that all makes sense to everyone.

I'm guessing that with the Data Written on Completion error and then the Stream Corrupt errors would suggest that there should be no surprise that the recovery with the modified IFW still fails ? Is that a fair assumption? Why it is asking for "disk 2" of the backup is unknown to me.

However, I can only give my deepest thanks to TB support - I don't know your name(s) but I can only say you are nearly a life saver - while the data is not life critical, it is extremely important data and personal - baby photos that can't be replaced and so on, as well as basic movies, music, data, etc. Nonetheless, it appears that I recovered 100% of the file at this point.

I'm happy to hear any other suggestions on doing a restore that completes with a partition structure or leaves me in way that I don't have to do this data recovery with recovery tools - to be sure that I haven't missed something in the recovery process.

The more perfect we can make it the better, but if you consider it closed, I can accept that. I have my data, as far as I can tell.

Again, pure and utter appreciation for your help and solution !! What you did and suggested worked, not error free, but as far as I can tell, I have my data.

I'm open to more ideas, but thrilled when I saw it all happen. Thank you again so much. I'm happy to provide any testimonials !!!!!!!

Happy New Year and thanks for saving me on this !!!!

That would be expected since it appears to not have completed - didn't find
the end of the data it was still looking for on top of the data written on
completion. So it was asking / looking for more data in the next file.
It's also expected there will be no partition created IF it needed more data
for that partition. Which is why it was mentioned to create a partition at
the same start location as the original (and should be the same size or
larger), then restore the partition over the top of it, then reboot on the
ISC or other message when it can't continue (the partition entry would be
there and be accessible since it existed prior). You could have used BIBM
or PartWork in IFL to undelete it if you restored to the same location as
well.

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

Alright, here is the current status - VERY GOOD news, not perfect as would
be most hoped, but great - and in advance, thank you very very much to TB
support folks:

- I created the grab file from my TBI backup and e-mailed it to support and
they e-mail back a modified version of the 2.93 IFW program
- I ran imagew64 /recover and chose my backup file that gave me issues
- The restore then proceeded nearly perfectly
- After 3 and 1/2 hours of IFW /recover restoration it then gave an error
message that it asked for me to Insert Disk 2 of the backup with a file
extension of .1 ... it was expecting a second part of the backup file -
which doesn't exist of course
- I then chose to reboot instead of "cancel"
- This error/failure message came 3 1/2 hours into the restore with only 35
MB remaining to restore of the 379,837 MB (or so, I can't recall at the
moment) .... so, it was nearly 100% finished when it failed.
- After rebooting, the disk/partition structure did not exist - there was no
visible partition created in Windows or any other means

Yeah, that's what I exected and appreciate your details. Of interest, for the hell of it, I did the following. I ran the restore process again with /recover and this time when it got to the same point of the error (35 MiB remaning) asking for a second disk, I clicked cancel to cancel the process - it gave me 2 or 3 more messages and then closed. Then, I used another tool to do a boot sector repair on the destination disk/partition and rebooted. And that did it - after rebooting Windows saw that partition AND ALL the data - I have confirmed for the most part that all my files are intact, usable, and in the proper directory structure.

Thanks again !!!!!!!

I'm curious if the future general public/retail release will include the changes you made to the executable for me.

it's in the next version.

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

I'm curious if the future general public/retail release will include the
changes you made to the executable for me.