Save the hard drive

If the computer is used for a long time, it will inevitably get stuck. If it is just a card, it will be a little more acceptable. Nima turned on the blue screen. The first thing that comes to mind is: poisoning. After half a day, no virus was detected. Depressed, Is there too much garbage? Restore directly. After the restoration, the speed will go up, and the blue screen will not be displayed, and the boot of a virtual machine will not be stuck.

However, the blue screen started after a while. After an abnormal shutdown, the system prompts the disk self-check. Therefore, the system conducts the self-check. There will be more than one xxx file record unreadable. Listen to the noisy voice of the hard disk... Well, I think that hardware startup accounted for a large part of the previous boot time. Is it because the hard disk is about to be decommissioned?

It is initially assumed that the hard disk has a logical bad track. chkdsk is used to detect and repair the hard disk, but the boot detection is slow. After detection, many unreadable file records are displayed. So I found several tools online:
1. boot the efficiency source with a USB flash disk as a floppy disk:
The following methods are widely used on the Internet:
Use usboot to make a USB flash drive into a fdd boot disk
Create an empty floppy disk image, attach it to the virtual machine, and run the installation program on the Virtual Machine to obtain the soft drive image fd0.img. Copy it to the grub directory in the USB flash drive boot directory.
Use grub4usb to modify menu. lst to enable fd0.img on the USB flash drive.

Problem:A large USB flash drive cannot be made into a fdd boot disk, and usboot fails to be created.

2. Enable the efficiency source with a USB flash drive as a disc:
Open the iso file, which contains an iso file and a pdf file.
Extract the iso
Disk Partitions from mass production to USB disks.
Starting from the USB-ODD, you can enter the rate source.

Problem:No hard disk is found. The efficiency source does not support the SATA interface. Use the IDE interface. The BIOS settings are fruitless.

3. PQ test Disk:

Select disk C and test the disk. An error is reported.

Problem:Unable to operate, Incompatible System

After a long time, it was ineffective, and too much data was difficult to format. Throw the keyboard and open a chkdsk to let it go slowly.
The result is very fast --. Bad blocks are also lost. Do you know that a disk detection has been silently fixed for me?
Optional |
After the instance is started, use hd tune pro to test. In the health condition, the C5 indicator is yellow and dozens of sectors to be allocated are displayed. Immediately perform error detection. After the detection is complete, several places are marked with red, and the approximate location is recorded. Directly scan for the roughly damaged area of the DG and try to fix it after scanning. After a long wait, I fixed some items, but some parts of drive C and drive D failed to be repaired. During the HD tune test, C5 increased a lot.
Later, I thought there was still a lot of available space for the system disk. Could I directly resize the system disk and shield the bad channels. So I used the PM partition in WINPE. After waiting for a long time, an error occurred, "the partition file system is damaged ". It is estimated that a bad track has been detected. Considering that the system disk may be limited after the system is restored, the repair was successful again in WINPE with DG. C5 warning miraculously disappears. Isn't it a physical bad track?