I try to install squeeze in a non-interactive / automatic installation using
current stable partman-auto with preseeding using the following recipe:
## Partitioning
d-i partman-auto/disk string /dev/sda
d-i-partman-auto/purge_lvm_from_device boolean true
d-i partman-auto/method string lvm
d-i partman-lvm/device_remove_lvm boolean true
d-i partman-lvm/confirm boolean true
#d-i partman-md/device_remove_md boolean true
#d-i partman-md/confirm boolean true
d-i partman-auto/expert_recipe string \
boot-root :: \
100 1000 512 \
$lvmignore{ } \
$primary{ } $bootable{ } \
method{ format } format{ } \
use_filesystem{ } filesystem{ ext3 } \
mountpoint{ /boot } \
. \
2048 2500 200% linux-swap \
$lvmignore{ } \
method{ swap } format{ } \
$primary{ } \
. \
25000 25000 50000 ext3 \
$defaultignore{ } \
vg_name{ system } \
method{ lvm } \
. \
50000 50000 -1 ext3 \
$defaultignore{ } \
vg_name{ data } \
method{ lvm } \
. \
2000 2000 10000 ext2 \
$lvmok{ } \
in_vg{ system } \
method{ format } format{ } \
use_filesystem{ } filesystem{ ext3 } \
mountpoint{ / } \
. \
5000 5000 50000 ext2 \
$lvmok{ } \
in_vg{ system } \
method{ format } format{ } \
use_filesystem{ } filesystem{ ext3 } \
mountpoint{ /usr } \
. \
10000+100% 10000 10000+120% ext2 \
$lvmok{ } \
in_vg{ system } \
method{ format } format{ } \
use_filesystem{ } filesystem{ ext3 } \
mountpoint{ /var } \
. \
25000 30000 -1 ext2 \
$lvmok{ } \
in_vg{ data } \
method{ format } format{ } \
use_filesystem{ } filesystem{ ext3 } \
mountpoint{ /gluster/xen } \
.
This used to work fine in the past - but now it returns an error partitioning
and creating the LVMs on the very same machinewhere it worked before - only our
local mirrors are updated from the regular upstream mirrors - so it seems
partman changed it's behaviour lately
Regarding the error that occurs I found the following lines in /var/log/partman
:
Jul 26 09:59:28 debconf: Adding [VG] -> [data]
Jul 26 09:59:28 debconf: <-- 0
Jul 26 09:59:28 debconf: --> METAGET partman-lvm/text/in_use description
Jul 26 09:59:28 debconf: <-- 0 In use by LVM volume group data
Jul 26 09:59:28 partman-lvm: Physical volume '/dev/sda5' is already in volume
group 'data'
Jul 26 09:59:28 partman-lvm: Unable to add physical volume '/dev/sda5' to
volume group 'system'.
Jul 26 09:59:28 debconf: --> INPUT critical partman-auto-lvm/vg_create_error
Why does partman try to create the second volume group in the same partition ?
Is there any error in my definition that I don't see?
Any hints from the pro's ?
Cheers
Andreas Balg
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/B24F5E6925C28F49A2EDEB173CBB2C96010FEAE657@SFMEXCCREX.sfdrs.local
