Red Hat Bugzilla – Bug 166774
Anaconda crashes at "Installing Bootloader..." on Kickstart install using SATA
Last modified: 2007-11-30 17:11:12 EST
Description of problem:
Anaconda crashes at the "Installing Bootloader..." stage of kickstart installs
using SATA disks.
File "/usr/bin/anaconda", line 1160 in ? intf.run(id, dispatch)
File "/usr/lib/anaconda/text.py", line 496 in run dispatch.gotoNext()
File "/usr/lib/anaconda/dispatch.py", line 174 in gotoNext self moveStep()
File "/usr/lib/anaconda/dispatch.py", line 242 in moveStep rc =apply(func,
File "/usr/lib/anaconda/bootloader.py", line 172, in writeBootLoader
File "/usr/lib/booty/bootloaderInfo.py", line 1140 in write justConfig | ( not
File "/usr/lib/booty/bootloaderInfo.py", line 846 in writeGrub f.write("(%s)
/dev/%s\n" % (self.grubbyDiskName(drive),
File "/usr/lib/booty/bootloaderInfo.py", line 934 in grubbyDiskName return
"hd%d" % drivelist.index(name)
ValueError: list.index(x): x not in list
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot server with PXE
2. Feed it attached kickstart file
3. Wait for it to be -almost- done.
Grub is installed.
The line in bootloader.py:
return "hd%d" % drives.index(name)
is interesting, but I do not know whether patching it is a possible solution, or
how to patch it.
Created attachment 118112 [details]
Kickstart file sans password
I have found a workaround, commenting out "--driveorder=sda" results in no crashes, although I am
uncertain of why.
Can you provide the complete traceback? What do the drives in your system show
Created attachment 118266 [details]
Current KS file
Strangely, when reverted to the old Kickstart file, I did not get the same
error. The install just froze. I have attached my current, working ks file,
which is very similar.
My servers are dual-Opteron and have 2x120gb and 2x80gb, all SATA barracudas,
that show up as sda through sdd
Still need the traceback...
I am no longer able to duplicate the bug due to changes in other parts of the PXE configuration used on
site. The original bug report contains everything that Anaconda spat out.
The full traceback contains a lot more information including things like the
syslog so that we can see what and how hardware is detected along with various
data structures used by the installer.