FS#26645 - Suppord reusing existing LVM setup

Attached to Project: Release Engineering
Opened by Bohumil Kriz (krizb) - Thursday, 27 October 2011, 11:10 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Monday, 26 November 2012, 04:51 GMT
Task Type Bug Report
Category AIF
Status Closed
Assigned To Dieter Plaetinck (Dieter_be)
Architecture All
Severity Medium
Priority Normal
Reported Version testbuild (specify!)
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Installation from latest core x86-64 CD, following instructions on:
https://wiki.archlinux.org/index.php/LVM

1. for regeneration kernel shoud be
mkinitcpio -p linux -b /mnt
instead of
mkinitcpio -p linux
because partitions of installed system is mounted to /mnt before firest reboot.

2. only "just created" LVM partitions can be selected for installation.
I had installation of another linux system (ScientificLinux 6) in the same VG,
but installation script didn't allowed me to select any of it's partitions
(I wanted to use swap partiton).
I don't know if it is a bug or "feature". It was not a problem to use older partitions
later, but it was just inconvinient for me.

Regards,

Bohumil
This task depends upon

Closed by  Gerardo Exequiel Pozzi (djgera)
Monday, 26 November 2012, 04:51 GMT
Reason for closing:  Deferred
Comment by Dieter Plaetinck (Dieter_be) - Thursday, 27 October 2011, 14:45 GMT
1) update the wiki page then? those instructions are not official, and are by the community, for the community. be part of the community.
2) I guess I could make AIF read already existing LVM setups, but that's a low-prio feature request. (as your use case is exceptional)
Comment by Nikolai Maziashvili (mkudro) - Sunday, 15 April 2012, 13:17 GMT
Regarding point one - if everything went OK you shouldn't have to run mkinitcio yourself. At the end of the installation process aif (being already chrooted into /mnt) will run that for you and asks you in the end about installing bootloader. If mkinitcpiio wasn't run then you should file a bug (i think) couse aif suppose to do it automatically. Well supposed to is i assumption i guess, better woring would be - one would expect aif to do that automatically :).

Regarding point two - before running /arch/setup you should "enable" logical volume in volume group which you intend to use. Or just enable them all for ease - [code]vgchange -ay[/code]. Otherwise they will not how up in the list.
RH lets anaconda to do that step for you, here you gotta do it yourself....i don't think arch users would really mind this ;).

Loading...