Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.
When you got to Destination partition type did you select primary partition or a logical partition? Did you enable or disable "Resize drive to fill unallocated space?
Both selections were greyed-out so that I could not make a selection. Ghost created on the new drive a primary partition and the new partition was larger than the C: partition I was copying by 11MB.
Searching the Symantec Knowledge Base, I found the following document that might help:
http://service1.symantec.com/SUPPORT/powerquest.nsf/0/0426f8f401d3b928652574ab006c2119
Please let me know if this helps. Thanks!
I chose the Ghost options to run chkdsk on the source drive and the destination drive. So I don't need to run it separately, do I?
I ran chkdsk on each drive after Ghost failed, and my source drive was OK, but my destination drive was repaired.
I may run a low level format of the destination drive and attempt to run Ghost again. I'm busy, so it may take me a few days to get to this.
I reformatted the destination drive. And I ran the Ghost drive image attempt again. And you may not believe me, but it worked without errors this time 
And I still cannot explain why it did not work the first time.
I inspected the drives afterwards, and the destination drive had 0.5Gb fewer bytes used than the source drive. But I may assume that this is due to block size issues rather than to missing data. Let me know your opinions regarding this thought if you have comments to add to the thread.