preseeding partitions does not work correct

Bug #568290 reported by Allo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
partman-partitioning (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: partman-partitioning

We work with the Preseed-System to install ubuntu jaunty, and want to upgrade to lucid, soon. our preseed (see below for the partman options) works fine on jaunty, but lucid says the partitioning is invalid (too many primary partitions?). If i say "continue"
 and "no" on returning to the partitioning-menu, it installs with the right partition layout, as given by the preseed file.

### Partitioning
# If the system has free space you can choose to only partition that space.
# Alternatives: custom, some_device, some_device_crypto, some_device_lvm.
d-i partman-auto/init_automatically_partition select biggest_free

# Alternatively, you can specify a disk to partition. The device name must
# be given in traditional non-devfs format.
# For example, to use the first SCSI/SATA hard disk:
d-i partman-auto/disk string /dev/sda
# Note: If you want to use whatever disk is available, no matter
# what its device name, comment the line above out. This will only work if
# the system only has one disk.
# In addition, you'll need to specify the method to use.
# The presently available methods are: "regular", "lvm" and "crypto"
d-i partman-auto/method string regular

# If one of the disks that are going to be automatically partitioned
# contains an old LVM configuration, the user will normally receive a
# warning. This can be preseeded away...
#d-i partman-auto/purge_lvm_from_device boolean true
# And the same goes for the confirmation to write the lvm partitions.
#d-i partman-lvm/confirm boolean true

# You can choose from any of the predefined partitioning recipes.
# atomic: All files in one partition (recommended for new users)
# home: Separate /home partition
# multi: Separate /home, /usr, /var, and /tmp partitions
# small_disk (alpha architecture only):
# Small-disk (< 1GB) partitioning scheme

d-i partman-auto/choose_recipe select expert

d-i partman/confirm_write_new_label boolean true
d-i partman/choose_partition select finish
d-i partman/confirm boolean true
d-i partman-lvm/confirm boolean true

# Or provide a recipe of your own...
# The recipe format is documented in the file devel/partman-auto-recipe.txt.
# If you have a way to get a recipe file into the d-i environment, you can
# just point at it.
#d-i partman-auto/expert_recipe_file string /hd-media/recipe

# If not, you can put an entire recipe into the preconfiguration file in one
# (logical) line. This example creates a small /boot partition, suitable
# swap, and uses the rest of the space for the root partition:
d-i partman-auto/expert_recipe string \
      boot-root :: \
       100 200 200 ext3 \
                      $primary{ } $bootable{ } \
                      method{ format } format{ } \
                      use_filesystem{ } filesystem{ ext3 } \
                      mountpoint{ /boot } \
              . \
              500 200000 20000 ext3 \
                      method{ format } format{ } \
                      use_filesystem{ } filesystem{ ext3 } \
                      mountpoint{ / } \
              . \
              12000 200000 -1 ext3 \
                      method{ format } format{ } \
                      use_filesystem{ } filesystem{ ext3 } \
                      mountpoint{ /home } \
              . \
              64 512 150% linux-swap \
                      method{ swap } format{ } \
              .

# This makes partman automatically partition without confirmation, provided
# that you told it what to do using one of the methods above.
d-i partman/confirm_write_new_label boolean true
d-i partman/choose_partition select finish
d-i partman/confirm boolean true

Revision history for this message
Allo (allo) wrote :

can be closed, problem was lucid is less tolerant, if the second size value is too large for the disk.

Changed in partman-partitioning (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.