|
FIXED DISK ERROR CODES
This section lists the errors that could
be encountered during the Fixed Disk diagnostic tests or during
a drive format, along with suggestions for correction. Keep
in mind that with IDE drives, the control circuitry is in
the drive, not on the motherboard. Also, when errors occur
because of incompatibility between drives, the error will
sometimes disappear if the order of the drives is changed
(swapping Master and Slave, or Primary and Secondary). Of
course, the proper changes must then be made with jumpers
and settings.
Code 01: Invalid Function Error
– The command sent to the drive was not accepted. The
most likely cause is either the drive unit or the cable. If
the system is a PS/2, the BIOS will not support the direct
format of the drive.
Code 02: Address Mark Not Found
– The diagnostic could not find the Address Mark for
the given sector. On MFM and RLL drives that do not use a
voice-coil head actuator, it could mean the heads are misaligned.
A low-level format will correct the problem. It could also
mean that the drive type is not set in CMOS. On IDE drives,
this error is a physical defect and the address should be
added to the Bad Sector map before doing a low-level format.
Code 03: Disk Write Protect
– This error should never occur while testing a hard
drive, and would indicate electronic failure in the drive
control circuitry.
Code 04: Sector Not Found
– This can occur if the servo information on the platter
for that sector is damaged or there is an electronic failure
in the drive control circuitry. It could also be mis-aligned
heads (MFM or RLL drives). A low-level format may be able
to correct the problem. If the error occurs during a low-level
format, it is a fatal error and the drive should be replaced.
Code 05: Reset Failed –
Usually caused by electronic failure in the control circuitry.
If there are two or more hard drives in the system, this error
may indicate an incompatibility between a Master Drive and
its Slave.
Code 06: Disk Change –
This error should never occur during testing of a hard drive.
Code 07: Drive Param Activity Failed
– Either the drive parameters are set incorrectly
in CMOS or the controller does not correctly translate the
parameters. Verify the settings and try the test again.
Code 08: DMA Overrun –
This error would occur if another device is trying to use
the same DMA channel as the disk drive or if the drive controller
is failing. If a new device was recently added to the system,
the first thing to try would be removing the device and running
the test again.
Code 09: Data Boundary Error
– This indicates that another device is using the same
DMA channel as the fixed disk. See DMA Overrun above for solutions.
Code 0A: Bad Sector Flag –
On the fixed disk, this is not an error. It shows that the
flagged sector has already been added to the Bad Sector Map
and is not being used by the system. If it is known that the
sector is good, the flag can be removed by performing a low-level
format without first setting this sector in the Bad Sector
Map.
Code 0B: Bad Cylinder Detected –
This error code should not occur during the Fixed Disk tests.
Code 0C: Invalid Media –
This error code should not occur during the Fixed Disk tests.
Code 0D: Invalid Number of Sectors
– This error indicates that the fixed drive is set incorrectly
in CMOS or the controller is improperly jumpered. If these
causes are eliminated, then an electronic failure exists in
the drive, controller or cable.
Code 0E: Control Data Address Mark
– The servo information is damaged or there is an electronic
failure. If the error occurs in different locations of the
drive, suspect electronic failure. If it’s at the same
place each time, run a low-level format to map out the bad
sector. If the error occurs during a low-level format, it
is a fatal error and the drive should be replaced.
Code 0F: DMA Arbitration Out of Range
– Could be hardware failure, but first check the setup
of the system, and remove any recently installed devices to
eliminate conflicts.
Code 10: Uncorrectable CRC/ECC Error
– This is most likely a physical defect in
the requested sector, which can be corrected by mapping during
a low-level format. With MFM or RLL drives, it may indicate
mis-alignment of the heads.
Code 11: ECC Corrected Data Error
– The requested sector had an error that was
within correctable limits for the ECC circuitry. If data integrity
is of extreme importance, the sector can be marked bad during
a low-level format.
Code 20: Controller Failure
– Although this message occurs when the controller has
failed to properly control the drives, the problem could be
in the drive or the cable as well as the controller. If there
are two or more drives, it may result from an incompatibility
between a Master Drive and its Slave.
Code 40: Seek Failed –
This could result from a physical defect on the platter, which
can be corrected by a low-level format, or by a failure of
the seeking circuitry of the drive.
Code 80: Timeout Error –
This error will occur when the drive does not respond to the
controller commands. Before replacing hardware, check the
CMOS setup and the IRQ status for the drive and also check
that the drive and controller jumpers are correctly configured.
Before retesting, run the Controller Test to reset the drive.
Code AA: Drive Not Ready
– Run the controller test to reset the drive. If the
failure persists, it indicates electronic failure in the drive,
controller or cable.
Code BB: Undefined Error
– Either the fixed disk controller or cable.
Code CC: Write Fault –
A failure occurred while attempting to write to the drive.
Source of the problem could be electronic or mechanical.
Code E0: Status Register Error –
The fixed disk controller is not sending the proper signal
to the BIOS. The fault is with either the controller or the
cable.
Code FF: Sense Operation Failed –
This error should never be reported during the Fixed Disk
tests.
Controller Internal Diags Failed
– The controller circuitry is failing, or there
is an incompatibility between two drives.
Controller Write Buffer Failed
– This indicates a failure of the write buffer on the
drive itself, not the controller.
Controller Read Buffer Failed –
This indicates a failure of the read buffer on the drive itself,
not the controller.
Controller Compare Buffer Data Failed
– This indicates a failure of the fixed drive’s
buffer circuitry, on the drive itself, not on the controller
card.
Controller Recalibrate Failed –
The drive’s heads failed to properly seek Track 0. Either
the heads or Track 0 of the platter is damaged. Either is
a fatal error for the drive.
Controller Reset Failed
– The drive failed to respond to the reset command.
This failure could occur in the drive, the controller or the
cable.
Click on the following
links to find out more about using Micro-Scope
to handle Viruses and the low-level
formatting features can save you HOURS
OF TIME - and info on how to trouble shoot hard
drives.
USING
MICRO-SCOPE TO REMOVE VIRUSES
TROUBLE-SHOOTING
HARD DRIVES
Recent Review:
 "In
the service business, time is money. The Micro2000 Universal
Diagnostic Toolkit is worth its weight in gold for any service
company. The cost of the product is quickly recovered because
of faster turn around time when fixing problem systems. The
product also helps control business costs simply because technicians
are more accurately diagnosing what parts they require for
system repairs." Compunotes
Click on the FEATURES link above for a full listing
of all the features!
- Works on all Intel™ compatible computers.
- Operating system independent.
- LAN Card Testing.
- Unlimited memory testing.
- Multi-processor testing.
- Much more...
Platforms Supported - Micro-Scope runs on ANY PC with
an Intel or Intel compatible processor (from 386/486 to the
latest Pentium, AMD and Cyrix CPUs), with ISA, EISA, PCI,
PCMCIA, Plug & Play, and hosting any operating system including
all Windows versions, DOS, OS2, Linux and UNIX.
|
