Restoreparts does not identify partitions adequately
A partition and disk imaging/cloning program
Brought to you by:
steven_shiau
Menu
▾
▴
When using the 'restoreparts' function,
clonezilla-live-20150217-utopic-amd64
lists partitions as sda1, sda2 etc. with no further information about the partition identification.
The previous version I used was
clonezilla-live-20140915-trusty-amd64
and this identified the partitions fully, as they are identified when using 'saveparts'.
I would welcome the return of the fuller identification. It is very easy to select incorrectly when the full identification is missing.
Thanks for reporting this issue. We will fix this recently.
Steven.
Today I did a test here, when you choose the partitions "from image", it shows something like:
=====================
Choose the partition(s) from image to restore to destination disk (ALL DATA │
│ ON THE PARTITION WILL BE LOST AND REPLACED!!) The partition name is the │
│ device name in GNU/Linux. The first partition in the first disk is "hda1" or │
│ "sda1", the 2nd partition in the first disk is "hda2" or "sda2", the first │
│ partition in the second disk is "hdb1" or "sdb1"... If the system you want │
│ to save is MS windows, normally C: is hda1 (for PATA) or sda1 (for PATA, │
│ SATA or SCSI), and D: could be hda2 (or sda2), hda5 (or sda5)... (Press │
│ space key to mark your selection. An asterisk (*) will be shown when the │
│ selection is done) │
│ │
│ [ ] sda1 disk(sda)_partition(1) │
│ [*] sda5 disk(sda)_partition(5)
=====================
Then when you choose the destination partitions, it shows:
=====================
Choose the target partition(s) to be overwritten (ALL DATA ON THE PARTITION │
│ WILL BE LOST AND REPLACED!!) │
│ The partition name is the device name in GNU/Linux. The first partition in │
│ the first disk is "hda1" or "sda1", the 2nd partition in the first disk is │
│ "hda2" or "sda2", the first partition in the second disk is "hdb1" or │
│ "sdb1"... If the system you want to save is MS windows, normally C: is hda1 │
│ (for PATA) or sda1 (for PATA, SATA or SCSI), and D: could be hda2 (or sda2), │
│ hda5 (or sda5)... │
│ │
│ sda1 4.7G_ext4(In_VMware_Virtual_S)_No_disk_serial_no │
│ sda5 2.9G_ext4(In_VMware_Virtual_S)_No_disk_serial_no │
│ sdb1 4.7G_ext4(In_VMware_Virtual_S)_No_disk_serial_no │
│ sdb5 2.9G_ext4(In_VMware_Virtual_S)_No_disk_serial_no │
│ sdc1 20G_reiserfs(In_VMware_Virtual_S)_No_disk_serial_no
=====================
Therefore I think this is appropriate. For the first selection, it's from the image, therefore it's not necessary to show the partition identification, because it's from the "image", the partition name is not really related to the local partition.
For example, an image for sda2 (previous saving) could be restored to local partition sdb3.
Do you agree?
Thanks.
Steven.
Last edit: Steven Shiau 2015-03-30
I'm afraid I don't agree. As a Windows user I like to see names which are meaningful to me. I will wait for the next edition before moving from the version I am currently using. Thaks.