Bug 13472 - Cannot partition (error reading partition table)
Summary: Cannot partition (error reading partition table)
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer
Version: 6.2
Hardware: i386
OS: Linux
high
high
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-07-04 18:46 UTC by darkwing
Modified: 2005-10-31 22:00 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-10-19 22:06:01 UTC
Embargoed:


Attachments (Terms of Use)

Description darkwing 2000-07-04 18:46:07 UTC
I get this error when using the standard installer, when I use fdisk i can 
see the partition table en edit it. What going wrong. In RH6.1 the same 
thing happened.

Comment 1 Michael Fulbright 2000-07-07 01:41:01 UTC
Could you describe in more detail how you get the error message to occur?

Was this in the text or graphical installer?



Comment 2 darkwing 2000-07-07 18:21:10 UTC
with both the text, graphical and expert installer, this things happens.
The message appears when I select whatfor installation it will be (gnome 
workstation, kde workstation etc.). When i switch to another console and try to 
partitioning with fdisk ('fdisk /tmp/hda') every works fine. The installer v5.x 
give not a problem

Comment 3 Michael Fulbright 2000-07-13 18:48:45 UTC
If you choose custom install can you manually partition using disk druid?


Comment 4 darkwing 2000-07-15 16:27:33 UTC
No, the error message comes before that; it doesn't matter what kind of 
installation I choose..

Comment 5 Michael Fulbright 2000-08-17 20:43:46 UTC
If you do a text install, wait until you get the 'Welcome to ...' screen and hit
'Alt-F2' to goto a screen with a consolve prompt.  Type 'cat /proc/partitions'
and report back what you see.

Comment 6 Michael Fulbright 2000-10-19 22:05:58 UTC
Please reopen this bug if you continue to have problems.


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