I have been having this problem for a few days now. I have been trying to clone my HDD to a new SSD and this error pops up. I have have not found any info relating to it and this is the only error/info that Rescuezilla gives me.
I have a feeling that R.Z. is trying to clone over empty space and I do not know why or If that is the case.
My HDD is 2.4TB/4TB full and my SSD is 0TB/4TB full (The SSD is brand new)
From the cryptic error message, I think the issue here is your new 4TB SSD may actually be very slightly smaller than the source 4TB disk. Likely by perhaps a few kilobytes.
This would block Rescuezilla's internal tool sfdisk from performing the clone of the partition table.
I can't immediately confirm, but it seperately may be related to the sector size possibly being different (512 bytes vs 4096 bytes), but that would also impact the ability to clone the partition table.
I will do some investigation, but regardless of the underlying reason, this issue will certainly persistent to block your clone between these two disks for the current version of Rescuezilla (v2.6.1), until this bug is fixed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have been having this problem for a few days now. I have been trying to clone my HDD to a new SSD and this error pops up. I have have not found any info relating to it and this is the only error/info that Rescuezilla gives me.
I have a feeling that R.Z. is trying to clone over empty space and I do not know why or If that is the case.
My HDD is 2.4TB/4TB full and my SSD is 0TB/4TB full (The SSD is brand new)
From the cryptic error message, I think the issue here is your new 4TB SSD may actually be very slightly smaller than the source 4TB disk. Likely by perhaps a few kilobytes.
This would block Rescuezilla's internal tool
sfdiskfrom performing the clone of the partition table.I can't immediately confirm, but it seperately may be related to the sector size possibly being different (512 bytes vs 4096 bytes), but that would also impact the ability to clone the partition table.
I will do some investigation, but regardless of the underlying reason, this issue will certainly persistent to block your clone between these two disks for the current version of Rescuezilla (v2.6.1), until this bug is fixed.