Menu

problem backing up tablet

Help
Robert S
2015-10-04
2015-12-13
  • Robert S

    Robert S - 2015-10-04

    I'm trying to clone emmc in my dualboot android/win10 x86 tablet, but clonezilla clones only first 7 partitions
    output from parted

    Model: MMC CWBD3R (sd/mmc)
    Disk /dev/mmcblk0: 62.5GB
    Sector size (logical/physical): 512B/512B
    Partition Table: gpt
    Disk Flags: 
    
    Number  Start   End     Size    File system  Name                                  Flags
     1      1049kB  106MB   105MB                android_bootloader2
     2      106MB   211MB   105MB   fat16        android_bootloader                    boot, esp
     3      211MB   242MB   31.5MB               android_boot
     4      242MB   274MB   31.5MB               android_recovery
     5      274MB   275MB   1049kB               android_misc
     6      275MB   292MB   16.8MB               android_metadata
     7      292MB   4318MB  4027MB  ext4         android_system
     8      4318MB  4586MB  268MB   ext4         android_cache
     9      4586MB  26.1GB  21.5GB  ext4         android_data
    10      26.1GB  26.1GB  1049kB               android_persistent
    11      26.1GB  26.1GB  8389kB  ext4         android_config
    12      26.1GB  26.1GB  10.5MB  ext4         android_factory
    13      26.1GB  26.2GB  134MB   fat32        android_EFI system partition          boot, esp
    14      26.2GB  26.2GB  16.8MB               android_Microsoft reserved partition  msftres
    15      26.2GB  62.0GB  35.8GB  ntfs         android_Basic data partition          msftdata
    16      62.0GB  62.5GB  524MB   ntfs         android_Basic data partition          hidden, diag
    

    output from blkid

    /dev/sda1: LABEL="MYLINUXLIVE" UUID="F4CD-7D9B" TYPE="vfat"
    /dev/loop0: TYPE="squashfs"
    /dev/mmcblk0p2: SEC_TYPE="msdos" LABEL="ANDROIDIA" UUID="F60A-BB6B" TYPE="vfat" PARTLABEL="android_bootloader" PARTUUID="2568845d-2332-4675-bc39-8fa5a4748d15"
    /dev/mmcblk0p7: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4" PARTLABEL="android_system" PARTUUID="38f428e6-d326-425d-9140-6e0ea133647c"
    /dev/mmcblk1p1: UUID="4AB4011AB40109E1" TYPE="ntfs"
    /dev/mmcblk0: PTUUID="e67d4565-68b6-11e5-b25b-806e6f6e6963" PTTYPE="gpt"
    /dev/mmcblk0p1: PARTLABEL="android_bootloader2" PARTUUID="114eaffe-1552-4022-b26e-9b053604cf84"
    /dev/mmcblk0p3: PARTLABEL="android_boot" PARTUUID="49a4d17f-93a3-45c1-a0de-f50b2ebe2599"
    /dev/mmcblk0p4: PARTLABEL="android_recovery" PARTUUID="4177c722-9e92-4aab-8644-43502bfd5506"
    /dev/mmcblk0p5: PARTLABEL="android_misc" PARTUUID="ef32a33b-a409-486c-9141-9ffb711f6266"
    /dev/mmcblk0p6: PARTLABEL="android_metadata" PARTUUID="20ac26be-20b7-11e3-84c5-6cfdb94711e9"
    /dev/mmcblk1: PTTYPE="dos"
    

    output from /proc/partitions

    major minor  #blocks  name
    
       1        0      65536 ram0
       1        1      65536 ram1
       1        2      65536 ram2
       1        3      65536 ram3
       1        4      65536 ram4
       1        5      65536 ram5
       1        6      65536 ram6
       1        7      65536 ram7
       1        8      65536 ram8
       1        9      65536 ram9
       1       10      65536 ram10
       1       11      65536 ram11
       1       12      65536 ram12
       1       13      65536 ram13
       1       14      65536 ram14
       1       15      65536 ram15
       7        0     151180 loop0
     179        0   61071360 mmcblk0
     179        1     102400 mmcblk0p1
     179        2     102400 mmcblk0p2
     179        3      30720 mmcblk0p3
     179        4      30720 mmcblk0p4
     179        5       1024 mmcblk0p5
     179        6      16384 mmcblk0p6
     179        7    3932160 mmcblk0p7
     179       24       4096 mmcblk0rpmb
     179       16       4096 mmcblk0boot1
     179        8       4096 mmcblk0boot0
       8        0    1945600 sda
       8        1    1943552 sda1
     179       32   62652416 mmcblk1
     179       33   62636032 mmcblk1p1
    
     
  • Steven Shiau

    Steven Shiau - 2015-10-14

    Thanks for reporting this. It seems blkid also only lists the 1st 7 partitions, and not all of them are shown in /proc/partitions.
    This will be very inconsistent...
    How did you install that dual boot system? Please describe that in detail. I need to find a machine and follow your steps to create the same environment then try to reproduce the problem here.

    Steven.

     
  • Robert S

    Robert S - 2015-10-27

    the device is teclast x98 pro
    the install process consist of flashing the android image using intel phone flash tool, which besides other things also flashes the attached gpt.bin file and then booting winPE from flash drive which installs windows automatically using attached script. Both android and windows images are original from manufacturer.
    The whole installation process with all required files is described in detail in this forum http://techtablets.com/forums/topic/how-to-dualboot-androidwindows-on-k9c3/

     
  • James Cameron

    James Cameron - 2015-10-28

    This is because the kernel used in Clonezilla was built with CONFIG_MMC_BLOCK_MINORS=8, limiting the number of discovered partitions on an eMMC device to seven.

    The Clonezilla kernel would need to be rebuilt especially for this situation. No doubt the kernel normally used on your Android system has that feature already.

    Or. you might try using partclone.dd carefully in the command shell. This would get you a clone of the /dev/mmcblk0 device, which contains the gpt partition table and all partitions, even the ones above 7.

    See also:

     
  • Steven Shiau

    Steven Shiau - 2015-11-04

    @James,
    This is weird... The Linux kernel 4.2.0-1-686-pae (https://packages.debian.org/sid/linux-image-4.2.0-1-686-pae) from Debian actually uses 256 for that:
    $ grep CONFIG_MMC_BLOCK_MINORS /boot/config-4.2.0-1-686-pae
    CONFIG_MMC_BLOCK_MINORS=256

    @Robert,
    Which version of Clonezilla live did you use?

    Steven.

     
  • Robert S

    Robert S - 2015-11-07

    I was using clonezilla-live-20150805-vivid-amd64.iso, now I tried clonezilla-live-2.4.2-61-amd64.iso and it can see all the partitions, thanks

     

    Last edit: Robert S 2015-11-08
  • Steven Shiau

    Steven Shiau - 2015-11-09

    @Robert,
    Cool. Thanks for confirming that.

    Steven.

     
  • Galland

    Galland - 2015-11-29

    @Robert
    As you I try to backup my Teclast X98 Pro with clonezilla
    I try 2.4.2-61-amd64 with no success:
    "Unable to find a medium containing a live file system"
    I see some posts with this problem.
    I a new to X98 and clonezilla, probably I miss something.
    Couild you help me ?
    Dominique

     
  • Galland

    Galland - 2015-12-06

    To complete my previous post.
    Firts I try to prepâre my USB stick with Lili, and the boot fails with "Unable to find a medium containing a live file system"
    After I use Tuxboot and I was able to save my tablet.

     
  • Galland

    Galland - 2015-12-07

    False hope, it worked only once.At the second retry the same problem happened. Here the boots messages:
    efi: requested map not found
    esrt: ESRT header is not in the memory map
    ignoring BGRT: invalid status 0 (expected 1)
    ...
    Unable to find a medium containing a live file system" ..
    BusyBox...

    /bin/sh: can't access tty: job control turned off
    I dont understand why its worked by luck only once.?
    Someone can help me ?
    Device is Teclast X98 Pro
    Clonezilla is .clonezilla-live-2.4.2-61-amd64

     
  • Steven Shiau

    Steven Shiau - 2015-12-13

    Looks like the Linux kernel on clonezilla live 2.4.2-61 does not support your hardware. Please try to use the latest testing Clonezilla live, 2.4.5-3 or 201512072-wily:
    http://clonezilla.org/downloads.php
    They come with newer Linux kernel so it might help.

    Steven.

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.