3tb drive only shows 371 mb

It is possible the drive has a partition installed. If the drive is new type 'Partition' into the windows task bar to your bottom left and delete the partitions on the drive by right clicking, then select create a new partition using all 3,000,000mb.
 


I mistakenly posted 371mb. I should have stated 371GB totally allocated on my 3tb external hard drive . I'm running Win 7 32bit. Anyone else had this problem and resolved it??
I apologize for not answering directly but, at one point of experimentation I made the entire drive 1 partition. No workee.
Then I partitioned a 1 gig MBR in an adjacent drive with a new letter and also created a new GPT letter for the expansion. Results were the same minus 1 gig of space in the GPT partition.
 


The method above should still work.
 


 
Some external enclosures are configured with 4KB sector sizes. WD and Seagate both configure their 3TB externals in this way in order to maintain compatibility with Windows XP. When inside the enclosure, the drive presents with a single 3TB MBR partition (with 4KB sector size). If you then remove this drive and install it inside your computer, you expose the drive's native 512-byte sector size. Windows now sees a partition that is 1/8th its original size, namely 375GB.
 
Not ,sure whether you got my last response but, the GPT partition formatted as NTFS with 4kb sectors by default.
Changing it to 512kb,128kb, nor 64kb in Windows resulted in a solution. The Expansion 3tb continues to defy and retaliate.
Again I emphasis this is an expansion drive to a 500gb, Win 7, 32 bit OS.
I might have considered removing the drive from the enclosure and installing it in the case but, I'm sure it would void the 2 year warrantee I purchased.
I refuse to settle for obsolescence for closure on this issue, too many others have succeeded.. This fight continues " Man vs. Machine"! :)
 
You are confusing sector size with cluster size. Clusters are file system concepts (ie logical) whereas sectors are physical concepts. The bridge firmware inside the enclosure determines the sector size of the USB mass storage device, irrespective of any setting within any file system.

Seagate supplies DiscWizard for partitioning and formatting its external drives.
 


DAAH, you are absolutely correct. thanks for sticking with me on this. Moving along, I resigned to Diskwizard before reading your reply. I'm am now Humbled to following a post on you tube to add this drive from hell then taking a stab at partitioning it , the drive size still stays at 372 gb whether converted to MBA or GPT. The pull-down for the maximum drive size will not go beyond 372 gb . It does render an option for MB, GB and TB but will not allow a manual change to TB.
 
Ive tried Crystalmark, Hdsentenel, Easyus, Seatools, Diskwizard,Microsoft Disk Manager, Formating to GPT, Creating 2 or more partitions, moving the 3TB external to another WIN7 32 Bit, and XP.
Now Ive got a support ticket open with Seagate and that means my patience is going to be tested. They seem to be good at 1 experimental suggestion per day. At their rate, this problem might be resolved in about 2 WEEKS!
DMDE appears to be no more than another application for formatting the drive to GPT. None of the above applications have increased my drive to its advertised 3TB or even close. I'm at the point where I'm envying anyone who's getting 700gb plus out of this thing...now that's bad...anyone else wanna chime in?
 
CrystalDiskInfo reports the drive's Identify Device data. These data will tell us the actual capacity that the physical drive is reporting. The problem is that there are about a dozen layers of abstraction (aka obfuscation) between the hardware and the OS.

DMDE is a disc editor. It shows us the actual contents (bits and bytes) in sector 0. Sector 0 is where the partition table lives.

At the moment you have provided us with no conclusive information that would allow us to determine where the capacity limitation is occurring. Is it happening within the physical drive, or the bridge firmware in the enclosure, or in the OS?
 

Ok. You really sound like you're taking this to the next level. I apologize as the previous suggestions simply showed capacities not segmenting the components to identify the culprit. I am formatting the drive, currently at 87%. As soon as that's complete, I'll begin your utility applications, report the results and send screen shots if that would help. Thanks.

 
My sincere gratitude to you and others for your help. Now it's time for me to return the favor. What I discovered in the long run of resolving this problem was using the Seatools diagnostic utility which offered several test, one of which was a a Short DSt test which failed. I also ran a Long DST test that passed.Per Seagate if either of these test failed, the diagnosis represented a bad drive or a drive that was on the verge of failing. "That is why the NUMEROUS HARD DRIVE FORMATING processes did not work. HDSENTENEL also gave suspicious clues after finding a 75% functional surface. I should have known when there were no led lights for any visual status on the unit and after exchanging this unit a second time to get one that fired up right out the box at (2.71 tb) The native Seagate utilities setup software was missing on my last Expansion Drive. Now I've got to clean up all of the Trojans and Malware that highjacked my browser I contacted from all the other troubleshooting software I downloaded. My advice to all is get the extended warranty. It saved me by being able to return the unit to the store after the 15 day exchange period expired. Seagate wanted at best a $9.50 charge, non guaranteed 2 day turn around RMA process. Glad I purchased the former.