160 GB HD only showing 123 gigs...

[anchoryanker]

it's a seagate, what could be causing this?

[HookeyStreet]

Originally Posted by anchoryanker

it's a seagate, what could be causing this?

Have you got the most recent BIOS for your motherboard as an old BIOS may limit your HDD size, or your motherboard may not support HDD's of that size

[Steevo]

Your motherboards BIOS must support 48bit LBA.
You must have service pack 2 installed.

[_33]

SOLUTION:

- Get the software MHDD32 v4.6FL (disk image)
- write the image on a blank 1.44 floppy disk
- Boot your system with the floppy disk
- then press F1 for the list of options
- find the option that enables you to change the LBA
- Look on your defective HDD for the LBA value and use that
- Assign the value and reformat if necessary (low level format)
- Reassign main partition to the max value of your HDD (160GB should be now available)

voilà. The reason your HDD decided to shrink it's usable space is becvause of bad sectors (usually). You may fix this yourself with the appropriate software. I hava a maxtor that reported 32GB and it's 160GB. This is exactly what I did. There is a Low LevelFormat software on the net called LLF.

[anchoryanker]

have service pack 2

don't know what 48 bit LBA is.

My mobo (according to CPU-Z) is an

ASUS kelut v 2.02
chipset via km400
southbridge via vt8237

bios

phoenix technologies, ltd
ver 3.03
02/09/04


Ive only shown 123 gigs (127gig, if you count the OS partition) from the day i installed the HD.

[_33]

Originally Posted by anchoryanker

have service pack 2

don't know what 48 bit LBA is.

My mobo (according to CPU-Z) is an

ASUS kelut v 2.02
chipset via km400
southbridge via vt8237

bios

phoenix technologies, ltd
ver 3.03
02/09/04


Ive only shown 123 gigs (127gig, if you count the OS partition) from the day i installed the HD.

Chances are your mobo can't see more than 128GB space. Sadly. It is part compatibility and part age/generation factor. Look for a possible driver for the HDD manufacturer for your windows that will enable the full 160GB.

[newmodder]

go to

Control panel
administrative tools then
computer managment then
then disk managment and see what it says.right clcik on it and refresh.or you may have not formatted the disk before windows install

[Alec§taar]

LBA registry hack (to enable full use of disks of size > 128gb, iirc that is the "size-limitation"):

http://support.microsoft.com/default...b;en-us;303013

How to enable 48-bit Logical Block Addressing support for ATAPI disk drives in Windows XP

View products that this article applies to.
Article ID : 303013
Last Review : May 31, 2004
Revision : 6.0
This article was previously published under Q303013
INTRODUCTION
This article describes the Microsoft Windows XP Service Pack 1 (SP1) 48-bit Logical Block Addressing (LBA) support for ATA Packet Interface (ATAPI) disk drives that can increase the capacity of your hard disk to more than the current 137 gigabyte (GB) limit.

Note Windows XP does not support 48-bit LBA support unless you are running Windows XP SP1. If you want to use 48-bit LBA support, you must apply Windows XP SP1 or later. Windows XP Media Center Edition and Windows XP Tablet PC Edition already include SP1.

For additional information about the latest service pack for Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:
322389 How to obtain the latest Windows XP service pack
MORE INFORMATION
Windows XP SP1 includes 48-bit LBA support for ATAPI disk drives. With this support, you can use hard disks that are larger than the current 137 GB limit. By default, support is enabled in SP1. To determine if you are running SP1, right-click My Computer and then click Properties. On the General tab, Service Pack 1 will be listed under "System."

To determine if you have the latest ATAPI driver, verify that you have version 5.1.2600.1135 or later of the Atapi.sys file in your %systemroot%\system32\drivers folder. (Or version 5.1.2600.1152 for Windows XP 64-Bit Edition.) To do this, follow these steps:
1. Click Start, click Search, and then click All Files and Folders.
2. Type Atapi.sys, and then click Search.
3. If you do not find the Atapi.sys file in your %systemroot%\system32\Drivers folder, click More advanced options in Search Companion, click Search hidden files and folders, and then repeat step 2.

For additional information about how to search for hidden and system folders, click the following article number to view the article in the Microsoft Knowledge Base:
302347 How to search for hidden or system files in Windows XP
4. Right-click Atapi.sys in your %systemroot%\System32\Drivers folder, and then click Properties.
5. Note the file version on the Version tab.
If Atapi.sys is not version 5.1.2600.1135 (or version 5.1.2600.1152 for Windows XP 64-Bit Edition), obtain and install the hotfix that is described in Microsoft Knowledge Base article 331958.

For additional information about this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:
331958 Hard disk may become corrupted when entering standby or hibernation or when writing a memory dump
By default, the original release version of Windows XP Home Edition and of Windows XP Professional do not have 48-bit LBA support. Your computer must meet the following requirements to use 48-bit LBA ATAPI support:
• 48-bit LBA-compatible BIOS.
• 137-GB hard disk or larger.
• You must have Windows XP SP1 installed.
For the original release version of Windows XP Home Edition or of Windows XP Professional, you can enable 48-bit LBA for testing purposes. To do this, set the EnableBigLba registry value to 1 in the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\Atapi\Parameters\
Warning Data corruption may occur if either of the following conditions is true:
• You use this registry value to enable 48-bit LBA support in the original release version of Windows XP Home Edition or of Windows XP Professional.
• You install an earlier version of Windows on a disk partition that was previously created by a 48-bit aware operating system, such as Windows XP SP1. And that disk partition is equal to or larger than the current addressable limit of 137 GB.
Note The previous registry setting is ignored in Windows XP SP1 and later. If you try to enable the 48-bit LBA ATAPI support in the original release version of Windows XP Home Edition or of Windows XP Professional by editing the previous registry setting, and you did not meet the minimum requirements, the following issues may occur:
• The registry value EnableBigLba is disabled. If you have a 48-bit compatible BIOS that can support a hard disk that has a capacity that is greater than 137 GB, only the first 137 GB of the hard disk are addressable. The rest of the hard disk is not used.
• The registry value EnableBigLba is enabled, but you do not have a 48-bit LBA compatible BIOS and the capacity of the hard disk is not greater than 137 GB.

If you enable the 48-bit LBA ATAPI support by editing the registry setting, but you lack both a 48-bit LBA compatible BIOS and a hard disk that has a capacity that is see comment than 137 GB, you have not changed the system. The hard disk continues to function as a standard hard disk.
• The registry value EnableBigLba is enabled without a 48-bit LBA compatible BIOS, but you have a hard disk with a capacity that is larger than 137 GB.

If you enable 48-bit ATAPI support in the registry and you have a hard disk that has a capacity that is see comment than 137 GB, but you do not have a 48-bit LBA compatible BIOS, only the first 137 GB of the hard disk are addressable. The remainder of the hard disk is not used.
To enable 48-bit LBA support by using an unattended installation with the Microsoft System Preparation (Sysprep) tool, follow these steps:
1. Copy the following text into Notepad and save the text as the 48bitLba.inf file:

[version]
signature="$CHICAGO$"
SetupClass=BASE

[DefaultInstall]
AddReg=48bitlba.Add.Reg

[48bitlba.Add.Reg]
HKLM,"System\CurrentControlSet\Services\Atapi\Para meters","EnableBigLba",0x10001,1
2. Create a file named Cmdlines.txt that includes the following lines:

[Commands]
"rundll32 setupapi,InstallHinfSection DefaultInstall 128 .\48BITLBA.INF"
3. Locate the Sysprep\I386 folder in the Sysprep image, and then create a $OEM$ subfolder in this folder.
4. Copy the 48bitlba.inf and Cmdlines.txt files into the Sysprep\I386\$OEM$ folder.
5. In your Sysprep.inf file, add a key named InstallFilesPath to the [Unattended] section. This key must have the following value: InstallFilesPath = "C:\sysprep\i386"
To add the previous settings to the Images folder that was created with the Riprep.exe program, follow these steps:
1. On the remote installation server that contains the Riprep image, create a Sysprep\I386\$OEM$ folder in the following folder:
RemoteInstall\Setup\Language\Images\Riprep_dir_nam e\I386\Mirror1\UserData
Note Language is "English" for the English language, and Riprep_dir_name is the unique name that you selected for the Riprep image.
2. Copy the 48bitlba.inf and Cmdlines.txt files into the $OEM$ folder.
3. Modify the Riprep.sif file (and any other template files for this Riprep image that you have created) in the following folder:
RemoteInstall\Setup\Language\Images\Riprep_dir_nam e\I386\Templates\Riprep.sif
To do this, add the OemPreinstall and InstallFilesPath values:

[Unattended]
OemPreinstall = "Yes"
InstallFilesPath = "C:\sysprep\i386"
4. Close and then save the file.
OEMs can turn on this support by using the Microsoft Windows OEM Preinstallation Kit.

For more information, see the OEM Preinstallation Kit or the following Microsoft Web site:
http://www.microsoft.com/oem



APK

[Firedomain]

thats way 2 much info for me 2 read!!!! i was just looking around at posts.. but wow...... im 2 damn lazy 2 read than.... next post!...

i was gonna suggest the disk manager if u bought it 2nd hand.
& if it is in multiple partitions then id suggest Acronis Disk Director Suite 10 very handy for partition managing.

[Necrofire]

I'm sorry, you won't ever see the entire 160GB.
By doing the conversion from decimal to binary, you get....

160000000000 bytes, divided by 1073741824 (bytes in 1 GB) you get ~149GB max anyway.

Having 127GB doesn't say anything about not having 48-bit LBA, since the hard limit is 137GB, and having a larger hard drive causes some interesting errors after formatting it.

I'm not sure about why you have 127GB of available, but I am sure that it's not because of LBA.

[sneekypeet]

hey fellas he had this issue a year and a half ago...lol

Still ok to post helpful solutions tho i guess

[Hawk1]

Originally Posted by Necrofire

I'm sorry, you won't ever see the entire 160GB.
By doing the conversion from decimal to binary, you get....

160000000000 bytes, divided by 1073741824 (bytes in 1 GB) you get ~149GB max anyway.

Having 127GB doesn't say anything about not having 48-bit LBA, since the hard limit is 137GB, and having a larger hard drive causes some interesting errors after formatting it.

I'm not sure about why you have 127GB of available, but I am sure that it's not because of LBA.

Lol - I dont think he cares at this point. He asked almost a year and a half ago.

Edit: no offense meant - I just find it funny thinking what the OP would say if he saw it.

[Firedomain]

wow... just shows how much attention we pay to the post dates!

[Urbklr]

Lol....this is funny....If your here still Anchoryanker (lol...nice name) SAY SOMETHING!!!

[panchoman]

i believe i had a similiar problem, dont remember the specifics but it has something to do with the DDO(its like a bit of software and shit on drives that helps when the bios has trouble with the drive, lba limit, etc. etc.) and so i just wrote 0's to the whole drive using seatools for dos and it went away. oh and make sure that you have sp2. slipstream it into your xp installation if you're installing from xp and then dl'ing sp2