It began to write the recup_dir.15 onwards then during pass2.Īfter pass2 a run named bruteforce started, which looped and I learned (googled) that this happens with bigger drives and bruteforce should nly be used for small flash drives. I assumed that it is now using the 500GB MacintoshHD as some kind of swap or RAM, hence the free space filling up, until 200MB left.Īfter pass1 I was again asked to select a destination drive, this time i created a folder on my OhneTitel1 drive and selected that. The only option available was "close window". I didn't select MacintoshHD for Photorec, so it can't be holding the recup_dir.x files, I guess.ĭuring the recovery process, after pass1 the Mac GUI (Photorec itself runs in Terminal sudo) gave a notice that informed about not enough buffer (allthough I had 16GB RAM) and that therefore the recovery would take longer. "OhneTitel1" (the HDD, where the recovered files should be saved) "OhneTitel" (the HDD that files had to be recovered from) MacintoshHD (my OS, 500GB, over 100GB free) My destination HDD, where the recovered files should go has subdirectories (folders) starting with recup_dir.15. Photorec writes the recovered files in a subdirectory that it names recup_dir.1, recup_dir.2 and so on. How do I find them and how do I free the disc space?Ģ. 200MB free space left, but I can't find any data that has been added to this drive. my internal drive with the OS had something over 100GB free space, now it has ca. Successfully (StellarPhoenix Mac data recovery did fail in that attempt only finding like one frame of every movie)īad news (and here is my question: what should I do?):ġ. Good news: Photorec can find lost DV files (like those from old iMovie Version up to iMovieHD6).
0 Comments
Leave a Reply. |