Red Hat Bugzilla – Bug 111147
anaconda traceback when installing on LVM
Last modified: 2007-11-30 17:06:59 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Description of problem:
When trying to install RHEL3-ES after defining LVM partitions,
anaconda crashes after packages selection, but before actually
installing the packages.
Subsequent installation attempts have the LVM partitions already
defined in the Disk Druid (so only volume labels have to be assigned),
but lead to an identical crash.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start installation
2. define LVM partitions
3. select packages
Actual Results: Anaconda traceback
Possibly related to bug #110285 ? (different tracebacks, though)
Hardware : dual IDE drives on IBM BladeCenter HS20 blade.
(Priority set to high, because no install = no RHEL)
Created attachment 96238 [details]
Created attachment 96239 [details]
Created attachment 96240 [details]
Created attachment 96241 [details]
Are you installing without formatting your volumes?
Comment #5 : If I am not mistaken (quite a while ago since I tried the
install, server is idle since then), I formatted on the first attempt,
and not on the second one (as anaconda recognized the LVM partitions
from the previous attempt).
IIRC, the traceback is from the second attempt.
Would you like me to try and perform a new installation, with formatting ?
Yes, that would be very beneficial.
I reinstalled, with RHEL3 AS (academic license) replacing the failed
ES installation. I removed all existing partitions in Disk Druid, and
repartitioned (with appropriate LVM partitions) ; taking no chances, I
selected the default server installation, no extra packages.
Formatting and installation went without a hitch.
I leave it at your discretion whether or not to close the bug ; it
speaks for itself I'll provide you with any extra information/logs you
might see fit.