Bug 209278 - Anaconda Exception at disk partitioning
Summary: Anaconda Exception at disk partitioning
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda   
(Show other bugs)
Version: rawhide
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2006-10-04 10:01 UTC by Michal Babej
Modified: 2013-07-31 23:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-10-04 15:23:40 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Anaconda exception (49.38 KB, text/plain)
2006-10-04 10:01 UTC, Michal Babej
no flags Details

Description Michal Babej 2006-10-04 10:01:45 UTC
Description of problem:
Anaconda raises Exception while doing disk partitioning

Version-Release number of selected component (if applicable):
not sure, on rescuecd from Oct 2

How reproducible:
possibly always.... at least 3 times it happened to me

Steps to Reproduce:
1. pre-create partitions on disk using VT/2 shell or whatever method (and create
new filesystems on them)
2. boot installation, until anaconda wants partition setup
3. select custom disk layout
4. delete pre-created partitions
5. try to create a new partition
Actual results:
exception, reboot.

Expected results:
normal operation

Additional info:
well, i know its weird to do a pre-partitioned setup, it was a little
experiment, i was playing around with filesystems, wanted to know whether its
possible to create a LUKS/cryptsetup root partition, then i couldn't find out
how, so i gave up and tried to delete part-s and create a normal ext3 one

Comment 1 Michal Babej 2006-10-04 10:01:45 UTC
Created attachment 137728 [details]
Anaconda exception

Comment 2 Chris Lumens 2006-10-04 15:23:40 UTC
This is fixed in Rawhide and will be in FC6 final.

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