Drive copy fails - /tmp/ocs_onthefly_src.GtQU3J/d2d-pseudo does not exist

[Mike Clarke]

I'm using clonezilla-live-3.1.0-22-amd64.iso to clone a Windows 10 system from an 80GB HDD onto a 480GB SSD using the beginner mode with default options but it fails saying that /tmp/ocs_onthefly_src.GtQU3J/d2d-pseudo does not exist

Cloning the source device to /dev/sdb. Running:
LC_ALL=C ocs-sr --ocsroot /tmp/ocs_onthefly_src.GtQU3J -l en_US.UTF-8 --batch -j2 -scr -p true -g auto -e1 auto -e2 -r -j2 -sfsck -k1 -icds ld2d_restoredisk d2d-pseudo sdb
Setting the TERM as linux
Starting /usr/sbin/ocs-sr at 2023-08-09 11:06:49 UTC...
Start preparing device name cache files in /tmp/ocs-cache//...
The file /proc/partitions remains the same. Skip generating disk(s) list file.
The file /proc/partitions remains the same. Skip generating partitions(s) list file.
Both /proc/partitions and blkid output do not change. Skip generating file system cache file related to the dev(s).
********.
Clonezilla image dir: /tmp/ocs_onthefly_src.GtQU3J
********.
Shutting down the Logical Volume Manager
Finished Shutting down the Logical Volume Manager
The directory for this inputted image name does NOT exist: /tmp/ocs_onthefly_src.GtQU3J/d2d-pseudo
Program terminated!!!!
Checking if udevd rules have to be restored...
Now syncing - flush filesystem buffers...
Ending /usr/sbin/ocs-onthefly at 2023-08-09 11:06:55 UTC...
///NOTE/// Remember to remove the source disk or the cloned destination disk before you boot this machine.
Otherwise when two identical systems exist on the same machine, the restored OS will be confused, and the booting might fail.

[Steven Shiau]

Is this issue reproducible on testing Clonezilla live 3.1.1-12 or 20230807-*?
https://clonezilla.org/downloads.php

Steven

[Mike Clarke]

OK, I've tried both clonezilla-live-3.1.1-12-amd64.iso and clonezilla-live-20230807-lunar-amd64.iso but both show the main problem.

One thing I did notice as things scrolled up the screen was a warning that there were conflicting GPT and MBR records on the source drive, perhaps that might be relevant. At some point in the past the drive would have been partitioned for GPT. When Windows 10 was installed the existing partitions were deleted and the drive was reconfigured for MBR by the Windows installer. It's possible that this might not have deleted the backup GPT partition table.

[Steven Shiau]

Maybe that's the culprit. So first you backup important data, then try to erase the unnecessary GPT partition table.
Then clone it again.

Steven

[Mike Clarke]

I've zeroed out the last few blocks of the drive to remove any residual GPT backup partition table but Clonezilla still fails with the same error and still reports conflicting GPT and MBR records.

The source disk is an old one which I don't intend to use after copying Windows to a new drive which I've now managed to do with a trial version of Macrium Reflect so I'll not spend any more time trying to find out what was causing the problem.