[Bug 1770093] Re: Ubiquity crashes with mount points that are FAT16/32

[Dave Jones]

I'm not sure we should be encouraging people to try the installer on the
Pi (for which we provide pre-installed images instead); still I don't
see any particular harm in adding support for this to ubiquity for those
that want to play with it.

The only thing that slightly concerns me with the patch is whether any
*other* platforms use /boot/firmware for a non-FAT boot partition, and
hence whether the test should be refined to be more Pi-specific? Testing
for a "Raspberry Pi" prefix in /proc/device-tree/model would do the
trick if that's desired?

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

Title:
  Ubiquity crashes with mount points that are FAT16/32

Status in partman-basicfilesystems package in Ubuntu:
  In Progress
Status in partman-basicfilesystems source package in Xenial:
  In Progress
Status in partman-basicfilesystems source package in Bionic:
  In Progress
Status in partman-basicfilesystems source package in Eoan:
  In Progress
Status in partman-basicfilesystems source package in Focal:
  In Progress

Bug description:
  [impact]

  when installing on pi with ubiquity, the /boot/firmware partition gets
  mounted with extra parameters that causes ubiquity to crash.

  [test case]

  see original description.

  [regression potential]

  this removes the additional mount params from (only) the
  /boot/firmware mount, so any regression would likely involve problems
  with that partition.  Also since this patches the installation path,
  regressions may occur during installation.

  [scope]

  Debian does not include the extra mount parameters, so Debian does not
  need patching.

  This package has been unchanged since bionic.  The code needing
  patching is unchanged between xenial and bionic.

  This needs patching in all releases (Xenial, Bionic, Eoan, Focal).

  [original description]

  Hi, I've used ubiquity as an installer for the Raspberry Pi 2/3.  One
  of the quirks of the Pi is its need for a FAT formatted boot
  partition.  The Pi packages (flash-kernel etc) expect this to be
  mounted at /boot/firmware.  However if I give ubiquity this mount
  point then it soon crashes.

  I believe the problem is to do with the mount options that are
  automatically given to fat partitions.  I've solved this by applying a
  patch to the partman-basicfilesystems package.  Please see attached.

  I'm not sure whether this is the correct fix, or a more generic fix
  should be applied to ubiquity and FAT partitions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/partman-basicfilesystems/+bug/1770093/+subscriptions