Bug 45500 - Anaconda fails if you have an extended partition with no local volumes
Summary: Anaconda fails if you have an extended partition with no local volumes
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Brent Fox
QA Contact: Brock Organ
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-06-22 11:10 UTC by Vidar Langseid
Modified: 2007-04-18 16:33 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2001-06-25 22:19:12 UTC


Attachments (Terms of Use)

Description Vidar Langseid 2001-06-22 11:10:54 UTC
Description of Problem:

Sometimes you may want to partition the disk more after the installation
is done. If you create an extended partition under the installation, but
do not create a logical volume, you are in trouble. Anaconda aborts the
installation and you have to reboot.

Next time you boot up anaconda it stops BEFORE you are asked if you want to
partition the disk with fdisk or disk druid.

In order to fix it you have to press [Ctrl] + [Alt] + [F2] and start fdisk
manually

How Reproducible:Always


Steps to Reproduce:
1. Create boot part = 50Mb, hda1
2. Create swap =256Mb, hda2
3. Create root part = 4000Mb, hda3
4. Create a extended part, hda4
5. Do NOT create any logical volumes

Actual Results:
Anaconda shows an error message :
"An error occured reading the partition table  for the block
device hda. The Error was:

Logical partition of type 0 detected

..."

Expected Results:
The installation should continue, or at last give you a chance to fix it.

Additional Information:

Comment 1 Brent Fox 2001-06-25 22:19:07 UTC
All the existing partitioning code is being replaced, so this issue should not
appear in future releases.


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