#435 Support imaging MTD block & eMMC breaks full disk imaging

[shh]

Hello,
I'm using Ubuntu-based testing images, a Plucky from June and 20251005-questing.
The following change now completely breaks full disk backuping of a Dell Optiplex 5080.

• Support imaging MTD block & eMMC boot devices[...]

Clonezilla somehow detects a /dev/mtdblock0, but dmsg and journalctl already shows I/O-error on this.
Selecting full disk backup now includes this partition and I get an error ald faulty image at the end (after clonezilla tries this partition).
I think this is just a temp-device used from UEFI for firmware-updates.
Suggestions: Revert including MTD blocks per default, or let us choose.

See according log attached.
Please let me know if you need additional logs.

Best regards...

[Steven Shiau]

Thanks for your feedback.
Normally partclone.dd will just dump the raw data. However, we will check why it finished but still gave the warning about the hardware issue.

[Steven Shiau]

It looks like some of the MTD block device is not well supported by Linux kernel, and it might give some I/O errors. That causes Partclone, even in dd mode, failing to save the device as an image.
As you have suggested, we have disabled saving MTD block device by default. It can be enabled in expert mode using "-smtd" in Clonezilla live >= 3.3.0-22 or 20251017-*:
https://clonezilla.org/downloads.php
Please give that a try and let us know the results.
Thank you.

[shh]

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...

[Steven Shiau]

Thanks for your feedback.
Actually we have no idea about the "/dev" issue you mentioned. If you can reproduce this issue in a VM, please share the image of VM so that we can try to reproduce the issue here.