eMMC errors upon cloning / installing

Jesse KaukonenJesse Kaukonen New Member Posts: 42 ✭✭

We cloned several Upboards with clonezilla. 3 of them succeeded, 4th one got stuck. We had to cut power to it, and tried to clone a disk image again. Clonezilla printed several errors about the disk, after which we attempted to install standard ubilinux 4. When trying to resize the partition, several errors were printed. After this failed ubilinux 4 install I booted the system, and BIOS showed no partitions of any kind except for the USB stick containing the installer. After I removed the USB stick, the device didn't boot at all - not even BIOS. After removing BIOS battery for 30 minutes the board booted to the USB stick, same disk errors were shown and the board became unable to boot to BIOS again.

ERROR: Bad battery
ERROR: Bad Date/Time

Does this particular Up have a broken emmc? It's an unused Up from a recent shipment. Is there a way to test the emmc device itself for errors, then maybe manually create the emmc partitions?

Here's what e2fsck and fdisk have to say:

8 [email protected] ~ # e2fsck /dev/mmcblk0                           :(
e2fsck 1.43.6 (29-Aug-2017)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/mmcblk0

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

/dev/mmcblk0 contains `DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,2), end-CHS (0x3ff,255,63), startsector 1, 30539775 sectors, extended partition table (last)' data
8 [email protected] ~ #                                               :(


8 [email protected] ~ # fdisk -l                                      :(
Disk /dev/mmcblk0: 14.6 GiB, 15636365312 bytes, 30539776 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 893C6070-4F32-4733-9001-E11DA25BE3CB

Device           Start      End  Sectors  Size Type
/dev/mmcblk0p1    2048  1050623  1048576  512M EFI System
/dev/mmcblk0p2 1050624 30539742 29489119 14.1G Linux filesystem




Disk /dev/mmcblk0boot1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mmcblk0boot0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sda: 14.4 GiB, 15483273216 bytes, 30240768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x17a44bd2

Device     Boot Start     End Sectors  Size Id Type
/dev/sda1  *        0 3121151 3121152  1.5G  0 Empty
/dev/sda2         164  131235  131072   64M ef EFI (FAT-12/16/32)


Disk /dev/loop0: 1.4 GiB, 1478569984 bytes, 2887832 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
[email protected] ~ #

Comments

  • Jesse KaukonenJesse Kaukonen New Member Posts: 42 ✭✭
    edited June 2018

    We got another Up with eMMC issues. BIOS doesn't show the eMMC as a boot device. Loading Ubilinux 4 installer fails with mmc0 errors. Here's dmesg output from the installer.

    The relevant part is:

    [   10.978948] mmc0: SDHCI controller on ACPI [80860F14:00] using ADMA
    ...
    ...
    [   12.701645] mmc0: error -110 whilst initialising MMC card
    

    fdisk does not show the device at all. This wasn't a Clonezilla related issue, but seemingly happened after the Up was powered from a regular 5V / 6A PSU after having been earlier powered by the PoE bridge. We wonder if the PoE bridge had some capacitor still charged when the normal PSU was plugged in and this is related to the issue.

  • ccaldeccalde Administrator, Moderator, Emutex Posts: 331 admin

    Hi @Jesse Kaukonen ,

    What a pity to hear that...

    Which BIOS version are you using?
    The issue with the eMMC is within Ubilinux4 only? Also for Ubuntu?
    Did you try to install the OS using the entire disk space?

    Cheers!

  • Jesse KaukonenJesse Kaukonen New Member Posts: 42 ✭✭
    edited June 2018

    On these Ups we had Ubilinux 4. We currently have no way of installing an OS of any kind as the eMMC isn't found. They were sent back via an RMA procedure, but I'm mostly wondering if there's a way to further debug this at our end.

    The BIOS is UPC1DM07.

Sign In or Register to comment.