[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#511442: debian-installer: guided-with-lvm no longer allows multiple primary, partition



On  Tue, 16 Jun 2009 17:15:46 -0400, Anthony Awtrey wrote:
> Well, in some cases it looks like the autopartition-lvm is passing
> around incorrect values for partition sizes and offsets. For example,
> my failure case passes the following parameters to parted-server's
> command_new_partition() function.

Okay, looks like both 516347 and 511442 may have a common root cause

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511442

Ferenc Wagner says in bug 511442: "Then lvm_extents_from_human in lvm-base.sh assumes SI kilobytes [kB] to compute the number of extents to create the LV with, which thus gets a factor of 1024/1000 smaller than expected."

It appears that this new method used to determine sizes may not work in all cases.

I have a number of different systems that I want to use the same preseed partman-auto-lvm expert recipe on. The basic partition structure I want is a root (with the kernel boot files) on a maximum 10GB primary partition with the rest of the disk allocated in an LVM volume. Right now I only have swap and home in the lvm, but I planned on allocating other small volumes for special purposes.

What I have discovered is that changing the size of the primary root partition or adding an additional primary partition influences the way the LVM calculations work or fail. I have about 10 different boxes with different sized hard drives ranging from 40GB to 160GB. I have failed to come up with a single recipe that works across all the different platforms.

The errors range from "Can't have a partition outside the disk!" to "Unexpected error while creating volume group" and those errors change depending on how much space is allocated in the primary partitions. I can often tweak the size of the primary paritions to make one platform work, but then other platforms with different sized partitions will fail.

I have finally given up and gone back to using regular partitions with labels, but I still have a series of hardware / lvm recipe combinations that fail reliably and will be happy to test a fix if someone can tell me how to supersede the signed udeb packages with my updated and unsigned ones.

Tony



Reply to: