• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Maxtor 250 gb incorrect size

mafiatfc

n00b
Joined
Aug 7, 2004
Messages
6
I have a Maxtor 7Y250M0 250GB SATA HDD, The drive is used as BASE, I have controllers for the drive, I also have Maxtor big drive fix. I loose nearly 20GB of space, no matter what I do the drives max space is 233. Any segustions at all, low level maybe, utilites, your thoughts on why this would happen?
 
It could be just a "rounding eror" from maxtor. Would you buy a 233 GB hard drive? They round their drives up some for promotional reasons but this is still a lot. I have a 120 gig drive that is only 111 gigs. I think it might to do with the fact they the hard drive manufacturers need to use a multiple of 8 but there isn't always a multiple close. So they usally round up.
 
There reason is there are 2 definitions of a gigabyte. System ram is always counted in base 2. ie- 1k = 1024, 1M = 1048576, 1G = 1024x1024x1024 = 1073741824. Microsoft uses this system to measure disk space as well. This also makes sense, since on a PC HD disk blocks are multiples of 512 bytes.
Now our lovely hard drive manufacturers, OTOH, like to make thier disks look as large as possible. So they count in base 10. 1K = 1000, 1M = 1000000, 1G = 1000000000.
This leaves us w/ a difference of 2.4% for 1K, 4.86% for 1M, and 7.37% for 1G.
as it happens... 250.1818 = 233 * 1073741824/1000000000. So your drive is exactly what they said it was. It's just that Maxtor & MS count differently.
AFAIK *ALL* of them do this. I've never seen a drive that the BIOS, Windows (or any flavor of UNIX) reports as being whatever size it was marketed as, at least not recently enough to remember.

edit: This thread should be in Storage...
 
zandor said:
I've never seen a drive that the BIOS, Windows (or any flavor of UNIX) reports as being whatever size it was marketed as, at least not recently enough to remember.

i recently bought a 120gb Maxtor drive to combine with my WD 120gb drive to run raid 0 and it was much to my chagrin to find out that the Maxtor actually had 120gb, cuz my WD only had 111gb availible which essentially had me wasting 9gb to run raid 0
 
zandor said:
There reason is there are 2 definitions of a gigabyte. System ram is always counted in base 2. ie- 1k = 1024, 1M = 1048576, 1G = 1024x1024x1024 = 1073741824. Microsoft uses this system to measure disk space as well. This also makes sense, since on a PC HD disk blocks are multiples of 512 bytes.
Now our lovely hard drive manufacturers, OTOH, like to make thier disks look as large as possible. So they count in base 10. 1K = 1000, 1M = 1000000, 1G = 1000000000.
This leaves us w/ a difference of 2.4% for 1K, 4.86% for 1M, and 7.37% for 1G.
as it happens... 250.1818 = 233 * 1073741824/1000000000. So your drive is exactly what they said it was. It's just that Maxtor & MS count differently.
AFAIK *ALL* of them do this. I've never seen a drive that the BIOS, Windows (or any flavor of UNIX) reports as being whatever size it was marketed as, at least not recently enough to remember.

edit: This thread should be in Storage...

damn dude.. thanks for that info! I always wondered what the hell they were thinking.
 
Back
Top