Wrong HDD size

  • Thread starter Thread starter ZTK
  • Start date Start date
Z

ZTK

This is about a hard disk I bought last month. It's an 80GB Seagate
Barracuda 7200 rpm PATA drive, model No.ST380011A. It works except
that BIOS auto-detect, Fdisk, Windows and Partition Magic 8 all see it
as a 32GB drive. The 32GB limiting jumper is NOT used.

I tested it with three different mobos, all current models. They all
identify the model number correctly, and there's no problem
partitioning and formatting it as a 32GB drive. Entering the CHS
values manually simply indicates the calculated capacity. Configuring
it as cable select or changing the access mode to Large or LBA makes
no difference. Auto-detect reports it as -

Capacity - 33821 MB
Cylinders - 65530
Heads - 16
Precomp - 0
Landing zone - 65529
Sector - 63

I'm inclined to think it's simply a manufacturing error. I reported it
to Seagate but did not receive a reply. My supplier already sent me a
replacement last month and I sent back the drive in question today, so
the matter is more of academic interest than a pressing problem. But
I'm curious to know if anyone has ever come across a case like this.
 
ZTK said:
This is about a hard disk I bought last month. It's an 80GB Seagate
Barracuda 7200 rpm PATA drive, model No.ST380011A. It works except
that BIOS auto-detect, Fdisk, Windows and Partition Magic 8 all see it
as a 32GB drive. The 32GB limiting jumper is NOT used.

I tested it with three different mobos, all current models. They all
identify the model number correctly, and there's no problem
partitioning and formatting it as a 32GB drive. Entering the CHS
values manually simply indicates the calculated capacity. Configuring
it as cable select or changing the access mode to Large or LBA makes
no difference. Auto-detect reports it as -

Capacity - 33821 MB
Cylinders - 65530
Heads - 16
Precomp - 0
Landing zone - 65529
Sector - 63

I'm inclined to think it's simply a manufacturing error. I reported it
to Seagate but did not receive a reply. My supplier already sent me a
replacement last month and I sent back the drive in question today, so
the matter is more of academic interest than a pressing problem. But
I'm curious to know if anyone has ever come across a case like this.


it's probably a bios limitation rather than a drive problem...
you need to use either a software "overlay" program
or else get a pci controller
 
philo said:
ZTK said:
This is about a hard disk I bought last month. It's an 80GB Seagate
Barracuda 7200 rpm PATA drive, model No.ST380011A. It works except
that BIOS auto-detect, Fdisk, Windows and Partition Magic 8 all see it
as a 32GB drive. The 32GB limiting jumper is NOT used.

I tested it with three different mobos, all current models.
.............[snip]................
I'm inclined to think it's simply a manufacturing error. I reported it
to Seagate but did not receive a reply. My supplier already sent me a
replacement last month and I sent back the drive in question today, so
the matter is more of academic interest than a pressing problem. But
I'm curious to know if anyone has ever come across a case like this.

it's probably a bios limitation rather than a drive problem...
you need to use either a software "overlay" program
or else get a pci controller

Perhaps you missed the part where I said that "I tested it with three
different mobos, all current models". Those mobos are all working with
80GB or larger drives.
 
This is about a hard disk I bought last month. It's an 80GB Seagate
Barracuda 7200 rpm PATA drive, model No.ST380011A. It works except
that BIOS auto-detect, Fdisk, Windows and Partition Magic 8 all see it
as a 32GB drive. The 32GB limiting jumper is NOT used.

I tested it with three different mobos, all current models. They all
identify the model number correctly, and there's no problem
partitioning and formatting it as a 32GB drive. Entering the CHS
values manually simply indicates the calculated capacity. Configuring
it as cable select or changing the access mode to Large or LBA makes
no difference. Auto-detect reports it as -

Capacity - 33821 MB
Cylinders - 65530
Heads - 16
Precomp - 0
Landing zone - 65529
Sector - 63

I'm inclined to think it's simply a manufacturing error. I reported it
to Seagate but did not receive a reply. My supplier already sent me a
replacement last month and I sent back the drive in question today, so
the matter is more of academic interest than a pressing problem. But
I'm curious to know if anyone has ever come across a case like this.

Check their support as some WD drives need all the jumpers off to be
correctly seen as a Master so double check their jumper legends
against their on-site references just in case?



--
Free Windows/PC help,
http://www.geocities.com/sheppola/trouble.html
remove obvious to reply
email (e-mail address removed)
Free original songs to download and,"BURN" :O)
http://www.soundclick.com/bands/8/nomessiahsmusic.htm
 
Shep© said:
Check their support as some WD drives need all the jumpers off to be
correctly seen as a Master so double check their jumper legends
against their on-site references just in case?
Thanks for the interest, but I've used quite a few Seagate
Barracuda drives including this particular model, and am familiar
with their jumper settings. No, that's not it. I was wondering if
there was some factor I'd overlooked, but I guess it was just a
defective piece.
 
Thanks for the interest, but I've used quite a few Seagate
Barracuda drives including this particular model, and am familiar
with their jumper settings. No, that's not it. I was wondering if
there was some factor I'd overlooked, but I guess it was just a
defective piece.

I had a mother board(can't remember what make) that I had to set the
detection from auto to manual and then press the enter key so it
manually,"Auto-Detected",if that makes sense :&




--
Free Windows/PC help,
http://www.geocities.com/sheppola/trouble.html
remove obvious to reply
email (e-mail address removed)
Free original songs to download and,"BURN" :O)
http://www.soundclick.com/bands/8/nomessiahsmusic.htm
 
HDD Size

I'm currently having a simular problem,....I've been running an AMD Sempron 3000+ 2.0G cpu/mb with an ST380011A 80 Gig master drive, and a Western Digital 40 Gig slave drive for a few years with no problems. A few days ago, I tried to swap the WD 40Gig HDD with a WD 120Gig HDD. My 80Gig master drive is still fine, but the 120Gig only shows up as 32Gig. I've been experimenting with jumper settings but I'm not there yet. Any ideas?
 
Back
Top