Hello,
i tryed to autoinstall two physical volumes, one on /dev/sda4 and one on
/dev/sdb, with the same volume_group system. But it won't work. Following my
partition section. The error message where "vgcreate -A n -s 4096k system
/dev/system vgcreate -- ERROR can't create a new physical volumes on
/dev/sda4".
Listing:
<partitioning config:type="list">
<drive>
<device>/dev/sda</device>
<reuse>all</reuse>
<partitions config:type="list">
<partition>
On Tue, 2 Jul 2002, Georg Wallner wrote:
i tryed to autoinstall two physical volumes, one on /dev/sda4 and one on /dev/sdb, with the same volume_group system. But it won't work. Following my partition section. The error message where "vgcreate -A n -s 4096k system /dev/system vgcreate -- ERROR can't create a new physical volumes on /dev/sda4".
This does not work with the current autoyast system - I hope Anas is working on this issue... Yours, Volkmar -- Volkmar Glauche Department of Neurology E-Mail glauche@uke.uni-hamburg.de UKE Hamburg WWW http://glauche.home.pages.de/ Martinistr. 52 Phone 49(0)40-42803-5781 20246 Hamburg Fax 49(0)40-42803-9955
* Georg Wallner
Hello,
i tryed to autoinstall two physical volumes, one on /dev/sda4 and one on /dev/sdb, with the same volume_group system. But it won't work. Following my partition section. The error message where "vgcreate -A n -s 4096k system /dev/system vgcreate -- ERROR can't create a new physical volumes on /dev/sda4".
This problem, is 'partly' solved in the updated package. The only problem currently available is when you try to configure LVM using autoinstall on an already configured disk, i.e. you installed LVM and now you are trying to install again. Then yast might complain that the VG is already there. I have dome several tests and with a blank harddsik (or a harddisk without previous LVM configuration) it works fine.
Listing: <partition> <size>max</size> <filesystem-id config:type="integer">142</filesystem-id> ^^^^^^^^^^^^^^ should be filesystem_id, and normally not needed if lvm_group is defined.
system </partition> </partitions>
Anas
--
Anas Nashif
Helo,
Am Freitag, 5. Juli 2002 04:50 schrieb Anas Nashif:
This problem, is 'partly' solved in the updated package. I use the package rpm -qa | grep -i auto Yast2-trans-autoinst-2.5.14-6 Yast2-module-autoinst-2.5.26-0 Are there newer ones?
The only problem currently available is when you try to configure LVM using autoinstall on an already configured disk, i.e. you installed LVM and now you are trying to install again. Then yast might complain that the VG is already there. I have dome several tests and with a blank harddsik (or a harddisk without previous LVM configuration) it works fine. After I fail wiht autoinstallation, i do following: dd if=/dev/zero of=/dev/sda bs=1k count=100 dd if=/dev/zero of=/dev/sdb bs=1k count=100 With this, the partition table should be erased, and a new LVM should be possible.
My already listing:
<partitioning config:type="list">
<drive>
<device>/dev/sda</device>
<partitions config:type="list">
<partition>
participants (3)
-
Anas Nashif
-
Georg Wallner
-
Volkmar Glauche