Bug 704259 - ValueError: Cannot remove extended partition sda4. Logical partitions present.
Summary: ValueError: Cannot remove extended partition sda4. Logical partitions present.
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 15
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: anaconda_trace_hash:47041493260f7ddc4...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-12 15:34 UTC by Juan Manuel Rodriguez
Modified: 2011-05-17 18:43 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-17 18:43:00 UTC
Type: ---

Attachments (Terms of Use)
Attached traceback automatically from anaconda. (688.69 KB, text/plain)
2011-05-12 15:34 UTC, Juan Manuel Rodriguez 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Juan Manuel Rodriguez 2011-05-12 15:34:00 UTC 
The following was filed automatically by anaconda:
anaconda 15.27 exception report
Traceback (most recent call first):
  File "/usr/lib/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 367, in _removeDevice
    "Logical partitions present." % dev.name)
  File "/usr/lib/python2.7/site-packages/pyanaconda/storage/devicetree.py", line 411, in registerAction
    self._removeDevice(action.device)
  File "/usr/lib/python2.7/site-packages/pyanaconda/storage/__init__.py", line 855, in destroyDevice
    self.devicetree.registerAction(action)
  File "/usr/lib/python2.7/site-packages/pyanaconda/partIntfHelpers.py", line 202, in doClearPartitionedDevice
    storage.destroyDevice(p)
  File "/usr/lib/python2.7/site-packages/pyanaconda/iw/partition_gui.py", line 1314, in deleteCB
    device):
ValueError: Cannot remove extended partition sda4.  Logical partitions present.
Comment 1 Juan Manuel Rodriguez 2011-05-12 15:34:16 UTC 
Created attachment 498568 [details]
Attached traceback automatically from anaconda.
Comment 2 David Lehman 2011-05-12 17:45:48 UTC 
It looks like you actually had two crashes. The first one was probably caused by having some partitions in use while performing the install. This led to some bad state in which the on-disk information does not agree with what the kernel/OS sees. To remedy the problem you should either reboot or, if that does not work, use parted to remove the sda5 and sda6 partitions and then try again to install.

Please report the results so I can update the bug's status.
Comment 3 Juan Manuel Rodriguez 2011-05-16 17:55:45 UTC 
Yeah, I had tried both Fedora 14 and Fedora 15 Anacondas to be honest, (And even Centos 5 and Centos 6 where unable to format it) and they decided to mount sda5/6. I could not get them to umount, and even gparted failed to partition both partitions. 

Rebooting did not solve this issue. 

dd if=/dev/zero of=/dev/sda solved the issue, but took about 40 minutes to get blank aa 80gb harddrive. 

I just wanted to report the bug, but since I've managed to solve it, I can't provide more feedback at the moment.
Comment 4 Juan Manuel Rodriguez 2011-05-16 20:36:07 UTC 
Just to clarify, I meant Centos 5.6 and 4.8. Centos 6 isn't out yet.
Comment 5 Chris Lumens 2011-05-17 18:43:00 UTC 
If you are able to reproduce this in the future, please feel free to reopen.  Thanks.
Note You need to log in before you can comment on or make changes to this bug.