Restoring Issues, Destination Not Large Enough

User discussion and information resource forum for BootIt Bare Metal.

Restoring Issues, Destination Not Large Enough

Postby jimburns » Sat Jun 16, 2012 2:55 pm

Ok, what gives here. This is my first time working with BIBM and Image for DOS, but this is ridiculous for a GUI utility. I made the image with IFD of a Windows drive with a capacity of 400+Gb but of Data of only 37GB and try as I might each time I try to restore this to a, now repartitioned drive of 120G I receive "Destination is not Large Enough." I appreciate the apparent power of IFD but jeeeze, the GUI interface should at least be pretty much point and click for all but the most esoteric options.

What am I missing? I've broken down my girl's laptop and apparently can't put it back together.

Thanks,

/j
jimburns
 
Posts: 7
Joined: Fri Jun 15, 2012 11:05 am

Re: Restoring Issues, Destination Not Large Enough

Postby jimburns » Sat Jun 16, 2012 3:11 pm

Am I on drugs? Somebody is... the IFD manual is certainly not insync with the latest version, and I purchased the entire bundle.... I've made one image, then a single followup differential... the manual states if I pick a differential image to restore IFD will ask me to select the base image... NOPE! Never does...

Then, after picking my image file to "restore from" and other config choices, I get this confusing question,

[attachment=0]IMG_1138.jpg[/attachment]

So, what in the world is this? There is certainly nothing in IFD about this particular dialog.

Lost.

Help appreciated,

/j
Attachments
IMG_1138.jpg
Odd Question
IMG_1138.jpg (131.36 KiB) Viewed 3740 times
jimburns
 
Posts: 7
Joined: Fri Jun 15, 2012 11:05 am

Re: Restoring Issues, Destination Not Large Enough

Postby jimburns » Sat Jun 16, 2012 3:36 pm

So while the search function in these forums is braindead, searching with google did turn up a thread where support posted a link to, <http://www.terabyteunlimited.com/kb/article.php?id=554>

However, AGAIN, the instructions do not match reality.

When I select Backup in an attempt to get to the "compact" option for an EXISTING image... a weak and illogical interface choice at that, I can apparently go no further than the root of any drive selected. I have no problem drilling down a couple of directories to find my image file for a restore (that still doesn't work, mind you) but can't do the same to compact it?

This is turning into a nightmare....

Any clarity appreciated,

/j
jimburns
 
Posts: 7
Joined: Fri Jun 15, 2012 11:05 am

Re: Restoring Issues, Destination Not Large Enough

Postby TeraByte Support » Sat Jun 16, 2012 5:19 pm

see http://www.terabyteunlimited.com/kb/article.php?id=554


"jimburns" wrote in message news:2597@public.bootitbm...

Ok, what gives here. This is my first time working with BIBM and Image for
DOS, but this is ridiculous for a GUI utility. I made the image with IFD of
a Windows drive with a capacity of 400+Gb but of Data of only 37GB and try
as I might each time I try to restore this to a, now repartitioned drive of
120G I receive "Destination is not Large Enough." I appreciate the apparent
power of IFD but jeeeze, the GUI interface should at least be pretty much
point and click for all but the most esoteric options.

What am I missing? I've broken down my girl's laptop and apparently can't
put it back together.

Thanks,

/j

TeraByte Support
 
Posts: 2311
Joined: Thu May 05, 2011 3:37 pm

Re: Restoring Issues, Destination Not Large Enough

Postby TeraByte Support » Sat Jun 16, 2012 5:22 pm

Selecting an existing image isn't going to give you compact, you have to
compact the source, the data is already in the backup image.

You can drill down to image files if you like, just double click the
directory or highlight it and press enter.

"jimburns" wrote in message news:2599@public.bootitbm...

So while the search function in these forums is braindead, searching with
google did turn up a thread where support posted a link to,


However, AGAIN, the instructions do not match reality.

When I select Backup in an attempt to get to the "compact" option for an
EXISTING image... a weak and illogical interface choice at that, I can
apparently go no further than the root of any drive selected. I have no
problem drilling down a couple of directories to find my image file for a
restore (that still doesn't work, mind you) but can't do the same to compact
it?

This is turning into a nightmare....

Any clarity appreciated,

/j

TeraByte Support
 
Posts: 2311
Joined: Thu May 05, 2011 3:37 pm

Re: Restoring Issues, Destination Not Large Enough

Postby jimburns » Sat Jun 16, 2012 6:24 pm

Yes.. I've read <http://www.terabyteunlimited.com/kb/article.php?id=554>

But, given what I've learnt so far, intellect must consider this a software design bug. To wit, let's assume there is a reason to do a deep sector by sector image of a hard drive and to PURPOSELY maintain, shall we call it, the drives native fragmentation. That is, all freespace from the first data bit to the last are considered part of the image. LET'S ASSUME, there is a reason to do this.

The question then becomes, should the default operation of the software do this, or should it instead, always compact the REAL data only such that users can always restore their images to any drive or partition large enough to hold the restored data. The questions is, what percentage of users think of their 500Gb windows drive or partition as encompassing 256G because of the way IFD looks at it by default, compared to those that look at it as encompassing 37GB because that's the size of the REAL data, regardless of how it's spread across the disk.

I could be wrong, I'm still just getting up to speed on BIBM and IFD... and I've not even tried IFW yet. I'm coming over from years of using Ghost 2001, and 2003 which always came down on this question the intelligent way. But, if I'm reading this correctly, and I have to remember to "compact" my images so I don't have 256G images but 37G images, then this is a software design bug as their is NO intelligent reason for the default action of the software to be as it is. The default action should be as Ghost, to always compact, and for the, I'd bet almost negligible, percentage of users who would see value in retaining an image of 256G, this should be a switchable option.

I'm disappointed.

/j
jimburns
 
Posts: 7
Joined: Fri Jun 15, 2012 11:05 am

Re: Restoring Issues, Destination Not Large Enough

Postby Brian K » Sat Jun 16, 2012 8:14 pm

jimburns wrote:
> as their is NO intelligent reason for the default action of the software to be as
> it is. The default action should be as Ghost, to always compact, and for the, I'd
> bet almost negligible, percentage of users who would see value in retaining an image
> of 256G, this should be a switchable option.

jimburns,

That's how we like it. We want the restored sectors to be in the same relative position as the original partition. Performance reasons.
Brian K
 
Posts: 1174
Joined: Thu Aug 11, 2011 6:11 pm

Re: Restoring Issues, Destination Not Large Enough

Postby mjnelson99 » Sun Jun 17, 2012 7:47 am

I attempted to do a restore on my laptop to the exact SAME
partition either the same day or the next. The image was
created with IFW and I was using IFL from a SD card to restore.

It came up 8 MB TOO large for the restore to go through.
Fortunately, at that point I still had the infamous 100 MB
partition present. I resized that down enough so I got my 8
MB necessary for the restore.

Still don't know why this was possible in a matter of only a
day or two on the same sized partition that was imaged.

That had not happened previously over a period of about 5
years of using TBI products. Needless to say, it was a shock
when it did happen.

I can't help but wonder if doing a defrag before an image is
created would move data that is near the end of the
partition up closer to the front so it is not spread all
over the place.
Mary

On 6/16/2012 10:14 PM, Brian K wrote:
> jimburns wrote:
>> as their is NO intelligent reason for the default action of the software to be as
>> it is. The default action should be as Ghost, to always compact, and for the, I'd
>> bet almost negligible, percentage of users who would see value in retaining an image
>> of 256G, this should be a switchable option.
>
> jimburns,
>
> That's how we like it. We want the restored sectors to be in the same

relative position as the original partition. Performance
reasons.
>
>

mjnelson99
 
Posts: 766
Joined: Thu Aug 11, 2011 6:24 pm

Re: Restoring Issues, Destination Not Large Enough

Postby DrTeeth » Sun Jun 17, 2012 8:28 am

On Sun, 17 Jun 2012 07:47:18 PDT, just as I was about to take a herb,
mjnelson99 disturbed my reverie and wrote:

>Still don't know why this was possible in a matter of only a
>day or two on the same sized partition that was imaged.

Even if one did not conciously change data on the partition, it could
be down to the plethora of temporary files written to disk...it only
takes 1 in the 'wrong' place. I'm surprised that it hasn't happened
more often TBH.
--

Cheers

DrT
______________________________
We may not be able to prevent the stormy times in
our lives; but we can always choose to dance
in the puddles (Jewish proverb).
DrTeeth
 
Posts: 970
Joined: Fri Aug 12, 2011 11:58 am

Re: Restoring Issues, Destination Not Large Enough

Postby TeraByte Support » Sun Jun 17, 2012 9:30 am

That would have to do with your alignment options.

"mjnelson99" wrote in message news:2609@public.bootitbm...

I attempted to do a restore on my laptop to the exact SAME
partition either the same day or the next. The image was
created with IFW and I was using IFL from a SD card to restore.

It came up 8 MB TOO large for the restore to go through.
Fortunately, at that point I still had the infamous 100 MB
partition present. I resized that down enough so I got my 8
MB necessary for the restore.

Still don't know why this was possible in a matter of only a
day or two on the same sized partition that was imaged.

That had not happened previously over a period of about 5
years of using TBI products. Needless to say, it was a shock
when it did happen.

I can't help but wonder if doing a defrag before an image is
created would move data that is near the end of the
partition up closer to the front so it is not spread all
over the place.
Mary

On 6/16/2012 10:14 PM, Brian K wrote:
> jimburns wrote:
>> as their is NO intelligent reason for the default action of the
>> software to be as
>> it is. The default action should be as Ghost, to always compact, and
>> for the, I'd
>> bet almost negligible, percentage of users who would see value in
>> retaining an image
>> of 256G, this should be a switchable option.
>
> jimburns,
>
> That's how we like it. We want the restored sectors to be in the same

relative position as the original partition. Performance
reasons.
>
>

TeraByte Support
 
Posts: 2311
Joined: Thu May 05, 2011 3:37 pm

Next

Return to BootIt Bare Metal