Install to fat32 fails

[Joshua Powers]

Description:
Choosing to install with a fat32 filesystem fails

Logs:
Curtin log: https://paste.ubuntu.com/26399728/
Subiquity log: https://paste.ubuntu.com/26399727/

[Ryan Harper (raharper)]

This looks like a fat32 as rootfs; that's not something we're going to support.

I'm happy to add some documentation changes to indicate which filesystems we can support as rootfs if needed.

Also, if possible, can we get the the subiquity curtin config files attached to the bug? That'll help understand how what curtin is being asked to do.

[Joshua Powers (powersj)]

Where would I find those config files?

[Ryan Harper (raharper)]

On Tue, Jan 16, 2018 at 3:05 PM, Joshua Powers <email address hidden>
wrote:

> Where would I find those config files?
>

/tmp/subiquity-curtin-install.conf

> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1743632
>
> Title:
> Install to fat32 fails
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1743632/+subscriptions
>

[Joshua Powers (powersj)]

install.conf: https://paste.ubuntu.com/26400693/
install.log: https://paste.ubuntu.com/26400694/

> /tmp/subiquity-curtin-install.conf

tangent: any reason to not put them in /var/log/curtin?

[Ryan Harper (raharper)]

Confirmed config to use fat32 on rootfs (/); which we don't support (Ubuntu
doesn't support this either)
I think subiquity needs to disallow fat32 as rootfs. We can also reject
this in curtin as well if needed.

On Tue, Jan 16, 2018 at 4:53 PM, Joshua Powers <email address hidden>
wrote:

> install.conf: https://paste.ubuntu.com/26400693/
> install.log: https://paste.ubuntu.com/26400694/
>
> > /tmp/subiquity-curtin-install.conf
>
> tangent: any reason to not put them in /var/log/curtin?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1743632
>
> Title:
> Install to fat32 fails
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1743632/+subscriptions
>

[Michael Hudson-Doyle (mwhudson)]

Ah yes, this all makes sense. I guess /usr or various other mount points as fat32 won't work either? Is there any sane way to make a comprehensive list?

As to why not /var/log/curtin, no real reason but it's all a live session anyway so it's not like it makes a lot of difference. We should make the log files end up somewhere sensible on the target system but that's not really relevant when the install fails :-)

[Michael Hudson-Doyle (mwhudson)]

It's a total hack but we could refuse to format a mount point $mnt as fat32 if /rofs/$mnt is a directory...

[Ryan Harper (raharper)]

On Tue, Jan 16, 2018 at 5:15 PM, Michael Hudson-Doyle <
<email address hidden>> wrote:

> Ah yes, this all makes sense. I guess /usr or various other mount points
> as fat32 won't work either? Is there any sane way to make a
> comprehensive list?
>

I suspect we could get away with whitelisting /boot/EFI as the only vfat32
that the installer
supports (and drop FAT32 from the fs choice for now).

No linux installer does arbitrary fat32 filesystems AFAIK

[Ryan Harper (raharper)]

On Tue, Jan 16, 2018 at 5:34 PM, Michael Hudson-Doyle <
<email address hidden>> wrote:

> It's a total hack but we could refuse to format a mount point $mnt as
> fat32 if /rofs/$mnt is a directory...
>

Yeah, but then you need to handle errors during the curtin install and that
leaves the user with
a nasty experience.

I'd think better to up-front block broken configurations. I'd rather see a
bug or report complaining
that subiquity won't let users create FAT32 rootfs or FAT32 /var instead
of why did subiquity let
me use FAT32 for /var.

>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1743632
>
> Title:
> Install to fat32 fails
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1743632/+subscriptions
>