Otherwise, creating such a filesystem can easily destroy the wrong data - hence only attempt this if you know very well what you're doing. However I knew perfectly where to create this filesystem, especially because it did not border with the lost partition. So I could speed up search a lot by creating a filesystem in an empty partition before the missing one, so that Testdisk would skip that space. If there is a lot of free space (without a filesystem) before the partition, this might be very slow. Once it thinks it found a partition and you confirm its guess, it will skip searching inside the partition. If the partition entry is just removed, Testdisk will look for the start of the partition in sensible positions (by default, at the start of every cylinder, since partitions should usually be cylinder-aligned), ignoring the existing partition table. A (dangerous) tip to speedup Testdisk from my own experience But if you're really impatient (as I am) and you know very well what you're doing, you might want to read on. Otherwise, it might take more time, but probably waiting is the most sensible option. If you indeed just removed one partition, it should be fast.
I had the luxury of an empty HFS+ partition, so I just removed it and recovered it using Testdisk - it was rather fast. 2) Locate the disk which you want to edit in the left-hand sidebar. The main pane to the right shows information about the drive which you currently have selected. The sidebar on the left shows your connected drives, with their sub-partitions. I tried using Testdisk 6.13 (latest stable release) and it worked like a breeze for both NTFS and HFS+. 1) Launch Disk Utility from /Applications/Utilities, or via Spotlight.
0 kommentar(er)
