For those that are having this problem with Samsung 1000GB showing up as 32MB. I have found a solution that worked for me.
When I purchased the Samsung Spinpoint F1 Series HD103UJ 1TB SATA2 7200RPM. I installed it into an External USB/ESATA case and it detected as a 1000GB drive. I then copied over a 200+GB of data onto the drive. The next morning, I rebooted my server so that I could reorganize the drives in my machine. I didn't actually do anything except tell Windows Server 2003 to reboot.
Upon Windows rebooting. I was missing my new drive, atleast I though I was missing it, because there was a 32MB drive there. So I powered down the removeable case and powered it back up. But still there was no 1000GB drive present, just a 32MB. I found this very strange. I then tried the drive on my notebook and still 32MB.
I then started googling and found that this sometimes happens with the Samsung 1000GB and Gigabyte motherboards, which is what I was using. I then found, on a few fourms, that there was an application supplied by Samsung called
ESTOOL, which can fix the problem. I downloaded this application but it failed to allow me to update the LBA. It still wanted to set the drive at 32MB. The then found there was a another version of this application
SAMSUNG HUTIL v2.10, but these would not work either. The application keep returning Access Denied or Timeout Errors.
After reading some more forums, I can across an application called
MHDD which people said fixed there problems when the Samsung ESTOOL didn't work. So I downloaded this application and followed the instructions to "UNCUT" the drive and then I tried the HPA command but still no luck. Drive was stuck in 32MB mode.
After nearly 8 hours of searching and running these programs. I found a link to another program called
HDAT2.
I followed Method 1 from the FAQ on that site
Q1: I received a 40 GB drive in replacement for a 20 GB model in PC. The drive is reported as 20 GB capacity. How can i get full capacity ? which involves SET MAX and adjusting the LBA on the drive, this is very similar to to the methods used in the ESTOOL and MHDD, but once again it failed.
I then moved on to Method 2. Which is to restore the Device Configuration Menu and reset the DCO, after selecting the restore method under this menu. My drive was back. FIXED, now showing 1000GB (931GB actually)
The problem appears to be related to the drive being set from 48 bit LBA to a 24 bit LBA, this stops the other programs from being able to change the LBA to the correct size.
I hope this is helpfully to others with this problem.
HDAT2 SAVED MY DRIVERegards
Disfusion