[WBEL-users] Problem with kickstart
Alex Tkachenko
alex@ingrian.com
Mon, 03 May 2004 12:32:17 -0700
--=-23Q00omXzUU7g/TyTqfn
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
On Fri, 2004-04-30 at 20:41, Alex Tkachenko wrote:
> The part of kickstart file which determines the hard drive layout:
>
> clearpart --linux
> part raid.15 --size=100 --ondisk=hda --asprimary
> part raid.16 --size=100 --ondisk=hdc --asprimary
> part raid.18 --size=12288 --ondisk=hdc
> part raid.17 --size=12288 --ondisk=hda
> part raid.20 --size=100 --grow --ondisk=hdc
> part raid.19 --size=100 --grow --ondisk=hda
> raid /boot --fstype ext3 --level=RAID1 raid.15 raid.16
> raid pv.22 --fstype physical volume (LVM) --level=RAID1 raid.17 raid.18
> raid pv.23 --fstype physical volume (LVM) --level=RAID1 raid.19 raid.20
> volgroup Volume00 pv.22 pv.23
> logvol swap --fstype swap --name=LogVol01 --vgname=Volume00 --size=1024
> logvol / --fstype ext3 --name=LogVol00 --vgname=Volume00 --size=2048
> logvol /var --fstype ext3 --name=LogVol02 --vgname=Volume00 --size=8192
With the layout configuration as per above kickstart installation will
fail to properly parse raided lvm config lines.
To address the issue, two ways are possible.
1. Remove fs type specification; kickstart will guess the right type
from the id, which should start with "pv":
raid pv.22 --level=RAID1 raid.17 raid.18
raid pv.23 --level=RAID1 raid.19 raid.20
OR
2. Put the fstype argument in double quotes:
raid pv.22 --fstype "physical volume (LVM)" --level=RAID1 raid.17
raid.18
raid pv.23 --fstype "physical volume (LVM)" --level=RAID1 raid.19
raid.20
Many thanks to Steve Phillips and Kirby Bohling who helped to find the
way out.
Have a great day,
Alex
--=-23Q00omXzUU7g/TyTqfn
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.0.10">
</HEAD>
<BODY>
On Fri, 2004-04-30 at 20:41, Alex Tkachenko wrote:<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE><FONT COLOR="#006259"><I>The part of kickstart file which determines the hard drive layout:
clearpart --linux
part raid.15 --size=100 --ondisk=hda --asprimary
part raid.16 --size=100 --ondisk=hdc --asprimary
part raid.18 --size=12288 --ondisk=hdc
part raid.17 --size=12288 --ondisk=hda
part raid.20 --size=100 --grow --ondisk=hdc
part raid.19 --size=100 --grow --ondisk=hda
raid /boot --fstype ext3 --level=RAID1 raid.15 raid.16
raid pv.22 --fstype physical volume (LVM) --level=RAID1 raid.17 raid.18
raid pv.23 --fstype physical volume (LVM) --level=RAID1 raid.19 raid.20
volgroup Volume00 pv.22 pv.23
logvol swap --fstype swap --name=LogVol01 --vgname=Volume00 --size=1024
logvol / --fstype ext3 --name=LogVol00 --vgname=Volume00 --size=2048
logvol /var --fstype ext3 --name=LogVol02 --vgname=Volume00 --size=8192</I></FONT></PRE>
</BLOCKQUOTE>
<BR>
With the layout configuration as per above kickstart installation will fail to properly parse raided lvm config lines.<BR>
To address the issue, two ways are possible.<BR>
<BR>
1. Remove fs type specification; kickstart will guess the right type from the id, which should start with "pv":<BR>
<BR>
<FONT COLOR="#006259"><I><TT>raid pv.22 --level=RAID1 raid.17 raid.18<BR>
raid pv.23 --level=RAID1 raid.19 raid.20</TT></I></FONT><BR>
<BR>
OR<BR>
<BR>
2. Put the fstype argument in double quotes:<BR>
<BR>
<FONT COLOR="#006259"><I><TT>raid pv.22 --fstype </I></FONT>"<FONT COLOR="#006259"><I>physical volume (LVM)</I></FONT>"<FONT COLOR="#006259"><I> --level=RAID1</I></FONT> <FONT COLOR="#006259"><I>raid.17</I></FONT> <FONT COLOR="#006259"><I>raid.18<BR>
raid pv.23 --fstype </I></FONT>"<FONT COLOR="#006259"><I>physical volume (LVM)</I></FONT>"<FONT COLOR="#006259"><I> --level=RAID1 raid.19 raid.20</TT></I></FONT><BR>
<BR>
Many thanks to Steve Phillips and Kirby Bohling who helped to find the way out.<BR>
<BR>
Have a great day,<BR>
Alex
</BODY>
</HTML>
--=-23Q00omXzUU7g/TyTqfn--