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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968890
Title:
operating system cannot boot on eMMC memory
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1968890/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
