Updated:04:27 PM EST Nov 24

this is ggmania.com subsite

rss feed 
top 100
submit news

FREE eBooks

CD/DVD tools
Free Antivir

Forex Brokers Reviewed

Booty Bingo

New Look Bingo

Mummies Bingo

M Jackpots

(C) 2006-2017 TechAmok
All Rights Reserved.

How to fix a 1TB hard drive that suddenly changes to 32MB in size - TechAmok

How to fix a 1TB hard drive that suddenly changes to 32MB in size - [guides]
05:36 AM EDT - Jul,11 2009 - (1 comments)

PC Stats posted a guide about fixing a 1TB hard drive that suddenly changes to 32MB in size.
The loss of factory hard drive capacity seems to be an increasingly common occurrence with very large capacitym 1TB hard drives, but it's not specific to any one hard drive manufacturer. It can happen to brand new drives or existing hard drives full of data. In either case the data portion of the drive isn't generally affected. If a new or existing hard drive in your computer suddenly pops up with a capacity of 32MB, or another value equally small compared to the true drive size, don't freak out, the data should still be there. Here's what typically happens; a large capacity hard drive of between 500GB, 750GB, 1TB and 1.5TB suddenly appears to loose most of its capacity for no apparent reason. In many situations the capacity of the hard drive shrinks to 0.0GB or 32MB (and occasionally 32GB) and becomes inaccessible to the Windows Vista.

What's happening, to put it simply, is that the portion of the hard drive responsible for telling the computer how big it is, is mis-reporting that value. We don't have a good technical explanation for what causes this issue to randomly strike PC users, but suffice to say a portion of the drive firmware known as the LBA48, HPA and DCO records becomes corrupted.

Our experience with the loss of factory hard drive capacity bug came whilst setting up a new PC with two fresh 1TB Western Digital Caviar Black SATA hard drives. Both SATA drives had been formatted and were working fine. After hard power-off reboot one of the 1TB disks suddenly became a lot smaller than it actually was.

Instead of reporting it's true capacity of 1000GB, or 1TeraByte, the Western Digital Caviar Black Edition SATA hard drive appeared to both the Microsoft Windows Vista operating system and the motherboard BIOS with a false capacity of 32MB. Somehow 999.968GB of storage space had disappeared into thin air! The new drive capacity of 32MB just seemed a little too specific to be random, so we did a little investigating. What we found is that quite a few PC users have experienced the exact same situation - a new or existing large capacity hard drive suddenly looks to the computer like it's only 32MB, or 32GB in size. If the hard drive was previously filled with 1000GB worth of data you can imagine the shock of seeing it reduced to 32MB! Incidently, the 32MB figure seems to be drawn from the hard drives' onboard cache memory.

last 10 comments:

(02:13 PM EDT - Jul,13 2009) - admin
The Seagate's bug was worse ....

Add your comment (free registrationrequired)

Short overview of recent news articles

Nov,24 2017 Apple Applies For Flexible Display Patent
Nov,23 2017 Samsung to unveil Galaxy S9 and S9+ at CES in January
Nov,23 2017 VRMark Cyan Room DirectX 12 benchmark
Nov,21 2017 Honor 7X Boasts Twin Cameras, 18:9 Display
Nov,21 2017 Emily Ratajkowski goes topless in a pair of bikini bottoms
Nov,21 2017 GameStop Black Friday Ad Reveals Deals
Nov,21 2017 This is our world by Steve Cutts
Nov,20 2017 Intel Aims to End Legacy BIOS Support by 2020
Nov,20 2017 Philip K. Dick's Electric Dreams - Official Trailer
Nov,20 2017 Incredibles 2 Official Teaser Trailer
Nov,19 2017 Xbox One X Tear-Down
Nov,19 2017 Surface Book 2 gets torn down, repairs are tough
Nov,18 2017 Xbox Game Pass $1 Black Friday Deal
Nov,18 2017 NVIDIA shows the power of VR at Autodesk University 2017
Nov,18 2017 The best pics on the Internet #241
Nov,17 2017 Germany Bans Children's Smartwatches
Nov,17 2017 The Tesla Semi Revealed
Nov,17 2017 Bitcoin Passes $8,000 For the First Time in History
>> News Archive <<

TechAmok - Privacy Policy        loading time:0.01secs