When using biggest_free, you are unable to specify a drive
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
partman-auto (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: partman-auto
With the Dell factory process, we have a specific scheme that two partitions are created before Ubiquity (and consequently partman-auto) activate. These two partitions must remain in place.
In our seed file we are specifying:
d-i partman-
d-i partman-
The expected behavior is that the expert_recipe is placed into the free space. This works properly when only a single drive is present.
When a second drive is added to the mix, it always chooses the bigger drive because it doesn't have those two existing partitions.
Logically, you might expect that it would be able to specify which disks to check like this:
d-i partman-auto/disk string /dev/sda
Unfortunately, the biggest_free recipe ignores this variable. The only time it is used is when you also specify:
d-i partman-auto/method string regular
In doing this, free space isn't taken into consideration at all. The recipe gets used, but wipes away both of the existing partitions on /dev/sda.
So I see two possible solutions:
1) Letting init_automatica
2) Expand display.
The former option seems like a better solution though to me.
Related branches
Changed in dell: | |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in dell: | |
assignee: | nobody → superm1 |
status: | Confirmed → Fix Committed |
Changed in dell: | |
status: | Fix Committed → Fix Released |
Changed in somerville: | |
assignee: | nobody → Mario Limonciello (superm1) |
importance: | Undecided → High |
status: | New → Fix Released |
no longer affects: | dell |
I agree that having the biggest_free autopartitioning method listen to partman-auto/disk seems like the best option here.