Main Forum > General Computer Support

CHKDSK repeats error logs

<< < (3/3)

makinero:
The NTFS file system - is resistant to damage ...
but you want or do not want - can sometimes spoil.
It is not the fault of the hard drive and only file system that is not perfect.
Frequently can occur when working on the computer, you turn it off safely.
I eg. Start the morning ... could it be these errors arise after the completion of the work on your computer ...
Eg. Some activities are performed in the background (typical for various applications) (and suddenly you are trying to shut down your computer - and Windows quits, but perhaps not in the correct way)
Everyone will say: It's the fault drive, you have a damaged HDD, check the SMART and many other things that have nothing to do with it, the probability is high that the drive is 100% healthy ... and only the fault of the file system ...

Julian - It makes no sense to use the chkdsk /r or chkdsk /f /r
/r super-a long time scans large disks with large amount of files
Use the /r when bad sectors, clusters, etc.!
If a typical errors - always use the /v(if you want to quickly check and analyze disk) or /v /f(If you want to correct minor errors[unused descriptors]Index $SII
Index $SDH . .  or repair bitmap volumes[to make corrections to the file system])$I30(directory) ... $O(file)

CHKDSK


--- Code: ---Options test:

[x][ ]Standard
[x][ ]Thorough (scanning the surface of the test)
[x][ ]Check whether corrupt
-------------------------------------
[x][ ] Error Correction
[x][ ] Extended
--- End code ---


--- Code: ---[x] Enable
[ ] Disable
--- End code ---

Julian:
Meh I think it makes perfect sense I want to see a full layout of what chkdsk is reporting at the boot time since I'm not physically at the computer. Yes it takes a little longer but it repairs parts of the file system  So they don't have to run chkdsk 3 times just to fix it. And I want to see if Windows is reporting anything in bad sectors because if Windows detects it then the hard drive is pretty much dying because Windows is not great at detecting hard drive failure. And when it does it's pretty close to being imminent. And yes you are correct that there are a lot of people that blame hdd as failing when it reality it's a faulty filesystem that needs reparing.  Hence why I say to do the chkdsk /f /r everything gets checked even free space.

makinero:
In Windows7, file check takes a very long time, for comparison, Windows 2012 fast scan ... eg. For 100 or 200 or 300 million files


--- Quote ---Windows Server 2012

•Improved self-healing: NTFS instantaneously self-heals more issues online without requiring chkdsk to run offline. This reduces the number of times that chkdsk is required to run.


•Online analysis: In the previous model, almost all of the offline time required to run chkdsk was spent scanning and analyzing the drive. In Windows Server 2012, the analysis phase of chkdsk, which was responsible for the majority of the offline time, becomes an online, background task. This allows the volume to remain online and available while the system determines whether there is corruption. There is also added logic in the model that verifies the type of corruption is not transient, preventing unnecessary analysis.


•Corruption correction: When the scan is completed, Windows Server 2012 informs the administrator (by using events and the management consoles), that the volumes need to be repaired and suggests a solution, such as performing a remount or reboot. Because the analysis phase has already completed, no additional scanning or detection is required. Chkdsk directly fixes the identified corruption, and the offline time is minimized to seconds. Therefore, the offline time for a volume is no longer proportional to the number of files on the volume, but rather to the number of corruptions on the volume.



--- End quote ---

Navigation

[0] Message Index

[*] Previous page