--onpart conflicts with --clearpart. In order to use --onpart, the partition must already exist. When you specify --clearpart, it clears the partition table, so the partition can't exist! Ditch the --clearpart, use fdisk in the %pre section, and achieve partitioning nirvana. On Fri, Mar 30, 2001 at 02:41:49PM -0800, Carl Riches declared the following: > > I am trying to install Red Hat 7.0 on a Dell PowerEdge 1550 rackmount > server. The installation requires kickstart due to some special hardware > initialization, and Dell provides a model ks.cfg file for this. However > this file needs to be modified for our local needs, and the file fails in > the disk partitioning section of the kickstart process. Anaconda barfs > and puts this message on the screen: > > Traceback (innermost last): > File "/usr/bin/anaconda", line 438, in ? > intf.run(todo, test = test) > File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/text.py", line 1030, in run > rc = apply (step[1](), step[2]) > File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/textw/partitioning_text.py", line 134, in __call__ > todo.lilo.allowLiloLocationConfig(todo.fstab) > File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/lilo.py", line 124, in allowLiloLocationConfig > if bootDevice[0:2] == "md": > TypeError: unsliceable object > > Local variables in innermost frame: > fstab: <fstab.NewtFstab instance at 828a128> > self: <lilo.LiloConfiguration instance at 82702d8> > bootDevice: None > > ToDo object: > (itodo > ToDo > p1 > (dp2 > S'method' > p3 > (iimage > CdromInstallMethod > p4 > (dp5 > S'progressWindow' > p6 > > <failed> > > > Here is the disk partitioning section of the ks.cfg file: > > zerombr yes > clearpart --linux > part / --size 256 --ondisk sda --onpart sda2 > part /usr --size 4000 --ondisk sda > part swap --size 2000 --ondisk sda > part /tmp --size 256 --ondisk sda > part /var --size 512 --ondisk sda > part /opt --size 512 --ondisk sda > part /home --size 256 --ondisk sda > part /ws --size 128 --ondisk sda --grow > > /dev/sda1 contains a system utility partition that Dell puts onto the disk > as part of the initialization process. I want the Linux root partition > (/) to end up as sda2. Is there a bug in kickstart that is not letting me > do this? > > Thanks, > Carl G. Riches > Software Engineer > Department of Mathematics > Box 354350 voice: 206-543-5082 or 206-616-3636 > University of Washington fax: 206-543-0397 > Seattle, WA 98195-4350 internet: riches@xxxxxxxxxxxxxxxxx > > > > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/kickstart-list -- Randolph R. Russell Phone: 919-547-0012 x333 RHCE Certification Manager FAX: 919-547-0024 Red Hat, Inc. Email: rrussell@xxxxxxxxxx gpg: 1024D/B04CC2D6 5602 3F73 E70A D0BE 1923 D1D0 9CCD EA1C B04C C2D6
Attachment:
pgpfcA5LAnKWf.pgp
Description: PGP signature
