Previous 1 50 51 52 53 54 Next 1,473 Replies Latest reply: Aug 1, 2015 4:48 PM by Ectoplasm88 Go to original post Branched to a new discussion.
  • SumnerRain Level 1 Level 1 (0 points)

    At the very first screen, when you chose the drive (after chosing to make a log file or not), shoulnd't there be more than one media?  Yesterday I had two.  Nevermind, I should be chosing "sudo" right?

     

    Screen Shot 2013-10-25 at 11.07.35 AM.png

  • Christopher Murphy Level 3 Level 3 (555 points)

    Stop.

     

    This screen says rdisk1. The previous results you gave for fdisk and gpt used rdisk0, why is there a difference?

  • Christopher Murphy Level 3 Level 3 (555 points)

    Post the results from the command diskutil list

  • SumnerRain Level 1 Level 1 (0 points)

    TestDisk will try to restart itself using the sudo command to get
    root (superuser) privileges.

     

    sudo may ask your user password, it doesn't ask for the root password.
    Usually there is no echo or '*' displayed when you type your password.

     

    TestDisk 6.14, Data Recovery Utility, July 2013
    Christophe GRENIER <grenier@cgsecurity.org>
    http://www.cgsecurity.org
      [Restored]
    Last login: Fri Oct 25 11:25:38 on ttys000
    Macintosh:~ Heather$ diskutil list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *750.2 GB   disk0
       1:                        EFI EFI                     209.7 MB   disk0s1
       2:                  Apple_HFS Macintosh HD            600.0 GB   disk0s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
       4:       Microsoft Basic Data                         75.3 GB    disk0s4
    /dev/disk1
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                            Sims3EP10              *4.7 GB     disk1
    Macintosh:~ Heather$

  • tomd007 Level 1 Level 1 (0 points)

    Hello ava_jack,

     

    I might be comming back to you late, but if you haven't solved the problem, here are the initial steps:

     

    In order to know how to preceed, we need to know the current status of your partitions. So go to terminal and type the following:

     

    sudo fdisk /dev/rdisk0

    sudo gpt -r -v show /dev/rdisk0

     

    these commands will only work if you have already downloaded and installed "gdisk" available here: gdisk

     

    You might also need (for later) to donwload "TesDisk" available here: http://www.cgsecurity.org/wiki/TestDisk_Download

     

    Let me know the current status of your computer and what have you done so far so as I can try en see how I can help.

  • Christopher Murphy Level 3 Level 3 (555 points)

    fdisk and gpt commands are included in OS X and are not a part of gdisk so they can be run before doing anything else.

  • SumnerRain Level 1 Level 1 (0 points)

    Here is my screenshot for when I chose "sudo".

     

    Screen Shot 2013-10-25 at 12.54.14 PM.png

  • tomd007 Level 1 Level 1 (0 points)

    well - when I first tried, Terminal didn't recognise the commands, so that I had to download that software and then it worked well. I don't know why it was like that in my case.

  • Christopher Murphy Level 3 Level 3 (555 points)

    choose the 2nd one, /dev/rdisk0

  • Christopher Murphy Level 3 Level 3 (555 points)

    could be that there was a bungled search path for your user which was fixed when gdisk was installed. fdisk and gpt have been installed since the dawn of OS X.

  • SumnerRain Level 1 Level 1 (0 points)

    Disk0 and rdisk0 yielded the same results.  The missing partition is #4, right?  I just need the start and end numbers for the [bootcamp] before moving on to gdisk steps, correct?  Sorry if I am being a pain, I just want to make sure I don't eff this up.

     

    Screen Shot 2013-10-25 at 1.10.19 PM.png

  • tomd007 Level 1 Level 1 (0 points)

    Hi Chriss, is there a way I can give you points for all your help? - I don't know how to do it.

  • Csound1 Level 8 Level 8 (44,775 points)

    tomd007 wrote:

     

    Hi Chriss, is there a way I can give you points for all your help? - I don't know how to do it.

    Anf Chris certainly deserves them but unfortunately points can only be awarded by the poster that started the thread.

  • Christopher Murphy Level 3 Level 3 (555 points)

    No, that's not the correct information. Maybe tom or frank can speak up about how they got testdisk to scan the disk for their missing volume. What your screen shot shows is the quick scan (I think), which has grabbed the information from either the MBR or GPT, which has the wrong information. So if you plug these values into gdisk, you'll be plugging in the same values it already has. (So you won't make things worse, but it won't fix it either.)

  • Christopher Murphy Level 3 Level 3 (555 points)

    OK I just set this up in qemu/kvm to test it out.

     

    sudo ./testdisk /dev/rdisk0

     

    I get a menu and can use arrow keys to choose a media, there is only one, and the "button" down below is  proceed. So I just hit enter.

     

    The partition table type default is EFI GPT so I choose that.

    The Analyze option is the next default, so I choose that. So far I've only chosen defaults.

     

    Now it shows me a list of partitions, one of which I know is wrong. The default here is Quick Search so I choose that also. It immediately lists three things while continuing to analyze cylinder with a countdown, but the 3rd item is already the missing volume I'm looking for. But it's continuing to scan.

     

    So depending on the drive size, it might take a while longer than it did for my test (a tiny 8GB virtual disk) to find the NTFS volume you're after. And it might have more than one it proposes, only one is correct. Once it's done, you'll have a list and can highlight entries with the up/down arrow key. Highlight one and type P for "list files". If that's the wrong possibility, it'll probably say something like "can't open file system. filesystem seems damaged." So quit to back up, down arrow key to try the next suggestion. Then type P again.

     

    Finally, instead of "can't open file system" I get a folder structure that looks like the folders/files I'm looking for. Right above this are three numbers which are the start, end, and size values. You can also backup with quit, and see the most recent selection you chose, and this time there are column heading (kinda nice) that correspond to those same values.

     

    So the values you're after are start and end. They go in gdisk as "First sector" and "Last sector". So give that a shot.

Previous 1 50 51 52 53 54 Next