Requirements to break the 137GB (128GB Binary) Barrier

I

Ice Czar

Guest
Just found this site
http://www.48bitlba.com
dedicated solely to this issue



Requirements to break the 137GB (128GiB Binary) Barrier

On many systems, the IDE/ATA interface uses a 28-bit addressing which cannot
recognize more than 137GB of storage. To overcome this capacity barrier, drives
higher than this capacity have adopted a 48-bit addressing system which can be supported in newer computer systems with updated controller chips, BIOS codes, and operating system
drivers (refer to your system documentation for more details). If your system does not support drives of this size, you have a few options

originally posted by aneima6
what if i have two hard drives. both on the same channel but one on slave and other on master. one is 120gb and the other 40gb. does this sticky apply to my situation?
Click to expand...
Good Question
This is a 137GB or more per HDD issue, not collective storage above 137GB
XP\W2K

W2K w\ SP3 or better or XP w\ SP1
or You must enable the support in the Windows registry.
48bit LBA support for ATAPI in W2K
Enable 48bit LBA for ATAPI in XP

and

48bit LBA (Large Block Addressing) mobo BIOS support (check for updates)
or
Chipset Driver patch in some cases see Intel Driver updates below


OR


a 48bit LBA capable IDE controller card (or IDE RAID Card)
Since a PCI controller card employs SCSI drivers, this is completely a non-issue, and even the service packs arent required



Win98\ME
At this time Windows 98 does not natively support 137GB drives.
a controller card that supports 48bit LBA is your only solution


Win95
Windows 95 does not properly support drives larger than 32GB without a high probability for data corruption.


Software Driver Updates
(800 Series Intel Chipsets Only)
The Intel Application Accelerator (IAA) adds 48-bit LBA support for the 800 series Intel chipsets. Intel also provides information on how to identify your chipset.

WarningIf your system's old boot drive is less than 137GB and uses a drive overlay program (DDO) to overcome a previous BIOS capacity limitation then the Intel Application Accelerator is incompatible with your system. If you have this legacy configuration, the Ultra ATA host adapter card is the only solution for Windows 98SE. If you install the Intel Application Accelerator on this type of system, loss of data will occur.

FDISK
FDISK shows the normal capacity without wrapping (137GB translated using 1048 vs 1000) however since there is an extra digit it may appear to the user that it is showing 13 GB rather than 131GB.


Seagate Support
Western Digital Support
Maxtor Support
Hitachi Support




Background
BIOS Geometry Translation
BIOS Capacity Limitations
BIOS Handling of oversized Disks

If you need info on how to overcome previous capacity barriers refer to
the Advanced HDD Issues Thread 12th Post


please post any mobo or the BIOS upgrade required for a specific mobo to enable 48-bit LBA to this thread, also post mobos that will NOT support 48-bit LBA, so that we can compile a list ;)





Some additional Info

W2K Registry Key notes

SYMPTOMS
Windows 2000 Service Pack 2 (SP2) and earlier versions of Windows 2000 do not support 48-bit Logical Block Addressing (LBA) as defined in the ATA/ATAPI 6.0 specification.

RESOLUTION
To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

NOTE: If you enable 48-bit LBA ATAPI support by editing the preceding registry key, but your system does not meet the minimum requirements, you may observe the following behaviors:
Operating systems that do not have 48-bit LBA support enabled by default (such as Microsoft Windows 98, Microsoft Windows Millennium Edition (Me), or Windows 2000) that are installed on a partition that spans beyond the 28-bit LBA boundary (137GB) will experience data corruption or data loss.

The installation of operating systems that do not have 48-bit LBA support enabled by default (such as Windows 98, Windows Me, or Windows 2000) on a partition that is beyond the 28-bit LBA boundary (137 GB) is unsuccessful and leaves behind a temporary installation folder.

If you install hotfixes that enable 48-bit LBA before you install Windows 2000 Service Pack 3 (SP3), the appropriate registry key will be automatically created during the installation of SP3 to preserve the data integrity of the hard disk.

After you enable 48-bit LBA support by adding the appropriate registry key, data corruption may occur if you remove the registry key or if you remove (uninstall) SP3 for Windows 2000.

If you install a copy of Windows 2000 that includes SP3 (SP3 integrated) on a large hard disk that has already been preformatted by using a 48-bit LBA-enabled operating system, the ATAPI subsystem may report hard-disk space greater than that which is addressable without the 48-bit LBA support (larger than approximately 137 GB) during the text-mode portion of Setup. In this case, the hard disk's partition table information has already been created. To fix the incorrect disk information, delete the partition by using either a disk partitioning utility or by deleting and then re-creating the partition during the text-mode portion of Setup. After you create the new partition, quit Setup by pressing F3, and then restart the Windows installation process. The ATAPI subsystem now correctly shows approximately 137 GB of hard disk space.

The EnableBigLba registry value is disabled:

If you have a 48-bit compatible BIOS that can support a hard disk that has a capacity of more than 137 GB, only the first 137 GB of the hard disk is addressable. The remainder of the hard disk is not used.

The operating system must be installed on the first partition that is smaller or equal to 137 GB when the EnableBigLba registry value is enabled but when you do not have a 48-bit LBA compatible BIOS.

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 of more than 137 GB, the hard disk continues to function as a standard hard disk with an addressable limit of 137 GB.

The operating system must be installed on the first partition that is less than or equal to 137 GB and the rest of the hard disk divided into one or more remaining partitions when the EnableBigLba registry value is enabled on a computer without a 48-bit LBA compatible BIOS that has a hard disk with a capacity of more than 137 GB.

Note: these are excerpts, refer to the link above for the full entry



XP Registry Key notes

SUMMARY
This article describes the Windows XP Service Pack 1 (SP1) 48-bit Logical Block Addressing (LBA) support for ATA Packet Interface (ATAPI) disk drives that can enable the capacity of your hard disk to exceed the current 137 gigabyte (GB) limit.

Note 48-bit LBA support is not enabled and therefore supported without Windows XP SP1. Windows XP Media Center Edition and Windows XP Tablet PC Edition already include SP1.



Note: The preceding registry setting is ignored in Windows XP SP1 and later. If you attempt to enable the 48-bit LBA ATAPI support in the original release of Windows XP Home Edition or Windows XP Professional by editing the preceding registry setting and you did not meet the minimum requirements, you may observe the following behavior:
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 does not exceed 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 greater 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 greater 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.

Note: these are excerpts, refer to the link above for the full entry

--------------------------------------------------------------------------------------------------


you need both SP1(XP) and a controller that can deal with it, be it the onboard IDE controller\BIOS or an add in card's controller ( a modern one that supports drives over 137)

if you upgrade SP1 after the install, the space would then get recognized and youll be able to partition it. And the corruption issues should go away, let me find the documentation
hmmm...still might need the patch not sure

for XP
http://support.microsoft.com/defaul...port/kb/articles/q303/0/13.asp&NoWebContent=1

and for W2K
http://support.microsoft.com/defaul...port/kb/articles/q305/0/98.asp&NoWebContent=1


If you have a 48-bit compatible BIOS that can support a hard disk that has a capacity of more than 137 GB, only the first 137 GB of the hard disk is addressable. The remainder of the hard disk is not used.

The operating system must be installed on the first partition that is smaller or equal to 137 GB when the EnableBigLba registry value is enabled but when you do not have a 48-bit LBA compatible BIOS.

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 of more than 137 GB, the hard disk continues to function as a standard hard disk with an addressable limit of 137 GB. (But in XP you get the problem below)

The operating system must be installed on the first partition that is less than or equal to 137 GB and the rest of the hard disk divided into one or more remaining partitions when the EnableBigLba registry value is enabled on a computer without a 48-bit LBA compatible BIOS that has a hard disk with a capacity of more than 137 GB.

and the corruption issue in XP

Hard Disk May Become Corrupted When Entering Standby or Hibernation or When Writing a Memory Dump
http://support.microsoft.com/default.aspx?scid=kb;[LN];331958 < youll need to cut and paste that sorry :p

SYMPTOMS
If your computer has an ATA Packet Interface (ATAPI) hard disk that is larger than 137 gigabytes (GB), you may experience any of the following symptoms:
Your computer may restart instead of resuming from hibernation.
You may experience hard disk corruption when your computer enters either standby or hibernation.
You may experience hard disk corruption when Windows XP writes a memory dump file as a result of an unrecoverable Windows error (or Stop error)
Note If you experience hard disk corruption, you may also experience other symptoms including problems starting, restarting, or shutting down Windows XP, problems running programs, or problems opening or saving documents.

CAUSE
The ATAPI driver for Windows XP Service Pack 1 (SP1) does not use 48-bit Logical Block Addressing (LBA) when it writes memory dump files or hibernation files. Additionally, the flush cache command is not issued to a large hard disk that has 48-bit LBA enabled when Windows XP enters standby or hibernation.

RESOLUTION
Windows XP Home Edition, Windows XP Professional, Windows XP Media Center Edition, Windows XP Tablet PC Edition
The following file is available for download from the Microsoft Download Center:

Download the Q331958_WXP_SP2_x86_ENU.exe package now.

More> (reference and different download for 64 bit
----------------------------------------------------------------------------------------------------------

Originally posted by SMPWorksForME
is my Asus A7m266-D compatible with 48 bit LBA?
Click to expand...

HDINFO Tool

Features:

Provides information about ATA devices installed on a system.

Can help determine whether 48-bit LBA device is properly connected to your system.

Includes BIOS test for 48-bit LBA which will run on any system with any OS.

Works with hard drives which have not been partitioned.

Reports OS information you need to know for 48-bit LBA support.

Provides information about various ATA modes useful to determine if BIOS has configured your hard drive for maximum performance

The Full version runs $10, the evaluation version doesnt test for 48bit LBA sorry, Im going to look over some of the freeware Ive collected, that supplies alot of this same info and see if there are any updates that might test for 48bit LBA support.
 
Hmm. I'm kind of confused. You've said this:


Ice Czar said:
W2K w\ SP3 or better or XP w\ SP1
and
48bit LBA (Large Block Addressing) mobo BIOS support (check for updates)
or
Chipset Driver patch in some cases see Intel Driver updates below
OR
a 48bit LBA capable IDE controller card (or IDE RAID Card)
Click to expand...


Which ones are required? Those OSes and one of the three things from the OR list? Or just one of the last two things in the OR list, or both one of those OSes and BIOS support?
 
STICKY!!!!!

Change the title to "Question: Why does my 160+ gb harddrive only shows up as 127gb? Answer inside.
 
Good god, this needs a sticky (doug!) 25% of the questions on this section of the hardforums are about this issue. It's in the 'ANSWERS' sticky, but apparently not alot of people read that before posting.
 
Win98\ME
At this time Windows 98 does not natively support 137GB drives.
a controller card that supports 48bit LBA is your only solution

Win95
Windows 95 does not properly support drives larger than 32GB without a high probability for data corruption.
Click to expand...

This is not entirely true... Neither 98/ME nor 95 support drives larger than 137GB stabily mainly because of the disk tools in use in both OSes. http://support.microsoft.com/kb/184006/en-us Yes a PCI card would let you address the entire drive but you will still need to split it into several partitions smaller than 137GB.

Win95B and C (which both support FAT32 filesystems natively) have the same limitation as 98/ME as far as drives larger than 137GB. Win95A does not support FAT32 and is therefor limited to only 2GB partitions.
 
Ok so I have a question that I didn't see an answer to.

I restalled WinXP Pro on a 200GB Seagate I had lying around (previously XP was on a 80GB).

But I ran into the 137 limit even though the bios says 200. I'm pretty sure the bios had no problem seeing the entire drive but my rather old copy of XP does.

So how I do INSTALL a fresh copy of XP onto this drive and get it to be partitioned as one single 200GB chunk?

I read about slipstreaming but:

-- Don't know if I need to just grab SP2 or do I need to get SP1 as well? My XP CD is pretty old.

-- Don't know if slipstreaming is the *only* way to install XP onto this HD or is there like a boot from floppy disk with some magical file that will allow XP to partition it as one single drive?

-- I don't have a copy of Nero or any other burning software, which means it's going to be difficult for me to burn a copy onto a CD. Can I perform this from a secondary HD?

-- I don't have a copy of Partition Magic either.



Thanks all,


Ty
 
Tly said:
Ok so I have a question that I didn't see an answer to.

I restalled WinXP Pro on a 200GB Seagate I had lying around (previously XP was on a 80GB).

But I ran into the 137 limit even though the bios says 200. I'm pretty sure the bios had no problem seeing the entire drive but my rather old copy of XP does.

So how I do INSTALL a fresh copy of XP onto this drive and get it to be partitioned as one single 200GB chunk?

I read about slipstreaming but:

-- Don't know if I need to just grab SP2 or do I need to get SP1 as well? My XP CD is pretty old.

-- Don't know if slipstreaming is the *only* way to install XP onto this HD or is there like a boot from floppy disk with some magical file that will allow XP to partition it as one single drive?

-- I don't have a copy of Nero or any other burning software, which means it's going to be difficult for me to burn a copy onto a CD. Can I perform this from a secondary HD?

-- I don't have a copy of Partition Magic either.



Thanks all,


Ty
Click to expand...

Gparted will partition that for you. Then for free burning software, use this.
 
SP2 is a cumulative update. It can be directly slipstreamed without SP1 being present first. And yes, doing so will allow for XP setup to see and create >137GB partitions :)
 
Many thanks to both of you. Getting it all squared away very soon.

Thanks again!!!
 
RyanVM said:
SP2 is a cumulative update. It can be directly slipstreamed without SP1 being present first. And yes, doing so will allow for XP setup to see and create >137GB partitions :)
Click to expand...

True. This obviates the 137 GB barrier and also adds support for 48-bit LBA.

NOTE: Because Windows XP Media Center Edition 2005 includes Service Pack 2, slipstreaming is not necessary. Also, there is an apparent *marking errata* regarding certain versions of the ICH5R southbridge (included with the 875P chipset). Support for SATA is not clearly implemented in all versions of this southbridge (in particular, with the ASUS P4C800 Deluxe and P4C800-E Deluxe); only the E includes native support from Intel for SATA, while the older 800 Deluxe requires the included Highpoint controller (also included with the E) for SATA support. It is for this reason that I have referred to the ICH5SR southbridge (though it's marked as ICH5R) to separate RAID-only support from SATA+RAID (including SATA RAID) support, which is included in the ICH5SR variant.
 
It's linked to in the stickied ANSWERS thread. There are lots of other common questions in there, too; people just don't search before posting a new thread.
 
Is there a new thread somewhere (or maybe some updated info here) for the 2TB limit? Seems like a pertinent question to answer in the sticky seem as though we have 1TB drives and RAID on many Mobos in the market now.
 
jen4950 said:
Is there a new thread somewhere (or maybe some updated info here) for the 2TB limit? Seems like a pertinent question to answer in the sticky seem as though we have 1TB drives and RAID on many Mobos in the market now.
Click to expand...
NTFS doesn't support volumes larger than 2TB.
Convert your disk to a GPT disk and you will be fine.
 
jen4950 said:
Is there a new thread somewhere (or maybe some updated info here) for the 2TB limit? Seems like a pertinent question to answer in the sticky seem as though we have 1TB drives and RAID on many Mobos in the market now.
Click to expand...
Windows 2000, XP (not sure about Vista) 32-bit are limited to 2TB volumes. I do not remember if 64-bit is also affected by this.
cyr0n_k0r said:
NTFS doesn't support volumes larger than 2TB.
Convert your disk to a GPT disk and you will be fine.
Click to expand...

I tried this with XP Pro SP2 32-bit and I was not given the option to convert my disks to GPT. Once I installed Server 2003 (Server 2000 will do this too), then I was able to extend my volume beyond that. Just a bit of FYI, Linux is not affected by this as they do not limited the volume sizes.
 
cyr0n_k0r said:
NTFS doesn't support volumes larger than 2TB.
Convert your disk to a GPT disk and you will be fine.
Click to expand...

Incorrect. NTFS is a filesystem. It's size limitation is far beyond any system people on this forum would build. I believe, NTFS does have a 2TB file size limit though.

The legacy MBR (LBA 0) will only address 2TB volumes which is why you have to use GPT (LBA 1).

XP x64, Server 2003 SP1, Vista, Itanium versions of Windows, and *nix systems support GPT partitioning. XP 32 bit does not (it's missing EFI support which GPT depends on).
 
You must log in or register to reply here.
Back
Top