Red Hat Bugzilla – Bug 461453
Anaconda crash during install with USB-disk-based ks.cfg
Last modified: 2009-07-14 10:33:04 EDT
Description of problem:
I am seeing a consistent anaconda crash with the following setup. Note that the instructions below assume 1 PATA/SATA HD, and that the USB disk will be assigned sdb and have 1 partition...
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1 - take a revisor-created ISO
2 - store it in a USB flash drive vfat formatted with this script (it stores the whole ISO on disk)
3 - on the syslinux menu, add to the kernel cmdline: ks=hd:sdb1:ks.cfg
4 - when stage 1 asks about the install source, pick 'hard drive' and point it to /dev/sdb1 , path 'iso'
5 - anaconda works through the installation correctly, until it is done with installing rpms...
6 - the anaconda debug dialog pops up...
I entered debugging mode, I found myself in this location of the code
File "/usr/lib/booty/bootloaderInfo.py", line 939, in grubbyDiskName
return "hd%d" % self.drivelist.index(name)
and name was sdb, but self.drivelist was ["sda"].
Created attachment 316026 [details]
Created attachment 316027 [details]
Testing a bit more indicated that the problem is with the disk format. The bug was triggered with the installation running from a vfat-formatted FAT32 partition.
The same disk, repartitioned and reformatted to ext3 completes installation without a hitch.
We might have already fixed this in Rawhide. Can you give us a try and see if it's still a problem?
Are anaconda / anaconda-runtime compatible with F9 in general, and revisor/pungi in particular?
I am seeing the same problem when installing F9 from stock DVD with kickstart on (FAT) USB.
the only way install sompletes is with --clearpart all (which also clears the USB stick with the kickstart info).
--clearpart linux will keep the USB stick intact, but fail on grubby
Can you give this a try with F10?
I will try it out, but it would be a real help if this could be fixed/backported to F9, because I can't yet use F10 for certain computers.
Actually -- narrowed this down to the driveorder option. We are hitting this problem: http://kbase.redhat.com/faq/docs/DOC-15568
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '9'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 9's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 9 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.
If you would like to reopen this bug, it needs to be tested against F11 - storage code has been almost entirely rewritten, and this bug could have been fixed.
We will not be backporting any fixes into previous releases.