I certainly don't question what you have done, and I appreciate your
meticulous testing, but I would love to see this notion replicated with
a completely different system and set of hard drives. I have done this
on several occasions and, although I did not do any hash test, I have
never run into any obvious issues with files. My method of doing this
in the past was basically the same thing you did:
I would use gparted to make the main Windows 7 partition on the source
partition small. I would then boot that same system again, just to make
sure it's ok and to allow chkdsk to re-verify the file system. Then I
created a "parts" image. Before restoring to the smaller target drive,
I would create the appropriate partitions on the target drive. I
usually try make them slightly larger than the imaged partitions. I
used gparted to do this, and of course also to set the small first
partition bootable. Then perform the clonezilla restore to those
partitions. I must admit that I don't always know the magic number to
set the partition sizes, and sometimes have to redo that and make them
slightly larger before I get it to work.
I've used the above procedure quite a few times with XP systems. When
doing the same thing with Windows 7, I find that I frequently will have
to boot to a Windows 7 installation medium, and let it "repair the boot
issues" with the system. This always seems to work.
But, again, when having this procedure complete successfully, I have
never been aware of any sort of issues with files. I'm wondering if
there could possibly be some other explanation for what you observed.
One of these days (too busy now!), I will try to go through this myself.
On 03/24/2012 02:42 AM, jumpingspo...@hushmail.com wrote:
> Those 2 files were just random installer files (either .exe or .msi)
> that I happened to have handy. I forgot exactly what they were, but I
> put them on the desktop as a way to see whether any files got damaged.
> By the way, the hashes only changed when I cloned to a smaller hard
> drive; they remained the same, as they should have, when I cloned to a
> hard drive of identical size. Further evidence that the files did get
> damaged can be found in the missing icons; those 2 installers had icons
> on the source drive but not on the destination drive after Clonezilla
> had finished restoring the image. This basically shows that cloning to a
> smaller hard drive caused the file corruption. Clonezilla remains
> perfect for my imaging needs when I restore an image to the same hard
> drive (and I assume it works just as well for larger sized hard drives).
>
> I really don't mind doing testing, but since I've exhausted even
> Steven's method and Gary's method, I don't have much hope at this point.
> If anybody has any new suggestions or corrections to what I did, I'll be
> happy to do the testing.
--
-Bill-
---------------------------------------------
Bill Gurley, Technical Director
Department of Chemistry
Univ. of Tennessee, Knoxville
865-974-3145 (office)
---------------------------------------------
------------------------------------------------------------------------------
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
