Page 1 of 1

Problem w/v3.03

Posted: Thu Oct 20, 2016 8:12 am
by tbifan39
There may be a problem with IFL GUI v3.03. I made an image of my C drive and then attempted to restore it. The backup went fine. The Restore, however, deleted ALL partitions; except the C drive. The PC would not boot. I assume this was because the EFI partation was deleted. The D drive had some of my image backups that also got lost. Fortunately, I have some older images on a separate drive, Including an image of the entire drive I made when I purchased the system. This allowed my to recover the partitions and my drive makeup.

I then tried to restore just the C drive from an older, but more recent image. It too deleted the partitions. This image was made from an older version of IFL (2.99-00?). This tells me that it was not the backup process that is the problem.

I reverted back to v2.99-00 and restored from the image of the entire drive and then restored from an image of just the C drive. It worked. I am now in the process of reinstalling program that were not in the image and updating Windows and other programs...a lot of work. I will be sticking with v2,99-00 for the foreseeable future. I used automatic during the restore process every time and I used default options for the backups. It is the same process I have always used. I have changed nothing except the version of IFL GUI. Btw, I used the 32 bit no net version. I have disabled Fast Startup...it has been disabled from the beginning. I did get an error message and the end of the restore with 3.03. I don't remember what it said...something about reduction failed, I think? I hope this is enough info to help you track down the problem. I did approx. a year of browsing history and bookmarks. I will be keeping extra copies of my images on a separate drive from now on.

My system is running Windows 10 Pro 64bit with Anniversary Update.

Re: Problem w/v3.03

Posted: Thu Oct 20, 2016 5:45 pm
by TeraByte Support
yes there is, it's if doing auto restore for a single item, it will set the
starting lba to 0 (because of a typo on the variable name).

Don't use auto restore for single item on 3.03. We'll have a fix soonest.

"tbifan39" wrote in message news:12708@public.image...

There may be a problem with IFL GUI v3.03. I made an image of my C drive and
then attempted to restore it.

Re: Problem w/v3.03

Posted: Thu Oct 20, 2016 8:03 pm
by TeraByte Support
3.03a is out to correct that.

"tbifan39" wrote in message news:12708@public.image...

There may be a problem with IFL GUI v3.03. I made an image of my C drive and
then attempted to restore it. The backup went fine. The Restore, however,


Re: Problem w/v3.03

Posted: Fri Oct 21, 2016 8:07 am
by tbifan39
TeraByte Support wrote:
> yes there is, it's if doing auto restore for a single item, it will set the starting lba to 0 (because of a typo on the variable name).

> Don't use auto restore for single item on 3.03. We'll have a fix soonest.

Glad you found the bug and fixed it...too bad we were not told about the bug before we used it. Need to test your software more thoroughly before releasing it. I will stick with 2,99-00 for now. I can't afford to have that happen to me again. Too much work to reinstall everything.

Re: Problem w/v3.03

Posted: Fri Oct 21, 2016 8:33 am
by Brian K
tbifan39 wrote:
. Too much
> work to reinstall everything.

tbifan39,

I'm confused. Why would you reinstall everything when you had a backup you could have restored without using the Auto choice?

Re: Problem w/v3.03

Posted: Fri Oct 21, 2016 3:13 pm
by tas3086
I agree with tbifan39. If a backup completes, and validates, then the demand is that the restore should work. If a restore fails, then the reliability of the total process is in jeopardy. All hell breaks loose to correct the problem. Thankfully Terabyte came out with an immediate fix. Other companies would have taken months, and not admitted the problem. Overall reliability however, is still diminished.

I might suggest that quality control was lacking here, but there is a way to improve. Some of us would probably volunteer to test pre-release, beta versions of the programs. While this might not spot all problems, it would not hurt, and may actually help spot a problem before it is catastrophic for others.

Re: Problem w/v3.03

Posted: Sat Oct 22, 2016 2:41 am
by tbifan39
> tbifan39,
>
> I'm confused. Why would you reinstall everything when you had a backup you could have
> restored without using the Auto choice?

Brian K,

The only images I had after 3.03 deleted the partitions were an image of the entire drive (made 2 yrs ago) and an image of the C drive (made a year ago) on a separate drive.. I restore those images and then had to reinstall programs that were not in the image. I also had to uninstall programs I no longer used. I then had to update programs to their current version. I also had to reinstall the Anniversary Update for Windows 10, which too a long while.

Re: Problem w/v3.03

Posted: Sat Oct 22, 2016 2:51 am
by Brian K
tbifan39,

I understand. As I make a backup image daily I was slow to appreciate your images were old. But wait, you made an image of your C: drive with 3.03. You can still restore this image as long as you don't use the Auto choice. I've run tests since I saw your post and a manual restore or a command line restore is fine. As you have discovered, using Auto wasn't fine.

Edit... If you haven't overwritten the data partition you should be able to undelete it.

Re: Problem w/v3.03

Posted: Sat Oct 22, 2016 7:35 pm
by Bob Coleman
Brian K wrote:
> tbifan39,
>
> I understand. As I make a backup image daily I was slow to appreciate your
> images were old. But wait, you made an image of your C: drive with 3.03.
> You can still restore this image as long as you don't use the Auto choice.
> I've run tests since I saw your post and a manual restore or a command line
> restore is fine. As you have discovered, using Auto wasn't fine.
>
> Edit... If you haven't overwritten the data partition you should be able to
> undelete it.

I'm not sure, but I think perhaps the image of C: effectively destroyed itself during an attempt to restore it with Auto when the bug was present.

Re: Problem w/v3.03

Posted: Sat Oct 22, 2016 9:04 pm
by Brian K
Bob,

I did this test on a UEFI system with these partitions...

Recovery
ESP
MSR
Win10
Data

The first 4 partitions were imaged with IFW 3.03. The Win10 image was restored using the Automatic choice with IFL 3.03. Part Work showed Win10 as the only partition on the drive. Start LBA 0. The Drive was VOL Partitions.

Change Disk Type, Yes. The Win10 partition was gone. The image of the first 4 partitions was restored to Free Space using the Normal method with IFL 3.03 (not Automatic). Using Part Work, the Data partition was Undeleted.

Win10 booted and the Data partition was present. All back to the original configuration.