Just for the records - this problem appears when you call lvremove
within the /target chroot environment by in-target.
If you remove in-target from your late_command and by this invoke
lvremove within d-i's rootfs, it works.
Andreas
--
To UNSUBSCRIBE, email to
Hi,
We are hitting this too now after years using lvremove in
late_command. Also while Squeeze was testing we were using this
without any problem.
Anyway problem seems to be that the late_command is invoked chrooted
in /target.
While calling lvremove from the debian-installer rootfs
Package: debian-installer
Version: 20090123
Severity: normal
for etch I was using the following preseed lines to setup my systems
partition with LVM:
d-i partman-auto/purge_lvm_from_device boolean true
d-i partman/confirm_write_new_label boolean true
d-i partman/confirm boolean true
d-i
Package: debian-installer
Version: 20090123
Severity: normal
With etch's debian-installer we used the preseed lines below to
automatically setup our partitions. /boot and / as primary
partitions, all others as logical volumes.
d-i partman-auto/init_automatically_partition \
select Guided -
4 matches
Mail list logo
