500gb drive seen as 60gb in windows

NYJimbo

Well-Known Member
Reaction score
2,010
Location
Long Island
Customer brings in a HP desktop running Vista - 64-sp2, claims he is running out of drive space. In explorer I see a 60gb C: and a 11gb D:. Machine is a fairly recent HP and came with this 500gb drive so its not a attempt to use a bigger drive that might not be supported.

In the BIOS it shows the 500gb drive and in windows ->computer->manage it shows a 465gb drive with a 454gb C: and a 11gb D:

Bios updated to latest rev, ALL windows updates install, latested chipset and all drivers installed, system protection showing vssadmin using only 3gb for restore points, various boot disks show a 454 C: with only 42gb used. Ran D7 and Ccleaner tools, turned off restore points (after checking for usable good one), checked pagefile size, used spacesniffer to check C: but it shows it as a 48 gb or so partition with 8 gb free and not the 454 it should be.

awsmbr finds nothing. ran every imaginable virus cleaning program including tdsskiller/roguekiller/mbam/combofix/etc. SMART is totally clean.

Tried to run HDAT2 but cannot do it on that machine, does not see the drives due to drivers. "capacity restore" will produce "cannot load driver" so cannot use that. Used every tool available in D7, but nothing.

SFC/chkdsk/fixboot/fixmbr, all produce no change and not noticeable errors.

Customer says he has been getting "low disk space" errors for 6 months so cant try some system restores in case its something weird in there.

What am I missing ? Either its something simple or there is something hidden that I cant expose.

Attached are two photos:
 

Attachments

  • MANAGE.JPG
    MANAGE.JPG
    71.8 KB · Views: 72
  • EXPLORER.JPG
    EXPLORER.JPG
    80.8 KB · Views: 67
Last edited:
I would clone to a known good drive to see if you get the same kind of results. At least that would let you know whether the issue is with the drive itself or with the machine. Good luck. Looking forward to seeing how this one pans out.

EDIT: I would boot the machine from a Linux disc to see if the drive still shows the same before cloning.
 
Last edited:
This is just a customers play machine. He told me its ok to reformat after doing a data grab so I am not going to clone it. I would like to see if I can find out what is wrong and fix it on this drive so I can learn from it.
 
I had an external drive do this to me recently.

A 1TB drive that showed up at somewhere just over 100GB.

I had to do a low level format and re partition the drive to get the space back, which of course meant shuffling the 100GB of data back and forth.
 
This is just a customers play machine. He told me its ok to reformat after doing a data grab so I am not going to clone it. I would like to see if I can find out what is wrong and fix it on this drive so I can learn from it.

Definitely odd. Does the drive still show the same when booting to an offline OS?
 
I had the same problem on a Mac recently. I didn't get much help in that thread. I was busy and the machine was in Chinese, so I didn't get a chance to play with it. I just assumed that something messed up the partition tables, and reloaded it.
 
Is the drive one that uses advanced formatting 2048K sectors?

50GB x 8 = 400B
11GB x 8 = 88GB
----------------
66GB x 8 = 488GB

Attaching a fsutil output. I cant imagine this drive came out of the assembly line with this drive size issue.
 

Attachments

  • FSUTIL.jpg
    FSUTIL.jpg
    68.6 KB · Views: 65
Open the drive with R-Studio. It should make sense of things. I usually run into these issues when the drive is from a USB enclosure where the bridge does the conversion to the 2M sectors.
 
Open the drive with R-Studio. It should make sense of things. I usually run into these issues when the drive is from a USB enclosure where the bridge does the conversion to the 2M sectors.

Ok, will have to try later, too busy in here right now. Thanks.
 
Back
Top