Bug 10114
Summary: | Problems with fdisk (and disk druid) a large disk drive | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Kevin Arnold <mnimbus> |
Component: | util-linux | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.1 | CC: | juergen, rhw, rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-01-19 21:14:10 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
Kevin Arnold
2000-03-10 19:10:21 UTC
Not sure if this is connected with your problem, but do you have all the partitions starting and finishing on cylinder boundaries? Given the numbers you qoute, I would expect to see the following partition table created: /dev/hda1 * 1 2 16033+ 83 Linux native /dev/hda2 3 198 1574370 b Win95 FAT32 /dev/hda3 199 394 1574370 83 Linux native /dev/hda4 395 3310 23422770 5 Extended /dev/hda5 395 1178 6297448+ b Win95 FAT32 /dev/hda6 1179 1701 4200966 b Win95 FAT32 /dev/hda7 1702 2486 6305481 83 Linux native /dev/hda8 2486 3010 6618748+ 83 Linux native Do those figures look right to you? I got exactly the same problem. I tried several ways to bring it to work, but they all failed. The hard disk is a IBM DPTA 20.5GB. The Mainboard was a Asus P5A. I get the same error messages, even if I append kernel options like "linear" or "hda=..." for the geometry of the disk. A computer with the same disk and a Asus P3BF showed the same behaviour. On a MSI Board with Athlon and this hard disk, I got it without any options to work. (Yes, I tried to install 3 Linux-Windows machines) I searched for differences in addressing or other Bios options, but I found none. Even more curious is the fact, that when I put a hard disk, where it didn4t work in a the computer that runs, the error messages are still there. I don4t believe that both hard disks are defect. I did some experiments and Linux-fdisk fails whenever I try to partition more then about 8GB. If I make the partitions with windows-fdisk, Linux-fdisk can4t read the partition table if there are partitions above 8GB. This limit sounds like a known problem, but even after reading the Large-Disk-Howto and some experiments with kernel options, I found no way to fix the problem. sorry, I found the problem. The jumpers of the hard disk were incorrectly set. Perhaps the above problem is the same. Look for the settings of the jumpers for the number of heads and sectors. Now the installation was no problem. assigned to jbj |