Always disk checking

There are three reasons for this problem (usually only two on the Internet ):

First, I have never encountered such a bad track, so as long as I don't often attack hard disks, there will be no bad track. If it is true, I should follow the online method to say, block bad channels.

Second, file inconsistency or errors, usually caused by abnormal shutdown. You can do this with a disk checking at startup without worry!

Third: serious file errors. I do not know whether it is serious or not, but disk checking is required every time I start the system, which cannot be tolerated at this time.

The reason for this is that VMware is used as a virtual system and the actual hard disk is used as the virtual system. As a result, when grub selects the system, it accidentally selects the running Windows, this is disastrous. I quickly reset the virtual machine. But the result is that the actual machine will need the hard disk to detect the edisk in the future, because the edisk originally had my pagefiles. Solution:

First switch the virtual cache to another disk.

Run the command fsutil dirty query X: (X indicates the partition you want to view). First, check whether the E disk is faulty. The result shows "damaged".-I was shocked.

Run the command CHKNTFS/f x: X to fix the partition. This command has no side effects, you don't have to worry about using the/F parameter to fix the error. -- I fixed the problem in this command.

If not, use CHKNTFS/X: X to block the boot detection disk. This means you know something, but you need to block the detection. I have never used this command.

 

Other solutions on the Internet (I also refer to the steps below ):

 

A. If the partition of Windows XP is FAT32, convert it to NTFS, which can greatly reduce the self-check caused by various reasons. The conversion method is as follows:
1. Click "run" in the "Start" menu, type "cmd" (not including double quotation marks), and click "OK;
2. type the following command in the command line:
Convert X:/Fs: NTFS (X is the partition of your system)
3. The system will prompt you to restart the next restart to perform the conversion operation.

B. If the partition of the Windows XP system is NTFS and the system still has the problem of self-check, then:
1. Click "run" in the "Start" menu, type "cmd" (not including double quotation marks), and click "OK;
2. type the following command in the command line:
Fsutil dirty query X: (x is the partition of your system)
Check whether dirty bit is set for the disk. If yes, it may be a problem with the hard disk itself. Please contact the hard disk manufacturer or computer dealer for detection.
3. To prevent the system from automatically detecting the volume marked with dirty bit, run the following command to exclude the volume:
CHKNTFS/X: (x is the partition of your system)
4. check whether there are corresponding add-ons in the task plan and startup items. If yes, delete them.
5. Open Registry Editor and enter the following registry key:
HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Session Manager
Check whether the multi-string key value bootexecute under it is a value similar to the following:
Autocheck autochk/r \?? \ D:
If yes, delete/r \?? \ D: OK.

 

By the way, add the detailed explanation of chkdsk:

 

Based on the file system used, chkdsk creates and displays the disk status report. Chkdsk also lists and corrects disk errors. If no parameter is specified, the chkdsk displays the disk status in the current drive.

Syntax
Chkdsk [volume:] [[Path] FileName] [/f] [/v] [/r] [/x] [/c] [/l [: size]

Parameters
Volume:
Specify the drive letter (separated by a colon), mount point, or volume name.
[Path} FileName]
Specify the location and name of the file or file set that requires chkdsk to check the fragment. Use wildcard characters (* And ?) You can specify multiple files.
/F
Fix disk errors. The disk must be locked. If the chkdsk cannot lock the drive, a message is displayed asking if you want to check the drive the next time you restart the computer.
/V
When checking the disk, the name of each file in all directories is displayed.
/R
Locate the bad sector and restore readable information. The disk must be locked.
/X
It is only used on NTFS. If necessary, force uninstall the volume first. All open handles of the drive are invalid. /X also includes the/f function.
/I
Only use with NTFS. Perform full checks on index items to reduce the time used to run chkdsk.
/C
Only use with NTFS. Skip the periodic check in the folder structure to reduce the time required to run chkdsk.
/L [: size]
Only use with NTFS. Change the log file size to the size entered by the user. If this parameter is omitted,/l displays the size of the current log file.
/?
Display help at the command prompt.
Note
Run chkdsk
To run the chkdsk command on a fixed disk, you must be a member of the Administrators group.

Check the locked drive upon restart
If you want chkdsk to fix disk errors, you cannot open files on the drive before. If a file is opened, the following error message is displayed:

Chkdsk cannot run because the volume is in use by another processwocould you like to schedule this volume to be checked the next time the system restarts? (Y/N)

If you choose to check the drive the next time you restart the computer, after you restart the computer, chkdsk automatically checks the drive and fixes the error. If the drive partition is a boot partition, chkdsk automatically restarts the computer after checking the drive.

Report disk errors
The chkdsk command checks the usage of the disk space and File Allocation Table (FAT) and NTFS file system. The Chkdsk provides information specific to each file system in the status report. The status report displays errors found in the file system. When running chkdsk on an active partition, if the/f command line option is not included, it may report false information because the drive cannot be locked. Chkdsk should be used occasionally to check errors on each disk.

Fix disk errors
The chkdsk command can fix disk errors only when the/f command line option is specified. The Chkdsk must be able to lock the drive to correct the error. Because the repair usually changes the disk file allocation table and sometimes data is lost, chkdsk will first send the following confirmation message:

10 lost allocation units found in 3 chains.

Convert lost chains to files?

If you press Y, Windows saves all lost links in a file named Filennnn. chk in the root directory. After the chkdsk is completed, you can check whether these files contain the required data. If you press N, Windows will repair the disk, but it does not save the contents of the lost allocation unit.

If you do not use the/f command line option, chkdsk sends a message when a file needs to be repaired, but it does not fix any errors.

If chkdsk/f is used on a large disk (for example, 70 GB) or a disk with a large number of files (millions), it may take a long time (for example, several days) to complete. Because the chkdsk will not surrender control until the work is completed, the computer will be unavailable during this period of time.

Check the FAT Disk
The chkdsk Status Report of the FAT disk is displayed in the following format in Windows:

Volume Serial Number is B1AF-AFBF

72214528 bytes total disk space

73728 bytes in 3 hidden files

30720 bytes in 12 directories

11493376 bytes in 386 user files

61440 bytes in bad sectors

60555264 bytes available on disk

2048 bytes in each allocation unit

35261 total allocation units on disk

29568 available allocation units on disk

Check NTFS Disk
In the following Windows format, the chkdsk Status Report of the NTFS disk is displayed:

The type of the file system is NTFS.

CHKDSK is verifying files...

File verification completed.

CHKDSK is verifying indexes...

Index verification completed.

CHKDSK is verifying security descriptors...

Security descriptor verification completed.

12372 kilobytes total disk space.

3 kilobytes in 1 user files.

2 kilobytes in 1 indexes.

4217 kilobytes in use by the system.

8150 kilobytes available on disk.

512 bytes in each allocation unit.

24745 total allocation units on disk.

16301 allocation units available on disk.

Use chkdsk if the file is opened
If an opened file exists on the drive, chkdsk will send an error message after the/f command line option is specified. If the/f command line option is not specified and an open file exists, chkdsk reports the missing allocation unit on the disk. This may happen if the opened file is not recorded in the file allocation table. If chkdsk reports the loss of a large number of allocation units, you can consider restoring the disk.

An error occurred while searching for the physical disk.
Use the/r command line option to find physical disk errors in the file system. For more information about how to use recover to repair physically corrupt files, see "".

Reporting bad sector of a disk
When the disk is preparing for running for the first time, chkdsk reports that the bad sectors are marked as corrupted. They do not pose danger.

Exit code
The following table lists the exit codes reported by the chkdsk after the task is completed.

Exit Code Description
No error found.
1 error found and fixed.
2. the disk has been cleared (for example, fragment collection), or the disk has not been cleared because/f is not specified.
3 because the/f option is not specified, the disk cannot be checked, the error cannot be repaired, or the error is not fixed.

The fault recovery console provides the chkdsk command with different parameters.
Example
If you want to check the disk in drive D and repair Windows errors, type:

Chkdsk d:/f

If an error occurs, chkdsk pauses and displays the message. When the Chkdsk completes the task, a report with disk status is displayed. You cannot open any files on the specified drive unless the chkdsk has completed the task.

On the FAT disk, to check the non-adjacent blocks of all files in the current directory, type:

Chkdsk *.*

The Chkdsk displays the status report and then lists the files that meet the non-adjacent block conditions.