I was trying to disk clone 64gb Kali Linux FD to a new 128gb FD.
I performed the disk to disk clone using Clonezilla.
Upon completion, everything cloned except the Persistence partition 2 59Gb.
I re-booted into Clonezilla to clone the Persistence partition SDB2 into
the 128gb SDC2 partition. Partition to Partition clone.
Result: The 59gb sdb2 Source Persistence was erased and the 59gb Target sdc2
remained unchanged.
I do have a full backup of the 64gb source from 2 month ago.
But I was wondering if Clonezilla does a separate internal backup of your
source file prior to executing the operation.
Do you know name/location of the backup if it exist?
Any idea why the partition to partition failed in Clonezilla?
I have on my desktop, UUI volume from my source 59gb Partition 2 showing the following folders(see below).
Would any of these folders help me get my SDB2 partition?
"Partition to Partition clone.
Result: The 59gb sdb2 Source Persistence was erased and the 59gb Target sdc2 remained unchanged." -> Oops... I have no idea why. By default Clonezilla won't touch the source disk. It just reads, not to write or modify anything on the source disk.
Is this issue always reproducible there? Could you please tell us how to reproduce it? Thanks.
Steven
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I did a 2nd rerun of my problem stated above. Here are my results:
BTW: I did not run the Partition-to-Partiton clone function with my second test.
I have 2 attachemnts for your review.
Second Test:
Launch Clonezilla. Source file 64gb fd, Target 128gb fd.
Selected option Disk Clone to Disk Clone.
Did not select clone Bootloader when asked.
At the end of the disk clone job, received error message: “Partclone Failed to clone /dev/sdc2 to /dev/sdd2”
Trouble cloning the persistence data (sdc2) to the Target FD (sdd2).
It appears the problem originates from the Cloning disk-to-disk.
Still don’t understand why my 10gb Persistence data/apps was hosed during my first run.
If you review my screenshot Dev/sdc2 64gb Source. I don’t see anything unusual with the structure/format of the FD. The primary (persistence) file exist correctly having ext4 file type.
I only saved 1 text document into the persistence. My first test I had 10gb of data.
Looking at the target sdb2, it did not create a primary partition after disk cloning. Only 59.62gb of un-allocated space. The remaining (gb) space on this FD was Un-allocated. It did create the 5gb Kali live. When I purchase the 128gb. I did nothing to the format. Just popped it into the USB for cloning.
First Test Recap:
When I performed the Clone-to-Clone then Partition-to-Partition in my first run, the source fd was exactly as sdb2 screenshot. The resulted file format after the Part-to-Part run showed the following:
5gb Kali Live,
3gb UUI,
remaining 59gb format un-allocated. Wiping out the persistence partition.
For the Target, first run sdb2, was untouched. Same as the screenshot.
BTW: I did get the same error message stated above during the first test run of Disk Clone.
After checking the 64gb file. I decided to run the Part-to-Part operation. End-First-Test-Recap:
Going forward:
64gb – I am in the process of rebuilding the 10gb of data lost. Not found on my previous backup.
128Gb - I have now re-created the 128gb from scratch reinstalling the ISO and reformatting the partition. I’ll look for another cloning software that can successful perform disk-to-disk clone 64gb fd onto 128gb fd.
If anybody has any ideas what might have happen please let me know.
"Partclone Failed to clone /dev/sdc2 to /dev/sdd2" -> Is that possible you can manually run partclone for that? Like:
ocs-onthefly -e1 auto -e2 -r -j2 -sfsck -k -pa choose -f sdc2 -t sdd2
Then please post the output for the above command. Thanks.
Steven
Last edit: Steven Shiau 2017-02-27
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi.
I was trying to disk clone 64gb Kali Linux FD to a new 128gb FD.
I performed the disk to disk clone using Clonezilla.
Upon completion, everything cloned except the Persistence partition 2 59Gb.
I re-booted into Clonezilla to clone the Persistence partition SDB2 into
the 128gb SDC2 partition. Partition to Partition clone.
Result: The 59gb sdb2 Source Persistence was erased and the 59gb Target sdc2
remained unchanged.
I do have a full backup of the 64gb source from 2 month ago.
But I was wondering if Clonezilla does a separate internal backup of your
source file prior to executing the operation.
Do you know name/location of the backup if it exist?
Any idea why the partition to partition failed in Clonezilla?
I have on my desktop, UUI volume from my source 59gb Partition 2 showing the following folders(see below).
Would any of these folders help me get my SDB2 partition?
Thanks.
TC
/media/root/UUI/autorun.inf
/media/root/UUI/boot
/media/root/UUI/dists
/media/root/UUI/firmware
/media/root/UUI/g2ldr
/media/root/UUI/g2ldr.mbr
/media/root/UUI/install
/media/root/UUI/isolinux
/media/root/UUI/license.txt
/media/root/UUI/live
/media/root/UUI/md5sum.txt
/media/root/UUI/pool
/media/root/UUI/setup.exe
/media/root/UUI/System Volume Information
/media/root/UUI/tools
/media/root/UUI/Uni-USB-Installer-Copying.txt
/media/root/UUI/Uni-USB-Installer-Readme.txt
/media/root/UUI/uui
/media/root/UUI/win32-loader.ini
"Partition to Partition clone.
Result: The 59gb sdb2 Source Persistence was erased and the 59gb Target sdc2 remained unchanged." -> Oops... I have no idea why. By default Clonezilla won't touch the source disk. It just reads, not to write or modify anything on the source disk.
Is this issue always reproducible there? Could you please tell us how to reproduce it? Thanks.
Steven
Update from the Op:
I did a 2nd rerun of my problem stated above. Here are my results:
BTW: I did not run the Partition-to-Partiton clone function with my second test.
I have 2 attachemnts for your review.
Second Test:
Launch Clonezilla. Source file 64gb fd, Target 128gb fd.
Selected option Disk Clone to Disk Clone.
Did not select clone Bootloader when asked.
At the end of the disk clone job, received error message:
“Partclone Failed to clone /dev/sdc2 to /dev/sdd2”
Trouble cloning the persistence data (sdc2) to the Target FD (sdd2).
It appears the problem originates from the Cloning disk-to-disk.
Still don’t understand why my 10gb Persistence data/apps was hosed during my first run.
If you review my screenshot Dev/sdc2 64gb Source. I don’t see anything unusual with the structure/format of the FD. The primary (persistence) file exist correctly having ext4 file type.
I only saved 1 text document into the persistence. My first test I had 10gb of data.
Looking at the target sdb2, it did not create a primary partition after disk cloning. Only 59.62gb of un-allocated space. The remaining (gb) space on this FD was Un-allocated. It did create the 5gb Kali live. When I purchase the 128gb. I did nothing to the format. Just popped it into the USB for cloning.
First Test Recap:
When I performed the Clone-to-Clone then Partition-to-Partition in my first run, the source fd was exactly as sdb2 screenshot. The resulted file format after the Part-to-Part run showed the following:
5gb Kali Live,
3gb UUI,
remaining 59gb format un-allocated. Wiping out the persistence partition.
For the Target, first run sdb2, was untouched. Same as the screenshot.
BTW: I did get the same error message stated above during the first test run of Disk Clone.
After checking the 64gb file. I decided to run the Part-to-Part operation.
End-First-Test-Recap:
Going forward:
64gb – I am in the process of rebuilding the 10gb of data lost. Not found on my previous backup.
128Gb - I have now re-created the 128gb from scratch reinstalling the ISO and reformatting the partition. I’ll look for another cloning software that can successful perform disk-to-disk clone 64gb fd onto 128gb fd.
If anybody has any ideas what might have happen please let me know.
Thanks.
TC
"Partclone Failed to clone /dev/sdc2 to /dev/sdd2" -> Is that possible you can manually run partclone for that? Like:
ocs-onthefly -e1 auto -e2 -r -j2 -sfsck -k -pa choose -f sdc2 -t sdd2
Then please post the output for the above command. Thanks.
Steven
Last edit: Steven Shiau 2017-02-27