Hello, I'm trying to get a kickstart install going with RH 7.0. After getting an install I liked, I used mkkickstart to make the attached ks.cfg, which I copied to a boot disk. When I tried the kickstart install, I got the attached error, with the suggestion that I send it to you. I hope it's useful to you - please let me know if you need more info. -ben heavner ----------------------ks.cfg---------------------------- lang en_US network --bootproto dhcp cdrom device ethernet eepro100 keyboard "us" zerombr yes clearpart --linux part swap --size 259 install mouse genericps/2 timezone America/New_York xconfig --server "SVGA" --monitor "generic monitor" rootpw --iscrypted $1$uSil3.HB$B8Yk7rJp1Qj6vaScWLOsn1 auth --useshadow lilo --location mbr %packages filesystem glibc <--snip--> gnuplot %post ----------------------anacdump.txt----------------------- 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 8285360> self: <lilo.LiloConfiguration instance at 82838c0> bootDevice: None ToDo object: (itodo ToDo Local variables in innermost frame: fstab: <fstab.NewtFstab instance at 8285360> self: <lilo.LiloConfiguration instance at 82838c0> bootDevice: None ToDo object: (itodo ToDo p1 (dp2 S'method' p3 (iimage CdromInstallMethod p4 (dp5 S'progressWindow' p6 <failed>
Passed to QA to reproduce.
verified ... this is an issue with hardware raid cards (such as the SA5300) ... thanks for your report!
Assigning to a developer.
Um... but I don't have a RAID card - I'm installing on a pretty average inexpensive box (no SCSI even)
I had a similar problem. I also generated a kickstart file with mkkickstart. The kickstart file produced contains a swap partition entry and no others: zerombr yes clearpart --all part swap --size 141 install When I added entries for / and /boot like: part /boot --size 20 part / --grow installation proceeded without any problems. Problem remains that anaconda should come with the DiskDruid screen when these lines are left out. The machine I did the install on is an ordinary Intel Pentium system with one IDE drive and no SCSI controller. For reference the first part of the ks.cfg file, that caused the problem follows. I hope this will be of help. My conclusion: This also shows that mkkickstart does not guarantee to produce correct output. ------------- ks.cfg -------------------------------- lang en_US network --bootproto dhcp nfs --server 10.0.22.2 --dir /home/ftp/RH70 keyboard "us" zerombr yes clearpart --all part swap --size 141 install mouse genericps/2 --emulthree timezone Europe/Amsterdam xconfig --server "Mach64" --monitor "generic monitor" rootpw --iscrypted $1$/3a3xfNw$M9m3VVS/q7/8VgNqwjydH/ auth --useshadow lilo --location mbr %packages --- etcetera --- %post ---------------- end of ks.cfg ---------------------------------
This is a problem due the style of the new /etc/fstab - using LABELS instead of devices names, so yes, kickstart failed because you didn't specify a partition structure. I submitted patches months ago to fix this issue but no new RPM yet.... To get my mkkickstart, go to either http://people.redhat.com/wolfgang/mkkickstart or http://www.dork.myip.org
*** This bug has been marked as a duplicate of 18863 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.