SD Card Recovery without data loss or corruption












1















I have a 128 GB Micro SD Card that I formatted as ext4 and used in a Chromebook for an Ubuntu Chroot Environment. I used it for quite some time that way. At some point, I either deleted everything off of it or formatted it using the Chromebook's simple formatting system.



After this, I stuck it in a GoPro Hero Session, and found that the GoPro didn't care to format the disk and could immediately write pictures and videos. No problem.



I went on a trip, took lots of photos and video, and then suddenly the GoPro was having trouble reading the disk. It was still able to record video and pictures (I assume) as I could turn on the recording mode and it didn't report any problems. From what I could tell, 128 GB is too much for this GoPro Session.



When I plug this into a computer (Chromebook, Mac OSX, Ubuntu) I either get an error (Chromebook & OSX) or I have the disk mount, but no viewable file structure when I open it with a file explorer. Totally empty.



If I right click, and click Properties (on Ubuntu), I get a report that the disk is formatted ext3/ext4, 128 GB and has 45.1 GB used, 71.9 GB free space. gparted is reporting the same thing.



I was able to successfully recover all 6 GB of photos using photorec. I didn't recover any videos, though.



I've used ddrescue to duplicate the disk to an image that I can work with. When I mount the image file, it behaves exactly the same way as the disk does (expected).



ddrescue output:




rescued: 125829 MB,

errsize: 0 B,

current rate: 12648 kB/s



ipos: 125829 MB,

errors: 0,

average rate: 19079 kB/s



opos: 125829 MB,

time since last successful read: 0 s



Finished




I ran a pass on the .IMG file with foremost -v -q -t mp4 -d but it finished with 0 files returned.



At this point, it doesn't actually seem to me that there has been either data loss or corruption. I'm not sure what actually is going on, but suspect that something has gone awry with the file system- being ext3/ext4 in a GoPro rather than FAT32 or exFAT.



EDIT: I just used Disk Usage Analyzer and found all of the largest files that photorec recovered. Among them are many large .bz2 files, with files in them with no extension that are timestamped for the time I would have recorded the footage. I can open them and view this information with an archive manager, but am unable to extract them.



EDIT 2: I tried running fsck and checked in /lost+found. All of my Linux files were there, but no videos, and not even the pictures that I had previously recovered with photorec.



I also tried to mount the image as exfat using sudo mount -o loop -t exfat SD_Card.img ~/mountpoint but it fails to mount.




FUSE exfat 1.2.8



ERROR: exFAT file system is not found.











share|improve this question

























  • Reason for downvote? Help me improve my post rather than remaining an anonymous downvoter.

    – Matt Zabojnik
    Jan 14 at 20:36











  • First off, very good that you've gotten yourself an image of the disk to work with to try to recover from. The less done to the original medium, the better. If it's showing a lot of used space but no actual files, you might could try fscking the partition and then looking in /lost+found perhaps?

    – DopeGhoti
    Jan 14 at 21:06











  • Alright, I've tried fscking and checked in /lost+found. All of my Linux files were there, but no videos, and not even the pictures that I had previously recovered with testdisk's photorec. Any other suggestions?

    – Matt Zabojnik
    Jan 17 at 19:02


















1















I have a 128 GB Micro SD Card that I formatted as ext4 and used in a Chromebook for an Ubuntu Chroot Environment. I used it for quite some time that way. At some point, I either deleted everything off of it or formatted it using the Chromebook's simple formatting system.



After this, I stuck it in a GoPro Hero Session, and found that the GoPro didn't care to format the disk and could immediately write pictures and videos. No problem.



I went on a trip, took lots of photos and video, and then suddenly the GoPro was having trouble reading the disk. It was still able to record video and pictures (I assume) as I could turn on the recording mode and it didn't report any problems. From what I could tell, 128 GB is too much for this GoPro Session.



When I plug this into a computer (Chromebook, Mac OSX, Ubuntu) I either get an error (Chromebook & OSX) or I have the disk mount, but no viewable file structure when I open it with a file explorer. Totally empty.



If I right click, and click Properties (on Ubuntu), I get a report that the disk is formatted ext3/ext4, 128 GB and has 45.1 GB used, 71.9 GB free space. gparted is reporting the same thing.



I was able to successfully recover all 6 GB of photos using photorec. I didn't recover any videos, though.



I've used ddrescue to duplicate the disk to an image that I can work with. When I mount the image file, it behaves exactly the same way as the disk does (expected).



ddrescue output:




rescued: 125829 MB,

errsize: 0 B,

current rate: 12648 kB/s



ipos: 125829 MB,

errors: 0,

average rate: 19079 kB/s



opos: 125829 MB,

time since last successful read: 0 s



Finished




I ran a pass on the .IMG file with foremost -v -q -t mp4 -d but it finished with 0 files returned.



At this point, it doesn't actually seem to me that there has been either data loss or corruption. I'm not sure what actually is going on, but suspect that something has gone awry with the file system- being ext3/ext4 in a GoPro rather than FAT32 or exFAT.



EDIT: I just used Disk Usage Analyzer and found all of the largest files that photorec recovered. Among them are many large .bz2 files, with files in them with no extension that are timestamped for the time I would have recorded the footage. I can open them and view this information with an archive manager, but am unable to extract them.



EDIT 2: I tried running fsck and checked in /lost+found. All of my Linux files were there, but no videos, and not even the pictures that I had previously recovered with photorec.



I also tried to mount the image as exfat using sudo mount -o loop -t exfat SD_Card.img ~/mountpoint but it fails to mount.




FUSE exfat 1.2.8



ERROR: exFAT file system is not found.











share|improve this question

























  • Reason for downvote? Help me improve my post rather than remaining an anonymous downvoter.

    – Matt Zabojnik
    Jan 14 at 20:36











  • First off, very good that you've gotten yourself an image of the disk to work with to try to recover from. The less done to the original medium, the better. If it's showing a lot of used space but no actual files, you might could try fscking the partition and then looking in /lost+found perhaps?

    – DopeGhoti
    Jan 14 at 21:06











  • Alright, I've tried fscking and checked in /lost+found. All of my Linux files were there, but no videos, and not even the pictures that I had previously recovered with testdisk's photorec. Any other suggestions?

    – Matt Zabojnik
    Jan 17 at 19:02
















1












1








1








I have a 128 GB Micro SD Card that I formatted as ext4 and used in a Chromebook for an Ubuntu Chroot Environment. I used it for quite some time that way. At some point, I either deleted everything off of it or formatted it using the Chromebook's simple formatting system.



After this, I stuck it in a GoPro Hero Session, and found that the GoPro didn't care to format the disk and could immediately write pictures and videos. No problem.



I went on a trip, took lots of photos and video, and then suddenly the GoPro was having trouble reading the disk. It was still able to record video and pictures (I assume) as I could turn on the recording mode and it didn't report any problems. From what I could tell, 128 GB is too much for this GoPro Session.



When I plug this into a computer (Chromebook, Mac OSX, Ubuntu) I either get an error (Chromebook & OSX) or I have the disk mount, but no viewable file structure when I open it with a file explorer. Totally empty.



If I right click, and click Properties (on Ubuntu), I get a report that the disk is formatted ext3/ext4, 128 GB and has 45.1 GB used, 71.9 GB free space. gparted is reporting the same thing.



I was able to successfully recover all 6 GB of photos using photorec. I didn't recover any videos, though.



I've used ddrescue to duplicate the disk to an image that I can work with. When I mount the image file, it behaves exactly the same way as the disk does (expected).



ddrescue output:




rescued: 125829 MB,

errsize: 0 B,

current rate: 12648 kB/s



ipos: 125829 MB,

errors: 0,

average rate: 19079 kB/s



opos: 125829 MB,

time since last successful read: 0 s



Finished




I ran a pass on the .IMG file with foremost -v -q -t mp4 -d but it finished with 0 files returned.



At this point, it doesn't actually seem to me that there has been either data loss or corruption. I'm not sure what actually is going on, but suspect that something has gone awry with the file system- being ext3/ext4 in a GoPro rather than FAT32 or exFAT.



EDIT: I just used Disk Usage Analyzer and found all of the largest files that photorec recovered. Among them are many large .bz2 files, with files in them with no extension that are timestamped for the time I would have recorded the footage. I can open them and view this information with an archive manager, but am unable to extract them.



EDIT 2: I tried running fsck and checked in /lost+found. All of my Linux files were there, but no videos, and not even the pictures that I had previously recovered with photorec.



I also tried to mount the image as exfat using sudo mount -o loop -t exfat SD_Card.img ~/mountpoint but it fails to mount.




FUSE exfat 1.2.8



ERROR: exFAT file system is not found.











share|improve this question
















I have a 128 GB Micro SD Card that I formatted as ext4 and used in a Chromebook for an Ubuntu Chroot Environment. I used it for quite some time that way. At some point, I either deleted everything off of it or formatted it using the Chromebook's simple formatting system.



After this, I stuck it in a GoPro Hero Session, and found that the GoPro didn't care to format the disk and could immediately write pictures and videos. No problem.



I went on a trip, took lots of photos and video, and then suddenly the GoPro was having trouble reading the disk. It was still able to record video and pictures (I assume) as I could turn on the recording mode and it didn't report any problems. From what I could tell, 128 GB is too much for this GoPro Session.



When I plug this into a computer (Chromebook, Mac OSX, Ubuntu) I either get an error (Chromebook & OSX) or I have the disk mount, but no viewable file structure when I open it with a file explorer. Totally empty.



If I right click, and click Properties (on Ubuntu), I get a report that the disk is formatted ext3/ext4, 128 GB and has 45.1 GB used, 71.9 GB free space. gparted is reporting the same thing.



I was able to successfully recover all 6 GB of photos using photorec. I didn't recover any videos, though.



I've used ddrescue to duplicate the disk to an image that I can work with. When I mount the image file, it behaves exactly the same way as the disk does (expected).



ddrescue output:




rescued: 125829 MB,

errsize: 0 B,

current rate: 12648 kB/s



ipos: 125829 MB,

errors: 0,

average rate: 19079 kB/s



opos: 125829 MB,

time since last successful read: 0 s



Finished




I ran a pass on the .IMG file with foremost -v -q -t mp4 -d but it finished with 0 files returned.



At this point, it doesn't actually seem to me that there has been either data loss or corruption. I'm not sure what actually is going on, but suspect that something has gone awry with the file system- being ext3/ext4 in a GoPro rather than FAT32 or exFAT.



EDIT: I just used Disk Usage Analyzer and found all of the largest files that photorec recovered. Among them are many large .bz2 files, with files in them with no extension that are timestamped for the time I would have recorded the footage. I can open them and view this information with an archive manager, but am unable to extract them.



EDIT 2: I tried running fsck and checked in /lost+found. All of my Linux files were there, but no videos, and not even the pictures that I had previously recovered with photorec.



I also tried to mount the image as exfat using sudo mount -o loop -t exfat SD_Card.img ~/mountpoint but it fails to mount.




FUSE exfat 1.2.8



ERROR: exFAT file system is not found.








ext4 data-recovery sd-card exfat






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 2 days ago







Matt Zabojnik

















asked Jan 14 at 20:30









Matt ZabojnikMatt Zabojnik

186




186













  • Reason for downvote? Help me improve my post rather than remaining an anonymous downvoter.

    – Matt Zabojnik
    Jan 14 at 20:36











  • First off, very good that you've gotten yourself an image of the disk to work with to try to recover from. The less done to the original medium, the better. If it's showing a lot of used space but no actual files, you might could try fscking the partition and then looking in /lost+found perhaps?

    – DopeGhoti
    Jan 14 at 21:06











  • Alright, I've tried fscking and checked in /lost+found. All of my Linux files were there, but no videos, and not even the pictures that I had previously recovered with testdisk's photorec. Any other suggestions?

    – Matt Zabojnik
    Jan 17 at 19:02





















  • Reason for downvote? Help me improve my post rather than remaining an anonymous downvoter.

    – Matt Zabojnik
    Jan 14 at 20:36











  • First off, very good that you've gotten yourself an image of the disk to work with to try to recover from. The less done to the original medium, the better. If it's showing a lot of used space but no actual files, you might could try fscking the partition and then looking in /lost+found perhaps?

    – DopeGhoti
    Jan 14 at 21:06











  • Alright, I've tried fscking and checked in /lost+found. All of my Linux files were there, but no videos, and not even the pictures that I had previously recovered with testdisk's photorec. Any other suggestions?

    – Matt Zabojnik
    Jan 17 at 19:02



















Reason for downvote? Help me improve my post rather than remaining an anonymous downvoter.

– Matt Zabojnik
Jan 14 at 20:36





Reason for downvote? Help me improve my post rather than remaining an anonymous downvoter.

– Matt Zabojnik
Jan 14 at 20:36













First off, very good that you've gotten yourself an image of the disk to work with to try to recover from. The less done to the original medium, the better. If it's showing a lot of used space but no actual files, you might could try fscking the partition and then looking in /lost+found perhaps?

– DopeGhoti
Jan 14 at 21:06





First off, very good that you've gotten yourself an image of the disk to work with to try to recover from. The less done to the original medium, the better. If it's showing a lot of used space but no actual files, you might could try fscking the partition and then looking in /lost+found perhaps?

– DopeGhoti
Jan 14 at 21:06













Alright, I've tried fscking and checked in /lost+found. All of my Linux files were there, but no videos, and not even the pictures that I had previously recovered with testdisk's photorec. Any other suggestions?

– Matt Zabojnik
Jan 17 at 19:02







Alright, I've tried fscking and checked in /lost+found. All of my Linux files were there, but no videos, and not even the pictures that I had previously recovered with testdisk's photorec. Any other suggestions?

– Matt Zabojnik
Jan 17 at 19:02












1 Answer
1






active

oldest

votes


















0














Running testdisk on the ddrescue image as per the instructions in this guide, I was able to recover all files.



The initial quickscan did not detect anything useful, but after the quickscan, a deepscan option is available.



Deepscan detected three partition file systems-




ext4, exFAT, exFAT




ext4 was labeled Linux. I did not try to recover anything from that partition. This is the partition that was mountable previously.



The first exFAT was unlabeled, and I was able to browse through it using terminal commands provided by testdisk. Contained in this partition table, which other programs such as gparted were unable to see, were all of the GoPro folders and files, in pristine order. Within the DCIM folder, I found all of my photos and videos with correct file names and time stamps- so recovery was not a matter of restoring corrupted files at all.



The second exFAT looked to be the same as the first, but the files were unreadable.






share|improve this answer























    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
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f494491%2fsd-card-recovery-without-data-loss-or-corruption%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    Running testdisk on the ddrescue image as per the instructions in this guide, I was able to recover all files.



    The initial quickscan did not detect anything useful, but after the quickscan, a deepscan option is available.



    Deepscan detected three partition file systems-




    ext4, exFAT, exFAT




    ext4 was labeled Linux. I did not try to recover anything from that partition. This is the partition that was mountable previously.



    The first exFAT was unlabeled, and I was able to browse through it using terminal commands provided by testdisk. Contained in this partition table, which other programs such as gparted were unable to see, were all of the GoPro folders and files, in pristine order. Within the DCIM folder, I found all of my photos and videos with correct file names and time stamps- so recovery was not a matter of restoring corrupted files at all.



    The second exFAT looked to be the same as the first, but the files were unreadable.






    share|improve this answer




























      0














      Running testdisk on the ddrescue image as per the instructions in this guide, I was able to recover all files.



      The initial quickscan did not detect anything useful, but after the quickscan, a deepscan option is available.



      Deepscan detected three partition file systems-




      ext4, exFAT, exFAT




      ext4 was labeled Linux. I did not try to recover anything from that partition. This is the partition that was mountable previously.



      The first exFAT was unlabeled, and I was able to browse through it using terminal commands provided by testdisk. Contained in this partition table, which other programs such as gparted were unable to see, were all of the GoPro folders and files, in pristine order. Within the DCIM folder, I found all of my photos and videos with correct file names and time stamps- so recovery was not a matter of restoring corrupted files at all.



      The second exFAT looked to be the same as the first, but the files were unreadable.






      share|improve this answer


























        0












        0








        0







        Running testdisk on the ddrescue image as per the instructions in this guide, I was able to recover all files.



        The initial quickscan did not detect anything useful, but after the quickscan, a deepscan option is available.



        Deepscan detected three partition file systems-




        ext4, exFAT, exFAT




        ext4 was labeled Linux. I did not try to recover anything from that partition. This is the partition that was mountable previously.



        The first exFAT was unlabeled, and I was able to browse through it using terminal commands provided by testdisk. Contained in this partition table, which other programs such as gparted were unable to see, were all of the GoPro folders and files, in pristine order. Within the DCIM folder, I found all of my photos and videos with correct file names and time stamps- so recovery was not a matter of restoring corrupted files at all.



        The second exFAT looked to be the same as the first, but the files were unreadable.






        share|improve this answer













        Running testdisk on the ddrescue image as per the instructions in this guide, I was able to recover all files.



        The initial quickscan did not detect anything useful, but after the quickscan, a deepscan option is available.



        Deepscan detected three partition file systems-




        ext4, exFAT, exFAT




        ext4 was labeled Linux. I did not try to recover anything from that partition. This is the partition that was mountable previously.



        The first exFAT was unlabeled, and I was able to browse through it using terminal commands provided by testdisk. Contained in this partition table, which other programs such as gparted were unable to see, were all of the GoPro folders and files, in pristine order. Within the DCIM folder, I found all of my photos and videos with correct file names and time stamps- so recovery was not a matter of restoring corrupted files at all.



        The second exFAT looked to be the same as the first, but the files were unreadable.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 8 hours ago









        Matt ZabojnikMatt Zabojnik

        186




        186






























            draft saved

            draft discarded




















































            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.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f494491%2fsd-card-recovery-without-data-loss-or-corruption%23new-answer', 'question_page');
            }
            );

            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







            Popular posts from this blog

            How to make a Squid Proxy server?

            Is this a new Fibonacci Identity?

            19世紀