 |
Boot Disk Read Error and Salvaging the Data From a Failed Drive |
 |
Experiencing a Non-System Disk Error due to a bad or damaged disk drive is
often caused by the Basic Input/Output System (BIOS) being unable to locate the
hard disk's boot sectors, and master boot record on your drive.
Important data could be lost if the correct steps are not taken and you are
experiencing boot problems. Immediately contact data-recovery specialists at
SalvageData UK if you determine that the problem is the result of a disk
drive. Do not attempt to fix the problem yourself by using off-the-shelf
products or utilities, and by no means open the drive outside the protection of
a class 100 clean room environment. By doing so, it’s very easy to damage the
drive, which could result in you permanently destroying and losing precious
data.
One reason you receive such an error message is that the BIOS cannot find the
drive, or one of the drives was not specified in the CMOS setup. Make sure that
all the floppy boot drives have been removed from your system because this could
be the cause for the error message.
Due to nearly 95 percent of all computer users working in the realm of PC
architecture, a similarity in error messages can be seen. Aside from variation
in a few words, the messages mostly have the same meaning. Thus, it is a wise
assumption that your problem is related to a disk drive failure.
Below you'll find some examples of commonly used IDE Hard Drive error messages.
They all are warnings of a failing or failed hard drive. There's a very good
chance you need our services if you receive any of these errors! Call a
SalvageData UK professional for a free consultation.
|
I/O Error
1700 Disk Read Error
1701 Fixed disk general POST error
1702 Drive/controller time-out error
1703 Drive seek error
1704 Controller failed
1705 Drive sector not found error
1706 Write fault error
1707 Drive track O error
1708 Head select error
1709 Error Correction Code (ECC) error
1710 Sector buffer overrun
1711 Bad address mark
1712 Internal controller diagnostics failure
1713 Data compare error
1714 Drive not ready
1715 Track O indicator failure
1716 Diagnostics cylinder errors
1717 Surface read errors
1718 Hard drive type error
1720 Bad diagnostics cylinder
1726 Data compare error
1730 Controller error
1731 Controller error
|
1732 Controller error
1733 BIOS undefined error return
1735 Bad command error
1736 Data corrected error
1737 Bad track error
1738 Bad sector error
1739 Bad initialization error
1740 Bad sense error
1750 Drive verify failure
1751 Drive read failure
1752 Drive write failure
1753 Drive random read test failure
1754 Drive seek test failure
1755 Controller failure
1756 Controller Error Correction Code (ECC) test failure
1757 Controller head select failure
1780 Seek failure; drive 0
1781 Seekfailure; drive 1
1782 Controller test failure
1790 Diagnostic cylinder read error; drive 0
1791 Diagnostic cylinder read error; drive 1 |
A majority of the above listed disk read errors indicate that you need
professional data-recovery help. Immediately stop what you're doing, and contact
SalvageData UK. Here's some background information explaining what causes such errors: Your computer BIOS performs a power-on self test (POST) when your system is
turned on. It does this to verify that everything is working properly on your
PC. When the BIOS boots your system to the point that it gains access to its
video subsystem, it displays the information about the PC during the booting
process. It uses the video system to correspond error messages like those above.
Different parts of your system can launch an error message depending upon how
far the booting process has progressed. As the BIOS is responsible for most of
the functions for booting, most error messages originate from there. Still,
other physical errors can be relayed to the OS, and are usually related to your
OS.
|
WARNING / PLEASE NOTE:
|
|
|
Never open the cover of a failed hard disk drive in attempt
to salvage or recover data. Today’s hard disk drives tolerances are very tight,
and the materials used are so technologically advanced that even the smallest
speck of dust, contaminant, or even gaseous vapor can disrupt the delicate
balance of the drives ecosystem. Any such disruption not only destroys the
drive, but all the data contained on it.
Data is written on the drives by one or more read/write heads that are designed
to manipulate magnetic particles on the disk surface. This read/write activity
happens with the read/write heads literally flying one -two-thousands the width
of human hair above the platters at speeds of anywhere from 4,000 to 15,000 RPM.
Our data salvaging and recovery process is conducted in a world-class 100 clean
room environment by a first-rate group of mechanical and electrical hard drive
engineers. They use carefully researched tools and materials to safely recover
and ensure the greatest possibility of success.
|
