Red Hat Bugzilla – Bug 61510
anaconda backtrace/related to grub.conf?
Last modified: 2007-04-18 12:41:02 EDT
Description of Problem:
backtrace after installing packages over nfs during upgrade of laptop
(hp omnibook 800CT) from rh6.2 to 7.2
Version-Release number of selected component (if applicable):
I'm not going to try. I'd have to reinstall rh6.2 and wouldn't be sure that that
would be the same installation
Steps to Reproduce:
Intend to attach backtrace.
Created attachment 49266 [details]
floppy dump from anaconda with backtrace
Did you have an /etc/grub.conf prior to the upgrade?
No, sorry. The system was, and is, booted using lilo. If there really was one
there at all it got there by accident from an automated script that installed it
when I wasn't looking. (The machine is mostly maintained remotely, but I had to
do the upgrade locally). What would have happened is that a script would have
been run to generate the file. I'll attach a typical grub.conf generated by the
script, but can't guarantee that it looks much like what was there before.
The current /etc/grub.conf is symlinked to /boot/grub/grub.conf, and that dates
from the time of the upgrade.
Created attachment 49305 [details]
A rough guess at what /boot/grub/grub.conf might have looked like
It looks like there was an /etc/grub.conf that wasn't readable but existed (like
a symlink to something non-existent or an absolute symlink). I've made some
changes so that this won't cause the installer to crash for future releases.
Yes, the link is absolute, so that probably was the cause.
The symlinks checks have been around for a while, closing.