Red Hat Bugzilla – Bug 64651
Anaconda Crash
Last modified: 2007-04-18 12:42:29 EDT
Description of Problem: Tried to upgrade from 7.2 to 7.3 Version-Release number of selected component (if applicable): 7.3-7 Actual Results: Upgrade Crashed after all components installed, when trying to update boot loader (Dump log below shows trying to run Lilo, but I use Grub!) Expected Results: Successful upgrade. Additional Information: Anaconda Dump: Traceback (innermost last): File "/usr/bin/anaconda", line 633, in ? intf.run(id, dispatch, configFileData) File "/usr/lib/anaconda/gui.py", line 353, in run self.icw.run (self.runres, configFileData) File "/usr/lib/anaconda/gui.py", line 814, in run mainloop () File "/usr/lib/python1.5/site-packages/gtk.py", line 2676, in mainloop _gtk.gtk_main() File "/usr/lib/anaconda/gui.py", line 529, in handleRenderCallback self.currentWindow.renderCallback() File "/usr/lib/anaconda/iw/progress_gui.py", line 135, in renderCallback self.intf.icw.nextClicked() File "/usr/lib/anaconda/gui.py", line 417, in nextClicked self.dispatch.gotoNext() File "/usr/lib/anaconda/dispatch.py", line 144, in gotoNext self.moveStep() File "/usr/lib/anaconda/dispatch.py", line 209, in moveStep rc = apply(func, self.bindArgs(args)) File "/usr/lib/anaconda/bootloader.py", line 893, in writeBootloader justConfigFile, intf) File "/usr/lib/anaconda/bootloader.py", line 732, in write justConfig | (self.useGrubVal)) File "/usr/lib/anaconda/bootloader.py", line 651, in writeLilo catchfd = 2, closefd = 1) File "/usr/lib/anaconda/iutil.py", line 118, in execWithCapture raise RuntimeError, command + " can not be run" RuntimeError: /mnt/sysimage/sbin/lilo can not be run Complete log file attached to bug.
Created attachment 56764 [details] Anaconda Dump
Please boot the installer with the 'linux mediacheck' option and test your CDs. They appear to be bad.
The CDs are very doubtful to be bad because I have successfully used them installing other machines. And they were burned from ISO files that had the exact same MD5 sum as was listed on your ftp site. I will try MediaCheck next time I use them, but I don't think it is a bad CD.
Different CD drives handle media differently in my experience with hundreds of bug reports :( Let us know if mediacheck passes on the system in question.
Sorry to take so long in getting back. I ran MediaCheck and all three discs passed the test. This WAS on the machine that had problems.
Thank you for testing the CDs - will assign to an engineer.
During the upgrade, did the bootloader screen say that it had detected grub or lilo? Also, what do your lilo.conf and grub.conf look like?
Answer 1) Lilo was detected, but I selected the option to replace with grub. There was no grub.conf before that time since lilo was in use. Lilo.conf was something similiar to the following (reconstructed from memory and looking at another lilo.conf, I am not physically at the machine in question and since it's a stand alone, I cannot access it remotely to look at the real one) prompt timeout=30 default=linux boot=/dev/hde map=/boot/map install=/boot/boot.b message=/boot/message lba32 image=/boot/vmlinuz-2.4.7-10 label=failsafe initrd=/boot/initrd-2.4.7-10.img read-only root=/dev/hde6 image=/boot/vmlinuz-2.4.18 label=linux initrd=/boot/initrd-2.4.18.img read-only root=/dev/hde6
Okay, I've added some sanity checking to the code in CVS to try to ensure this doesn't happen in the future