[Bug 475864] Re: Unable to kickstart with LVM partition scheme.

2018-06-07 Thread James
I just managed to get kickstart working with an expert recipe in 18.04. First, kickstart doesn't support the backslash syntax, so the entire recipe needs to be on one line. Second, as mentioned in #9, you need to surround the whole recipe with single quotes. Your preseed line should look like

[Bug 475864] Re: Unable to kickstart with LVM partition scheme.

2017-11-01 Thread Jim Campbell
I'm still seeing this on 16.04.3. The 'expert_recipe' partitioning string is being skipped / ignored. i.e., anything that looks like this: --- preseed partman-auto/expert_recipe string \ boot-root :: \ 500 500 500 ext4\ $primary{ }

[Bug 475864] Re: Unable to kickstart with LVM partition scheme.

2016-05-16 Thread Marco Schmidt
I tried the partitioning now for several ours and found a working config for xenial. bootloader --location=mbr clearpart --initlabel --drives sda partition --size 1000 --asprimary --fstype ext4 /boot partition --size 8000 --grow --asprimary pv.local volgroup local pv.local logvol --name root

[Bug 475864] Re: Unable to kickstart with LVM partition scheme.

2016-02-04 Thread Mark Hamzy
I just encountered this issue on xenial. I did define a /boot partition outside of the LVM grouping. FWIW, "d-i partman-auto-lvm/no_boot boolean true" does get past the issue Obviously this bug will never be fixed. :( -- You received this bug notification because you

[Bug 475864] Re: Unable to kickstart with LVM partition scheme.

2012-04-16 Thread Mick Pollard
I was able to get this working in Lucid amd64 with some preseed magic embedded into the kickstart file. This is a snippet from my test kickstart file. clearpart --all --initlabel part /boot --fstype ext4 --size 200 --asprimary part swap --size 1024 part pv.01 --size 1 --grow volgroup rootvg

[Bug 475864] Re: Unable to kickstart with LVM partition scheme.

2012-03-02 Thread rahulpalampur2...@gmail.com
Even now I can't create custom partitions using Kickstart file. It seems to overwrite those changes. Will this bug be solved or not? Its March 2012 now, 2+ years for bug to be in open state!!! -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 475864] Re: Unable to kickstart with LVM partition scheme.

2011-04-22 Thread ddouthitt
A year and a quarter, this bug still exists - and in Ubuntu Server 10.04 LTS. This far on and the bug still isn't assigned, and its importance is Undecided? Let's move on this! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 475864] Re: Unable to kickstart with LVM partition scheme.

2010-03-22 Thread ody
Noticed that my previous work around can be modified to work a little more properly. The reason that the partman-auto/expert_recipe portion of my preseed block was not working was a parse error on the behalf of kickseed. Instead of echoing the preseed information into the preseed.cfg file you

[Bug 475864] Re: Unable to kickstart with LVM partition scheme.

2010-02-25 Thread ody
I have hacked in a solution to this for my implementation using preseeding. My kickstart file now contains the following. # Selecting proper disk preseed partman-auto/disk string /dev/vda # Removing LVM partitions preseed partman-lvm/device_remove_lvm boolean true # Picking LVM preseed

[Bug 475864] Re: Unable to kickstart with LVM partition scheme.

2010-02-24 Thread ody
This is still affecting Lucid as of the builds available on Feb 24. Is there an alternate way to feed kickseed/partman your custom partitioning information that is documented or is this not going to be available by release? I am unable to upgrade my 100 Ubuntu systems beyond Jaunty and I am

[Bug 475864] Re: Unable to kickstart with LVM partition scheme.

2010-02-24 Thread ody
I did further testing today. If you go the route of preseeding partman you can get a little closer to the behavior that was working in Jaunty. I have dropped this into a preseed.cfg file # Selecting proper disk d-i partman-auto/disk string /dev/vda # Removing LVM partitions d-i

[Bug 475864] Re: Unable to kickstart with LVM partition scheme.

2009-12-10 Thread Jacques-Olivier Farcy
Hi, I am also preparing a kickseed file for Karmic deployment. I have the same problem, the lines : clearpart --all --initlabel part swap --size 512 --ondisk sda part / --fstype ext4 --size 8192 --ondisk sda part /home --fstype ext4 --size 1 --grow --ondisk sda Are not working, i have to do a

[Bug 475864] Re: Unable to kickstart with LVM partition scheme.

2009-11-05 Thread ody
** Attachment added: error1 http://launchpadlibrarian.net/35193906/error1 -- Unable to kickstart with LVM partition scheme. https://bugs.launchpad.net/bugs/475864 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs

[Bug 475864] Re: Unable to kickstart with LVM partition scheme.

2009-11-05 Thread ody
Previous attachment was in error. ** Attachment added: error1.png http://launchpadlibrarian.net/35194045/error1.png -- Unable to kickstart with LVM partition scheme. https://bugs.launchpad.net/bugs/475864 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 475864] Re: Unable to kickstart with LVM partition scheme.

2009-11-05 Thread ody
** Attachment added: error2.png http://launchpadlibrarian.net/35194060/error2.png -- Unable to kickstart with LVM partition scheme. https://bugs.launchpad.net/bugs/475864 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. --