Common troubleshooting steps for hard disks common faults 1: Hard Disks are not recognized by the System
The system cannot be started from the hard disk, nor can it be started from disk A into disk C. The existence of the hard disk cannot be found by using the automatic monitoring function in CMOS. Most of these failures occur on the connection cable or IDE port. The failure of the hard disk itself is unlikely. You can re-plug the hard disk cable or change the IDE port and cable to conduct replacement tests, you will soon find the fault. If the new hard disk is not accepted, a common cause is the master-slave jumper on the hard disk. If an IDE hard disk is connected to two hard disk devices online, the master-slave relationship should be clearly defined.
Common Fault 2: hard disks cannot be read/written or identified
This type of fault is generally caused by a CMOS setup fault. Whether the hard disk type in CMOS is correct directly affects the normal use of the hard disk. All current machines support "ide"
Auto
Detect, which can automatically detect the hard disk type. When the hard disk type is wrong, sometimes the system cannot be started, sometimes the system can be started, but a read/write error occurs. For example, if the hard disk type in CMOS is smaller than the actual hard disk capacity, the sectors behind the hard disk cannot be read or written. If the disk type is multi-partition, individual partitions will be lost. There is another important cause of failure. Because the current ide supports the Logic Parameter type, the hard disk can adopt "normal, LBA, large" and so on. If data is installed in normal mode, changing to another mode in CMOS will cause a read/write error on the hard disk. Because the ing relationship has changed, the original hard disk location cannot be read.
Common Fault 3: The system cannot be started
The fault is usually caused by the following four reasons:
1. The main Bootstrap program is damaged.
2. Partition Table Corruption
3. Invalid partition bit
4. Dos boot file corruption
Among them, the DOS boot file is the easiest to damage. After booting with the boot disk, You can transmit a boot file to the system. Fdisk can be used for primary boot program corruption and partition space corruption.
/MBR forced overwriting solution. Partition Table Corruption is troublesome. Because the partition cannot be identified, the system will treat the hard disk as an unpartitioned bare disk, so some software cannot work. But there is a simple method-using Windows
2000. Find a system with Windows 2000 installed and mount the damaged hard disk.
Will scan the new attached hard disk. Windows 2000 hard disk scan program chkdsk for hard disks damaged for various reasons
With good repair capability, the hard disk is basically repaired after scanning.
Partition Table Corruption is another form, which is called "partition ing" here. The specific manifestation is that a partition is the same as an active partition. It also includes the file structure, content, and partition capacity. If the partition content is changed in any zone, it will be reflected in another place, as if it was a ing shadow. I once met that 6.4g's hard drive is 8.4 GB (mapped to Zone C of 2 GB ). This problem is especially embarrassing. It does not affect the use of it. If it is not fixed, it will not happen. But when it is to be fixed, Norton's diskdoctor and pqmagic become blind, you can ignore the inconsistency between the total partition capacity and the actual disk size. To solve this problem, only ghost overwrites and uses the Norton rescue disk to restore the partition table.
Common Fault 4: Bad Sectors on Hard Disks
This is a shocking word for fear. IBM's reputation has been increasing recently. When you scan a hard disk using the Scandisk scanning program that comes with the Windows system, the system prompts that the hard disk may have a bad track, and then flash a piece of blue, a small yellow box slowly expand, then, a "B" is marked on a block "......
In fact, most of these bad channels are logical and can be repaired. There is no need for repair at all (it is said that the vendor developed the self-check tool because it cannot stand the fact that half of the hard drive is actually good ).
So what should we do when such a problem occurs?
If the program prompts a bad track when scanning the hard disk with "Scandisk", we should first re-use the self-check program of each brand hard disk for full scanning. Note: Do not select quick scan because it can only detect about 90% of problems. To reassure yourself, it is worthwhile to spend more time here.
If the result of the check is "successful Repair", it can be determined that it is a logical bad track, you can pat your chest to breathe; if not, there is no repair possibility, if your hard disk is still in warranty, replace it.
Because the logical bad track only marks the cluster number and will not be assigned to the file later. If it is a logical bad track, you only need to reformat the hard disk. However, to prevent possible discarding of formatting (because the cluster number has been marked as a bad cluster, the formatting program may accept this "reality" without checking it ", so discard the cluster), it is best to re-partition, such as IBM
Software such as DM is still quite fast, or ghost coverage is also acceptable, but both solutions will lose some data.
Common Failure 5: the hard disk capacity is obviously different from the nominal value
In general, the disk size after formatting will be smaller than the nominal value, but the gap will never exceed 20%. If the gap between the two is large, you should enter BIOS settings at boot. Make proper settings based on your hard disk. If not, it indicates that your motherboard does not support large-capacity hard disks. You can download the latest motherboard BIOS and refresh it. This type of fault occurs most when a large-capacity hard disk is used together with an older motherboard. In addition, BIOS settings may be messy due to sudden power outages or other reasons, which may also lead to such a failure.
Common Fault 6: no device can guide the system normally
This kind of fault is generally caused by the virus "logical lock" lock on the hard disk. "logical lock on the hard disk" is a very common prank. After the logical lock is in place, no matter what device is used, the system cannot boot normally, or even a floppy disk, optical drive, or dual hard disk is useless.
The principle of "logical lock" locking: The computer will search for the order of all logical disks when guiding the DOS system. When DOS is guided, first find the partition table information of the primary Boot Sector, find the logical disks of each extended partition. The "logical lock" modifies the normal primary boot partition record and points the first logical disk of the extended partition to itself. After dos finds the first Logical Disk at startup, searching for the next logical disk always finds itself, which forms an endless loop.
The easier way to unlock the "logical lock" is to "Hot Plug" the hard disk power supply. When the system is started, do not add the locked Hard Disk
Power supply. After the boot is complete, the power cord is attached to the hard disk "hot plug", so that the system can properly control the hard disk. This is a very dangerous method. In order to reduce the risk level, after encountering a "logical lock", we 'd better follow the following simple and safe methods.
1.
First, prepare a boot disk, and then use the binary editing tool (ultraedit recommended) on other normal machines to modify the I/O on the floppy disk. sys File (remember to change the attribute of the file to normal before modification). Specifically, search for the first "55aa" string in the file and change it to any other value. With this modified system floppy disk, you can start with the locked hard disk. However, because the partition table on the hard disk has been damaged, you cannot use "fdisk" to delete or modify the partition. You can use diskman or other software to restore or recreate the partition.
2.
Because DM is a hard disk tool that does not rely on the motherboard BIOS to identify the hard disk, even if the hard disk is set to "NONE" in the motherboard BIOS, DM can also identify the hard disk and perform operations such as partitioning and formatting, so we can also use the DM software to unlock the hard disk.
First, copy the DM to a system disk, connect it to the locked hard disk, start the system, press the "Del" key to enter the BIOS settings, and set all ide interfaces
"None", save and exit, and then start the system with a floppy disk. The system can start with a lock, because the system does not have a hard disk at all. Run DM after startup. You will find that DM can recognize the hard disk and select the hard disk for partitioning and formatting. This method is simple and convenient, but there is a fatal drawback that the data on the hard disk cannot be saved.
Common Failure 7: hard disks cannot be manually lifted during startup, and hard disks are not recognized by the System
Such faults are often the most terrible. The main cause of this failure is that the data in the primary Boot Sector of the hard disk is damaged, as shown in the loss of the primary boot logo or partition logo of the hard disk. The culprit of such a fault is often a virus, which overwrites the wrong data to the primary Boot Sector. Some common anti-virus software on the market provides the hard disk repair function. You may try it. However, if you do not have such a tool disk at hand, you can try to write all 0 data into the Main Boot Sector, and then re-partition and format it. The method is as follows: start the computer with a clean dos boot disk, enter a: \> and enter the following command (note in brackets ):
A: \> debug (enter the debug program)
-F 100 3ff0 (clear the content of the data zone as 0)
-A 400 (Add the following command)
MoV ax, 0301
MoV X, 0100
MoV CX and 0001
MoV dx, 0080
INT 13
Int 03
-G = 400 (execute the command to operate the disk)
-Q (release the debug program)
This method can generally restore your hard disk, but the data in it is hard to be saved because you need to partition and format it. The above are some common faults and Solutions of hard disks in daily use. I hope you will be inspired. If the failure of the hard disk is serious and cannot be handled using the above methods, it is likely that it is a mechanical failure. Because the structure of the hard disk is quite complex, it is not recommended that you disassemble it yourself. Instead, you should resort to professional personnel for repair.
Sequence of Hard Disk troubleshooting steps
