Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2271
  • Last Modified:

Maxtor 6B300S0 SATA 300GB reads as 127GB

I had Windows XP Pro running fine on this particular drive, but decided to clone over a Win XP Pro x64 installation from a 200GB drive. This entailed moving the 300 from one machine to another (newer) machine where the 200 was in use. Once attached the new machine reported the 300GB drive as only 127GB in size. That's where I stopped; no cloning took place. Since then moving the drive back to the original machine, using partition software to look at the drive, nor anything else has revealed the drive to be anything other than a 127GB drive. What procedure can I use to return functionality? Maxtor's utilities are useless. I can have this drive attached to an ASUS A8N32SLI Deluxe, or GigaByte K8NS Pro MB, so either way the drive will be behind an 'onboard' controller.
0
GrimDude
Asked:
GrimDude
  • 4
  • 3
  • 3
  • +9
3 Solutions
 
gurutcCommented:
Ok, what service pack revision do you have of XP?  There is a think called logical addressing that could be an issue.  You need to have 48 bit addressing support which I think comes in sp1 but for sure is there in sp2.

- Travis
0
 
AlfonsVHCommented:
Which partitioning software did you use to check the disk?

Have you already tried what Windows Disk Management says about the disks size? To do so, connect the disk to your computer; click Start - Run and type "diskmgmt.msc". Click the drive and check if all the partition space is used.
0
 
Dushan De SilvaCommented:
SET FROM BIOS to detect large Hard Drives. (Most of the times you motherboard will support). In default it will support up to 127GB.

BR Dushan
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
Craig_200XCommented:
if its not in the bios the drive partitioning sw should be from the MFR. this will install special bootsectors to be able to use the drive properly.
0
 
GrimDudeAuthor Commented:
The OS on the 300GB drive is Windows XP Pro sp2, but it will no longer boot (sorry I forgot to report that). The BIOS is set with LBA to Auto. Under Windows XP Pro x64 the Disk Management tool reports the drive as 127GB. I have tried Acronis Disk Director Suite v10.0, Migrate Easy, Partition Table Doctor, and VCOM Partition Commander with the result that all see the drive as 127GB (regardless of which system the drive is installed to). The Maxtor Utilities report the drive as 127GB also. Maxtor's diagnostic utility (PowerMax) cannot be used as the drive is controlled by an embedded controller (per Maxtor).
0
 
Craig_200XCommented:
if it wont boot.. load the xp cd. and select repair / console mode

then :

fixboot /mbr
0
 
bjqrnCommented:
You need to update your BIOS to exceed "the magic 127GB limit"
0
 
GrimDudeAuthor Commented:
Alright, repair console repairs the boot to the 127GB, but doesn't fix the drive so that 300GB can be seen/used.

My BIOS is up to date. Both systems have had large drives in use. In fact, this drive was working perfectly and all 300GB could be used. I'm hoping someone has seen this before, as in all my experience this should not have happened.
0
 
Craig_200XCommented:
did you try to use the mfr disk to reinstall boot sector for windows on the drive?
0
 
jalalmegadethCommented:
Hi

I had the same problem months ago when i got my harddrive

what i did, i used a partition tool to format it, and i created 4 partitions (that's the maximum you can create)


there's another solution to get it, is to enable big LBA on the registery  

here are the steps :

#click on Start->Run, enter "regedit".
# Navigate to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi\Parameters registry subkey
# From the Edit menu, select New, DWORD Value
# Enter the name EnableBigLba, then press Enter
# Double-click the new value, set it to 1, then click OK
# Close the registry editor
# Then restart

0
 
pcchecksCommented:
if you go into the bios..it says that the HDD is 127Gb? or where does it report that?
0
 
scrathcyboyCommented:
The 127 GB limit is built into the BIOS.  If you cannot get more than that, you need to go into the BIOS and fix that issue with different LBA addressing modes.  Older MBs cannot be fixed, but the ASUS 8X series I know for a fact can address a 300 GB drive.  I think the problem is, you formatted the drive on a system that did not recognize a drive bigger than 127 GB because of its BIOS limitation.

You will have to remove the partition on the drive, using the new ASUS board, then make a full partition of 300 GB.  It should do this.  Dont go any further if it does not recognize it.  If so, look at the back of the drive at the jumpers, it might be set to "CLIP" at 127 GB limit.  This is a common setting for drives last year.
0
 
rindiCommented:
SATA shouldn't have the 127GB limit, normally that is only set on IDE drives. Maybe as has been mentioned before, there is a 127GB Cap set for the disk. To remove the possibility of that, remove all the jumpers on the DISK, as SATA normally don't need any jumpers except for something like that.

Get the UBCD, it contains most manufacturer's utilities, and even if maxtor say's it won't work, it still may...

http://ultimatebootcd.com
0
 
Dell100Commented:
That is besides the point, as I have yet to see a SATA board that does not support 48 Bit LBA (Came out 2000), and any way the limitation is 137GB and not 127GB. The problem could be partitioning (with a hidden partition or only half the space used) or  a faulty HDD (you got a misbranded 160GB and not  a 300GB, it happens ! ). Trying running a HDD diags, and if possible test HDD in another system, if either fails, RMA the HDD. It is under manafacturers warrantry for at least 1 year and more likely 3 years.

Download
http://www.ultimatebootcd.com

Great, diags and partion tools.
0
 
gurutcCommented:
Another ultimate boot cd, my favorite:  www.ubcd4win.com

this is the ultimate boot cd for windows version

- Travis
0
 
rindiCommented:
The problem with that one, you first have to build it with your windoze source, but I agree, once built, it is good.
0
 
OAC TechnologyProfessional NerdsCommented:
have you tried setting the cylinder limitation jumper on the hard disk?
0
 
GrimDudeAuthor Commented:
As far as I know there are no jumpers on the hard drive at all. I am going to try the UBCD today and see if I can get anything to work. I was able to use a utility (I forget the name) to see the cylinders/heads/sectors in use and noted that only about 1/3 of the heads were in use and about the same on sectors.
0
 
Dell100Commented:
RMA the Hardrive with your computer supplier. It looks like it was mis labeled.
0
 
GrimDudeAuthor Commented:
Negative, at one time it was seen as a 300GB drive and functioned properly. I'm about to try the UBCD approach and will report back.
0
 
gurutcCommented:
cool with me - gurutc
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

  • 4
  • 3
  • 3
  • +9
Tackle projects and never again get stuck behind a technical roadblock.
Join Now