Identify file name(s) associated with chkdsk corrupt file record segments
I have a Dell XPS15, 32 GB RAM, 1 TB SSD, Windows 10.
The following are the results from CHKDSK read-only:
The type of the file system is NTFS.
Volume label is OS.
WARNING! /F parameter not specified.
Running CHKDSK in read-only mode.
Stage 1: Examining basic file system structure ...
Progress: 0 of 516096 done; Stage: 0%; Total: 0%; ETA: 0:24:50
Progress: 27291 of 516096 done; Stage: 5%; Total: 2%; ETA: 0:24:19 .
Progress: 59292 of 516096 done; Stage: 11%; Total: 4%; ETA: 0:23:39 ..
Attribute record (80, "") from file record segment 1003F
is corrupt.
Progress: 107648 of 516096 done; Stage: 20%; Total: 8%; ETA: 0:00:15 ...
Progress: 137486 of 516096 done; Stage: 26%; Total: 10%; ETA: 0:00:15
Progress: 192769 of 516096 done; Stage: 37%; Total: 14%; ETA: 0:00:14 .
Progress: 253613 of 516096 done; Stage: 49%; Total: 18%; ETA: 0:00:12 ..
Progress: 253614 of 516096 done; Stage: 49%; Total: 18%; ETA: 0:00:12 ...
Progress: 311809 of 516096 done; Stage: 60%; Total: 22%; ETA: 0:00:12
Progress: 366821 of 516096 done; Stage: 71%; Total: 26%; ETA: 0:00:11 .
Progress: 421121 of 516096 done; Stage: 81%; Total: 29%; ETA: 0:00:11 ..
Progress: 475047 of 516096 done; Stage: 92%; Total: 32%; ETA: 0:00:11 ...
The total allocated size in attribute record (80, "")
of file A00000007ADAE is incorrect.
Deleted corrupt attribute list entry
with type code 80 in file 7ADAE.
Attribute record (80, "") from file record segment 21D8F
is corrupt.
Attribute record (80, "") from file record segment 74337
is corrupt.
Attribute record (80, "") from file record segment 74CF5
is corrupt.
Progress: 516096 of 516096 done; Stage: 100%; Total: 35%; ETA: 0:00:09
516096 file records processed.
File verification completed.
File record segment 21D8F is an orphan.
File record segment 74337 is an orphan.
File record segment 74CF5 is an orphan.
Progress: 16440 of 16440 done; Stage: 100%; Total: 26%; ETA: 0:00:14 .
16440 large file records processed.
Errors found. CHKDSK cannot continue in read-only mode.
Since it cannot continue, does that imply that there may be additional existing errors?
My understanding is that CHKDSK /R
will recover 'READABLE' information.
So, before I run chkdsk /r
, is there any way to identify the filename(s) associated with:
- file 7ADAE
- file record segment 1003F
- file record segment 21D8F
- file record segment 74337
- file record segment 74CF5
Once I identify the filenames I plan on restoring them from a recent backup after running
`chkdsk /r.
windows windows-10 hard-drive chkdsk
add a comment |
I have a Dell XPS15, 32 GB RAM, 1 TB SSD, Windows 10.
The following are the results from CHKDSK read-only:
The type of the file system is NTFS.
Volume label is OS.
WARNING! /F parameter not specified.
Running CHKDSK in read-only mode.
Stage 1: Examining basic file system structure ...
Progress: 0 of 516096 done; Stage: 0%; Total: 0%; ETA: 0:24:50
Progress: 27291 of 516096 done; Stage: 5%; Total: 2%; ETA: 0:24:19 .
Progress: 59292 of 516096 done; Stage: 11%; Total: 4%; ETA: 0:23:39 ..
Attribute record (80, "") from file record segment 1003F
is corrupt.
Progress: 107648 of 516096 done; Stage: 20%; Total: 8%; ETA: 0:00:15 ...
Progress: 137486 of 516096 done; Stage: 26%; Total: 10%; ETA: 0:00:15
Progress: 192769 of 516096 done; Stage: 37%; Total: 14%; ETA: 0:00:14 .
Progress: 253613 of 516096 done; Stage: 49%; Total: 18%; ETA: 0:00:12 ..
Progress: 253614 of 516096 done; Stage: 49%; Total: 18%; ETA: 0:00:12 ...
Progress: 311809 of 516096 done; Stage: 60%; Total: 22%; ETA: 0:00:12
Progress: 366821 of 516096 done; Stage: 71%; Total: 26%; ETA: 0:00:11 .
Progress: 421121 of 516096 done; Stage: 81%; Total: 29%; ETA: 0:00:11 ..
Progress: 475047 of 516096 done; Stage: 92%; Total: 32%; ETA: 0:00:11 ...
The total allocated size in attribute record (80, "")
of file A00000007ADAE is incorrect.
Deleted corrupt attribute list entry
with type code 80 in file 7ADAE.
Attribute record (80, "") from file record segment 21D8F
is corrupt.
Attribute record (80, "") from file record segment 74337
is corrupt.
Attribute record (80, "") from file record segment 74CF5
is corrupt.
Progress: 516096 of 516096 done; Stage: 100%; Total: 35%; ETA: 0:00:09
516096 file records processed.
File verification completed.
File record segment 21D8F is an orphan.
File record segment 74337 is an orphan.
File record segment 74CF5 is an orphan.
Progress: 16440 of 16440 done; Stage: 100%; Total: 26%; ETA: 0:00:14 .
16440 large file records processed.
Errors found. CHKDSK cannot continue in read-only mode.
Since it cannot continue, does that imply that there may be additional existing errors?
My understanding is that CHKDSK /R
will recover 'READABLE' information.
So, before I run chkdsk /r
, is there any way to identify the filename(s) associated with:
- file 7ADAE
- file record segment 1003F
- file record segment 21D8F
- file record segment 74337
- file record segment 74CF5
Once I identify the filenames I plan on restoring them from a recent backup after running
`chkdsk /r.
windows windows-10 hard-drive chkdsk
Not as far as I know.
– DavidPostill♦
Feb 26 at 15:00
add a comment |
I have a Dell XPS15, 32 GB RAM, 1 TB SSD, Windows 10.
The following are the results from CHKDSK read-only:
The type of the file system is NTFS.
Volume label is OS.
WARNING! /F parameter not specified.
Running CHKDSK in read-only mode.
Stage 1: Examining basic file system structure ...
Progress: 0 of 516096 done; Stage: 0%; Total: 0%; ETA: 0:24:50
Progress: 27291 of 516096 done; Stage: 5%; Total: 2%; ETA: 0:24:19 .
Progress: 59292 of 516096 done; Stage: 11%; Total: 4%; ETA: 0:23:39 ..
Attribute record (80, "") from file record segment 1003F
is corrupt.
Progress: 107648 of 516096 done; Stage: 20%; Total: 8%; ETA: 0:00:15 ...
Progress: 137486 of 516096 done; Stage: 26%; Total: 10%; ETA: 0:00:15
Progress: 192769 of 516096 done; Stage: 37%; Total: 14%; ETA: 0:00:14 .
Progress: 253613 of 516096 done; Stage: 49%; Total: 18%; ETA: 0:00:12 ..
Progress: 253614 of 516096 done; Stage: 49%; Total: 18%; ETA: 0:00:12 ...
Progress: 311809 of 516096 done; Stage: 60%; Total: 22%; ETA: 0:00:12
Progress: 366821 of 516096 done; Stage: 71%; Total: 26%; ETA: 0:00:11 .
Progress: 421121 of 516096 done; Stage: 81%; Total: 29%; ETA: 0:00:11 ..
Progress: 475047 of 516096 done; Stage: 92%; Total: 32%; ETA: 0:00:11 ...
The total allocated size in attribute record (80, "")
of file A00000007ADAE is incorrect.
Deleted corrupt attribute list entry
with type code 80 in file 7ADAE.
Attribute record (80, "") from file record segment 21D8F
is corrupt.
Attribute record (80, "") from file record segment 74337
is corrupt.
Attribute record (80, "") from file record segment 74CF5
is corrupt.
Progress: 516096 of 516096 done; Stage: 100%; Total: 35%; ETA: 0:00:09
516096 file records processed.
File verification completed.
File record segment 21D8F is an orphan.
File record segment 74337 is an orphan.
File record segment 74CF5 is an orphan.
Progress: 16440 of 16440 done; Stage: 100%; Total: 26%; ETA: 0:00:14 .
16440 large file records processed.
Errors found. CHKDSK cannot continue in read-only mode.
Since it cannot continue, does that imply that there may be additional existing errors?
My understanding is that CHKDSK /R
will recover 'READABLE' information.
So, before I run chkdsk /r
, is there any way to identify the filename(s) associated with:
- file 7ADAE
- file record segment 1003F
- file record segment 21D8F
- file record segment 74337
- file record segment 74CF5
Once I identify the filenames I plan on restoring them from a recent backup after running
`chkdsk /r.
windows windows-10 hard-drive chkdsk
I have a Dell XPS15, 32 GB RAM, 1 TB SSD, Windows 10.
The following are the results from CHKDSK read-only:
The type of the file system is NTFS.
Volume label is OS.
WARNING! /F parameter not specified.
Running CHKDSK in read-only mode.
Stage 1: Examining basic file system structure ...
Progress: 0 of 516096 done; Stage: 0%; Total: 0%; ETA: 0:24:50
Progress: 27291 of 516096 done; Stage: 5%; Total: 2%; ETA: 0:24:19 .
Progress: 59292 of 516096 done; Stage: 11%; Total: 4%; ETA: 0:23:39 ..
Attribute record (80, "") from file record segment 1003F
is corrupt.
Progress: 107648 of 516096 done; Stage: 20%; Total: 8%; ETA: 0:00:15 ...
Progress: 137486 of 516096 done; Stage: 26%; Total: 10%; ETA: 0:00:15
Progress: 192769 of 516096 done; Stage: 37%; Total: 14%; ETA: 0:00:14 .
Progress: 253613 of 516096 done; Stage: 49%; Total: 18%; ETA: 0:00:12 ..
Progress: 253614 of 516096 done; Stage: 49%; Total: 18%; ETA: 0:00:12 ...
Progress: 311809 of 516096 done; Stage: 60%; Total: 22%; ETA: 0:00:12
Progress: 366821 of 516096 done; Stage: 71%; Total: 26%; ETA: 0:00:11 .
Progress: 421121 of 516096 done; Stage: 81%; Total: 29%; ETA: 0:00:11 ..
Progress: 475047 of 516096 done; Stage: 92%; Total: 32%; ETA: 0:00:11 ...
The total allocated size in attribute record (80, "")
of file A00000007ADAE is incorrect.
Deleted corrupt attribute list entry
with type code 80 in file 7ADAE.
Attribute record (80, "") from file record segment 21D8F
is corrupt.
Attribute record (80, "") from file record segment 74337
is corrupt.
Attribute record (80, "") from file record segment 74CF5
is corrupt.
Progress: 516096 of 516096 done; Stage: 100%; Total: 35%; ETA: 0:00:09
516096 file records processed.
File verification completed.
File record segment 21D8F is an orphan.
File record segment 74337 is an orphan.
File record segment 74CF5 is an orphan.
Progress: 16440 of 16440 done; Stage: 100%; Total: 26%; ETA: 0:00:14 .
16440 large file records processed.
Errors found. CHKDSK cannot continue in read-only mode.
Since it cannot continue, does that imply that there may be additional existing errors?
My understanding is that CHKDSK /R
will recover 'READABLE' information.
So, before I run chkdsk /r
, is there any way to identify the filename(s) associated with:
- file 7ADAE
- file record segment 1003F
- file record segment 21D8F
- file record segment 74337
- file record segment 74CF5
Once I identify the filenames I plan on restoring them from a recent backup after running
`chkdsk /r.
windows windows-10 hard-drive chkdsk
windows windows-10 hard-drive chkdsk
edited Feb 26 at 1:20
Scott
16.1k113990
16.1k113990
asked Feb 26 at 0:56
LukeLuke
61
61
Not as far as I know.
– DavidPostill♦
Feb 26 at 15:00
add a comment |
Not as far as I know.
– DavidPostill♦
Feb 26 at 15:00
Not as far as I know.
– DavidPostill♦
Feb 26 at 15:00
Not as far as I know.
– DavidPostill♦
Feb 26 at 15:00
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1409398%2fidentify-file-names-associated-with-chkdsk-corrupt-file-record-segments%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1409398%2fidentify-file-names-associated-with-chkdsk-corrupt-file-record-segments%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Not as far as I know.
– DavidPostill♦
Feb 26 at 15:00