Verify Disk in OS X Lion

I have recently upgraded to OS X Lion on my MBP C2D, 4 GB. I went ahead to verify my disk which asked me to repair the disk. I inserted the Installation DVD but it gave an error that this DVD won't work on this version of the OS X. It asked me to install MAC OSX 23.1.1.
What do I do?

If you are already in Lion or in the Recovery HD using Disk Utilities to verify your disk and it wants you to repair it, you simply stay right there in Disk Utilities and click Repair Disk. You don't insert you previous OS X disk.
If you're verifying your disk some other way, please explain further.

Similar Messages

  • After clean install of Mountain Lion 10.8.5 no Gate Keeper and a ton a long list of differences in verify disk permissions after updating to Itunes 12.1

    HI everybody.
    I have a MacBopok Prop 15" from mid 2012, 2.6Ghz, Intel Core i7, 16GB RAM 1 TB SSD.
    As my Mac was running as fast as possible it  was getting slower down during start and shutdown, from 2 secopnds to 15 secconds during start and shutdown . Apps were crashing sometimes a freeze, total crash which made me go directly to Recovery HD and not my log in page after all the tricks I know I took it to service center where they zeroed my SSD HD and reinstalled Mountain Lion 10.8.5. Strangly enough Gate keeper was not in my preferences and a old version of Itunes 10.4 if I recall. The Mac is still slow while I reinstall all apps from App store and one for one documents and folders from my latest TM back up.
    Updated the Security update, and other updates had the same problem as many updating Iphoto 9.4.3 error 102, still have not been able.
    But running verify disk permissions there is a massive list of Itunes differences while I have not  even added one song. At least 60 to 70 differences. I know a lot of these differences are nothing to worry about but a clean install without Gate keeper and an old Itunes which after update to 12.1 has so many disk differences, this can not as it should be also as I have not added anything from my Itunes library. Any feedback or advice would be very much appreciated.
    Greetings
    Matt

    Do a backup. Boot to the Recovery Volume (command - R on a restart or hold down the option/alt key during a restart and select Recovery Volume). Run Disk Utility Verify/Repair and Repair Permissions until you get no errors. Then re-install the OS.
    OS X Recovery
    OS X Recovery (2)

  • Running Lion. Verified Disk. Warned HD corrupt, and need to restart from disk and run repair. No idea how to do this without a physical disk.

    Hi,
    My MacBook Pro has been acting up a little. I tried the usual repair options: repair permissions, zap P-ram, and Safe Boot (although I've never gotten the machine to Safe Boot properly since installing Lion). I ran Verify Disk and it stopped part way through, saying that the HD is corrupt. It instructed me to start up from the (installation?) disk and run the repair function from the disk utility. (I've included a screen shot of the Verify Disk screen). I have no idea how to go about this without a physical start up disk (Lion). I do have the disks that came with the computer at the time of purchase (Will one of those work?).
    Thanks,
    JGW

    Thank you!
    I was able to access the recovery function and used the Disk Utility to repair my HD.
    Would you recommend that I still re-install Lion?
    Again, thank you for taking the time to help me!
    Best wishes,
    JGW

  • I have a an imac with Lion OS x software 10.7.5. The built in DVD player will no longer play dvd;s and it says its an unsupported disc. I have done a risk disk permissions and verify disk and both say ok

    I have a an imac with Lion OS x software 10.7.5. The built in DVD player will no longer play dvd's  and it says its an unsupported disc. I have done a risk disk permissions and verify disk and both say ok.
    I haven't changed any settings regarding region codes

    You may have run discs from different regions,these would be commercial DVDs. If so most DVD players need to be told what region the disc is from. Have you done this by chance, if you are not sure look at the region numbers listed on the commerical DVDs you have and see if some use different numbers.

  • !!!HI, SO I BOUGHT MOUNTAIN LION ON MY MACBOOK PRO TRYING TO UPGRADE FROM SNOW LEOPARD, AND WHILE TRYING TO REINSTALL THE OS SETUP AS IT SHOWED IT COULDNT BE VERIFIED, I CROSSED OUT MOUNTAIN LION FROM MY PURCHASES, ITS NOW GONE, DO I HAVE TO BUY IT AGAIN?

    HI, SO I BOUGHT MOUNTAIN LION ON MY MACBOOK PRO TRYING TO UPGRADE FROM SNOW LEOPARD, AND WHILE TRYING TO REINSTALL THE OS SETUP AS IT SHOWED IT COULDNT BE VERIFIED, I CROSSED OUT MOUNTAIN LION FROM MY PURCHASES, ITS NOW GONE, DO I HAVE TO BUY IT AGAIN?

    Please google search for "Mountain Lion disk crash" before upgrading you mac pro. You might need to replace you Mac hard drive after the upgrade.So many people had the same problems including me.
    Be aware of the Mountain Lion upgrade problem.

  • Disk Utility in Mavericks Verify Disk gives no report

    When I use Disk Utility, version 13, in OS X Mavericks (10.9)  to verify a disk, it goes through the various steps ...
    Verifying volume “MacSSD”
    Starting verification tool:
    Checking file system
    Performing live verification.
    Checking Journaled HFS Plus volume.
    Checking catalog hierarchy.
    Checking extended attributes file.
    Checking volume bitmap.
    Checking volume information.
    ...and then gives no report at the end of the process -- the way it used to under Mountain Lion, where you'd see a (green) statement that the disk was OK. Instead, the Verify Disk button once again is highlighted.
    Am I correct that this is a change in behavior? and why no report -- not even in the log?? Is this just "no news is good news"?

    Apple doesn’t routinely monitor the discussions. These are mostly user to user discussions.
    Send Apple feedback. They won't answer, but at least will know there is a problem. If enough people send feedback, it may get the problem solved sooner.
    Feedback
    Or you can use your Apple ID to register with this site and go the Apple BugReporter. Supposedly you will get an answer if you submit feedback.
    Feedback via Apple Developer

  • Slow.  iMac 10.5.8.  Verified Disk Permissions and then Repaired Disk Permissions.  Not much improvement in speed.  How do I empty internet files from safari?

    iMac 10.5.8 is slow.  Verified Disk Permissions and then repaired.  No big improvement in speed.
    What about internet files (safari and firefox) ; caches and cookies?
    Thank you.

    Applejack might help.
    Download:
    http://sourceforge.net/projects/applejack/
    Article on using:
    http://reviews.cnet.com/8301-13727_7-10334620-263.html?tag=mfiredir
    It runs in single user mode, where it runs more safely than other maintenance/cleaning programs because there is less chance of interference from the OS. After installing (you won't see it in the Applications Folder) hold CMD-S at startup. You will get a black screen with MS-DOS like text. Just follow the prompts: type in "applejack AUTO" and it will run through the following:
    Correct any Disk problems.
    Repair Permissions.
    Clear out Cache Files.
    Repair/check several plist files.
    Dump the VM files for a fresh start.
    Trash old Log files.
    You can also run tasks selectively and for specific users by typing in "applejack." After running in "AUTO,"  you can go back and run it again as "applejack," steps 3 & 4 only, for your user.
    The first reboot will take much longer than usual, as it rebuilds caches. It may take several restarts to see the benefits. Because of the deep cache cleaning in AUTO mode some applications may tell you they are being opened for the first time.
    NOT YET UPDATED FOR LION
    (Adapted from post by BDAqua)

  • Repair Disk Error during Mountain Lion Install 2010 Macbook Pro

    Hello All,
    Last night like many of you I downloaded Mountain Lion to update to the newest Apple OS. During the install procress I was told my Harddrive was corrupted and needed to be repaired. After running the Verify Disk utility the following errors came up
    Checking Catalog file,
    Incorrect number of thread records
    Incorrect number of thread records
    Checking catalog hierarcchy.
    Invalid volume file count
    Checking volume information.
    The volume Macintosh HD was found corrupt and needs to be repaired.
    Then I used the repair utlity on the same screen.
    The message was that it had attempted to repair it three times and it could not do so.
    During the repair the error message incorrect number of thread records appeared twice.
    Afterwards it no longer showed that harddrive as mounted and I cannot boot back into it. When booting it gives me the option of the Install Boot, the Recovery Boot, or my Windows Partition boot.
    Two Questions
    Is there a way to boot back into the OS to recover my files, I have most backed up but would like to get a few more on my external HD?
    My other question is how can I sucessfully repair the disk so that I can do the above question and also install mountain lion.
    Thank you,
    Andrew

    If you have no current backups, DO NOT TRY TO BOOT.
    If you want to preserve the data on the internal drive(s), you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data, you can skip this step.
    There are several ways to back up a Mac that is unable to fully boot. You need an external hard drive to hold the backup data.
    1. Boot into Recovery (command-R at startup) or from a local Time Machine backup volume (option key at startup.) Launch Disk Utility and follow the instructions in the support article linked below, under “Instructions for backing up to an external hard disk via Disk Utility.”
    How to back up and restore your files
    2. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, boot the non-working Mac in target disk mode by holding down the key combination command-T at the startup chime. Connect the two Macs with a FireWire or Thunderbolt cable. The internal drive of the machine running in target mode will mount as an external drive on the other machine. Copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
    How to use and troubleshoot FireWire target disk mode
    3. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.

  • Verify disk failure on Mac Book Pro Toshiba hard drive

    I tried to run a verify disk on the Toshiba Hard drive on my computer and the following error keeps repeating. It will let me run a repair but the same error occurs after every verify.

    Welcome to Apple Support Communities
    You will be glad that's not a hardware problem, but it looks like your EFI partition is damaged. That volume is used to store firmware updates, as they are installed during the startup. If you don't have any problem while turning on your MacBook and you have an old MacBook, you can ignore these steps, but it's better to solve this problem.
    If you want to fix the problem, you will have to format the hard drive and reinstall OS X, so make a backup of your files with Time Machine > http://support.apple.com/kb/HT1427
    Then, hold Command, Option (Alt) and R keys while your Mac is starting to start up in Recovery, open Disk Utility and erase the hard disk > http://pondini.org/OSX/DU1.html A healthy EFI partition will be made.
    Finally, close Disk Utility and reinstall OS X. When the installation finishes, Mac OS X will ask you to restore the backup, so follow the steps.
    If you had OS X Lion before upgrading to OS X Mountain Lion, use Recovery Disk Assistant to create Recovery HD onto a USB drive and start up from it by holding the Option (Alt) key

  • Verify Disk Fails on 11" Mid-2011 MBA

    Hi,
    When using Disk Utility to Verify Disk, I get the following error:
    Unable to bootstrap transaction group 1877: invalid field value
    No valid commit checkpoint found
    The volume 5E475AC6-27BF-4533-89F3-A1E555405EDA was found corrupt and needs to be repaired.
    Problems were found with the partition map which might prevent booting
    Error: Storage system verify or repair failed.
    I tried searching, but didn't seem to be able to find anything related. Anybody have any ideas?
    Thanks!

    I have the same problem and my drive is encrypted with Filevault 2.  Here is a copy of my Disk Utility results-
    Verifying partition map for “TOSHIBA MK7559GSXF Media”
    Checking prerequisites
    Checking the partition list
    Checking for an EFI system partition
    Checking the EFI system partition’s size
    Checking the EFI system partition’s file system
    Checking all HFS data partition loader spaces
    Checking Core Storage Physical Volume partitions
    Checking storage system
    Checking volume.
    disk0s2: Scan for Volume Headers
    disk0s2: Scan for Disk Labels
    Logical Volume Group D6C6B140-FF84-4215-A23B-2F338FDB07DE spans 1 device
    Logical Volume Group has a 16 MB Metadata Volume with double redundancy
    Start scanning metadata for a valid checkpoint
    Load and verify Segment Headers
    Load and verify Checkpoint Payload
    Load and verify Transaction Segment
    Load and verify Transaction Segment
    Incorporate 1 newer non-checkpoint transactions
    Load and verify Virtual Address Table
    Load and verify Segment Usage Table
    Load and verify Metadata Superblock
    Load and verify Logical Volumes B-Trees
    Logical Volume Group contains 1 Logical Volumes
    Load and verify BFACC386-1738-482F-B4C8-438DC4A8850E
    Load and verify F8E6D497-E9AC-41A4-9917-AD101492A4C9
    Load and verify Freespace Summary
    Load and verify Block Accounting
    Load and verify Segment Cleaning
    Unable to bootstrap transaction group 5720: invalid field value
    Continue scanning metadata for an older checkpoint
    Load and verify Segment Headers
    Load and verify Checkpoint Payload
    Load and verify Transaction Segment
    Incorporate 0 newer non-checkpoint transactions
    Load and verify Virtual Address Table
    Load and verify Segment Usage Table
    Load and verify Metadata Superblock
    Load and verify Logical Volumes B-Trees
    Logical Volume Group contains 1 Logical Volumes
    Load and verify BFACC386-1738-482F-B4C8-438DC4A8850E
    Load and verify F8E6D497-E9AC-41A4-9917-AD101492A4C9
    Load and verify Freespace Summary
    Load and verify Block Accounting
    Load and verify Segment Cleaning
    Unable to bootstrap transaction group 5719: invalid field value
    Continue scanning metadata for an older checkpoint
    Load and verify Segment Headers
    Load and verify Checkpoint Payload
    Load and verify Transaction Segment
    Incorporate 0 newer non-checkpoint transactions
    Load and verify Virtual Address Table
    Load and verify Segment Usage Table
    Load and verify Metadata Superblock
    Load and verify Logical Volumes B-Trees
    Logical Volume Group contains 1 Logical Volumes
    Load and verify BFACC386-1738-482F-B4C8-438DC4A8850E
    Load and verify F8E6D497-E9AC-41A4-9917-AD101492A4C9
    Load and verify Freespace Summary
    Load and verify Block Accounting
    Load and verify Segment Cleaning
    Unable to bootstrap transaction group 5718: invalid field value
    Continue scanning metadata for an older checkpoint
    Load and verify Segment Headers
    Load and verify Checkpoint Payload
    Load and verify Transaction Segment
    Incorporate 0 newer non-checkpoint transactions
    Load and verify Virtual Address Table
    Load and verify Segment Usage Table
    Load and verify Metadata Superblock
    Load and verify Logical Volumes B-Trees
    Logical Volume Group contains 1 Logical Volumes
    Load and verify BFACC386-1738-482F-B4C8-438DC4A8850E
    Load and verify F8E6D497-E9AC-41A4-9917-AD101492A4C9
    Load and verify Freespace Summary
    Load and verify Block Accounting
    Load and verify Segment Cleaning
    Unable to bootstrap transaction group 5717: invalid field value
    No valid commit checkpoint found
    The volume D6C6B140-FF84-4215-A23B-2F338FDB07DE was found corrupt and needs to be repaired.
    Problems were found with the partition map which might prevent booting
    Error: Storage system verify or repair failed.
    This is a brand spanking new Macbook Pro 8,2 with a clean install of lion with my user account migrated from a time machine backup.  The weird thing is that if I boot to the recovery partition and verify the disk, it comes back clean with no errors.  When I log in again and run disk utility immediately after logging in, disk utility shows no errors.  I only get these errors after the machine has been on for a while.
    I have tried just doing a repair disk in the recovery partition to see if it would help but I still get the same errors after a few hours of use.  I think there is a bug with Filevault.
    I am using 10.7.1

  • Verify Disk results, confusing.. Can they be the cause of system lock ups?

    I have been experiencing strange freezes on my Mac Pro 2008 system.
    My boot disk is a 50% full 128GB SSD from Crucial and is running beautifully fast however for the past couple of weeks my system often freezes for anything from 3 seconds to 30 seconds and then the Finder restarts.
    After the Finder restarts everything continues running smoothly. As if nothing ever happend, no error reports, no apps crashed, nothing.
    I have verified disk permissions and verified the disk itself in Disk Utility but I am not quite sure what these results mean and if they could be the cause of these random lock ups.
    here are the results:
    Verify permissions for “Boot Disk”
    Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
    Group differs on "private/etc/hostconfig", should be 0, group is 20.
    Permissions verification complete
    Verifying volume “Boot Disk”
    Performing live verification.
    Checking Journaled HFS Plus volume.
    Checking extents overflow file.
    Checking catalog file.
    Missing thread record (id = 5888152)
    Incorrect number of thread records
    Checking multi-linked files.
    Checking catalog hierarchy.
    Invalid volume directory count
    (It should be 184294 instead of 184295)
    Checking extended attributes file.
    Checking volume bitmap.
    Checking volume information.
    The volume Boot Disk was found corrupt and needs to be repaired.
    Error: This disk needs to be repaired. Start up your computer with another disk (such as your Mac OS X installation disc), and then use Disk Utility to repair this disk.
    I would really appreciate it if someone that knows their way around this stuff could help me troubleshoot this.
    As for the problem of the system locking up it does not happen in the same application consistently.
    Often it happens in Firefox but it could equally often happen when working in Photoshop, browsing files in the Finder or trying to access the Spotlight search via the keyboard shortcut.
    When the system locks up I get the spinning beach ball and I can still move the mouse and click and even still access CMD+TAB app switcher, switch spaces and all those things, just applications become non responsive.
    If you need any more details please let me know.
    Thanks for reading,
    Jannis

    These are innocuous errors that you may safely ignore. However the disk error is a problem. Do the following:
    Repairing the Hard Drive
    Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger and Leopard.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors, then quit DU and return to the installer. Now restart normally.
    If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.

  • TM drive became read-only, only to be fixed by Verify Disk ?!?!

    Could one of you experts out there please explain this to me. My small brain can't wrap my mind around what happened -
    Yesterday I had to restore my system from a TM backup. After this, I decided to erase the TM drive and start backing up fresh. I did this, and for the past 5 hours, Time Machine has been happily backing up to this newly-erased partition.
    However, just a few minutes ago, I got an error message from TM. It said that the backup couldn't be completed because the volume was "read only". I couldn't believe this, so I checked out Get Info, and indeed it said that I only had read access to the volume that Time machine's been writing to for the past 5 hours! I found the KB article HT3275 that said to do a Repair on the TM drive. But Repair Disk was grayed out; only Verify Disk was lit.
    I checked around further, and couldn't come up with what caused this change in permissions, so I decided to do the Verify Disk just to see if there were any HD errors, but the partition came up clean. But then I couldn't believe my eyes - the Repair Disk button was now active! I switched back to Finder and did a Get Info on the TM partition, and it was back to allowing me Read/Write access!
    How could a Verify Disk operation cause the permissions to change from Read Only to Read/Write? The only system operation I did during those 5 hours of good TM backups was to change my Computer Name and uncheck "Use dynamic global hostname".
    Please, one of you Time Machine/OS X/UNIX gurus explain to this feeble mind what occurred here. I really need to know so that this won't happen again.
    Thanks.

    I tried running
    sudo fsck /dev/sdb1
    and got the following error:
    fsck from util-linux-ng 2.18
    fsck: fsck.ntfs: not found
    fsck: Error 2 while executing fsck.ntfs for /dev/sdb1

  • Disk Utility, Verify Disk & Repair Disk unavailable

    Hi there!
    I want to check my Hard Disk with Disk Utility, but none of the two buttons (Verify Disk & Repair Disk) are available, I started up from my Mac OS X installation disc, and once, it told me that the disk had errors and needed to backup my files, so I went back and backed up with Time Machine, then out of curiosity went again and I started up from my Mac OS X installation disc, and this time it told me that the disk was fine and there wasn't any errors, but when I open Disk Utility with my Mac, none of the buttons are available, is this normal?
    What should I do?
    Context: Before all this, I installed a program called Tuxera to create a NTFS partition but my Mac started to act weird, so I deactivate and uninstalled this program, that's when I went to verify the disk.
    Any Help would be gratefully appreciated

    I hope I'm wrong but it sounds very much like Tuxera did something to your startup disk. I would also be somewhat concerned about the integrity of any Time Machine Backups you made after you ran Tuxera.
    The safest thing to do would be to start up from your Snow Leopard disk and see if you can *restore your system and data from your Time Machine backups to an +external HD+* formatted using Mac OS Extended (Journaled) and GUID Partitioning. Formatting will erase all the data on that disk. *If you try to restore to the internal and it doesn't work you will probably lose most of your data.*
    Startup your Mac using the external and check very carefully to see that you have all your data and that everything works as it should. If it does you can safely reformat your internal drive from Disk Utility on the Leopard disk using Mac OS Extended (Journaled) and GUID Partitioning. After that you can clone the external drive to your Mac's internal drive or install from the Time Machine backups.
    If the Time Machine backup doesn't work you will need to run a disk data recovery utility to see if you can salvage your data from your internal drive.
    I don't use PC's so someone may be along with much better advice. However, unless and until someone more knowledgeable about PC file formats comes along to help *don't reformat your internal drive until you know your Time Machine backups are OK.*

  • Ok here goes nothing i have a late 2009 iMac 27  11.1 intel bought it refurbished and they installed mountain lion 10.8.4 on delivery w/o disks i think ran lion orig. idk & its been all problems 10.8.5 M.L so tried Maverick 10.9 now worse please help me

    ok here goes nothing i have a late 2009 iMac 27  11.1 intel bought it refurbished and they installed mountain lion 10.8.4 on delivery w/o disks i think ran lion orig. idk & its been all problems 10.8.5 M.L so tried Maverick 10.9 now worse please help me.....i still have backups of software for mountain lion 10.8 however i need to throw everything on a usb toshiba 1TB external storage for backup, plus from what ive read being i needed to try to go back and update the efi and frimware for my original model but when i found the right one it wont accept it.....and now i just tried to reinstall my mountain lion probably shoud have left in the cloud til i got backed up ...which i now needed to move my previous backed up stuff off the drive to reformat it properly as i read it being toshiba needs to be guid hard drive mac im relatively new to the whole mac thing and im just as ****** off as i was with PC ....lol i just wanna record music and have a steady workflow i do have a new 4s iphone and cloud storage but i believe my computers hacked or got malware or just ****** from incompatiable software ......and keychains not working for admin either PLEASE tell ,me what to do thx .....i will be so grateful im good with recording software and stuff bad with computers programing lol HELP me

    Hardware Overview:
      Model Name:          iMac
      Model Identifier:          iMac11,1
      Processor Name:          Intel Core i7
      Processor Speed:          2.8 GHz
      Number of Processors:          1
      Total Number of Cores:          4
      L2 Cache (per Core):          256 KB
      L3 Cache:          8 MB
      Memory:          16 GB
      Processor Interconnect Speed:          4.8 GT/s
      Boot ROM Version:          IM111.0034.B02
      SMC Version (system):          1.54f36
    Message was edited by: lnwko

  • 1)Could not start up os x 2)Only could start bootcamp 3)Tried resetting nvram 4)Could not start even in bootcamp 5)Verify disk says -. Verifying volume "Macintosh HD" Error: Live file system repair is not supported 6)Installed maverick on USB d

    1) Could not start up os x
    2) Only could start bootcamp
    3) Tried resetting nvram
    4) Could not start even in bootcamp
    5) Verify disk says …. Verifying volume “Macintosh HD”
    Error: Live file system repair is not supported
    6) Installed maverick on USB drive
    7) Boot from USB drive. Tried verifying HD: Volume header needs minor repair. The volume Recovery HD was found corrupt and needs to be repaired. Verifying volume “Macintosh HD”: Error: live file system repair is not supported.
    8) The terminal code says
    9) Last login: Wed Feb 11 14:09:47 on console
    10)  xxxx-MacBook:~ xxxx$ diskutil list
    11)  /dev/disk0
    12)  #: TYPE NAME SIZE       IDENTIFIER
    13)  0:      GUID_partition_scheme *160.0 GB   disk0
    14)  1: EFI EFI 209.7 MB   disk0s1
    15)  2:                  Apple_HFS Macintosh HD            80.1 GB disk0s2
    16)  3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
    17)  4:       Microsoft Basic Data 50.0 GB    disk0s4
    18)  /dev/disk1
    19)  #: TYPE NAME SIZE       IDENTIFIER
    20)  0:      GUID_partition_scheme *15.6 GB    disk1
    21)  1: EFI EFI 209.7 MB   disk1s1
    22)  2:                  Apple_HFS BOOT                    14.8 GB    disk1s2
    23)  3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
    24)  Saeedehs-MacBook:~ saeedehmirbagheri$ diskutil cs list
    25)  No CoreStorage logical volume groups found
    26)  Saeedehs-MacBook:~ saeedehmirbagheri$ sudo gpt -vv -r show /dev/disk0
    27)  Password:
    28)  gpt show: /dev/disk0: mediasize=160041885696; sectorsize=512; blocks=312581808
    29)  gpt show: /dev/disk0: PMBR at sector 0
    30)  gpt show: /dev/disk0: Pri GPT at sector 1
    31)  gpt show: /dev/disk0: Sec GPT at sector 312581807
    32)  start       size  index  contents
    33)  0          1 PMBR
    34)  1          1 Pri GPT header
    35)  2         32 Pri GPT table
    36)  34          6
    37)  40     409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
    38)  409640  156394528      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
    39)  156804168    1269544      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
    40)  158073712   56853648        
    41)  214927360   97652736      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
    42)  312580096       1679        
    43)  312581775         32         Sec GPT table
    44)  312581807          1         Sec GPT header
    45)  xxxx-MacBook:~ xxxx$ sudo fdisk /dev/disk0
    46)  Disk: /dev/disk0 geometry: 19457/255/63 [312581808 sectors]
    47)  Signature: 0xAA55
    48)  Starting       Ending
    49)  #: id  cyl  hd sec -  cyl  hd sec [     start - size]
    50)  ------------------------------------------------------------------------

    Thank you -
    I booted from external USB. The diskutil list output is from OS x booting from the USB, which shows the following:
    Saeedehs-MacBook:~ saeedehmirbagheri$ diskutil list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *160.0 GB   disk0
       1:                        EFI EFI                     209.7 MB   disk0s1
       2:                  Apple_HFS Macintosh HD            80.1 GB    disk0s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
       4:       Microsoft Basic Data                         50.0 GB    disk0s4
    /dev/disk1
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *15.6 GB    disk1
       1:                        EFI EFI                     209.7 MB   disk1s1
       2:                  Apple_HFS BOOT                    14.8 GB    disk1s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
    Saeedehs-MacBook:~ saeedehmirbagheri$ diskutil cs list
    No CoreStorage logical volume groups found
    I am not able to use target disk mode because I don't have firewire/thunderbolt ports.

Maybe you are looking for