[Ascii2]

CHKDSK has just run on a computer with multiple disks. CHKDSK was invoked by Windows XP Professional with Service Pack 1.

The main part of the CHKDSK report is:

Checking file system on G:
The type of the file system is NTFS.
Volume label is Local Disk.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.                         
The segment number 0x1a0f900000000 in file 0x1b0f9 is incorrect.
Correcting a minor error in file 110841.
Cleaning up 173 unused index entries from index $SII of file 0x9.
Cleaning up 173 unused index entries from index $SDH of file 0x9.
Cleaning up 173 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
Windows has made corrections to the file system.

1465136000 KB total disk space.
 525536320 KB in 232542 files.
     98532 KB in 36439 indexes.
         0 KB in bad sectors.
    326440 KB in use by the system.
      2048 KB occupied by the log file.
 939174708 KB available on disk.

      4096 bytes in each allocation unit.
 366284000 total allocation units on disk.
 234793677 allocation units available on disk.

It seems that there may have been a problem in file 110841 on the G: volume.

How would I determine which file file 110841 is?

[GrofLuigi]

DiskView or this maybe?

* Edit: Found something more

GL

This post has been edited by GrofLuigi: 26 August 2012 - 09:22 PM

[jaclaz]

Dmde is a modern tool with quite a number of useful options (including that of accessing $MFT entries):
http://softdm.com/

jaclaz

[Ascii2]

Thanks for the suggestions.

I shall examine them in the coming days.

[Ascii2]

WinHex 16.6 SR-4 x86 ( http://www.winhex.co...ex/index-m.html ) is also able to find an NTFS file by file number.

The issue described in this thread in now solved.

Thanks again for the contributions.

This post has been edited by Ascii2: 01 September 2012 - 02:20 AM

[jaclaz]

Ascii2, on 01 September 2012 - 02:20 AM, said:

WinHex 16.6 SR-4 x86 ( http://www.winhex.co...ex/index-m.html ) is also able to find an NTFS file by file number.

And as well *any* number of other applications.
Winhex is IMHO an excellent Commercial application , though buying a license for it, is not however "justified" or "needed" if you only want to know what file corresponds to a $MFT entry.
Ferrari's are beautiful ... .



jaclaz