Hard drive size limitation?

  • Thread starter Thread starter sdkoskey
  • Start date Start date
S

sdkoskey

I installed a new 180GB drive in my 2000 Advanced server
system today. The BIOS recognizes the drive as a 180GB
drive but when I boot into Windows, drive manager only
sees the drive as a 131GB drive. If I fdisk the drive
with a DOS disk, it shows up in Windows as the correct
size, but as soon as I remove the partition to create my
multiple partitions, it reverts back to a 131GB drive.

What am I missing?
 
I installed a new 180GB drive in my 2000 Advanced server
system today. The BIOS recognizes the drive as a 180GB
drive but when I boot into Windows, drive manager only
sees the drive as a 131GB drive. If I fdisk the drive
with a DOS disk, it shows up in Windows as the correct
size, but as soon as I remove the partition to create my
multiple partitions, it reverts back to a 131GB drive.

What am I missing?
Click to expand...

This is a known limitation, and an update patch is available from MS. Check
their website.

Meantime, there's an obvious workaround: W2K will recognise partitions
created with DOS Fdisk, so just use Fdisk to create the partitions you want,
and everything should be OK.
 
-----Original Message-----


This is a known limitation, and an update patch is available from MS. Check
their website.

Meantime, there's an obvious workaround: W2K will recognise partitions
created with DOS Fdisk, so just use Fdisk to create the partitions you want,
and everything should be OK.
Click to expand...


I can create A partition with FDISK. DOS (or Win98 DOS)
doesn't like big drives either. So, it displays the free
space on the drive as something like 50,000 MB. If you
use the whole thing to create one big partition, it
actually uses the entire 180GB. I haven't tried to split
the drive up using the incorrect 50GB display by
percentage. It may work.
The one problem I've run into though, is that if I create
the partition using DOS Fdisk, when I pull it up in
Windows and try to convert it to a Dynamic disk, it fails
because it can't find enough free space at the end of the
drive to complete the conversion.
Seems like I get one feature or the other but I can't get
both.
I'll try to find the fix on the MS web site.

Thanks for the reply Wolf.
 
This is normal
You need 1MB of free unpartitioned space for the operation to complete.This
space is needed for Windows to recreate and store the imformation of
upgraded disk.
 
Back
Top