From: Gordon@leaf.net.nz
On 2025-12-30, Monsieur wrote:
> Gordon wrote:
>> On 2025-12-30, Axel wrote:
>>>
>>> I wanted to clone my 500 Gb LM nvme disk to a 500 Gb mechanical drive,
>>> but Rescuezilla reports that the target disk is too small. ??
>>>
>>> https://auslink.info/linux/rz.jpg
>>>
>>> I also get that message when trying to create an image.
>>>
>>> Foxclone also reports that the disk is too small.
>>>
>>> https://auslink.info/linux/foxclone.jpg
>>>
>>> How come? thanks,
>>>
>> The destination disk is smaller that the source.
>>
>> Yes we are talking about maybe just a few bytes.
>
> It is not a question of "just a few bytes", it also happens when you
> make an image of a partition and then immediately write the image back
> to the *exact same* partition, without altering anything.
>
> https://imgur.com/a/bJQ3uYD
>
> This is a bug in CloneZilla that's been known for years and they keep
> trying to talk their way out of it. "You must be doing something wrong".
> Those guys just can't count. Partitions don't magically get smaller
> after making an image of them. Or at least they shouldn't.
>
> I really don't know how people trust their data with this awful mess of
> a program.
>
A bit of clarity
Two ways to clone the partition. 1) Copy the source to the destination. 2)
is to backup the partition by copying the source files and placing them in a
directory after compression.
I use Clonezilla the second way to the point that I have in my mind that is
all that Clonezilla does. Clearly it does more than this as there are menu
items. Thus I think we have a misunderstanding.
Your picture at https://auslink.info/linux/rz.jpg shows the problem. 5....
88864 bytes vs 5 ...80160 bytes or 8704 bytes difference.
There is an agreed issue that it is not possible to clone to a smaller
partition even if the active data does. One just has to accept this.
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
