I have a very interesting issue. I’m trying to restore a 500GB disk image from a 2TB hard drive onto a different 500GB hard drive from the one the image was created from. All seems to go well (find the image, find the 500GB drive, etc) until I tell Clonezilla to actually start the restore, where it partitions the 500GB drive and then gives a lovely red error: Unable to find target partition “sdb1”. While it was partitioning, I see “Error: /dev/sdb: unrecognized disk label” a few times. I also see “Warning: 0xEE partition doesn't start on sector 1. This can cause problems in some OSes.” followed by “The operation has completed successfully.”.
Any clues whatsoever? I’m quite lost, and really need the data from this image.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Which version of Clonezilla live did you use?
Could you please post the whole error messages on the screen? You can take a picture then post it. It's easier for us to understand.
Thanks.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm using 20141208-utopic-amd64. I've attached some pictures of the error messages. I can try again and take more pictures if needed, or if there's some way to log everything, I can do that.
I checked the error messages on ths screenshot you put, and found the issue might be on the sgdisk.
Normally when re-creating the partition table, it's like:
============================
Running: dd if=/dev/zero of=/dev/sdb bs=512 count=1
1+0 records in
1+0 records out
512 bytes (512 B) copied, 0.00167913 s, 305 kB/s
Error: /dev/sdb: unrecognised disk label
Running: sgdisk -l /tmp/trusty-x64-efi-20140421-tmp-cnvted/sdb-gpt.gdisk /dev/sdb
Creating new GPT entries.
The operation has completed successfully.
Informing the OS of partition table changes..... done!
============================
However, in the screenshot you posted, apparently something went wrong when sgdisk command was run. As you can see in https://sourceforge.net/p/clonezilla/discussion/Help/thread/91414a5a/7043/attachment/WP_20150116_003.jpg
After "sgdisk -l /tmp/*/sdb-gpt.gdisk /dev/sdb", it gave a warning and an error message "Error: /dev/sdb unrecognised disk label".
That's why the partition table of GPT disk was not created.
I have built gdisk 1.0.0 here: http://free.nchc.org.tw/drbl-core/pool/drbl/live-unstable/gdisk/gdisk_1.0.0-drbl1_amd64.deb
Could you please download and install it in Clonezilla live environment, then run the
sgdisk -l /home/partimag/$YOURIMAGE/sdb-gpt.gdisk/dev/sdb"
to see if it works or not.
//NOTE// The sgdisk command will overwrite all the data in the destination disk. Therefore use it only when your testing environment has no important data.
BTW, I will upload another testing release tomorrow which will include sgdisk 1.0.0, and you can test it if you wait.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was getting the same "unrecognised disk label" error as above when trying to clone a GPT disk using local-disk-to-local. I am happy to report that I succeeded with your live-2.4.1-6-i586 build just now, so it appears the changes to gdisk have fixed the problem. Thank you for fixing this!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Are you sure the disk is supported by Linux kernel?
Or maybe give Clonezilla live 20150119-vivid: http://clonezilla.org/downloads.php
It comes with Linux kernel 3.18 so the results my be different.
//NOTE// Backup important data before you use Clonezilla. Just in case.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
omg, i have this problem too, with the same screens and lost my os because the error doesnt let the boot anymore on the disk i wanted the restoration... anyway
what do you mean when you say "are you sure the disk is supported by linux kernel"
i used the same version as matthew, and the image was created by this version of clonezilla, so i suppose it is supported, isnt it?
i also checked with an option of clonzilla if it is restorable, and it is. (there was 3 partitions on the disk, all are "restorable")
so if the image was created, it means the disk was supported, wasn't it?
the disks are 2 identical western digital 1Tb.
please help
Last edit: gamez 2015-03-01
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It is in this case a
'local_disk_to_local_disk_clone'.
Any preliminary considerations
blkdev.list in the image (as an attachment) # should be known for us
partitiontable # GPT ?
3 partitions # WINRECOVER, WINDOWS(boot), DATA ?
2 identical Western Digital 1TB HDD
# often differences because of manufacturing defects of 2 Bytes or more [-icds in expert mode]
# if disks from different manufacturers install [disk driver] before you make savedisk
# a [defragmentation] of the old partitions should be made before, and perhaps an optimization too
# (a 500 GB savedisk image [compressed] can be from about 1.5 TB disk, but can not restored to a 500 GB disk)
# Make a backup for your [important data]
# Use a memory stick or flash card for Clonzilla Live
# Basically the partitions should be [equal or greater] than the old ones.
Possibilities
try to repair the partition table GPT with 'gparted live' recent version (Curtis Gedak Jul 25 '14)
or
Look for the blkdev.list of your old savedisk image.
With 'gparted live' recent version you can make the partitions.
Then restoredisk (with -icds in expert mode if necessary).
or
change the connection cables (sdb will be sda)
restoredisk (with -icds in expert mode).
or
local_disk_to_local_disk_clone
( http://clonezilla.org/clonezilla-live/doc/03_Disk_to_disk_clone/images/ocs-06-disk-to-local-disk-clone.png )
in Beginner mode or in Expert mode with parameter -rescue -icds
Last edit: Fuchs 2015-03-03
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
i saved an image of a 1tb disk in an external hdd, the image has a size of 90gb or so (no compression used). the restoration of the image fails even if the destination disk is the one from which the image was saved, so it can't be a problem of 2 bytes size difference or something like that, since the "initial" disk is the disk where i wanted to restore the image.
but something is not clear: why the error message is:
"unable to find target partition sdb1" why can't it find sdb1?
if the disk is sdb, so it should be to clonezilla to create this sdb1 partition, right? if it doesn't find sdb1, it is because clonezilla has not created the partition. so the error message should be "sdb1 can't be created" rather than "unable to find etc..?
an other question do you think i should only clone the partition where windows were installed, to be sure to have no problem with the restoration?
Last edit: gamez 2015-03-03
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Now I have understood you would like a normal simple
savedisk for sda/restoredisk for sda
Clonezilla (sdb1) on a memory stick is invisible. That's right.
Your savedisk image is on a connected external 1TB drive (sdc1). You now should see that.
(Windows often uses more than 1 partitions. Look for the blkdev.list in your image)
Last edit: Fuchs 2015-03-04
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
i wanted something simple: just clone all the disk to restore it later, to not have any things to do with partitions.
but it doesnt work.
the message error is the one diplayed on the screens uploaded by matthew.
are we unlucky? have we done something wrong? why our restoration is impossible?
Last edit: gamez 2015-03-04
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
"the image was created by this version of clonezilla, so i suppose it is supported, isnt it?" -> It depends. If the machine you save and restore is the same one, yes. If you save an image from machine A, then restore to different machine B, then maybe Clonezilla live can not find the disk on machine B due to kernel/hardware support issue.
Which version of Clonezilla live did you use? Did you try the latest Clonezilla live on http://clonezilla.org/downloads.php
?
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
this issue is common for all updated versions of clonezilla. there is a bug within order in the scripts that creates partition table and then deletes it cleaning mbr (with "dd if=/dev/zero")
Last edit: tomawyder 2015-03-23
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't know the which part of the code exactly (don't had time to view it all).
When i try old versions of live and SElive all goes well but in new ones after fdisk/gdisk partition table creation script calls
"dd if=/dev/zero of=/dev/sda count=.." and overwrites just created partition table.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hi,
I can confirm your suspicions
I make backup (dd option) with clonezilla "alternative stable releases - 20150217-utopic" version with an ibm Uefi server.
I'm not able to restore that image in that server an hour later: same server, same disks, same raid configuration, save clonezilla disk.
Using older version (clonezilla-live-20140915-trusty-amd64) for recovery, i have had success.
Bye
Stefano
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@stefanonovelli,
Thanks for your report. Somehow I just can not reproduce this issue here. I did a test for uEFI Windows 8.1, but it worked well.
Could you please show the file lists in the image dir?
Or even better, if you can provide remote access to your machine, please email me at "steven at clonezilla org".
Thanks.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have just started cloning several machines running UEFI Windows 8.1 64-bit and I am running into this same problem as well. I am not sure if they are GPT partitions (I believe so) but I will try to double-check and assist as much as I can in troubleshooting.
Here are the versions I have been trying so far:
20141208-utopic-amd64
2.4.1-2-amd64
2.4.0-7-amd64 (not 100% sure)
2.3.2-22-amd64 (not 100% sure)
2.3.1-18-amd64 (old version I used before, figured it was worth a shot)
Later I can try to have you remote-in but I do not have a VM. Maybe I will try to set that up. Meanwhile the only way I could think of is to use Intel vPro, which I've never really been able to use myself remotely for Clonezilla.
EDIT: I just confirmed, using 20140915-trusty-amd64 (which I used previously, still had the download saved) works fine restoring the image. Thanks Stefano!
Steven I can post the errors for you at some point tomorrow.
Last edit: teknoman 2015-04-09
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I have a very interesting issue. I’m trying to restore a 500GB disk image from a 2TB hard drive onto a different 500GB hard drive from the one the image was created from. All seems to go well (find the image, find the 500GB drive, etc) until I tell Clonezilla to actually start the restore, where it partitions the 500GB drive and then gives a lovely red error: Unable to find target partition “sdb1”. While it was partitioning, I see “Error: /dev/sdb: unrecognized disk label” a few times. I also see “Warning: 0xEE partition doesn't start on sector 1. This can cause problems in some OSes.” followed by “The operation has completed successfully.”.
Any clues whatsoever? I’m quite lost, and really need the data from this image.
Which version of Clonezilla live did you use?
Could you please post the whole error messages on the screen? You can take a picture then post it. It's easier for us to understand.
Thanks.
Steven.
I'm using 20141208-utopic-amd64. I've attached some pictures of the error messages. I can try again and take more pictures if needed, or if there's some way to log everything, I can do that.
I checked the error messages on ths screenshot you put, and found the issue might be on the sgdisk.
Normally when re-creating the partition table, it's like:
============================
Running: dd if=/dev/zero of=/dev/sdb bs=512 count=1
1+0 records in
1+0 records out
512 bytes (512 B) copied, 0.00167913 s, 305 kB/s
Error: /dev/sdb: unrecognised disk label
Running: sgdisk -l /tmp/trusty-x64-efi-20140421-tmp-cnvted/sdb-gpt.gdisk /dev/sdb
Creating new GPT entries.
The operation has completed successfully.
Informing the OS of partition table changes..... done!
============================
However, in the screenshot you posted, apparently something went wrong when sgdisk command was run. As you can see in
https://sourceforge.net/p/clonezilla/discussion/Help/thread/91414a5a/7043/attachment/WP_20150116_003.jpg
After "sgdisk -l /tmp/*/sdb-gpt.gdisk /dev/sdb", it gave a warning and an error message "Error: /dev/sdb unrecognised disk label".
That's why the partition table of GPT disk was not created.
I have built gdisk 1.0.0 here:
http://free.nchc.org.tw/drbl-core/pool/drbl/live-unstable/gdisk/gdisk_1.0.0-drbl1_amd64.deb
Could you please download and install it in Clonezilla live environment, then run the
sgdisk -l /home/partimag/$YOURIMAGE/sdb-gpt.gdisk/dev/sdb"
to see if it works or not.
//NOTE// The sgdisk command will overwrite all the data in the destination disk. Therefore use it only when your testing environment has no important data.
BTW, I will upload another testing release tomorrow which will include sgdisk 1.0.0, and you can test it if you wait.
Steven.
Hello Steven,
I was getting the same "unrecognised disk label" error as above when trying to clone a GPT disk using local-disk-to-local. I am happy to report that I succeeded with your live-2.4.1-6-i586 build just now, so it appears the changes to gdisk have fixed the problem. Thank you for fixing this!
Cool! Thanks.
Steven.
Are you sure the disk is supported by Linux kernel?
Or maybe give Clonezilla live 20150119-vivid:
http://clonezilla.org/downloads.php
It comes with Linux kernel 3.18 so the results my be different.
//NOTE// Backup important data before you use Clonezilla. Just in case.
Steven.
omg, i have this problem too, with the same screens and lost my os because the error doesnt let the boot anymore on the disk i wanted the restoration... anyway
what do you mean when you say "are you sure the disk is supported by linux kernel"
i used the same version as matthew, and the image was created by this version of clonezilla, so i suppose it is supported, isnt it?
i also checked with an option of clonzilla if it is restorable, and it is. (there was 3 partitions on the disk, all are "restorable")
so if the image was created, it means the disk was supported, wasn't it?
the disks are 2 identical western digital 1Tb.
please help
Last edit: gamez 2015-03-01
i just tryed with the last version 20150225 (something like that) and it is the same.
i have my datas cloned but i cant restore them.
clonezilla is the only free program i knew, so i used it but i cant retrive my datas :'(
It is in this case a
'local_disk_to_local_disk_clone'.
Any preliminary considerations
blkdev.list in the image (as an attachment) # should be known for us
partitiontable # GPT ?
3 partitions # WINRECOVER, WINDOWS(boot), DATA ?
2 identical Western Digital 1TB HDD
# often differences because of manufacturing defects of 2 Bytes or more [-icds in expert mode]
# if disks from different manufacturers install [disk driver] before you make savedisk
# a [defragmentation] of the old partitions should be made before, and perhaps an optimization too
# (a 500 GB savedisk image [compressed] can be from about 1.5 TB disk, but can not restored to a 500 GB disk)
# Make a backup for your [important data]
# Use a memory stick or flash card for Clonzilla Live
# Basically the partitions should be [equal or greater] than the old ones.
Possibilities
try to repair the partition table GPT with 'gparted live' recent version (Curtis Gedak Jul 25 '14)
or
Look for the blkdev.list of your old savedisk image.
With 'gparted live' recent version you can make the partitions.
Then restoredisk (with -icds in expert mode if necessary).
or
change the connection cables (sdb will be sda)
restoredisk (with -icds in expert mode).
or
local_disk_to_local_disk_clone
( http://clonezilla.org/clonezilla-live/doc/03_Disk_to_disk_clone/images/ocs-06-disk-to-local-disk-clone.png )
in Beginner mode or in Expert mode with parameter -rescue -icds
Last edit: Fuchs 2015-03-03
i saved an image of a 1tb disk in an external hdd, the image has a size of 90gb or so (no compression used). the restoration of the image fails even if the destination disk is the one from which the image was saved, so it can't be a problem of 2 bytes size difference or something like that, since the "initial" disk is the disk where i wanted to restore the image.
but something is not clear: why the error message is:
"unable to find target partition sdb1" why can't it find sdb1?
if the disk is sdb, so it should be to clonezilla to create this sdb1 partition, right? if it doesn't find sdb1, it is because clonezilla has not created the partition. so the error message should be "sdb1 can't be created" rather than "unable to find etc..?
an other question do you think i should only clone the partition where windows were installed, to be sure to have no problem with the restoration?
Last edit: gamez 2015-03-03
Now I have understood you would like a normal simple
savedisk for sda/restoredisk for sda
Clonezilla (sdb1) on a memory stick is invisible. That's right.
Your savedisk image is on a connected external 1TB drive (sdc1). You now should see that.
(Windows often uses more than 1 partitions. Look for the blkdev.list in your image)
Last edit: Fuchs 2015-03-04
yes my image disk has 3 partitions.
i wanted something simple: just clone all the disk to restore it later, to not have any things to do with partitions.
but it doesnt work.
the message error is the one diplayed on the screens uploaded by matthew.
are we unlucky? have we done something wrong? why our restoration is impossible?
Last edit: gamez 2015-03-04
is there a way to have email notification when an answer is done?
"the image was created by this version of clonezilla, so i suppose it is supported, isnt it?" -> It depends. If the machine you save and restore is the same one, yes. If you save an image from machine A, then restore to different machine B, then maybe Clonezilla live can not find the disk on machine B due to kernel/hardware support issue.
Which version of Clonezilla live did you use? Did you try the latest Clonezilla live on
http://clonezilla.org/downloads.php
?
Steven.
this issue is common for all updated versions of clonezilla. there is a bug within order in the scripts that creates partition table and then deletes it cleaning mbr (with "dd if=/dev/zero")
Last edit: tomawyder 2015-03-23
at 1st i used the same version as mattew: the version 20141208-utopic-amd64 and tryed the last version since our problem was not solved.
and the machine i saved and wanted to restore is the same one. (the only one i have at home, its a personnal use)
Hi, i have exactly the same problem. he formats sda1 and then doesn't find it. how do it get my image on this HDD?
[my excuses, seems I can't cancel a post. Mine was under the wrong topic.]
Last edit: Uwe Dippel 2015-03-25
@tomawyder,
Could you please identify where the bug is? Show us the codes so that it would be easier for us to fix that.
Thanks.
Steven.
I don't know the which part of the code exactly (don't had time to view it all).
When i try old versions of live and SElive all goes well but in new ones after fdisk/gdisk partition table creation script calls
"dd if=/dev/zero of=/dev/sda count=.." and overwrites just created partition table.
hi,
I can confirm your suspicions
I make backup (dd option) with clonezilla "alternative stable releases - 20150217-utopic" version with an ibm Uefi server.
I'm not able to restore that image in that server an hour later: same server, same disks, same raid configuration, save clonezilla disk.
Using older version (clonezilla-live-20140915-trusty-amd64) for recovery, i have had success.
Bye
Stefano
@stefanonovelli,
Thanks for your report. Somehow I just can not reproduce this issue here. I did a test for uEFI Windows 8.1, but it worked well.
Could you please show the file lists in the image dir?
Or even better, if you can provide remote access to your machine, please email me at "steven at clonezilla org".
Thanks.
Steven.
@CampingHero,
Which version of Clonezilla live did you use?
Which OS did you restore?
Windows 8.1 x64 version? Or?
MBR or uEFI?
Thanks.
Steven.
Last edit: Steven Shiau 2015-03-26
Hello Steven Shiau et al,
I have just started cloning several machines running UEFI Windows 8.1 64-bit and I am running into this same problem as well. I am not sure if they are GPT partitions (I believe so) but I will try to double-check and assist as much as I can in troubleshooting.
Here are the versions I have been trying so far:
20141208-utopic-amd64
2.4.1-2-amd64
2.4.0-7-amd64 (not 100% sure)
2.3.2-22-amd64 (not 100% sure)
2.3.1-18-amd64 (old version I used before, figured it was worth a shot)
Later I can try to have you remote-in but I do not have a VM. Maybe I will try to set that up. Meanwhile the only way I could think of is to use Intel vPro, which I've never really been able to use myself remotely for Clonezilla.
EDIT: I just confirmed, using 20140915-trusty-amd64 (which I used previously, still had the download saved) works fine restoring the image. Thanks Stefano!
Steven I can post the errors for you at some point tomorrow.
Last edit: teknoman 2015-04-09