shh

Some tests later: - 20251017-plucky: I created a new image and did a recovery. /dev is present on the src ext4-partition nvme0n1p2. After recovery, the /dev folder is missing - 20230903-lunar: I created a new image and did a recovery. /dev is present on the src ext4-partition nvme0n1p2. After recovery, the /dev folder is missing. I also did a recovery of an image created with the newer 20251005, (without any resulting /dev afterwards). This is weird, I don't know how this could happen. The old 20230903-lunar...

Hello! I just checked 20251017-plucky on this machine and could create a proper image, which is also recoverable to the same machine. Thanks for the fix! (However /dev directory is still missing after recovery. I had to create /dev afterwards - but i'm going to track that in the other ticket) Best regards...

Support imaging MTD block & eMMC breaks full disk imaging

So used blocks should contain all metadata, including the complete directory structure, right? The src ext4-filesystem contains a /dev folder - I just checked again, via external booting from a different system, and mounting the partition. Process is: - I take a complete image of the whole disk (=EFI(nvme0n1p1)+ext4(nvme0n1p2) - I restore this image completely, but after the completion go into /tmp/root**** (that's where nvme0n1p2 is mounted) and see what what restored. - in the restored partition...

I realize, that even an old 20230903-LU image doesn't create a /dev folder after restoring the partition. Hmm. Restoring an old Debian 12(!) image creates this /dev folder, so no problem. So this brand new Debian 13 Trixie isn't capable of creating /dev itself for mounting the udev-filesystem. And /dev doesn't seem to be imaged by Clonezilla. However, /dev afaik is a real folder on a source system, nothing virtual like /proc or /sys. And kernel/initrd seems to need it. So I think Clonezilla should...

Recovery of Debian13 image fails because /dev isn't created