Bug 39726 - diskdruid not partitioning whole hard drive / autopartitioning fails
Summary: diskdruid not partitioning whole hard drive / autopartitioning fails
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer
Version: 7.1
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Brent Fox
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-05-08 22:28 UTC by Jonathan M. Slivko
Modified: 2007-04-18 16:33 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-05-18 19:15:19 UTC
Embargoed:


Attachments (Terms of Use)

Description Jonathan M. Slivko 2001-05-08 22:28:29 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 95)

Description of problem:
I have a 13.6GB drive. However, the Red Hat 7.1 installer will not use the 
whole drive, it will leave 4.7xGB free, unpartitioned when partitioning 
into 1 partition. However, when making several partitions, 100% of the 
drive can be used.

How reproducible:
Always

Steps to Reproduce:
1. Run bootnet.img / drivers.img from floppy
2. load up NIC card driver
3. Go through install until autopartitioning, which will fail.
4. Select disk druid from menu option
5. Create swap and / partitions only
6. look at disk usage, huge ammounts of space are left over.

Actual Results:  I couldn't use all 13.6GB of my drive

Expected Results:  All 13.6GB should have been used on the drive.

Additional info:

Comment 1 Brent Fox 2001-05-09 14:38:14 UTC
Can you go to VC2 and type 'mknod hda' and then 'fdisk -l hda'.  That will tell
you what the partition table currently looks like.  Can you post the output of
that here?  There could be some older partitions left over from the past.  We
have not seen this kind of behavior with Disk Druid before.

Comment 2 Brent Fox 2001-05-18 19:15:14 UTC
Closing due to inactivity. Please reopen if you have more information.


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