Bug 90504 - Installer crashes before disk druid or fdisk
Summary: Installer crashes before disk druid or fdisk
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 8.0
Hardware: i586
OS: Linux
medium
high
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-05-08 22:17 UTC by alexCOS
Modified: 2007-04-18 16:53 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-05-13 16:48:26 UTC
Embargoed:


Attachments (Terms of Use)

Description alexCOS 2003-05-08 22:17:10 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)

Description of problem:
Error before partitioning my system..

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.install RH 8.0  , and before choosing Automatic or Disk Druid or Fdisk.
2.
3.
    

Actual Results:  system goes down..

Expected Results:  partition my harddisk with a partitioning tool

Additional info:

Traceback:

File "/usr/lib/anaconda/gui.py",line 632, in nextClicked
self.dispatch.gotoNext()
File "/usr/lib/anaconda/dispatch.py",line 150,in gotoNext
self.moveStep()
File "/usr/lib/anaconda/dispatch.py",line 115,in moveStep
rc=apply(func,self.bindArgs(args))
File "/usr/lib/anaconda/partitioning.py",line 57,in partitionObjectsInitialize
partitions.setFromDisk(diskset)
File "/usr/lib/anaconda/partitions.py",line 185,in setFromDisk
lvm.vgactivate()
File "/usr/lib/anaconda/lvm.py",line 56,in vgactivate
raiseSystemError,"vgchange failed"
System Error:vgchange failed

Comment 1 Michael Fulbright 2003-05-09 16:03:24 UTC
Do you have LVM configured previously on this system?

Comment 2 alexCOS 2003-05-09 16:22:53 UTC
No.. All it was on that computer was a Window 95 machine..

Comment 3 Michael Fulbright 2003-05-13 16:48:26 UTC
We resolved several issues like this one for our current release.


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