Red Hat Bugzilla – Bug 43435
RH 7.1 will not install
Last modified: 2005-10-31 17:00:50 EST
Description of Problem:
system failed during upgrade from 7.0 to 7.1
I have an anacdump.txt
Steps to Reproduce:
1. install from disk
Traceback (innermost last):
File "/usr/bin/anaconda", line 520, in ?
intf.run(todo, test = test)
File "/var/tmp/anaconda-7.1//usr/lib/anaconda/gui.py", line 391, in run
File "/var/tmp/anaconda-7.1//usr/lib/anaconda/gui.py", line 879, in run
File "/usr/lib/python1.5/site-packages/gtk.py", line 2554, in mainloop
File "/usr/lib/python1.5/site-packages/gtk.py", line 125, in __call__
ret = apply(self.func, a)
File "/var/tmp/anaconda-7.1//usr/lib/anaconda/gui.py", line 481, in
next = self.currentScreen.getNext ()
File "/var/tmp/anaconda-7.1//usr/lib/anaconda/iw/lilo_gui.py", line 101,
File "/var/tmp/anaconda-7.1//usr/lib/anaconda/lilo.py", line 483, in
raise IndexError, "unknown lilo label %s" % (default,)
IndexError: unknown lilo label None
Local variables in innermost frame:
self: <lilo.LiloConfiguration instance at 8567cf0>
Can you attach your existing /etc/lilo.conf file?
I did not originally submit this bug report, however i am experiencing the same
difficulties. Server is as follows.
HP Netserver 2000
SCSI 3 MegaRaid controller - Raid 5 array with 3 18 gig SCSI's Ultra 160
One Intel NIC - Pro100
Dual CUMine 533 processors
256 ECC Registered Memory
Ultra2 Onboard SCSI - SCSI CDRom
I am assuming you would like the lilo.conf file sent to firstname.lastname@example.org.
Please let me know if you would like it sent to a different location.
Created attachment 20742 [details]
here is a lilp.conf file that you requested
email@example.com, can you attach your complete debug error message that
Anaconda displays when it crashes?
Created attachment 20864 [details]
here is the bug report created during the installation
firstname.lastname@example.org, I think you are having a totally different problem. Your
issue looks like a duplicate of bug #37099.
The original bug reporter has still not responded, so I'm closing this bug due
to inactivity. email@example.com, please reopen this bug if you have more