Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
storage: restricted probes must gather fs info
In ubuntu-desktop-installer/issues/1772, a user formatted an existing partition as ext4, which triggered the ESP to be "mounted". Except this mount step also formatted the ESP. Previously, when we ran block probing, the restricted=False version failed, which caused it to run a restricted=True probe. The restricted=True probe looks at block devices, but does not gather filesystem information. The esp "mount" check is also willing to format the partition if it is unformatted. (We do not have a distinction between a partition that is unformatted and one for which we have not obtained filesystem information.) This user had block probing restricted=False fail due to LP: #2012722, where Ventoy was in use and we handled the device mapper entry poorly. While recreating the failure case, simply retesting with a build with the fix for LP: #2012722 is enough to avoid this problem. This is because the restricted=False probe passes, which means filesystem info is gathered, which means the mount step doesn't attempt to format it. There will inevitably be other block probing failure cases for restricted=False. restricted=True must not leave people so vulnerable to a partition reformat. Gather filesystem information during a restricted=True probe.
- Loading branch information