three.five.3 Evaluation and elimination of tough disk boot failure

The really hard disk boot failure typically occurs when the machine is began. This failure might be caused by the system itself or it may be attributable to a virus. The fault brought on by the virus can be solved by checking the anti-virus. The following will analyze the faults other than the virus.

1.HDD controller failure (tough drive handle failure)

This can be a timeout error that happens when the drive does not complete the operation within the specified time soon after the POST system sends a seek command towards the drive when beginning the machine. When this error occurs, the tough disk could possibly be broken.

two.C: drivefailure (tough disk C drive failure), RUNSETUPUTTLITY (run setting function), PresstoResume (press to restart)

This kind of failure is commonly simply because the kind setting parameters with the really hard disk usually do not match these used during formatting. Because formatted samsung memory card data recovery from the IDE difficult disk are logical parameters, in this case, after the floppy disk is started, the C drive may also study and write typically, but it can't be started.

3. InvalidDriveSpecification (invalid drive letter)

In the event the corresponding entry of a partition or logical drive within the partition table will not currently exist, then for the operating technique, the partition or logical drive does not exist, so this kind of failure is normally within the partition table. The easiest solution to repair this kind of failure is always to make a backup from the partition table in advance, including Pctoots9.0, Ky3000, and so on. have this function.

four.ErrorLoadingOperation.Method (incorrect operating method)

This sort of fault is prompted when there is an error reading the partition boot area (BOOT location), the purpose may very well be ①

The partition starting physical address indicated by the partition table is incorrect. As an example, as a result of misoperation

The beginning sector quantity (within the third byte) is changed from 1 to 0, so INT13H reports this error just after failing to read the disk. ② points

The track mark and sector ID on the track where the sector boot sector is situated are damaged plus the specified sector can't be found. ③ drive read

circuit failure.

5. The difficult disk cannot boot the technique. If there is a floppy drive, it will likely be booted by the A drive, displaying DRIVENOT, READYERROR (device not ready), InsertBootDisketteinA (insert the boot disk into the A drive), Pressanykeywhenready (press any key when prepared).

not detected samsung memory card data recovery is since the program is booted by the hard disk, and it truly is necessary to read the really hard disk 0 side 0 channel 1 sector through the INT19H within the BIOS to seek out the primary boot system and partition table. The motives for the failure of INT19H to study the master boot sector are: ① The tough disk read circuit is faulty, causing the study operation to fail, that is a hardware failure: (Snow 0 side 0 track format and sector ID are logically or physically broken, as well as the specified fan can't be identified Region: ③ There is absolutely no error in reading the disk, however the tail on the study MBR just isn't '55AA', the technique considers the MBR to be incorrect, which can be a soft fault.

6.Non ---- SystemDiSkOrDiskError

ReplaceAndPressanykeywhenready (non-system disk or disk error, press any key after re-changing the disk) The boot system in the DOSBOOT region finds an error after execution and reports this message. The feasible factors are: the first sector address on the root directory region of ​​the hard disk is out of bounds (following 540MB), and the disk reading error. Most of these failures are software program failures. When the BPB table is damaged, the difficult disk cannot be study and written normally immediately after booting using the floppy disk. , Can be repaired with NDD. If the BPB table is intact, only a simple SYS has been transferred towards the system to boot.

7.StartingWindows ... (and after that crash)

Commonly speaking, this really is simply because the executable files in CONFIG.SYS and AUTOEXC.BAT have already been broken, which makes the method freeze when it reaches this file. This fault is very basic, but mainly because there isn't any fault details, a lot of people are prone to misjudgment. When this phenomenon happens, and also you are confident that the system files are intact, you could eliminate the two files, or when the above message appears around the screen, promptly press the 'F8' essential, and then choose the single step to discover the colour warp Broken file.

8. InvalidPartitionTable (invalid partition table)

Immediately after locating the active partition, the master boot program will also decide whether the remaining three partition entry boot flag bytes (initial byte) are all 0, that may be, to confirm whether or not t here 's only one particular active partition. If one will not be 0, the system will report an error and crash.

9. InvalidMediaTypeRedingDriveX (X drive media form is invalid)

This message is prompted for the invalid BPB table within the DOSBOOT area. more info is a bridge that converts the logical address used by DOS to study and create the hard disk into a physical address. If the BPB table is broken, DOS cannot operate the disk.

10.HDCcontrollerfail (Failed to control the tough disk controller)

This type of fault is usually a hardware fault. Just after the POST plan sends a reset command for the controller, it does not get an interrupt response from the controller inside the specified time. It might be that the controller is damaged or the cable will not be connected. In addition, the failure of controller handle is also associated with the correct setting of challenging disk parameters.

11. The technique doesn't recognize the hard disk

The system can not start out in the hard disk, nor can it enter the C disk in the A disk or the optical drive, along with the challenging disk cannot be detected within the CMOS. This sort of failure may well seem around the connecting cable or IDE port. The tough disk itself is unlikely to fail. You'll be able to replace the really hard disk cable or replace the IDE port and cable for replacement test. You'll rapidly find the fault. If two difficult drives are connected to a data line, the master-slave connection will have to be clearly distinguished.

12. Failure brought on by CMOS

The appropriate variety of really hard disk in CMOS directly impacts the normal use from the challenging disk. At present, CMOS supports the 'IDEAutoDetect' function, which can automatically detect the kind of tough disk. When the really hard disk kind is incorrect, from time to time it might not be achievable to begin the program, often it can be began, but study and create errors will occur. One example is, if the really hard disk variety in CMOS is smaller than the actual challenging disk capacity, the sectors behind the tough disk will not be readable or writable. If it is in a multi-partition state, some partitions will probably be lost and can't be study. There is certainly also a fault. Considering the fact that the present IDE supports logical parameter forms, the hard disk can use 'Normal, LBA, Large', and so on. When the information is installed inside the general mode, plus the CMOS is changed to a further mode, A read / create error in the difficult disk will take place mainly because the mapping relationship has changed and also the original right hard disk location cannot be study.

13. Startup failure brought on by master bootloader

The principle boot plan is positioned inside the main boot sector of your difficult disk, employed to detect the correctness of the challenging disk partition, and figure out the active partition, after which give handle for the active partition of DOS or other operating systems. If this plan is broken, you are going to not have the ability to boot in the challenging drive, but it is possible to read and write towards the challenging drive right after booting from the floppy drive or optical drive. The approach to fix this fault is reasonably easy. It is most hassle-free to use Fdisk with the larger version of DOS. When operating FD / mbr, the principle boot plan from the difficult disk might be directly replaced (overwritten). In truth, the primary boot sector with the really hard disk is developed by this plan, Fdisk, EXE, includes a complete hard disk master boot system. Even though the DOS version is frequently updated, the principle boot system on the tough disk has not changed. From DOS3X to Windows95 DOS, as long as a DOS boot disk is found to begin the method and run this plan, it may be repaired.

14. Startup failure caused by partition table error

The partition table error can be a really serious error of the challenging disk, and diverse error levels will result in different losses. If there is no active partition logo, the pc cannot begin, but the difficult disk can be read and written just after the technique is booted in the floppy drive or the optical drive, and can be repaired by resetting the active partition through Fdisk. When the sort of a certain partition is wrong, it could cause the loss of a specific partition. The fourth byte of the partition table would be the partition kind value. The standard bootable DOS partition worth greater than 32MB is 06, when the extended DOS partition value is 05. Many men and women use this sort of worth to recognize the encryption technologies of a single partition. Restoring the original correct kind worth can restore the partition to typical. You will discover other information within the partition table for recording the start out or end address of the partition. The harm of these data will bring about confusion or loss of the partition. The readily available techniques are to utilize the backup partition table data to write back, or to get the partition table data from other really hard disks on the exact same type with all the similar partition status. The recovery tool can use tool computer software for example NU, which can be extremely handy to operate. Naturally, Debug also can be utilised for operation, but the operation is cumbersome and has specific dangers.

15. ’The partition valid flag is wrong

There's also an essential aspect inside the major boot sector in the tough disk, that is certainly its final two bytes: 55AA, this byte is a valid sign on the sector. When booting from a tough disk, floppy disk, or CD-ROM, these two bytes will be detected, if it exists, it can be considered that there is a challenging disk, otherwise the really hard disk will not be recognized. This can be made use of for the encryption technologies on the complete really hard disk, and also the Debug system is usually utilised for recovery processing. Also, when the DOS boot sector has no boot logo, the method startup will show as 'MmissingOperating.System'

16. Boot failure brought on by DOS boot program

The DOS boot method is primarily composed of DOS boot sectors and DOS technique files. System files mostly consist of 1 / O, SYS, MSDOS.SYS, COMMAND.COM, exactly where COMMAND.COM is actually a DOS shell file, which is usually replaced with other equivalent files, but by default it can be a necessary file for DOS startup. In the DOS method of WindowesXP, MSDOS.SYS is often a text file, which is a required file to begin Wmdows, but this file isn't necessary when only DOS is started. When the DOS boot fails, you can make use of the SYSC: command to transfer the method just after booting the program in the floppy disk or CD-ROM, it is possible to repair the fault, which includes the boot sector and technique files could be automatically repaired to a regular state.

17. Study and write failure attributable to FAT table

The FAT table records the storage address with the hard disk data, and each and every file features a set of FAT chains to specify the cluster address w here it is stored. The damage of FAT table suggests the loss of file content material. The DOS method itself gives two FAT tables. In the event the currently utilised FAT table is broken, you could make use of the second one to overwrite and repair it. Having said that, since not detected samsung memory card data recovery from the FAT table as well as the address of your second FAT table of the disks with diverse specifications are also not fixed, you will need to uncover the correct place when repairing. Some tool software program, including NU, has such a repair function, and it's also extremely hassle-free to utilize. This operation also can be achieved by utilizing Debug, that is, the second FAT table is often moved to the first table working with the corresponding command. In the event the second FAT table can also be broken, the challenging disk cannot be restored to its original state, however the information from the file continues to be stored in the data location of ​​the hard disk. You'll be able to use CHKDSK or SCANDISK commands to repair it, and ultimately get the CHK file The sector data with the FAT chain is lost. If it is actually a text file, the total or partial file content might be extracted from it.

18. Boot failure brought on by damaged table of contents

The directory table records data including the file name with the file in the really hard disk, as well as the most significant item will be the starting cluster quantity of the file. Considering the fact that the catalog table has no automatic backup function, a big variety of files will probably be lost in the event the catalog is damaged. 1 solution to lessen losses would be to use CHKDSK or SCANDISK program recovery system to look for CHK files from the tough disk. Due to the fact only the first cluster number is lost when the directory table is broken, every CHK file is really a total file, and most files is usually recovered by altering it towards the original name.