Analysis and elimination of hard disk guide type fault

Hard disk is the important medium of storing information, when the hard disk fails, it is a very important work to find out the cause of failure quickly, and the failure analysis of the virus is as follows, for reference:

HDD controller failure (hard drive control failure) after the post program sends a seek command to the drive, the drive does not complete the operation within the specified time, resulting in a timeout error.

C:drive Faiiure (hard drive C drive failure)

Run Setup uttlity (running Setup function)

Pressto Resume (Press to start again)

This failure is typically due to a mismatch between the type setting parameters of the hard disk and the parameters used in the original format. Because the IDE hard disk set parameters are logical parameters, so in most cases, after the floppy disk boot, C disk can read and write, but can not start.

Fault information: Lnvalid Drive specification (Invalid drive designation)

This indicates that the partition or logical drive you want to manipulate is not defined at all in the partition table. If a partition or logical drive does not already exist for the corresponding table entry in the partition, the partition or logical drive does not exist for the operating system. This failure, the problem must first be out in the partition table. The easiest way to fix this type of failure is to do a backup of the partition table beforehand, such as the Pctools9.0 BootSafe tool, and, of course, you can recalculate the partition table according to the data in the BPB table, but it is more complicated.

Ertor Loading Operation System (Mount operating system error) This type of failure is prompted when there is an error reading the partition boot sector (boot area). Possible reasons are: first, the partition table indicates that the partition's starting physical address is incorrect. For example, the third byte of the partition table entry (the starting Sector area code) is changed from 1 to 0, this indicates that the starting address of the partition is the indicated head, the No. 0 sector on the specified track (this is the physical address, the sector should start with 1), and the INT 13H read disk fails. Second, the track flag and sector ID of the track on which the partition boot sector resides are corrupted and the specified sector is not found. Third, drive read circuit failure. This is a rare situation, most of which is a random read error, because the system boot can proceed here, at least to indicate that a primary boot sector has been read correctly.

Can not enter the system, if there is a floppy drive, led by a drive, show drive not READY ERROR (device not ready)

Insert Boot diskette in a: (Inserting a boot disk to a drive)

Press any key when ready (pressing any key after ready)

After the end of the Biospost, if booted by the hard disk, the system will read the hard drive 0 side 0 1 sectors, looking for the main bootstrapper and partition table. Therefore, any way to use software to avoid the hard disk damage of the 0-side 0, and can successfully boot the operating system is not possible! Unless you overwrite the instructions for int 19H in the system BIOS.

INT 19H failed to read the main boot sector because: first, hard drive read circuit failure, so read operation failure, is a hardware failure; second, 0-face 0 Track format and sector ID logic or physical damage, the specified sector could not be found; third, there is no error in the read, but the MBR tail is not "55AA", The system considers the MBR to be incorrect and this is a soft fault.

Non-system disk or disk ertorreplace and press any key when ready (non-system disk or disk error, reseat after pressing any key)

The boot program in the DOS boot area was found to be an error and reported this information. Possible causes: drive reset failed, root zone first sector address out of bounds (after 544M), read disk error. Most of these failures are software failures, if the BPB table damage, that is, the floppy disk boot, the hard drive can not read and write, the ndd to repair; If the BPB table is intact, simply sys C: The delivery system will boot the drive, and if it fails, it may be as follows:

Disk boot failure (diskette boot failed)

Show "Starting MS-dos ..." and then panic.

When recovering a hard drive that fails to boot, the last point to note is that the executable in Config.sys and Autoexc.bat itself is corrupted, causing the system to panic when it executes to this file, prompting on the screen: "Starting MS-dos ..." and then panic. This fault is very simple, but because there is no fault information, the average person can easily be mistaken for system file damage. When this occurs, and you are sure that the system files are intact, you can remove the two files, or the above information on the screen, quickly press the key or hold the key (interrupt Config.sys installation and Autoexec.bat execution), or press the key (step into the CONFIG.SYSJ command ) to find the files that have been corrupted.