[Bug 1968890] Re: operating system cannot boot on eMMC memory

[Steve Langasek]

Is this reproducible if you install again from scratch?

Ubiquity does not run dosfsck (or fsck.vfat, which is the standard tool
we would actually use) because the purpose of these tools is to fix data
corruption on the filesystem.  In the common case, ubiquity is freshly
creating the filesystem on the EFI System Partition, so there would be
no reason to run fsck on it.

If your MMC disk already had an ESP on it before the installer ran, it's
possible there was pre-existing corruption which did not stop Ubuntu
from mounting it but did stop your firmware from being willing to use it
after reboot.

If this partition was freshly created by ubiquity, but was corrupted by
the time of reboot, it's possible there is a bug in ubiquity failing to
cleanly unmount the ESP at the end of the install; or it's possible
there are bugs in the Linux driver for this eMMC device resulting in
corruption (though if this was the case, you would likely find a lot
more corruption problems with the actual Ubuntu install, and not just on
the ESP).

** Changed in: ubiquity (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1968890

Title:
  operating system cannot boot on eMMC memory

Status in ubiquity package in Ubuntu:
  Incomplete

Bug description:
  I used ubuntu-mate 22.04 installer (i downloaded it on april 13th). on
  a usb stick (using dd) to install ubuntu-mate on a lenovo ideapad 1
  14ADA05 (MTM : 82GW0021FR).

  The laptop comes with eMMC 64Gb memory. The 22.04 installer manage to
  detect the eMMC drive (former installer couldn't) and did the install
  perfectly. But I couldn't boot on the eMMC after completing the
  install. Computer starts and is caught in "reboot system" loop (black
  screen, grey screen, etc)

  I booted on the ubuntu 22.04 flash USB and started Gparted. GParted told me that the FAT32 /boot/efi partition had issues (error message said that DOSFSTOOLS and MTOOLS were missing). I used apt-get to install both packages and performed a
      sudo dosfsck -rV /dev/mmcblk0p1
  from terminal. And it solved the problem at startup. Computer now starts fine.

  What I expected was that OS boot at first time. But I had to manually
  perform dosfsck on the FAT32 partition. I guess the installer might do
  it by itself, maybe the live system might include both DOSFSTOOLS and
  MTOOLS to properly configure this FAT32 /boot/efi partition in case of
  eMMC memory. I understand that linux-kernel only recently managed eMMC
  chips.

  Thx for your work anyway

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu81
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Wed Apr 13 15:11:30 2022
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash ---
  InstallationDate: Installed on 2022-04-13 (0 days ago)
  InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220330)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1968890/+subscriptions