I have a 22GB IBM DeskStar GXP model DJNA-372200, and a new 
motherboard whose BIOS detects the drive as having 43800 cylinders, 
16 heads 63 sectors, for a total size of 22606MB (this in NORMAL mode 
(award BIOS))

first the annoying but not critical problem, the bios shows the disk 
capacity as 22606, but when I check to see what the capacity I can 
get out of it from fdisk (by creating one full disk partition and 
checking the size) I only get 21145 or something close to that, about 
1000 MB are `missing' and unavailable, is this an fdisk bug? or is 
the BIOS wrong? I know disks often dont have the capacity advertised 
but a whole GB...??

now the obnoxious problem:

I want to farm out my partitions and have enough so that i may have 2 
distributions installed at once...

now when I try and partition this with the fdisk on redhat 6's 
installer, as soon as I start adding partitions to the extended 
partition the `v' command in fdisk gives a bunch of errors saying 
that partition 3 is overlapping partition 5 and partition 5 over laps 
6 and 6 overlaps 7 and so on till the last one which says it is not 
completely inside partition 4 (the extended partition) now it will 
write the table and does not seem to care, but when I hit done in 
redhats dialog asking whether to edit the device go back or continue 
it complains that there are not enough resources to read the 
partition table on /dev/hda, disk druid refuses to even look at the 
disk at this point and going back to fdisk works but the only thing 
that will fix it is removing the extended partition.

this is fdisk 2.8 for redhat...

I then decided to try a debian boot disk (of which I have no CD yet) 
and used its fdisk (version 2.9) and it will partition everything 
with no errors in a verify (v) except for about 1154 unused sectors 
it saves the partition table fine and the debian installer can make 
filesystems on the partitions just fine, but since I have no CD yet I 
cannot install debian (which is going to be my primary distribution 
next to redhat, if redhat will ever go) so I reboot back to the 
redhat installer and this time dont edit the partition table since 
its been done by the debian fdisk, still complains about no resources 
to read partition table blah blah blah, and going into fdisk and 
verifiying the table shows all the same errors it did when i had used 
it to do the partitioning...

ideas?


Best Regards,
Ethan Benson
To obtain my PGP key: http://www.alaska.net/~erbenson/pgp/

Reply via email to