You may have read a lot of articles on how to maintain Windows. The registry and system files are also backed up every day. But when your partition fails abnormally these backups are all useless-because the hard disk is used to boot the partition has a problem the system cannot boot to the command prompt at all and the recovery operation cannot start; or you use the system disk Started but the computer doesn’t recognize the hard disk at all and your backups are not very effective; or you find that you can enter Windows but one of the partitions is missing then the corresponding file data is gone... The following author is about the abnormality of these partitions Let’s analyze the fault and hope to help you:
One. Can’t boot the system at all.
This is the most serious and common problem. It is a problem with the partition table. This problem is mostly caused by viruses or logic bomb attacks. For example CIH in addition to attacking the motherboard’s BIOS also destroys the partition table by the way. Many boot sector viruses also like to attack the partition table or parasitic in it; in addition hard disk logic locks It is also a trick in the partition table.
Recovery method: You are required to have the correct partition table backup. The user who made the backup can easily recover and the data is basically not lost. If you don’t usually back up the partition table you have to try to repair it with the partition table reconstruction function provided by the KV series or other anti-virus software. This repair can only save the hard disk itself and there is no guarantee for the data in the partition. safe.
Two one or several partitions are missing
This is mostly a sequelae of failure to install multiple operating systems. Because Windows 2000 and XP released by Microsoft now support the NTFS format the user can format or convert the partition format to NTFS during installation. Novices may choose this format without knowing it. If the XP installation program crashes in the middle of the format conversion it is likely to corrupt the partition table; or if multiple operating systems are installed and uninstalled abnormally directly deleting the NT kernel operating system will also cause partition table errors.
In addition improper use of Ghost may also cause abnormal partitions. For example a machine was originally installed with 98 and 2000 dual systems and 2000 was installed on the G drive. After 98 crashed the owner used Ghost to restore. He had not installed 2000 when he originally backed up 98. Now when I start I enter 98 without system selection and I can’t see the G drive in 'My Computer' because he formatted G as NTFS and WIN9X does not support NTFS format regardless of the graphical interface or the boot disk. So the result can be imagined. For some new machines the JS map saves trouble and the operating system is installed directly by GHSOT so you may be able to see all partitions in Windows 98 but in pure Dos mode you cannot access one or more of the following partitions. This is because the partition table BUG caused by the difference between his GHOST backup and your machine hardware.
The solution: need to use the Windows installation program to repair or reinstall the system. If it doesn't work only back up the data and re-use the FDISK partition.
3. Why is there a hard disk partition in a dual hard disk system that cannot be accessed?
With the gradual price cuts of large hard drives more users have dual hard drives. For some people the motherboard does not support large hard drives over 32G and there is no tool management such as DM. It is not surprising that the dual hard drives cannot be recognized. But some machines are newly installed why can't I access the partition of the second large hard disk in WIN9X? This is closely related to the IDE patch for dual hard disk motherboards—because the built-in IDE driver of Windows 9X itself is imperfect the hard disk model is often not recognized and it is marked with TYPE46/47 and the ULTRA DMA function of the hard disk is also Did not really open. If you don't plan to upgrade to Windows 2000 or XP you have to install the IDE drivers and patches that come with the motherboard especially motherboards with VIA and SIS chipsets.
Without loading the patch Windows 98 usually only recognizes the hard disk set as the primary disk but the second hard disk that is not recognized in the BIOS or set to NONE is not supported by Windows 9X. ; Under the pure DOS state the second hard disk is completely gone. Dual hard disks will also cause the partition letter to change that is the first partition of the second hard disk usually occupies the 'D' letter.
Solution: The user must install the patch correctly before changing the order of the drive letter in the graphical interface and actually opening the ULTRA DMA function such as VIA's 4IN1 driver package. The author recommends that you upgrade to Windows 2000 or higher. The NT kernel operating system can automatically recognize most of the chipsets so as to manage your IDE hard drives well. For the drive letter problem the method of not setting the second hard disk primary partition is also acceptable please refer to related articles.
Four. Problems caused by deleting the primary partition and the extended partition order
A machine tried to install the Linux system but failed so the owner gave up LINUX and decided to reinstall WIN98. However he has been unable to install successfully. He used FDISK to delete the primary partition then repartitioned with the FDISK/MBR command and the low-level formatting command still did not work. He now runs SCANDISK to check that there is no problem with each partition but whenever he tries to install 98 the following message appears and he cannot continue the installation:
fault outside of ms-dos extend
Analysis: This is mostly because when you delete a partition you don’t pay attention to it first The failure caused by the extended partition and then to the primary partition although this probability is not very high; and the current partition tools including PQ partition master have a feature that is after the partition fails with this tool it will not be recognized when used again. The partition table written by this partition tool must be replaced by another partition tool. For example if you make an error with FDISK you will always get an error when you use FDISK. The same is true for PQ. After a partition crashes in the middle of a partition the volume label of the partition may not always be read correctly.
Solution: To delete a partition please delete the extended partition first and then delete the primary partition; if it cannot be done correctly with some partitioning software please switch to another one so it is best to have it ready on hand FDISK PQ or DISKMAN software just in case; in addition once again remind you to back up your partition table under normal conditions. If it doesn't work you can only use FDISK after re-low-level formatting.
5. Problems caused by cross-link errors on the partitions
If you use quick format (FORMAT/Q partitions) to clear data the cross-link errors on the partitions may cause you to install the operating system It always fails. Because the quick format does not detect the data situation of the partition it just deletes the data quickly.
Solution: If you find that the machine with the same configuration can successfully install Windows that is there is no problem with the hardware but the installation of the operating system on your machine is always unsuccessful please try to use the FORMAT method. Change your partition once. Some fake bad sectors must be formatted to repair them. In addition some novices are always confused about the capacity of their partitions. For example if you buy a new hard disk with a nominal 40G how come the total number of partitions is only 36 38G? There are two situations:
1. Windows calculation is very rough equating 1K with 1000 and theoretically the calculation capacity of 1K should = 1024 bytes
Windows 2000 partition abnormal failure troubleshooting