#217 No support for (e)MMC devices

[Carsten Schlote]

Clonezilla doen't handle MMC/eMMC devices correctly. It expects, that the partition device can be drived from the base device name by appending 1...$n. This works fine for traditional device like /dev/sda -> /dev/sda1 ... /dev/sda$n.

With MMC the device name was choosed to be mmcblk0 .. mmcblkX. The partition device are created by appending 'p1 ... p$n' e.g. mmcblk0 -> mmcblk0p1 ... mmcblk0p$n.

For this reason, Clonezilla fails to derive the proper names. Esp. the EFI-Grub installation requires manual fixes, as it tries to use e.g. mmcblk01 instead of mmcblk0p1.

So, Clonezilla need special handling for this sort of device file naming.

[Steven Shiau]

Which version of Clonezilla live did you use?
Did you try the latest stable Clonezilla live, i.e.
Clonezilla live 2.2.4-12 or 20140915-trusty on
http://clonezilla.org/downloads.php

Steven.

[FPhdeNK]

This bug is still the case as of the latest alternative testing Clonezilla live (20150512-vivid-amd64).

Device being restored to is mmcblk0. EFI partition is mmcblk0p2. update-efi-nvram-boot-entry tries to operate on mmcblk02 and cannot find it.

(Thankfully in my case the restore seems to have completed what it needs to and does work.)

********.
Running: update-efi-nvram-boot-entry -r /home/partimag/<...>/efi-nvram.dat /dev/mmcblk0
Updating boot entry of EFI NVRAM...
EFI system partition: /dev/mmcblk02
No partition boot entry from hard drive exists in EFI NVRAM.
EFI boot entries on this system:
*******.
**********.
EFI boot file in partition /dev/mmcblk02 was NOT found.
Program terminated!!