Does fsck.f2fs not support loopback image files?
I had a micro SD card that I had "adopted" so the Android phone I had could use the storage as apart of the total storage for applications and data. This worked for sometime till the micro SD failed. Luckily the micro SD card was able to be read-only so I made a image of the micro SD card using 'dd' before I sent it in for RMA.
I found and followed this guide https://nelenkov.blogspot.com/2015/06/decrypting-android-m-adopted-storage.html Since my phone was already rooted I was able to grab the needed decryption key inside of /data. Before doing anything more I made sure to make a copy of the image to work on in case fsck did anything weird.
Mounting everything as a loop device and decrypting per the guide above I found out that it was a f2fs partition. I ran fsck.f2fs on the decrypted partition so I could recover and it spat out errors after a long list of fixes. One being "[FSCK] SIT valid block bitmap checking [Failed...]" I know I could have probably ran PhotoRec at this point but that would have ruined the file structure and naming of any files contained inside the image, making this hard to recover data.
When I got the replacement card in the mail I decided to try imaging the copy I made earlier back to the new micro SD card and run fsck.f2fs on that. To my surprise it ran through a bunch of fix messages and succeeded. I ran it again to double check and it appared to fix the filesystem. I'm now able to recover the entire file structure and the files I wanted, mainly photos and videos which all appear normal.
TL;DR Does fsck.f2fs not support loopback image files? Why did fsck.f2fs work on hardware but not on a image?
linux data-recovery fsck f2fs
asked 47 mins ago
RansuDoragon
62
add a comment |
I had a micro SD card that I had "adopted" so the Android phone I had could use the storage as apart of the total storage for applications and data. This worked for sometime till the micro SD failed. Luckily the micro SD card was able to be read-only so I made a image of the micro SD card using 'dd' before I sent it in for RMA.
I found and followed this guide https://nelenkov.blogspot.com/2015/06/decrypting-android-m-adopted-storage.html Since my phone was already rooted I was able to grab the needed decryption key inside of /data. Before doing anything more I made sure to make a copy of the image to work on in case fsck did anything weird.
Mounting everything as a loop device and decrypting per the guide above I found out that it was a f2fs partition. I ran fsck.f2fs on the decrypted partition so I could recover and it spat out errors after a long list of fixes. One being "[FSCK] SIT valid block bitmap checking [Failed...]" I know I could have probably ran PhotoRec at this point but that would have ruined the file structure and naming of any files contained inside the image, making this hard to recover data.
When I got the replacement card in the mail I decided to try imaging the copy I made earlier back to the new micro SD card and run fsck.f2fs on that. To my surprise it ran through a bunch of fix messages and succeeded. I ran it again to double check and it appared to fix the filesystem. I'm now able to recover the entire file structure and the files I wanted, mainly photos and videos which all appear normal.
TL;DR Does fsck.f2fs not support loopback image files? Why did fsck.f2fs work on hardware but not on a image?
linux data-recovery fsck f2fs
asked 47 mins ago
RansuDoragon
62
add a comment |
I had a micro SD card that I had "adopted" so the Android phone I had could use the storage as apart of the total storage for applications and data. This worked for sometime till the micro SD failed. Luckily the micro SD card was able to be read-only so I made a image of the micro SD card using 'dd' before I sent it in for RMA.
I found and followed this guide https://nelenkov.blogspot.com/2015/06/decrypting-android-m-adopted-storage.html Since my phone was already rooted I was able to grab the needed decryption key inside of /data. Before doing anything more I made sure to make a copy of the image to work on in case fsck did anything weird.
Mounting everything as a loop device and decrypting per the guide above I found out that it was a f2fs partition. I ran fsck.f2fs on the decrypted partition so I could recover and it spat out errors after a long list of fixes. One being "[FSCK] SIT valid block bitmap checking [Failed...]" I know I could have probably ran PhotoRec at this point but that would have ruined the file structure and naming of any files contained inside the image, making this hard to recover data.
When I got the replacement card in the mail I decided to try imaging the copy I made earlier back to the new micro SD card and run fsck.f2fs on that. To my surprise it ran through a bunch of fix messages and succeeded. I ran it again to double check and it appared to fix the filesystem. I'm now able to recover the entire file structure and the files I wanted, mainly photos and videos which all appear normal.
TL;DR Does fsck.f2fs not support loopback image files? Why did fsck.f2fs work on hardware but not on a image?
linux data-recovery fsck f2fs
asked 47 mins ago
RansuDoragon
62
I had a micro SD card that I had "adopted" so the Android phone I had could use the storage as apart of the total storage for applications and data. This worked for sometime till the micro SD failed. Luckily the micro SD card was able to be read-only so I made a image of the micro SD card using 'dd' before I sent it in for RMA.
I found and followed this guide https://nelenkov.blogspot.com/2015/06/decrypting-android-m-adopted-storage.html Since my phone was already rooted I was able to grab the needed decryption key inside of /data. Before doing anything more I made sure to make a copy of the image to work on in case fsck did anything weird.
Mounting everything as a loop device and decrypting per the guide above I found out that it was a f2fs partition. I ran fsck.f2fs on the decrypted partition so I could recover and it spat out errors after a long list of fixes. One being "[FSCK] SIT valid block bitmap checking [Failed...]" I know I could have probably ran PhotoRec at this point but that would have ruined the file structure and naming of any files contained inside the image, making this hard to recover data.
When I got the replacement card in the mail I decided to try imaging the copy I made earlier back to the new micro SD card and run fsck.f2fs on that. To my surprise it ran through a bunch of fix messages and succeeded. I ran it again to double check and it appared to fix the filesystem. I'm now able to recover the entire file structure and the files I wanted, mainly photos and videos which all appear normal.
TL;DR Does fsck.f2fs not support loopback image files? Why did fsck.f2fs work on hardware but not on a image?
linux data-recovery fsck f2fs
linux data-recovery fsck f2fs
asked 47 mins ago
RansuDoragon
62
asked 47 mins ago
RansuDoragon
62
asked 47 mins ago
RansuDoragon
62
asked 47 mins ago
RansuDoragon
62
asked 47 mins ago
RansuDoragon
62
62
add a comment |
add a comment |
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%2f491284%2fdoes-fsck-f2fs-not-support-loopback-image-files%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f491284%2fdoes-fsck-f2fs-not-support-loopback-image-files%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
