5/7/2023 0 Comments Testdisk recover files ext4![]() If the journal is broken, what does that cause? There might be a problem with it indeed since the hard driwe was turned off suddently. Knowing inode_number you can get the inode itself as long as you have the superblockĪutomatic tools do that already, so if they fail there must be something else going on, like a problem with journal. Superblock recovery in theory should work, other than that you might want to check what fsck says about the journal, that may yield some hints.įilenames are basically data on disc, they are maps ("filename", inode_number) I also found online some info on how to recover the partition using backup superblocks, but all the offset i tried don't seem to work (doing the dry-run fsck gives me a superblock error).Īt this point i have no idea what to do, besides using photorec (which i would like to not resort said: ![]() However, whatever partition i try to open gives me no files: ![]() Using testdisk i can see partitions with the original partition name: I already made an image of the disk, and I'm working on that. ![]() I'd be nice to be able to recover it with the correct file names, so that the files would actually have context (most are source codes and stuff referenced via file name). Photorec of course can see everything, but with random file names. I desperately ^C but it was too late and the filesystem was gone, so now i'm trying to recover the data. Of course, since i was setting up the backup system, I didn't have any backup. While setting up my backup system (oh, the irony), I accidentally launched a mkfs.fat on my ext4 hard drive.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |