CHANGE_FILE_SYSTEM sometimes marks disk as changed unnecessarily
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
partman-base (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
Hi
I'm doing a weird install: booting from a SD card on an armel imx51 babbage board and installing to that SD card.
The SD card image from Ubuntu has two primary partitions, one of a special non-FS type (contains the bootloader in a special subpartitioning scheme) and another primary partition with a VFAT containing the installer and all.
Before starting the install I'm creating partition 3 and 4 of type linux and linux swap, then running "ubiquity --debug".
At the partitioning screen, I selected to format part 3 as ext4 and to use part 4 as swap.
When the install started, I then got a popup telling me that it failed to unmount partitions, something like "Installer needs to change partition table but can't because /cdrom is still mounted; please close apps using this mount point etc." (translated). [Go back] [Continue]
I think the installer shouldn't have to unmount anything in this case. Hitting continue and I'm then dropped to the partitioner welcome screen; note that my choice of "Custom partitioning" has not been preserved and "Install side by side" is selected by default.
Bye
Changed in ubiquity (Ubuntu): | |
importance: | Undecided → Low |
affects: | ubiquity (Ubuntu) → partman-base (Ubuntu) |
Changed in partman-base (Ubuntu): | |
status: | New → Triaged |
summary: |
- Requires unmounting partitions when no change to the partition table - were made + CHANGE_FILE_SYSTEM sometimes marks disk as changed unnecessarily |