I am trying to get a (shrunk) 60GB partition from a Thinkpad T60p to a Thinkpad T410 with an SDD.
I downloaded the latest version of Clonezilla yesterday, burned it on DVD, and saved the image of the source partition successfully onto a USB drive.
When I try to restore the image on the T410, I immediately get the "image may be corrupt" error. I use the default options and beginner mode in Clonezilla.
I also created an image of the target partition before I made the first restore attempt, just in case. It turns out that Clonezilla wipes out the target drive, even though there is the error about the corrupt image file. Luckily, I was able to restore that image just fine from the same USB drive. It seems that the images coming from the T60p do not restore on the T410. Is there a way to do this>
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
"It turns out that Clonezilla wipes out the target drive, even though there is the error about the corrupt image file." -> If you choose restoredisk, yes, Clonezilla will recreate the partition table, so basically from that on, the data on the disk are gone.
"It seems that the images coming from the T60p do not restore on the T410. Is there a way to do this" -> Do they have same size of disk? If so, yes. If not, make sure the destination disk must be equal or larger than the original one.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It would be also good to investigate the root cause of that "image may be corrupt error":
- Has the image been really corrupt?
- If yes - what options have you used on backup (did it use dd, partclone, ntfsclone). Any errors, unusual messages in logs?
- Can you reproduce this? (With same partition; with another one - maybe smaller; or even empty one).
- Have you tried to restore the image elsewhere? (Maybe to a file if yo're afraid to wipe-out whole disk partitions).
- You say you managed to restore partition from same USB drive - did you use the same image which reported possible corruption error before? Or you used another image (from previous version of Clonezilla; or from another imaging tool)?
Regards,
Yavor
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yavor,
Thank you for your questions. I can only answer some of them, and my focus is on rebuilding the machine now, since the restore did not work.
"- Has the image been really corrupt?"
How do I know?
"- If yes - what options have you used on backup"
I used the beginner mode.
"Any errors, unusual …"
It seems there are always errors when the tool starts or shuts down. The actual process did not generate any errors.
"- Can you reproduce this?"
Yes, it happens with every image that I create from the source partition.
"- Have you tried to restore the image elsewhere?"
No. It needs to restore to the target drive.
"- You say you managed to restore partition from same USB drive - did you use …"
I used the image from the target NTFS partition that I created with the same Clonezilla live dvd, also with "beginner" mode. So I was able to restore this image to the partition that it originally came from.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Did you use latest stable or latest testing version of clonezilla? There was a bug affecting ntfs cloning in underlying partclone.ntfs utility which is fixed in general but is not yet included in clonezilla stable (and is already in clonezilla testing). So if you're not using the testing version yet - you should try it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The error message "image may be corrupt" seems too general to me (it doesn't come from partclone) - so I suspect you didn't got hit by the bug I had in mind in my previous post. Any other messages around this error line? So far to me seems image file is OK.
Did you notice whether partition names (and numbers) in the new notebook are the same as in old one? If not - I remember there were some problems with that (e.g. if you go from /dev/hda1 to /dev/hda2). The error was very similar - and happens in the beginning since it's unable to find the image file at all (trying a wrong filename). A workaround was to either manually rename some stuff in image folder (better - copy of it) to make partition name match the target. Or you may use the underlying partclone utility directly specifing exact target partition name where you want to restore to.
You can also try using advanced options to generate some checksums and you may also specify large enough size so that your image is not split into too many particles. You can also switch off compression (if there is enough space) to make things simpler. Having single image file - it will be easier to use partclone.ntfs directly to restore the image.
Regards,
Yavor
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you, the hint with the different partition numbers was helpful! Once I renamed the files in the image folder and edited one of the files that contained the device name (sda1 instead of sda2), ntfsclone stared restoring the image.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am trying to get a (shrunk) 60GB partition from a Thinkpad T60p to a Thinkpad T410 with an SDD.
I downloaded the latest version of Clonezilla yesterday, burned it on DVD, and saved the image of the source partition successfully onto a USB drive.
When I try to restore the image on the T410, I immediately get the "image may be corrupt" error. I use the default options and beginner mode in Clonezilla.
I also created an image of the target partition before I made the first restore attempt, just in case. It turns out that Clonezilla wipes out the target drive, even though there is the error about the corrupt image file. Luckily, I was able to restore that image just fine from the same USB drive. It seems that the images coming from the T60p do not restore on the T410. Is there a way to do this>
By the way, all partitions involved are NTFS and the OS is Win 7 x64.
"It turns out that Clonezilla wipes out the target drive, even though there is the error about the corrupt image file." -> If you choose restoredisk, yes, Clonezilla will recreate the partition table, so basically from that on, the data on the disk are gone.
"It seems that the images coming from the T60p do not restore on the T410. Is there a way to do this" -> Do they have same size of disk? If so, yes. If not, make sure the destination disk must be equal or larger than the original one.
Steven.
It would be also good to investigate the root cause of that "image may be corrupt error":
- Has the image been really corrupt?
- If yes - what options have you used on backup (did it use dd, partclone, ntfsclone). Any errors, unusual messages in logs?
- Can you reproduce this? (With same partition; with another one - maybe smaller; or even empty one).
- Have you tried to restore the image elsewhere? (Maybe to a file if yo're afraid to wipe-out whole disk partitions).
- You say you managed to restore partition from same USB drive - did you use the same image which reported possible corruption error before? Or you used another image (from previous version of Clonezilla; or from another imaging tool)?
Regards,
Yavor
Yavor,
Thank you for your questions. I can only answer some of them, and my focus is on rebuilding the machine now, since the restore did not work.
"- Has the image been really corrupt?"
How do I know?
"- If yes - what options have you used on backup"
I used the beginner mode.
"Any errors, unusual …"
It seems there are always errors when the tool starts or shuts down. The actual process did not generate any errors.
"- Can you reproduce this?"
Yes, it happens with every image that I create from the source partition.
"- Have you tried to restore the image elsewhere?"
No. It needs to restore to the target drive.
"- You say you managed to restore partition from same USB drive - did you use …"
I used the image from the target NTFS partition that I created with the same Clonezilla live dvd, also with "beginner" mode. So I was able to restore this image to the partition that it originally came from.
Did you use latest stable or latest testing version of clonezilla? There was a bug affecting ntfs cloning in underlying partclone.ntfs utility which is fixed in general but is not yet included in clonezilla stable (and is already in clonezilla testing). So if you're not using the testing version yet - you should try it.
The error message "image may be corrupt" seems too general to me (it doesn't come from partclone) - so I suspect you didn't got hit by the bug I had in mind in my previous post. Any other messages around this error line? So far to me seems image file is OK.
Did you notice whether partition names (and numbers) in the new notebook are the same as in old one? If not - I remember there were some problems with that (e.g. if you go from /dev/hda1 to /dev/hda2). The error was very similar - and happens in the beginning since it's unable to find the image file at all (trying a wrong filename). A workaround was to either manually rename some stuff in image folder (better - copy of it) to make partition name match the target. Or you may use the underlying partclone utility directly specifing exact target partition name where you want to restore to.
You can also try using advanced options to generate some checksums and you may also specify large enough size so that your image is not split into too many particles. You can also switch off compression (if there is enough space) to make things simpler. Having single image file - it will be easier to use partclone.ntfs directly to restore the image.
Regards,
Yavor
Thank you, the hint with the different partition numbers was helpful! Once I renamed the files in the image folder and edited one of the files that contained the device name (sda1 instead of sda2), ntfsclone stared restoring the image.