Use gentoo to solve the problem of virus damage to the hard drive boot Zone

Use gentoo to solve the problem of virus damage to the hard drive boot zone-Linux general technology-Linux technology and application information. The following is a detailed description. Today, a friend came here to solve the hard disk problem. It causes no response after inserting the mobile hard disk into the computer. In severe cases, it may even crash. The reason seems to be that windows uses the automatic playback function when loading the mobile hard disk, but it cannot normally read the information of the mobile hard disk. Therefore, the machine no longer responds to user operations.

This problem does not occur in linux, because linux does not automatically load all partitions of the mobile hard disk, but you can freely select the partitions to be loaded, in addition, after loading, You do not issue further commands, and the system will not do anything on its own. As soon as it is inserted into windows, the mobile hard disk crashes and reaches my gentoo system, which can be correctly identified and read/written. Here we need to talk about it. At that time, the friend used the ntfs file system. My gentoo didn't choose to support this file system during installation, so I had to re-compile the kernel. It may be difficult to compile the kernel for many people. If you have compiled the kernel, you may feel that it is a complicated task. Therefore, I generally recommend FAT32 file systems with good versatility, or partition format, to all people I come into contact.

The friend solved the problem very easily. He just copied the content on the mobile hard disk as required, and then deleted the partition, ask him to partition again in windows.

I also found a problem in this process. When I delete a partition and create a new alert in the original location with the same size and format as the original one, the content still exists, in fact, the fdisk program under gentoo only modifies the partition table without damaging anything else. Therefore, if a virus destroys a partition table, you only need to use fdisk to delete the partition and create it again.

During the process of re-establishing the partition, I also found a problem. Although the initial position of the newly created partition is the same, the partition size is different. However, I helped him Delete and restore the three partitions, but the first problem occurred. The reason is not clear yet. There is not much time to figure out the problem, because it is necessary to read the partition table used and calculate the partition size one by one for comparison. So that's it.