Novice tutorial: boot failure solution for hard disk failure

Hard disk is very important for the computer, many of our files are stored in it, if the error occurs, the data may be destroyed, of course Hard disk failures are also very diverse. Today, the main solution is the solution to the hard disk boot failure.

1, HDD controller failure (hard disk drive control failure) After the POST program issues a seek command to the drive, the drive does not complete the operation within the specified time and a timeout error occurs. C:drive faiIure RUN SETUP UTTLITY Pressto Resume This type of fault is generally caused by the type setting parameters of the hard disk not matching the parameters used in the original format. Since the setting parameters of the IDE hard disk are logical parameters, in most cases, after the floppy disk is booted, the C disk can be read and written normally, but it cannot be started.

2, fault information: lnvalid Drive Specification (invalid drive designation) This is to indicate that the partition you want to operate or the logical drive is not defined at all in the partition table. If a partition or a logical drive does not already exist in the partition table, then the partition or logical drive does not exist for the operating system. This kind of failure, the problem must first appear in the partition table. The easiest way to fix such a fault is to back up the partition table in advance. For example, the Bootsafe tool of Pctools 9.0 can be used. Of course, the partition table can be recalculated based on the data in the BPB table, but it is more complicated.

3, Ertor Loading Operation System This type of fault is prompted when reading the partition boot sector (BOOT area) error. Possible reasons are as follows: First, the partition starting physical address indicated by the partition table is incorrect. For example, changing the third byte (starting sector number) of the partition table entry from 1 to 0 means that the starting address of the partition is the indicating head, the 0th sector on the specified track (here, the physical address, The sector should start with 1). After the INT 13H fails to read the disk, the error is reported. Second, the track mark and sector ID of the track where the partition boot sector is located are damaged, and the specified sector cannot be found. Third, the driver read circuit is faulty. This situation is relatively rare, most of which are random read errors, because the system boot can proceed here, at least indicating that a master boot sector has been correctly read.

4, can not enter the system, if there is a floppy drive, it is booted by A drive, display: DRIVE NOT READY ERROR (device is not ready) Insert Boot Diskette in A: (insert boot disk to drive A) Press any Key when ready (after pressing any key) After BIOSPOST is finished, if it is booted by the hard disk, the system will read the 0 channel 1 sector of the hard disk and look for the main boot program and partition table. Therefore, any method that uses software to try to avoid the 0-side 0 of the hard disk damage, and the ability to successfully boot the operating system is impossible! Unless you rewrite the relevant instructions of the INT 19H in the system BIOS. The reasons for the failure of the INT 19H to read the main boot sector are as follows: first, the hard disk read circuit is faulty, causing the read operation to fail, which is a hardware failure; second, the 0-side 0-track format and the sector ID are logically or physically damaged, and cannot be found. To the specified sector; third, there is no error in reading the disc, but the read MBR tail is not "55AA", the system thinks that the MBR is incorrect, which is a soft fault.

5, Non-System Disk or Disk Ertor Replace And press any key when ready (non-system disk or disk error, press any key after relocation) DOS BOOT area boot program found error, reported This information. Possible cause: Drive reset failed, the first sector address in the root directory area is out of bounds (after 544M), and the disk read error. Most of these faults are software faults. If the BPB table is damaged, the hard disk cannot be read and written normally after booting with a floppy disk. It can be repaired with NDD. If the BPB table is intact, simply SYS C: The transfer system will boot the drive if it fails. , then show: Disk Boot Failure

6, NO ROM BASIC (no solidified BASIC) SYSTEM HALT (system shutdown) This is a very old machine will appear prompt, the main boot program The role is to find an active partition (bootable partition) in the four entries of the partition table. If none of the four entries is the active partition, the system does not know where to boot the operating system, can only execute INT 188H, call the solidified BASIC program, if it does not solidify BASIC, it will cause a crash. The easiest way to fix this is to use FDISK's second function: Set activeparti-tion to specify a bootable partition.

7, display "Starting MS-DOS..." and then crash in the recovery of the hard disk can not boot soft fault, the last point worth noting is the executable in CONFIG.SYS and AUTOEXC.BAT The file itself has been corrupted, causing the system to crash when it reaches this file. The screen prompts: “Starting MS-DOS……”, then crashes. This fault is very simple, but because there is no fault information, it is easy for people to misjudge the system file corruption. When this happens and you are sure that the system files are intact, you can remove the two files, or the above information appears on the screen, quickly press the key or hold down the key (interrupt the CONFIG.SYS installation and AUTOEXEC.BAT execution) , or press the key (step through the commands in CONFIG.SYSJ) to find out the corrupted file.

There are probably these seven aspects. You can take a good look. It is best to make time to look at it patiently. It is very helpful for the problems encountered in the future. Of course, you have the best solution. I hope to help everyone.