[WBEL-users] Problem with kickstart

[Alex Tkachenko]

On Sat, 2004-05-01 at 07:04, Steve Phillips wrote:
> On Fri, 2004-04-30 at 23:41, Alex Tkachenko wrote:
> > Hi everybody,
> > 
> > I installed one system using GUI installer, and then I am trying to use
> > the same configuration to install another one (on identical platform)
> > using generated anaconda-ks.cfg. Installation fails with the message:
> > 
> > Traceback (most recent call last):
> >   File "/usr/bin/anaconda", line 1042, in ?
> >     instClass.setInstallData(id)
> >   File "/usr/lib/anaconda/kickstart.py", line 1207, in setInstallData
> >     self.readKickstart(id, self.file)            
> >   File "/usr/lib/anaconda/kickstart.py", line 674, in readKickstart
> >     handlers[args[0]](id, args[1:])
> >   File "/usr/lib/anaconda/kickstart.py", line 954, in defineRaid
> >     raise RuntimeError, "Tried to use an undefined partition in RAID
> > specificat"
> > RuntimeError: Tried to use an undefined partition in RAID specification
> > 
> > (output clipped because of minicom)
> > 
> > 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
> > 
> > Any help will be greatly appreciated.
> > 
> The exact same thing happens with RHEL 3, with this config, so it's not
> just a WBEL 3 issue. Also, there is no way to create that disk config
> using the kickstart GUI... LVM is conspicuously absent. 

Besides, LVM could be set up using only GUI version of the installer;
text version does not support it, that's why I tried to use kickstart -
my system is sitting in the rack and I only have a serial console
connection.

Thanks,
Alex