UPDATE on TEST 2
We have completed a successful redeployment of the newly captured image to a new drive in the original machine. All boots ok and so far nothing untoward has been discovered. Looking at the d1.partitions file shows continuous use of the space.
So, the original problem (prompting the question about deployment logs) whereby the source disk of the image capture was left with unused disk space, was likely caused by a failure of the capture process to resize the partition after shrinking. A subsequent capture of the same disk resulted in the “unexpected” partitioning scheme when the image was redeployed.
I will mark this problem as resolved.
Thanks for your time.
PaulG