automatic partitioning within kickstart does not work

Bug #537421 reported by LiohMoeller on 2010-03-11
50
This bug affects 9 people
Affects Status Importance Assigned to Milestone
kickseed (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: partman-partitioning

Trying to automatically partition a disk during kickstart, using something like this:

# Disk partitioning
bootloader --location=mbr
zerombr yes
clearpart --all --initlabel
part swap --size 1024 --ondisk sda
part / --fstype ext3 --size 2048 --grow --asprimary --ondisk sda

does not seem to work. The partitions are cleared successfully, but the partition layout is not applied. Instead a 'default' layout is suggested and must be confirmed with Enter to proceed the kickstart.

Release: Lucid Daily 2010-03-11

Best Regards
Marcus

Revision history for this message
LiohMoeller (liohmoeller) wrote :

Update: removing the --ondisk sda parameter seems to resolve the problem.

Revision history for this message
Colin Watson (cjwatson) wrote :

It would speed up handling of this bug if you could attach /var/log/syslog and /var/log/partman from a failing installation run (if the installation completes, those files are saved to /var/log/installer/). Thanks in advance.

affects: partman-partitioning (Ubuntu) → kickseed (Ubuntu)
Changed in kickseed (Ubuntu):
status: New → Incomplete
Revision history for this message
Stein Henrik Jensaas (steinhj) wrote :

I confirm this behavior, and will come back with some logs....

Revision history for this message
Stein Henrik Jensaas (steinhj) wrote :

Attached is my /var/log/installer/partman and .. syslog from a installation

Here is a part of my config:
url --url http://no.archive.ubuntu.com/ubuntu
bootloader --location=mbr
zerombr yes
clearpart --drives=sda --initlabel
part / --fstype ext4 --size 15360 --asprimary --ondisk sda
part swap --fstype swap --size 2028 --asprimary --ondisk sda
part /home --fstype ext4 --size 10240 --ondisk sda
part /disk1 --fstype ext4 --size 1024 --grow --ondisk sda

The installation Partition stops with an owerview page suggesting the following partitons:
134.8Gb / ext4 partition on sda1
    8.4Gb swap partition on sda5

(I confirm that the partitioning works if i remove the --ondisk sda )

Revision history for this message
Stein Henrik Jensaas (steinhj) wrote :
Revision history for this message
Stein Henrik Jensaas (steinhj) wrote :

From my syslog:
Mar 12 10:41:44 kickseed: unsupported restriction 'ondisk' for non-RAID
Mar 12 10:41:44 kickseed: unsupported restriction 'ondisk' for non-RAID
Mar 12 10:41:44 kickseed: unsupported restriction 'ondisk' for non-RAID
Mar 12 10:41:44 kickseed: unsupported restriction 'ondisk' for non-RAID
....

Changed in kickseed (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Max (bos) wrote :

Not sure if it's the same problem, but I'm getting unwanted prompts even without 'ondisk'.

==
part /boot --fstype ext2 --size 250
part pv.01 --size 1 --grow
volgroup vg pv.01
logvol / --vgname=vg --size=1 --grow --fstype ext3 --name=root
logvol /tmp --vgname=vg --size=1024 --fstype ext3 --name=tmp
logvol swap --vgname=vg --recommended --name=swap
==

Get a "Before the Logical Volume Manager can be configured, the current partitioning scheme has to be written to disk" prompt with Ubuntu 10.04.

The same kickstart script works fine with Ubuntu 9.10 without any prompts.

Revision history for this message
Mattias Andersson (matand) wrote :

I'm getting exactly the same error when I use either 'onpart' or 'usepart' (Ubuntu 10.10). In addition, the partitioner creates 8 new partitions after sda9, which is not what I was expecting.

My kickseed configuration file:

part /boot --fstype ext4 --size 1024 --asprimary --usepart sda1
part swap --size 4096 --asprimary --usepart sda2
part / --fstype ext4 --size 10240 --asprimary --usepart sda3
part /var --fstype ext4 --size 10240 --usepart sda5
part /usr --fstype ext4 --size 10240 --usepart sda6
part /opt --fstype ext4 --size 10240 --usepart sda7
part /tmp --fstype ext4 --size 10240 --usepart sda8
part /export --fstype ext4 --size 10240 --grow --usepart sda9 --noformat

My syslog file:

Jan 19 12:21:53 kickseed: unsupported restriction '--usepart'
Jan 19 12:21:53 kickseed: unsupported restriction '--usepart'
Jan 19 12:21:53 kickseed: unsupported restriction '--usepart'
Jan 19 12:21:53 kickseed: unsupported restriction '--usepart'
Jan 19 12:21:53 kickseed: unsupported restriction '--usepart'
Jan 19 12:21:53 kickseed: unsupported restriction '--usepart'
Jan 19 12:21:53 kickseed: unsupported restriction '--usepart'
Jan 19 12:21:53 kickseed: unsupported restriction '--usepart'

Revision history for this message
Amit Purohit (amit-purohit) wrote :

I was getting this problem. Though I could fix it by using combination of kickstart and preseed.
I had to add following to the preseed file so that the installation can continue unattened.

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/confirm_nooverwrite boolean true

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments