Bug 119479

Summary: Anaconda can not detect correctly hard disk partition table
Product: [Fedora] Fedora Reporter: VnPenguin <vnpenguin>
Component: anacondaAssignee: Jeremy Katz <katzj>
Status: CLOSED NEXTRELEASE QA Contact: Mike McLean <mikem>
Severity: high Docs Contact:
Priority: high    
Version: rawhideCC: jlaska
Target Milestone: ---   
Target Release: ---   
Hardware: athlon   
OS: Linux   
URL: http://nguyendai.org/pub/fc2-test2-disk1.png
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-08-15 15:30:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description VnPenguin 2004-03-30 20:47:33 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040126

Description of problem:
FC2-test2 installer can not detect correctly partition table of my
hard disk (Maxtor 80GB, LBA).
There are so many "Free space" with size <1, the same Start & End point.
See screenshots:
http://nguyendai.org/pub/fc2-test2-disk1.png
http://nguyendai.org/pub/fc2-test2-disk2.png

The same problem with FC2-test1. But RH9 and FC1 installers work well,
partition table was detected correctly.

The hard disk was partitionned by Partition Magic 8.0.


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Disk Partitioning Setup
2. Manually partition with Disk Druid
3. Next
4. Disk Setup --> problem!
    

Actual Results:  Stopped installation by myself because I have problem
with FC2-test1: by proceeding the installation, access mode of my hard
drive was modified by installer(?) and GRUB cann't boot at all. The
problem has fixed by redefining manually accesse mode in BIOS.

Expected Results:  Would like to see Anaconda could detect correctly
HDD like FC1!

Additional info:

Comment 1 Jeremy Katz 2004-04-15 17:58:30 UTC
Fixed in CVS

Comment 2 Jeremy Katz 2004-06-09 21:25:35 UTC
*** Bug 118440 has been marked as a duplicate of this bug. ***