[SOLVED] Wrong storage capacity

Jun 5, 2020
6
0
10
After some file corruption with my 6TB external HDD, and having it reformatted, now the capacity of the HDD that windows 10 file explorer and diskmanagement shows is wrong. If I click properties on the disk and go to Volumes tab, it says 5723149MB. Check the images below, Windows 10 reporting of the HDD seems inconsistent across everything. Anyone know how to fix this? When i first bought the drive, it showed up as 5.8TB or somewhere there.

I ran WinDirStat and it says I am only using about 169GB worth of data on the 6TB HDD, so it is taking up the correct amount of 5.45TB, reducing it to 5.29TB, which is worrying because I am losing a massive .3TB or so.

1.png


2.png

3.png

4.png
 
Last edited:
Solution
It's your base 10 numbering system thats at fault here. windows uses binary - bits and bytes (8bits is 1 byte) and 1kb is 1024 bytes. HDD's manufacturers measure in decimal to make their drives 'look' bigger and 1MB = 1,000,000 bits which is short a few from the 1,048,576 bits Windows calls 1MB.

Looking at your h: properties, you have 6,001,156,681,728 bytes
Dividing those bytes by 1048576 (bytes in a MegaByte) = 5,723,148.99Mb which is the capacity shown in your second pic
dividing that by 1024 to convert to gb = 5589GB Look familiar? (see your 3rd image)
dividing by 1024 again to convert to TB yields 5.458TB - see 1st pic

There's nothing wrong here.
Are you sure there's no other partitions ?

Nope, there are no other partitions. I noticed that the total disk capacity seems to reduce as I move files into it. I bought another WD 6 TB HDD as backup to test in case the one I have was faulty, and copying the content over to the new 6TB HDD caused it to also reduce to exactly 5.45TB in file explorer as well. So I think maybe something is wrong with HDD or Windows 10 just doesn't like 6TB HDDs.
 
It's your base 10 numbering system thats at fault here. windows uses binary - bits and bytes (8bits is 1 byte) and 1kb is 1024 bytes. HDD's manufacturers measure in decimal to make their drives 'look' bigger and 1MB = 1,000,000 bits which is short a few from the 1,048,576 bits Windows calls 1MB.

Looking at your h: properties, you have 6,001,156,681,728 bytes
Dividing those bytes by 1048576 (bytes in a MegaByte) = 5,723,148.99Mb which is the capacity shown in your second pic
dividing that by 1024 to convert to gb = 5589GB Look familiar? (see your 3rd image)
dividing by 1024 again to convert to TB yields 5.458TB - see 1st pic

There's nothing wrong here.
 
Solution

TRENDING THREADS