If IDE drive is the only device on the bus

• Is it at the end of the cable?
• Is it configured as master?

If drive is one of two devices on the bus

• Is the master drive attached at the end of the cable?
• Is one configured as master and the other as slave?

Check that all connectors are seated correctly

• Try unplugging and re-plugging cable.
• Pin 1 (red or red striped conductor) is located nearest to the power connector.

Check the cable

• If possible, try replacing the cable.
• Total cable length should not exceed 18 inches.

Check the pins

• Check for bent, pushed or missing pins

Run drive with all other devices disconnected

• Disconnect all non-essential components and try the drive by itself on the cable. If the drive works, reinstall one device at a time until you find the conflicting component.
• If the drive is in an external enclosure remove the drive from the enclosure and attach it directly to the internal IDE bus.

Install or replace a drive in a single-drive system

• The drive should be configured to cable select and should be attached to the black connector for systems using an 80-conductor cable, or to the middle of the cable for systems using the older 40-conductor cable.
• Note: the connectors on an 80-conductor cable are all different colors (black, blue and gray). The connectors on a 40-conductor cable are all the same color.

Install or replace a second drive in the system

• The drive should be configured to cable select and should be attached to the remaining connector on the cable.

System detects only 32 GB

Verify that the drive is configured correctly.

There is a setting called the "32GB Clip" which limits the drive to only 32 GB capacity. If any of the jumpers on the drive are in a horizontal position, you may have this setting enabled. For additional information, consult the jumper settings for your Hitachi drive.

If the drive is configured correctly and still reporting only 32 GB capacity, download the Feature Tool utility.

The Feature Tool provides the ability to view and change the actual capacity of the drive. The "current" capacity should match the "maximum" capacity. If they do not match, change the "current" capacity to match the "maximum" capacity.

For additional guidance, download the Feature Tool user’s guide.

System detects only 127-138 GB

1. If the system BIOS is physically detecting the drive at 137 GB, then you may have a BIOS limitation. Contact your system or motherboard manufacturer or visit their web site for updates that support the larger capacity drives.

If your system or motherboard is using an Intel-based processor and chipset, you also might need to obtain and install the latest version of the Intel Application Accelerator.

If your system or motherboard is using a VIA-based chipset, you might need to obtain and install the latest "4-in-1 Pack" for the VIA chipset.

2. If no BIOS updates are available, you can purchase an ATA controller card that will allow you to properly support the full capacity of the drive.

3. If the system is physically detecting the drive at full capacity, but Windows XP or Windows 2000 is only reporting 137 GB, use Windows Update to make sure that the latest service packs and updates are installed. Service Pack 1 for Windows XP and Service Pack 4 for Windows 2000 allows for proper support of drives larger than 137 GB.

4. If, after performing all of the above steps, you are still only showing 137 GB in the operating system, please refer to the following Microsoft Knowledgebase articles.

These articles outline a process of editing the registry to properly enable large hard disk support:

• Microsoft Knowledgebase articles or Windows 2000
• Microsoft Knowledgebase articles For Windows XP

5. Once all of the previous steps have been completed, you should have access to the full capacity of the drive in the operating system.

If this is a boot drive (the operating system is installed to it), you can now create a second partition to utilize the remaining capacity of the drive. If this is a secondary drive, you may need to do delete the exiting partition before you are able to access the full capacity of the drive.

The latest operating systems (Windows 2000 [sp3+], XP [sp1+], Vista and Linux) often ignore the BIOS support and directly address the drive capabilities. You may want to consider upgrading your operating system.

Repairing the MBR

Caution. You may lose your data if you use this process.

1. Backup any important data first. If this is not possible, contact the support center to explore recovery options.

2. At an MSDOS prompt run the “FDISK/MBR” command to restore the master boot record. From a DOS command line, type: FDISK/MBR. This will run and return you to a DOS prompt. FDISK/MBR will attempt to restore the default DOS MBR without overwriting important partition data, which may repair the problem without losing your data. At this point, reboot your system.

From the Windows XP or 2000 recovery console, type “FIXMBR” to repair the master boot record (Windows XP or 2000 systems only).

Caution: if you originally set up your drive with an overlay utility such as Disk Manager, FDISK/MBR likely will not work. FDISK/MBR is also likely to fail if more than four partitions exist or if you use certain dual boot programs. In these instances, contact the support center.

3. If restoring the MBR with the above procedures does not resolve the problem, run the Drive Fitness Test. Select “Utilities” then select “Erase Boot Sector” to completely erase the MBR and reinstall your operating system (this will overwrite your data).

Using earlier operating systems

Microsoft Windows NT, 95A, earlier versions of Linux and DOS must be installed within the first 1,024 cylinders of the drive (512 MB).

Later Linux kernels and Windows XP and 2000 do not have this limitation.

Attaching an Ultra ATA/100 or faster drive to a controller that supports these speeds

Use an 80-conductor cable and make sure that the devices are attached to the correct connectors:

• Blue - Controller (system).
• Black - Master device (HD0 or ID0).
• Gray - Slave device (HD1 or ID1).

Attaching an Ultra ATA/66 or faster drive to an Ultra ATA/33 controller

Obtain a BIOS update from your BIOS manufacturer if these instances occur:

• System hangs during boot with DMA enabled in Windows 98.
• System runs OK, but is actually transferring all data in PIO mode 4 in Windows 98.
• System refuses to complete the boot operation with a bus master driver added in Windows 95 OSR2.
• System refuses to complete the boot operation with a bus master driver added in Windows NT.

If a BIOS update is not available, use the Feature Tool utility to enable or disable Ultra ATA/66 or ATA/100 support on the disk drive. The disk drive will operate in Ultra ATA/33 mode, thus compatible with Ultra ATA/33 controllers.