Thanks everyone, I'm marking the thread as solved. > Searching the name of the files through all of them, my files started to show up. Most of the files were organized in numbered folders with (fortunately) the original name and their extensions in the right place. > At this point some folders were still there, many not there at all or not entirely. > I had testdisk restoring the partition and recovering NTFS boot sector from its backup. One of these of the NFTS one I was searching for. TestDisk Quick Search results in a partition that cannot be recovered and an error that the hard disk seems too small (remnants of adjusting partition sizes in the past): Continuing to the next screen: Quick search results: I can view files in the FAT32 LBA and Linux partitions, though the Linux partition is obviously missing a lot of files. > After testdisk finished the deep scan (after hours), it found something like 30 old partitions previously created over the last years. I'm happy to say I recovered all the data I was searching for. For example I directly operated on the damaged disk but I should have done as you say, it's way safer. I'm reading this only now, but these are all gold advices. I quickly downloaded and made my pendrive bootable with DiskGenius. From what Ive understood, I may have written incorrect Partition and now it has destroyed it. Now, it cannot be restarted and shows 'No Bootable Device found'. I selected my disk, pressed Intel, then Analyse, then write, then Restart. You fail? No problem, you still got a less broken copy around. So, in order to repair it, I used TestDisk. You take a copy of the data and operate on that copy - notably if you don't know what you do. Photorec can find most of my files but sorting them out again is going to take weeks. Mon Oct 22 23:38:58 2007 Command line: TestDisk /log /debug TestDisk 6. Good one Running Testdisk has found no partitions to fix. No extended partition TestDisk exited normally. If you screw your data, DO NOT ATTEMPT TO RESCUE IT. No partition found or selected for recovery searchpart() Disk /dev/hda - 756 MB / 721 MiB - CHS 23 255 63 (RO) Results. If you created a deviating PT and "used" the disk or, worse, created a new FS on the offset of the original NTFS partitions, you can start praying that your data can be recovered - but you'll get tons of anonymous files and file fragments (at best with proper extensions)Ģ. If you didn't otherwise write to the disk, all you really need to do is to re-create the original partition table - the first partition is now likely compromised, but that should be it. So, if I press P and try to copy the files inside it from this terminal, it says: Keys A: add partition, L: load backup, T: change type, P: list files,Įxt4 blocksize=4096 Large_file Sparse_SB Backup_SB, 657 GB / 612 GiB *=Primary bootable P=Primary L=Logical E=Extended D=Deleted Use Left/Right Arrow keys to CHANGE partition characteristics: Use Up/Down Arrow keys to select partition.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |