Not all space of hard drive is available

[VitalyPanov]

I just installed new mother board and hard drive 45 GB. But it shows that hard drive has 32 GB only. Please help me to find where the problem is and how to selve it. (I suspect that it could be in BIOS settings)

My mother board is: ABIT KT7-RAID VIA KT133 CHIPSET ULTRA ATA100 ATX FORM FACTOR 1xAGP(4X)/6xPCI/1xISA/3xDIMM

MY hard drive is: IBM 45GB ULTRA-ATA/100 DTLA307045/PN#07N3931 7200RPM 8.5MS 2MB BUFFER
Thank you in advance

 

[alex304]

First of all...what bios and OS are you using. There are known problems with Phoenix BIOS and Win98 when using HDD larger than 32 Gig. Make sure your BIOS is set to use Logical Block Addressing (LBA) translation. I believe there may be a fix for this on the MS website.

Alex

 

[CitrixEngineer]

ABIT KT7's use the brilliant AWARD BIOS.



When you installed the disk, did you choose the Auto Hard Disk detection option? It should have atuomatically set the drive to LBA or offered you the choice.

I know folk who use the DeskStar 75GB and Maxtor 80Gb drives on these boards with no problems.

Maybe there's an updated BIOS flash at

http://www.abit.nl/english/index.htm

Post back if you're still having problems - or have a look at

http://www.arstechnica.com,

where just about everyone seems to use this combination! Or look at

http://www.hardocp.com

I hope this helps

 

[sgwilks]

I just had same problem with my ibm deskstar 46gb drive,found a solution on ibm download page and get feature tool version 1.10,this fixed my problem,also flashed motherboard bios chip.

 

[ShaithisDanoveur]

With FAT32, the theoretical partition size limit is 2 TB (that's TERABYTES). However, Microsoft states that this limit is dependent on the ability of the machine's BIOS to provide proper drive translation. Otherwise, common size limitations I've run into are:

8GB for older machines
32GB for newer machines

I seem to remember a wacky one at 512 GB on the bench a while back as well...

For more complete information regarding the FAT32 file system and its caveats, see

http://support.microsoft.com/support/kb/articles/Q154/9/97.ASP

 

[Guest_imported]

I don't know if you have solved your problem yet.

I have the same one. I have been told these drives are "dual platter" type drives. I know that name doesn't make sense but.... the drives are split into two.

One 32 gig and One 13 gig... 32+13 = 45.

When I fdisked the drive fdisk recognized either the 13 or the 32 depending on my jumper settings. The remaining portion of the drive was seen but an error reading "drive two" was given....

I am sure you noticed the dual jumper areas on the back of the drive.

I have not figured out the correct jumper settings yet to get the whole drive recognized....

My search for the answer led me here. If anyone figures this mess out, please post it.

CyBOrz

 

[tecrec]

i've got the same problem so it would be nice if yer solved it to post your results.

i've talked just to about averyone and i must say it is a bios problem... mostly award i believe.

i've got a kt7raid also and i'm waiting for abit to post an update which solves this problem. My HD however is a Maxtor 40Gb and there are some maxtor utilities that suppossedly solve it...

anyway. if you find your way around it, please tell us. If i do, i will certainly.

tak!

d-.

 

[Guest_imported]

Hello there,

Not sure if this information is totally applicable (at least not hardware wise), but anyway...

I just bought a 40 gbyte Seagate drive and installed it on my PC which uses an ATC6220 motherboard. At first, the drive wasn't detected even with automatic settings in the CMOS, so I had to set a jumper on the disk in order to present a maximum size of 32 gbytes (if 32 was the limit) or 2 gbytes (if 2 was the limit). The drive was then detected. However, using fdisk, the drive could not be partitioned to use all 40 gytes, only 32 - the limit set by the switch. Seagate provide an application called DiskManager that allows the BIOS to see all 40 gbytes and partition and format accordingly. My original master could then be copied onto the new slave before setting the slave to be the master, removing the old master and, voila, I now have a 10 gbyte application partition and a 30 gbyte data partition.

It's quite likely that each disk manufacturer is sure to provide something similar and, given that this is a frequent problem, to provide a jumper setting to limit the size to 32 gbytes.

Don't know if this is any help.

Cheers.