Mailinglist Archive: opensuse-autoinstall (116 mails)

< Previous Next >
RE: [suse-autoinstall] autoyast2 and LVM creation
  • From: "Marlier, Ian" <ian.marlier@xxxxxxxxxxxxxxxxxxx>
  • Date: Thu, 3 Mar 2005 18:40:42 +0000 (UTC)
  • Message-id: <66EEBBD3485BB84C90CFA900A0A96E5502E8EA6D@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
And now I'll answer my own question, because I figured it out about 10
seconds after sending this e-mail.

The problem was this parameter:
Which I used when defining the size of the Logical Volume.

Unfortunately, this isn't a supported behavior. You have to specify a
size in the standard <size>XXXgb</size> format.

Which makes sense, but it would be nice to be able to do a
<size>max</size> (if anyone out there who's reading this happens to feel
like making that happen :-)

- Ian

-----Original Message-----
From: Marlier, Ian [mailto:ian.marlier@xxxxxxxxxxxxxxxxxxx]
Sent: Thursday, March 03, 2005 1:37 PM
To: suse-autoinstall@xxxxxxxx
Subject: [suse-autoinstall] autoyast2 and LVM creation

I found a message about this exact problem from way back (7 April 2004
but there wasn't an answer to it. I'm hoping that there might be one

When running an autoinstall using a control file that has an LVM group
configured in it, I consistently get an error that the Logical Volume
needs more space during the software selection configuration section.

After that message times out, the setup process continues, then halts
with an error when it tries to create the Logical Volume. The error in
that case is "lvm create_lv invalid parameter".

Once the second error comes up, I can manually create the Logical Volume
with the standard `lvcreate -n space vg_name` command.

I'm using autoyast2, and installing SuSE pro 9.2.

The relevant section of the configuration file is this:

<partitions config:type=3D"list">
<is_lvm_vg config:type=3D"boolean">true</is_lvm_vg>
<partitions config:type=3D"list">

To unsubscribe, e-mail: suse-autoinstall-unsubscribe@xxxxxxxx
For additional commands, e-mail: suse-autoinstall-help@xxxxxxxx

< Previous Next >
This Thread
  • No further messages