Recovering ext4 directory tree structure after corruption
A disk was mounted twice in LXC. This caused some error. Now, when the drive is mounted (on my Ubuntu 16.04 system), it shows no folders or files.
I've used a few restore tools, and from what I can tell, all the data is fine. However, the tools only restore the files, without indicating what directories they were in, and the data is almost useless without the folder structure. Is there a tool that focuses on recovering the directories as well?
I've tried the following tools:
fsck: thinks the disk is fine!
extundelete: can see missing directories, but nothing in those directories. Will restore most files to lost+found.
R-studio: can find individual files, but again no directory structure.
photorec: restores all individual files.
Recommendations on a tool that specifically handles repairing the corrupt directory structure?
linux filesystems ext4 data-recovery inode
edited Jan 28 at 2:36
G-Man
13.1k93465
asked Jan 27 at 22:50
NateNate
1
add a comment |
A disk was mounted twice in LXC. This caused some error. Now, when the drive is mounted (on my Ubuntu 16.04 system), it shows no folders or files.
I've used a few restore tools, and from what I can tell, all the data is fine. However, the tools only restore the files, without indicating what directories they were in, and the data is almost useless without the folder structure. Is there a tool that focuses on recovering the directories as well?
I've tried the following tools:
fsck: thinks the disk is fine!
extundelete: can see missing directories, but nothing in those directories. Will restore most files to lost+found.
R-studio: can find individual files, but again no directory structure.
photorec: restores all individual files.
Recommendations on a tool that specifically handles repairing the corrupt directory structure?
linux filesystems ext4 data-recovery inode
edited Jan 28 at 2:36
G-Man
13.1k93465
asked Jan 27 at 22:50
NateNate
1
(1) What? How is the data almost useless if you can’t see any files? (2) Please show us the output fromfsck. … … … … … … … … … … … … … … … … … Please do not respond in comments; edit your question to make it clearer and more complete.
– G-Man
Jan 27 at 23:48
@G-Man, please reread the post. I can get all individual files, but not in their original directory structure. Why this is necessary isn't the issue. Understanding how to get the directory structure recovered is.
– Nate
Jan 28 at 1:45
I have read the post several times, and I believe that I’ve finally figured out what you’re trying to say. I still believe that your first draft was unclear, and I still believe that you should show us the output fromfsck.
– G-Man
Jan 28 at 2:36
add a comment |
A disk was mounted twice in LXC. This caused some error. Now, when the drive is mounted (on my Ubuntu 16.04 system), it shows no folders or files.
I've used a few restore tools, and from what I can tell, all the data is fine. However, the tools only restore the files, without indicating what directories they were in, and the data is almost useless without the folder structure. Is there a tool that focuses on recovering the directories as well?
I've tried the following tools:
fsck: thinks the disk is fine!
extundelete: can see missing directories, but nothing in those directories. Will restore most files to lost+found.
R-studio: can find individual files, but again no directory structure.
photorec: restores all individual files.
Recommendations on a tool that specifically handles repairing the corrupt directory structure?
linux filesystems ext4 data-recovery inode
edited Jan 28 at 2:36
G-Man
13.1k93465
asked Jan 27 at 22:50
NateNate
1
A disk was mounted twice in LXC. This caused some error. Now, when the drive is mounted (on my Ubuntu 16.04 system), it shows no folders or files.
I've used a few restore tools, and from what I can tell, all the data is fine. However, the tools only restore the files, without indicating what directories they were in, and the data is almost useless without the folder structure. Is there a tool that focuses on recovering the directories as well?
I've tried the following tools:
fsck: thinks the disk is fine!
extundelete: can see missing directories, but nothing in those directories. Will restore most files to lost+found.
R-studio: can find individual files, but again no directory structure.
photorec: restores all individual files.
Recommendations on a tool that specifically handles repairing the corrupt directory structure?
linux filesystems ext4 data-recovery inode
linux filesystems ext4 data-recovery inode
edited Jan 28 at 2:36
G-Man
13.1k93465
asked Jan 27 at 22:50
NateNate
1
edited Jan 28 at 2:36
G-Man
13.1k93465
asked Jan 27 at 22:50
NateNate
1
edited Jan 28 at 2:36
G-Man
13.1k93465
edited Jan 28 at 2:36
G-Man
13.1k93465
edited Jan 28 at 2:36
G-Man
13.1k93465
13.1k93465
asked Jan 27 at 22:50
NateNate
1
asked Jan 27 at 22:50
NateNate
1
asked Jan 27 at 22:50
NateNate
1
1
(1) What? How is the data almost useless if you can’t see any files? (2) Please show us the output fromfsck. … … … … … … … … … … … … … … … … … Please do not respond in comments; edit your question to make it clearer and more complete.
– G-Man
Jan 27 at 23:48
@G-Man, please reread the post. I can get all individual files, but not in their original directory structure. Why this is necessary isn't the issue. Understanding how to get the directory structure recovered is.
– Nate
Jan 28 at 1:45
I have read the post several times, and I believe that I’ve finally figured out what you’re trying to say. I still believe that your first draft was unclear, and I still believe that you should show us the output fromfsck.
– G-Man
Jan 28 at 2:36
add a comment |
(1) What? How is the data almost useless if you can’t see any files? (2) Please show us the output fromfsck. … … … … … … … … … … … … … … … … … Please do not respond in comments; edit your question to make it clearer and more complete.
– G-Man
Jan 27 at 23:48
@G-Man, please reread the post. I can get all individual files, but not in their original directory structure. Why this is necessary isn't the issue. Understanding how to get the directory structure recovered is.
– Nate
Jan 28 at 1:45
I have read the post several times, and I believe that I’ve finally figured out what you’re trying to say. I still believe that your first draft was unclear, and I still believe that you should show us the output fromfsck.
– G-Man
Jan 28 at 2:36
(1) What? How is the data almost useless if you can’t see any files? (2) Please show us the output from
fsck. … … … … … … … … … … … … … … … … … Please do not respond in comments; edit your question to make it clearer and more complete.– G-Man
Jan 27 at 23:48
(1) What? How is the data almost useless if you can’t see any files? (2) Please show us the output from
fsck. … … … … … … … … … … … … … … … … … Please do not respond in comments; edit your question to make it clearer and more complete.– G-Man
Jan 27 at 23:48
@G-Man, please reread the post. I can get all individual files, but not in their original directory structure. Why this is necessary isn't the issue. Understanding how to get the directory structure recovered is.
– Nate
Jan 28 at 1:45
@G-Man, please reread the post. I can get all individual files, but not in their original directory structure. Why this is necessary isn't the issue. Understanding how to get the directory structure recovered is.
– Nate
Jan 28 at 1:45
I have read the post several times, and I believe that I’ve finally figured out what you’re trying to say. I still believe that your first draft was unclear, and I still believe that you should show us the output from
fsck.– G-Man
Jan 28 at 2:36
I have read the post several times, and I believe that I’ve finally figured out what you’re trying to say. I still believe that your first draft was unclear, and I still believe that you should show us the output from
fsck.– G-Man
Jan 28 at 2:36
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f497084%2frecovering-ext4-directory-tree-structure-after-corruption%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 Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f497084%2frecovering-ext4-directory-tree-structure-after-corruption%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
(1) What? How is the data almost useless if you can’t see any files? (2) Please show us the output from
fsck. … … … … … … … … … … … … … … … … … Please do not respond in comments; edit your question to make it clearer and more complete.– G-Man
Jan 27 at 23:48
@G-Man, please reread the post. I can get all individual files, but not in their original directory structure. Why this is necessary isn't the issue. Understanding how to get the directory structure recovered is.
– Nate
Jan 28 at 1:45
I have read the post several times, and I believe that I’ve finally figured out what you’re trying to say. I still believe that your first draft was unclear, and I still believe that you should show us the output from
fsck.– G-Man
Jan 28 at 2:36