Hi! The source drive with the shrunk partition does boot properly.
Immediately after the shrinking process, it ran some kind of disk
check, but it booted perfectly after that. After about 5 restarts, it
displayed some message about a page file, but still it booted fine. I
didn't use Clonezilla to make any images until I had already verified
that the source drive with (and without) the shrunk partition booted
fine. As far as aggression goes, I don't think I did anything too
drastic. I didn't even touch the 100 MB Windows 7 boot partition. All
I did was shrink the second partition where all the data was stored to
maximize the total amount of unallocated free space at the end of the
drive. This is roughly what Steven suggests doing in his guide, and
whatever happened as a result didn't seem to stop the source drive
from booting properly.
The "exact same disk layout" could be a problem. Since the sizes in
Gparted are in MiB instead of bytes, I have some trouble figuring out
how to make the partition sizes on the source and destination drives
exactly the same. By "exact same disk layout" I'm guessing you mean
that even if there's 1 byte of difference, the cloning will fail.
Please explain the significance of disk sizes. Also, the Windows
installation wasn't really moved to new hardware. I'm pretty sure it
was a machine with exactly the same hardware except a smaller hard
drive.
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Clonezilla-live mailing list
Clonezilla-live@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/clonezilla-live
