How to map directory number to its name

My system, as has been happening occasionally recently (since I installed
an SSD for C quit trying to boot today, complaining about corruption on
C:. I tried booting again and chkdsk ran. It reported about a dozen
issues with files all in a directory, 249333. It claims to have repaired
the index structure and now the system boots normally. sfc found no
integrity issues.

My question: is there a way to relate that 249333 to a directory name?
The dozen or so files it listed appeared to be part of an application and
I'd like to figure out what it was. (It's always bugged me that the
results of chkdsk at boot are not saved anywhere - that might be
generally impossible, however...)

TIA,
Jason

In article ,
, Jason says...

My system, as has been happening occasionally recently (since I installed
an SSD for C quit trying to boot today, complaining about corruption on
C:. I tried booting again and chkdsk ran. It reported about a dozen
issues with files all in a directory, 249333. It claims to have repaired
the index structure and now the system boots normally. sfc found no
integrity issues.

My question: is there a way to relate that 249333 to a directory name?
The dozen or so files it listed appeared to be part of an application and
I'd like to figure out what it was. (It's always bugged me that the
results of chkdsk at boot are not saved anywhere - that might be
generally impossible, however...)

TIA,
Jason

Checkdisk logs its results in the Event Log (Application). Right-click
the Application log and search for "Wininit".

--
Duncan.

Jason wrote:
My system, as has been happening occasionally recently (since I installed
an SSD for C quit trying to boot today, complaining about corruption on
C:. I tried booting again and chkdsk ran. It reported about a dozen
issues with files all in a directory, 249333. It claims to have repaired
the index structure and now the system boots normally. sfc found no
integrity issues.

My question: is there a way to relate that 249333 to a directory name?
The dozen or so files it listed appeared to be part of an application and
I'd like to figure out what it was. (It's always bugged me that the
results of chkdsk at boot are not saved anywhere - that might be
generally impossible, however...)

TIA,
Jason


The only numbering scheme I've heard of, is the
"file number" you can see in nfi.exe output. You
would have needed to run that in advance, to correlate
later on a failure. When Linux views NTFS partitions,
it treats the file number as an "inode number", as
a fake numbering scheme for compatibility purposes.
So you can also get these numbers while using a Linux
LiveCD, by using the "ls" option that displays the
inode number for the start of the file.

https://support.microsoft.com/en-us/kb/253066

http://download.microsoft.com/downlo...us/oem3sr2.zip

nfi.exe c: C:\users\username\downloads\nfi_for_c.txt

This is what a directory looks like.

File 78576
\Users\User Name\Downloads
$STANDARD_INFORMATION (resident)
$FILE_NAME (resident)
$FILE_NAME (resident)
$OBJECT_ID (resident)
$INDEX_ROOT $I30 (resident) --- a directory
$INDEX_ALLOCATION $I30 (nonresident)
logical sectors 181840-181911 (0x2c650-0x2c697)
$BITMAP $I30 (resident)

And this is a file. It has no $INDEX stuff. Note that
this file is so small, it has no logical sectors (a cluster).
Instead, it would be stored inside the $MFT entry. A fragmented
file stored in regular clusters, if the file was fragmented,
there would be multiple lines of "logical sectors". Files or
directories are not limited to just a single line of
logical sectors.

File 79336
\Users\User Name\Downloads\desktop.ini
$STANDARD_INFORMATION (resident)
$FILE_NAME (resident)
$DATA (resident)

HTH,
Paul

In article ,
says...
Checkdisk logs its results in the Event Log (Application). Right-click
the Application log and search for "Wininit".


I looked for that and didn't find it. Is that possibly because C: itself
was reported as corrupted?