[SOLVED]NTFS File System

[Angelika]

Example:

Code: [Select]

The attribute type 0x80 and the 0x4 occurrence tag are crossed

starting with 0x7b96a0 for about 0x4 clusters.

Why sometimes the File System gets corrupted even though the disk is 100% healthy.
These errors are very rare, but at an unexpected time sometimes such things happen when CHKDSK computer starts to detect errors.

What is "cross file" and why is this happening and how to avoid errors in the volume bitmap in the future?
On the Microsoft site there is no explanation why the File System sometimes gets corrupted and practically in every system there is a CHKDSK to repair or improve the File system.
Will regular cleanup of security descriptors help you avoid errors?
How to start a security descriptor instantly during each computer start. I remember my friend used to have something like that in XP, but the super-fast scan worked on every partition, even if the drive was big.

Event Log sometimes reports an NTFS error.
But what to do to immediately get a notification, for example, on the Desktop if there is a situation or in the System tray???

[Boggin]

I occasionally get Bit map error correction in a chkdsk /f

As to why they occur, I don't know but it is obviously a trait of Windows in that a chkdsk will repair it as well as a sfc /scannow to repair some file corruption.

Even Shane's Windows Repair can become corrupted for no apparent reason and is why it does a self check on starting it.

A regular chkdsk or sfc /scannow may be something we should all do.

They are part of my pre-steps prior to creating a system image.

[Angelika]

CHKDSK is not always the best solution.
Sometimes, when trying to repair a graphic file, it will cause irreparable damage.
How do I know which file exactly is defective?
Why run a data recovery tool on big disks when it wants to recover only a specific file and not even know which one has been corrupted. So why recover 1TB of data just for one important file eg 2MB?
CHKDSK does not provide any additional information about files that need to be corrected. It's all nonsense! 

Why there is no tool that can specify a specific file on disk if I know:
NTFS File ID
Directory NTFS File ID

The necessary tools that have the option to search on disk or partition table.

Code: [Select]

NTFS File ID
Directory NTFS File ID
Example:
C:\Windows NTFS File ID: 671
C:\Windows Directory NTFS File ID: 5


E:\Pliki\w_4f4d6b.jpg NTFS File ID: 52 Directory NTFS File ID: 40


Shows file name, path.





CHKDSK will not show what path to file, what name, nothing.

[Boggin]

If it isn't a system file then Windows tools won't repair it.

This is why you should create regular system images when things are working as they should.

[Angelika]

Nobody here talks about system files (it's not important), here are just some other important non-system data.
CHKDSK /V Verbose shows only the file ID.
How to find a quick file in (MFT) full path name to a file knowing only the file ID or folder ID?
With such knowledge, you can quickly and easily find out what files and data you need to restore, or if not, if they are unnecessary and can be forgotten.

Pliku (file) number id.
What is this file?
No file or path name.
Is there any solution to this problem, so after the ID find out what file it is ??

Nie mozna zlokalizowac atrybutu ze znacznikiem wystapienia 0x0
i odwolaniem do segmentu 0x719000000000629. Oczekiwany typ atrybutu to 0x80.
Usuwanie uszkodzonego rekordu atrybutów (128, "")
z segmentu rekordów pliku 1577.
Nie mozna zlokalizowac atrybutu ze znacznikiem wystapienia 0x0
i odwolaniem do segmentu 0x3e000000000632. Oczekiwany typ atrybutu to 0x80.
Usuwanie uszkodzonego rekordu atrybutów (128, "")
z segmentu rekordów pliku 1586.
Nie mozna zlokalizowac atrybutu ze znacznikiem wystapienia 0x0
i odwolaniem do segmentu 0x61f000000000e30. Oczekiwany typ atrybutu to 0x80.
Usuwanie uszkodzonego rekordu atrybutów (128, "")
z segmentu rekordów pliku 3632.
Nie mozna zlokalizowac atrybutu ze znacznikiem wystapienia 0x0
i odwolaniem do segmentu 0x1f30000000046da. Oczekiwany typ atrybutu to 0x80.
Usuwanie uszkodzonego rekordu atrybutów (128, "")
z segmentu rekordów pliku 18138.