Ghost Solution Suite

Hi
If I created an image with 3 partitions and cloned it from a 40 gig drive then restored it to a 20gig drive Ghost 7 would tell me the target drive may be too small but would let me proceed. This worked fine as I knew the image would fit as it mostly consisted of free space. Now if I do this with GSS 1.1 it just refuses to clone with an error message. Is there an answer to this?


cheers Gary

what is the partition size for each partition? also how much data is in each partition? I think it would be good to know filesystem you are using for these partitions as well.

HI Ethan
thanks for the reply. Your quite right I should have put some more detail. Partition 1 and 3 are about 17gb each and partition 2 is about 4gb. partition 1 and 2 are NTFS and partition 2 is unformatted. I know I should have reduced the partition size initially but this had never been a problem before we used GSS1.1




Cheers Gary

Thanks for that info; just out of curiosity is there an error number attached to the message you get? Any number associated with a message or error ties the message to a specific location in the source code that we can work back from.

Hi Nigel
The error code was "Error 40011 destination drive too small" at which point a clone initiated from console stops or a clone initiated from Ghost server with disk exits from Ghost on the client machine and returns to a dos prompt. When I used to do this with Ghost 7 it would say "the destination drive may be too small do you want to procede" I would say yes and it would work so long as the data did not exceed the available space.
Hope this helps

Cheers Gary

I had a chat with Rob Chester and Mark Gladding about this - they were actually having a conversation about some of the NTFS size-estimation code at the time, which was helpful. Anyway, the advice they suggested was that to stop Ghost actually bailing out, you could try the -ntexact switch with Ghost. That will disable a code path that is trying to be clever about some NTFS things, but which contains a separate size estimation check of its own that's a fatal error instead of a "do you want to proceed" warning like it should be.

One other possibility is trying with -or switch. This will turn off internal consistency checks which stopps you proceed. If there is an actual issue, it will fail at that time.

Hi
Thanks for your replies Nigel and Krishantha I shall give that a go and report back to you.

Cheers Gary