Red Hat Bugzilla – Bug 49218
Anaconda exception at grub installation
Last modified: 2007-04-18 12:34:47 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010716
Description of problem:
For the first install using beta2 everything went perfectly up until
it got to post install where it gave a traceback.
Steps to Reproduce:
1. Normal install of workstation using Gnome
Actual Results: Traceback given during post install.
Created attachment 23767 [details]
Traceback file created
To try to pin this down some... IDE or SCSI drives? Any hardware RAID
controllers? Software RAID used for / or /boot?
Look at beta hardware description #19, this was done installing to
This machine has three drives, hda, sda, sdb.
This is a very similiar problem encountered with beta1, look to
Sorry didn't say but NO RAID at all.
This defect considered MUST-FIX for Fairfax gold-release.
It's a bit different from the traceback in beta1 -- did you try to install the
bootloader to the MBR or the boot partition?
Created attachment 24068 [details]
Beta2 install log
Finally got it to install, hate to tell you what I did. I thought I had
tried all the modes, since I normally start with the text mode.
Anyway going back once again to the text mode and it allowed me the
choice of whether to use grub or lilo and it installed just fine.
However in the graphic mode this option never comes up, so I assume it
defaulted to grub and installing to the MBR but it gave the traceback
Can you reproduce it in GUI mode still with beta2 and the update disk at
Sorry to be dense but how do you use this update img ?
To quote from msf's message to testers-list --
"Just use this like any updates disk for the installer, ie., put a 'updates' at
the end of the command line you give the boot disk (use the beta 2 boot disk, it
is not changed) and you will be prompted to insert the update disk.
To make the update disk, download the file above and
dd if=update-disk-07182001.img of=/dev/fd0 bs=1440k"
Sorry I had already done that, it just won't boot from the disk. I tried
it on a couple of different machines.
You boot with the normal boot disk (/cdrom) and just type linux updates at the
syslinux prompt and insert the update disk when prompted
Ok this image works just fine in the Graphic mode.
Created attachment 25290 [details]
Traceback after the full install got almost completed.
Got this same respsonse doing a full install on beta 3 [Roswell] using this
same hardware, beta hardware description #19.
It goes through the complete install, up to the install of lilo,grub never
asking which one I want then crashes with the traceback attached.
I then went back and tried to use the old update.img I used to install with
beta2 but this crashed right away, I didn't save that traceback but assumed
since it was the one you gave me for beta2 it wouldn't work.
Not sure if I did this last one right, but since this started as a
beta2 bug, I just reopened this bug for beta3 since it appears to
be the same.
Or should it have just been opened as a new bug under beta3 ?
*** Bug 50260 has been marked as a duplicate of this bug. ***
There should be a screen right after the partitioning screen which offers you
various bootloader options, including at the top of the screen, which bootloader
you wish to use. And you don't see this screen?
No, after the Disk setup screen, I see the "boot loader password configuration
screen"which says I have already picked GRUB and only allows me to
input a grub password.
This is the same thing that happened with beta2 until the updated img
Something I forgot to mention, this is using beta3 and the hardware is
beta hardware description #19 which has 3 drives in the machine.
hda has windows installed.
sda has debian installed.
sdb is being used for beta testing.
One last thing I noticed I didn't mention, this only seems to occur
in Gui or expert modes, text seems to work fine.
Text mode gives me the choice of lilo or grub during the install process.
Tracked to being due to expert mode magic... fixed in CVS