Bug 60089 - Crashing creating volume group
Summary: Crashing creating volume group
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-02-19 21:28 UTC by Frank Sweetser
Modified: 2007-04-18 16:40 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:48:29 UTC
Embargoed:


Attachments (Terms of Use)
anaconda traceback of volume group creation crash (63.37 KB, text/plain)
2002-02-19 21:29 UTC, Frank Sweetser
no flags Details

Description Frank Sweetser 2002-02-19 21:28:28 UTC
Created partition table using RH rescue cd

hda1 -> ext3 /boot
hda2 -> swap
hda3 -> lvm
hda4 -> extended
hda5 -> lvm
hda6 -> lvm
hda7 -> lvm
hda8 -> lvm
hda9 -> lvm

hda3 and hda5 were placed into volume group rootvg, which contained the / 
partition.  hda6 and hda7 were placed into homevg, which contained the /home 
partition.  hda8 and hda9 were not placed into any volume groups.  anaconda 
trace attached.

Comment 1 Frank Sweetser 2002-02-19 21:29:56 UTC
Created attachment 46084 [details]
anaconda traceback of volume group creation crash

Comment 2 Frank Sweetser 2002-02-19 21:39:16 UTC
Tried again leaving no LVM partition unallocated, same crash.

Comment 3 Jeremy Katz 2002-02-19 23:06:46 UTC
Did you change the partition layout on the disk?  If so, dupe of 59756

Comment 4 Frank Sweetser 2002-02-19 23:34:02 UTC
No.  The installer did see hda1 as vfat (remenants of a windows install), which
was reselected as format as ext3, but the partition type was already ext2. 
Nothing in the on-disk partition table was changed.

Comment 5 Michael Fulbright 2002-03-26 17:33:03 UTC
Deferring to future release.

Comment 6 Red Hat Bugzilla 2006-02-21 18:48:29 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


Note You need to log in before you can comment on or make changes to this bug.