New 300G drive only shows as 128G in Win2K Server

  • Thread starter Thread starter h7qvnk7q001
  • Start date Start date
H

h7qvnk7q001

I installed a new Seagate SATA 300GB drive in a Dell SC420 server. In
Win2K Server's (SP4) disk management, it shows up as 128GB capacity.

I'm not using any form of RAID.

In a 3rd party partitioning program, the new drive reports a capacity
of 286Gbytes (the expected value). I created the new drive's partition
as NTFS (7) using this tool (Terabyte Bootit-NG).

The SC420 has other drives larger than 128G - the primary SATA drive
is 160G, and there is another 300G drive connected by USB2.0 which has
full capacity available in Win2K.

What else is needed to get Win2K Server to recognize a 300G NTFS
volume?

The system already has the 48 bit LBA support (KB305098)
installed since it is working with another 300GB drive.

Is there something else I'm missing? Is there something special about
adding a second SATA drive?

Thanks,

Tim.
 
I installed a new Seagate SATA 300GB drive in a Dell SC420 server. In
Win2K Server's (SP4) disk management, it shows up as 128GB capacity.

I'm not using any form of RAID.

In a 3rd party partitioning program, the new drive reports a capacity
of 286Gbytes (the expected value). I created the new drive's partition
as NTFS (7) using this tool (Terabyte Bootit-NG).

The SC420 has other drives larger than 128G - the primary SATA drive
is 160G, and there is another 300G drive connected by USB2.0 which has
full capacity available in Win2K.

What else is needed to get Win2K Server to recognize a 300G NTFS
volume?

The system already has the 48 bit LBA support (KB305098)
installed since it is working with another 300GB drive.

Is there something else I'm missing? Is there something special about
adding a second SATA drive?
Click to expand...

There shouldn't be...

Assuming that the drive is recognized by the BIOS as 300GB and Windows
really does have the latest service pack and has 48 bit LBA support enabled,
you should see the full 300GB in Disk Management. If not, try clearing the
partition table and rebooting. I've seen similar symptoms from weird
partition tables. Maybe your 3rd party partitioning program is strange.
 
Gary,

I ran the Seagate DiscWizard program. It fixed the problem. I wish I
knew exactly what it did, though.

Thanks,

Tim
 
It must have been a problem with the partition table if the Seagate
DiscWizard fixed it.

--

- Gary Chanson (Windows SDK MVP)
- Abolish Public Schools



Gary,

I ran the Seagate DiscWizard program. It fixed the problem. I wish I
knew exactly what it did, though.

Thanks,

Tim
Click to expand...
 
Back
Top