Third, the hard disk hard disk is the warehouse responsible for the storage of our information, and the fault of the hard disk will cause the system to cause the system unable to start and the data loss, then how should we deal with the common fault of the hard disk? Common faults 1: The system does not recognize the hard disk
The system cannot start from the hard disk, and the CMO is not entered from the A disk, and the automatic monitoring function in CMOS cannot find the existence of the hard disk. This fault is mostly on the connecting cable or IDE port, the possibility of the hard disk itself is not large, and the fault can be found quickly by replacing the hard disk cable or change the IDE port and cable, etc.. If the newly connected hard drive is not accepted, a common reason is that the main slave jumper on the hard disk, if a two hard disk device on a IDE hard drive is, it is necessary to clear the primary relationship. Common faults 2: The hard drive cannot read or not identify this fault is generally caused by the CMOS setting failure. The hard disk type in CMOS correctly affects the normal use of the hard disk. Now the machine supports the "IDE Auto Detect" functionality that automatically detects the type of hard disk. When the hard disk type is incorrect, sometimes it is simply unable to start the system, sometimes it can be started, but read-write errors will occur. For example, the hard disk type in the CMOS is less than the actual hard disk capacity, the sector behind the hard disk will not be read or written, and if it is a multi-partition state, the individual partition will be lost. There is also an important cause reason. Since the current IDE supports logical parameter type, the hard disk can be used "Normal, LBA, Large", etc. If the data is installed in general mode, it is changed to other modes in CMOS. The read and write error failure of the hard disk will occur because the mapping relationship has changed, and the originally hard disk position will not be read. Common faults 3: The system cannot initiate cause this failure to be based on the following four reasons: 1. Main boot program corruption 2. Partition table corruption 3. Partition valid bit error 4. DOS boot file is damaged, the DOS boot file is the easiest After booting the boot disk, it is possible to transfer a boot file to the system. The main boot program is damaged and the partition effective bit is generally possible to use FDISK / MBR to force override resolution. Damage in partitioning table is more troublesome, because the partition cannot be identified, the hard disk will be processed as an unscaded bare disk, thus causing some software to work. However, there is a simple method - use Windows 2000. Find a system with Windows 2000, hung up the damaged hard drive, after power on, because Windows 2000 is scanned to ensure that the system hardware stability will be scanned. Windows 2000 hard disk scanner Chkdsk has a good repair capability for a variety of reasons, and the hard disk is also fixed. There is also a form of damage to the partition table. Here I am called "partition mapping", the specific performance is the same partition as the active partition. The same includes file structure, content, partition capacity. If there is a change in the partition content in any area, it will be reflected in the other, it seems to be the shadow of the map. I have met, the 6.4G hard drive becomes 8.4g (mapped 2G C zone). This problem is particularly embarrassing. This issue does not affect the use. If you don't fix it, it will not be repaired. I have no problem with you. Dry this issue, only GHOST covers and use Norton's rescue disk to restore the partition table. Common faults four: Hard disks have bad deeds this is a shocking, people who are afraid of people. Recently, IBM reputation is also under the river.
When you use the disk scanning program scanned disk scanning program SCANDISK with the system Windows system, the system prompts that the hard disk may have a bad track, then flashing a horror blue, a small yellow square slowly stretches, then, A "B" is marked on a square ... In fact, most of these bad things are logical bad tracks, which can be repaired. It is not necessary to make repairs (it is said to develop self-test tools because half of the hard disk that can't be repaired is just a good "cruel" fact). So, how should we deal with this problem? Once the program prompts if the program prompts have bad roads when scanning the hard drive with "Scandisk", first we should reuse the self-test procedures of each brand hard disk. Note that you don't choose to quickly scan because it can only find about 90% of the problem. In order to make yourself rest assured, spend more time is worth it. If the result of the inspection is "successfully repair", it can be determined to be logical bad track, you can pat the chest acknowledish; if not, then there is nothing to fix, if your hard drive is still a shelf life, then change it! Bar. Since the logic bad road is only tagged by clustering, it is no longer assigned to file usage. If it is a logical bad track, you can reformat the hard disk. However, in order to prevent formatting possible discarding phenomena (because the tags have been marked on clusters indicate that the formatting program may have no inspection, this "reality" is discarded, and the cluster is discarded), it is best to be a heavy partition, use Software such as IBM DM is still quite fast, or GHOST coverage can also, but these two programs will lose more data. Common faults 5: The hard disk capacity and nominal value are significantly invisible, the hard disk format will be less than the nominal value, but this gap will never exceed 20%, if the gap between the two is large, it should be entered when booting BIOS settings. It is reasonable based on your hard drive. If you can't still do it, you may be that your motherboard does not support a large-capacity hard disk. At this point you can try to download the latest motherboard BIOS and refresh to solve it. This fault occurs in a large-capacity hard drive with the older motherboard. In addition, the BIOS settings may occur due to sudden power-off and other reasons, which may cause this failure. Common fault six: No matter what equipment used, it is not possible to guide the system normally. This fault is generally due to the "logical lock" of the hard disk is locked, "hard disk logic lock" is a very common mischief. After the logical lock, no matter what equipment is used, it is not necessary to guide the system normally, even floppy disk, optical drive, and dual hard drives have no effect. "Logic Lock" Lock Principle: Computer will search all the order of all logical trays when booting the DOS system. When DOS is booted, first go to the partition table information of the main boot sector, then find the logic of the extension partition plate. "Logic Lock" modified normal primary boot partition record, pointing the first logical disk of the extension partition to yourself, so that DOS looks for the first logical disk while starting, find yourself, so A dead cycle is formed. The method for unlocking "logical lock" is "hot plug" hard disk power supply. That is, when the system starts, do not power the locked hard disk, and then give the hard disk "hot" on the power line after starting, so that the system can control the hard drive normally. This is a very dangerous way. In order to reduce the degree of danger, after "logic lock", everyone is best to handle according to the following relatively simple and secure methods.
