Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 85066 - exception occured during disk partitioning
Summary: exception occured during disk partitioning
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 8.0
Hardware: other
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-02-25 09:15 UTC by Francisco Jorge
Modified: 2007-04-18 16:51 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-02-25 12:09:32 UTC


Attachments (Terms of Use)

Description Francisco Jorge 2003-02-25 09:15:20 UTC
Description of problem:

When trying to partition the disk with disk-druid, anaconda says that onother 
partitioning tool has wrongly partitioned the disk, but it gives me the option 
of ignoring this error. I ignore it, but then I get the following error:

+-------------+ Exception Occurred +-------------+               
               |                                                |               
               | An unhandled exception has occurred.  This   # |               
               | is most likely a bug.  Please copy the full  # |               
               | text of this exception or save the crash     # |               
               | dump to a floppy then file a detailed bug    # |               
               | report against anaconda at                   # |               
               | http://bugzilla.redhat.com/bugzilla/         # |               
               |                                              # |               
               | Traceback (most recent call last):           # |               
               |   File "/usr/bin/anaconda", line 694, in ?   # |               
               |     intf.run(id, dispatch, configFileData)   # |               
               |   File "/usr/lib/anaconda/text.py", line     # |               
               | 446, in run   
     dispatch.gotoNext()                      # |               
               |   File "/usr/lib/anaconda/dispatch.py",      # |               
               | line 150, in gotoNext                        # |               
               |     self.moveStep()                          # |               
               |   File "/usr/lib/anaconda/dispatch.py",      # |               
               | line 215, 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 184, in setFromDisk        
               |     lvm.vgscan()                             # |               
               |   File "/usr/lib/anaconda/lvm.py", line 38,  # |               
               | in vgscan                                    # |               
               |     raise SystemError, "vgscan failed"       # |               
               | SystemError: vgscan failed                 


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


How reproducible:
Have not tried to reproduce it

Steps to Reproduce:
1.
2.
3.
    
Actual results:
Disk won't get formatted

Expected results:


Additional info:

Comment 1 Francisco Jorge 2003-02-25 12:09:32 UTC
I have found the problem. I was using an installation kernel without LVM 
support. I have built a new kernel with LVM support and the error dissappeared.


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