bz2 files, with files in them with no extension that are timestamped for the time I would have recorded the footage. 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.ĮDIT: I just used Disk Usage Analyzer and found all of the largest files that photorec recovered. IMG file with foremost -v -q -t mp4 -d but it finished with 0 files returned.Īt this point, it doesn't actually seem to me that there has been either data loss or corruption. When I mount the image file, it behaves exactly the same way as the disk does (expected). I've used ddrescue to duplicate the disk to an image that I can work with. I was able to successfully recover all 6 GB of photos using photorec. 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. 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. From what I could tell, 128 GB is too much for this GoPro Session. 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. I went on a trip, took lots of photos and video, and then suddenly the GoPro was having trouble reading the disk. At some point, I either deleted everything off of it or formatted it using the Chromebook's simple formatting system.Īfter 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. I have a 128 GB Micro SD Card that I formatted as ext4 and used in a Chromebook for an Ubuntu Chroot Environment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |