My partition menu in Disk Utility is greyed out in recovery partition

So upgraded to yosemite and after a while decided that i would do a clean install of it because it didn't update the recover partition and i could no longer boot into Ubuntu partition. So i made my bootable drive and booted into it. I was met with:
When i clicked on the hard drive in the sidebar that it was only 300gbs, which is the size of my os x partition.
I then went to the partition menu and i could not change anything there. I can't resize anything or repartition anything.
I've tried to do multiple things in terminal from recovery and bootable disk but to no avail. It still won't work. The thing is that when i type diskutil list into terminal i get
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:          Apple_CoreStorage                         300.0 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
   4:       Microsoft Basic Data                         1.0 MB     disk0s4
   5: 0FC63DAF-8483-4772-8E79-3D69D8477DE4               195.0 GB   disk0s5
   6:                 Linux Swap                         4.2 GB     disk0s6
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS Macintosh HD           *299.6 GB   disk1
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS MacBook Pro Back Up     398.2 GB   disk2s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk2s3
   4:                  Apple_HFS Back up of files        100.9 GB   disk2s4
/dev/disk0 is the internal hard drive that i want to reformat, /dev/disk1 i don't know what that is. It could be an internal thing in the drive? And /dev/disk2 is my external hard drive that is running mavericks that i writing this on.
I've tried resetting PRAM and SMC but that didn't help.
Didn't know if reinstalling the OS would help?
What i want to get is to reformat /dev/disk0 so that i have a 500gb hard drive that i can then do a clean install of yosemite on and then possibly make an ubuntu partition later. PLEASE HELP!!!

And, this was from the Internet Recovery utilities window, right? OK, this next suggestion depends on which MBA model you have. Check the link below. If your model came with Lion pre-installed then it is capable of using Internet Recovery. If it came with a late version of Snow Leopard it can be upgraded via a firmware update. You will find this in the link below.
Computers that can be upgraded to use OS X Internet Recovery
Be sure you backup your files to an external drive or second internal drive because the following procedure will remove everything from the hard drive.
Boot to the Internet Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND-OPTION- R keys until a globe appears on the screen. Wait patiently - 15-20 minutes - until the Recovery main menu appears.
Note: You will need an active Internet connection. I suggest using Ethernet
            if possible because it is three times faster than wireless.
Once the Utility Menu appears select Disk Utility and click on the Continue button. Now try removing the partition again. If you have the same error, then do the following:
From the screen's menubar select Terminal from the Utilities menu. Enter the following at the prompt:
     diskutil list
Press RETURN. You should see a display of your devices. Next enter:
     diskutil unmountDisk force /dev/disk0
Press RETURN. Now, if this works your internal drive should be unmounted. Return to Disk Utility and try the process of removing the partition.

Similar Messages

  • Partition Tab in Disk Utility is Greyed Out

    Basically I wanted to try out Mac OS X Yosemite, so I created a partition on my hard drive. Now, I am trying to remove this partition, because it is no longer needed, but Disk Utility is simply not allowing me to.
    I heard there may be a way to solve this using Terminal. Is that possible?
    Any answers and/or helpful comments is appreciated in advance. Thank you.

    And, this was from the Internet Recovery utilities window, right? OK, this next suggestion depends on which MBA model you have. Check the link below. If your model came with Lion pre-installed then it is capable of using Internet Recovery. If it came with a late version of Snow Leopard it can be upgraded via a firmware update. You will find this in the link below.
    Computers that can be upgraded to use OS X Internet Recovery
    Be sure you backup your files to an external drive or second internal drive because the following procedure will remove everything from the hard drive.
    Boot to the Internet Recovery HD:
    Restart the computer and after the chime press and hold down the COMMAND-OPTION- R keys until a globe appears on the screen. Wait patiently - 15-20 minutes - until the Recovery main menu appears.
    Note: You will need an active Internet connection. I suggest using Ethernet
                if possible because it is three times faster than wireless.
    Once the Utility Menu appears select Disk Utility and click on the Continue button. Now try removing the partition again. If you have the same error, then do the following:
    From the screen's menubar select Terminal from the Utilities menu. Enter the following at the prompt:
         diskutil list
    Press RETURN. You should see a display of your devices. Next enter:
         diskutil unmountDisk force /dev/disk0
    Press RETURN. Now, if this works your internal drive should be unmounted. Return to Disk Utility and try the process of removing the partition.

  • Hi, i have tryed to install os x leopard, (its a old imac) , disk utility is greyed out , my install dvd cant find any hdd to install on , my only way to format and configure is through terminal but dont know what commands to execute

    hi, i have tryed to install os x leopard, (its a old imac) , disk utility is greyed out , my install dvd cant find any hdd to install on , my only way to format and configure is through terminal but dont know what commands to execute...
    i tryed diffrent commands such as diskutil eraseDisk JHFS+ Disk1
    diskutil list , wont show up my harddrive , i now its functionally cause it shows up in disk utility with name and i can get info about it , but everything is greyed out can only switch between "erase , partition , recover , Raid ,....
    when i click the apple in the top left corner the whole menu is greyed out... what to do ?  help me please
    Sincerly AppleNoob92
    p.s i have no experience in apple imac's at all never used before, but im kinda windows nerd so computers i understand but this imac make my insane, cant seem to find any solutions anywhere on the WWW....

    Your HD may be crashed, so you probably should use the oringinal install discs to run Apple Hardware Test in extended mode. If error codes appear this confirms a hardware failure. In addition you cannnot repair the HD using Disk Utility from the startup disk, you have to use the origninal Install discs that shipped with the computer or the most up-to-date version of OS X on a disc that you have.

  • Disk Utility from local SSD and Recovery Partition disagree

    Hi,
    When I run Disk Repair from my 15" MBP's SSD, I get this:
    Verifying volume “Macintosh HD”Verifying storage systemChecking volumedisk0s2: Scan for Volume Headersdisk0s2: Scan for Disk LabelsLogical Volume Group B133BE17-6899-41E8-B2B2-342B022BB2CC on 1 devicedisk0s2: Scan for Metadata VolumeLogical Volume Group has a 29 MB Metadata Volume with double redundancyStart scanning metadata for a valid checkpointLoad and verify Segment HeadersLoad and verify Checkpoint PayloadLoad and verify Transaction SegmentLoad and verify Transaction SegmentIncorporate 1 newer non-checkpoint transactionLoad and verify Virtual Address TableLoad and verify Segment Usage TableLoad and verify Metadata SuperblockLoad and verify Logical Volumes B-TreesLogical Volume Group contains 1 Logical VolumeLoad and verify 77248876-460F-4A19-B657-5A4CBF702894Load and verify 60268981-5213-4655-8A8A-743044EF5359Load and verify Freespace SummaryLoad and verify Block AccountingLoad and verify Live Virtual AddressesNewest transaction commit checkpoint is validLoad and verify Segment CleaningThe volume B133BE17-6899-41E8-B2B2-342B022BB2CC appears to be OKStorage system check exit code is 0.Verifying file system.Using live mode.Performing live verification.Checking Journaled HFS Plus volume.Checking extents overflow file.Checking multi-linked files.Incorrect number of file hard linksChecking catalog hierarchy.Checking extended attributes file.Checking volume bitmap.Checking volume information.The volume Macintosh HD was found corrupt and needs to be repaired.File system check exit code is 8.Error: This disk needs to be repaired using the Recovery HD. Restart your computer, holding down the Command key and the R key until you see the Apple logo. When the OS X Utilities window appears, choose Disk Utility.
    Then, when I run Disk Repair from the Recovery Partition, it says the disk is completely fine.
    What should I do? Thanks very much!

    Exact same problem on 2011 MBA.
    - Noticed message after Time Machine backup failed.
    - Ran verify with the following results
    - restarted with command+R then ran verify and repair in recovery mode with success (all fine)
    - ran verify again, fails, again.
    Modal message:
    This disk needs to be repaired using the Recovery HD. Restart your computer, holding down the Command key and the R key until you see the Apple logo. When the OS X Utilities window appears, choose Disk Utility.
    Verify history:
    Verifying partition map for “APPLE SSD SM256E Media”Checking prerequisitesChecking the partition listChecking for an EFI system partitionChecking the EFI system partition’s sizeChecking the EFI system partition’s file systemChecking all HFS data partition loader spacesChecking booter partitionsChecking booter partition disk0s3Verifying file system.Checking Journaled HFS Plus volume.Checking extents overflow file.Checking catalog file.Checking multi-linked files.Checking catalog hierarchy.Checking extended attributes file.Checking volume bitmap.Checking volume information.The volume Recovery HD appears to be OK.File system check exit code is 0.Checking Core Storage Physical Volume partitionsVerifying storage systemChecking volumedisk0s2: Scan for Volume Headersdisk0s2: Scan for Disk LabelsLogical Volume Group 238CA2E7-7C17-4312-8A15-BF------ on 1 devicedisk0s2: Scan for Metadata VolumeLogical Volume Group has a 29 MB Metadata Volume with double redundancyStart scanning metadata for a valid checkpointLoad and verify Segment HeadersLoad and verify Checkpoint PayloadLoad and verify Transaction SegmentIncorporate 0 newer non-checkpoint transactionsLoad and verify Virtual Address TableLoad and verify Segment Usage TableLoad and verify Metadata SuperblockLoad and verify Logical Volumes B-TreesLogical Volume Group contains 1 Logical VolumeLoad and verify 6464BE20-9BFC-4291-A56F-8FCF1E09FA78Load and verify B6790A78-7D56-4264-9A62-D37D5F0ABAAALoad and verify Freespace SummaryLoad and verify Block AccountingLoad and verify Live Virtual AddressesNewest transaction commit checkpoint is validLoad and verify Segment CleaningThe volume 238CA2E7-7C17-4312-8A15-BF69A8----- appears to be OKStorage system check exit code is 0.The partition map appears to be OK
    Verifying volume “Firefly”Verifying storage systemChecking volumedisk0s2: Scan for Volume Headersdisk0s2: Scan for Disk LabelsLogical Volume Group 238CA2E7-7C17-4312-8A15-BF69A82AFA9B on 1 devicedisk0s2: Scan for Metadata VolumeLogical Volume Group has a 29 MB Metadata Volume with double redundancyStart scanning metadata for a valid checkpointLoad and verify Segment HeadersLoad and verify Checkpoint PayloadLoad and verify Transaction SegmentIncorporate 0 newer non-checkpoint transactionsLoad and verify Virtual Address TableLoad and verify Segment Usage TableLoad and verify Metadata SuperblockLoad and verify Logical Volumes B-TreesLogical Volume Group contains 1 Logical VolumeLoad and verify 6464BE20-9BFC-4291-A56F-8FCF1E09FA78Load and verify B6790A78-7D56-4264-9A62-D37D5F0ABAAALoad and verify Freespace SummaryLoad and verify Block AccountingLoad and verify Live Virtual AddressesNewest transaction commit checkpoint is validLoad and verify Segment CleaningThe volume 238CA2E7-7C17-4312-8A15-BF69A----- appears to be OKStorage system check exit code is 0.Verifying file system.Using live mode.Performing live verification.Checking Journaled HFS Plus volume.Incorrect block count for file 1768734(It should be 10022 instead of 51590)(It should be 5144 instead of 1298272)Incorrect number of file hard linksChecking catalog hierarchy.Invalid directory item count(It should be 44653 instead of 44654)Invalid directory item count(It should be 34 instead of 33)Checking extended attributes file.Volume bitmap needs minor repair for orphaned blocksChecking volume information.Invalid volume free block count(It should be 31229092 instead of 29894396)File system check exit code is 8.Error: This disk needs to be repaired using the Recovery HD. Restart your computer, holding down the Command key and the R key until you see the Apple logo. When the OS X Utilities window appears, choose Disk Utility.

  • Disk utility fails to resize portable drive partitions with error message "requested change in size is too small".

    I am using a 1TB WD studio passport portable drive with my 2011 MacBook Pro. I have the portable drive partitioned into 4 volumes: 355 GB, 320 GB, 320 GB, & 4 GB.  But Disk Utility won't allow me to split the third of those into 160 GB /160 GB.  All volumes verify as seeming "to be okay".  Seems if Disk Utility could create me a 4GB partition that 160 GB is plenty big enough, right?  Something's not right; Can you help me with this please?

    What is on those partitions and or the partition you want to split in two?
    If you don't have any data on partitions or if you can save it someplace else for the time being then why not just Re-Partition the whole drive into the sizes you now want.

  • Disk Utility - Solution for a Weird MediaKit Partition "too small" Error

    I found a very suggestive article, could be a silver bullet for this kind of problem.
    *http://ubuntuforums.org/showthread.php?t=760190*
    +*quote from SWedd*+
    +In my case, it was caused by the Apple_Bootstrap partition (created during Ubuntu install), of format unknown to OSX. This partition was positioned right after my Macintosh_HD partition. To enlarge my Macintosh_HD I needed to use diskutil to erase the Apple_Bootstrap partition to a blank "MS-DOS" partition. Then I could use Disk Utility to Delete the MS-DOS partition. After that I could resize my Macintosh_HD freely.+
    In my understanding, if you failed to increase the size of a certain partition, it might mean a partition just after that partition is corrupted or broken (whether or not it is corrupted, you can know it by using command "diskutil info ...").
    With command "diskutil eraseVolume ..." you can erase the partition in question, then with "diskutil mergePartitions ..." merge the partition you want to increase in size and the partition you just erased. Now you can increase the size without any error.
    Anyway, diskutil can do several things which Disk Utility can't do.
    To resort to diskutil is sure worthwhile.
    Message was edited by: Shigerello

    Welcome to the Apple forums and thanks for the information.
    Warning:
    The terminal command
    diskutil
    should be used with care, as with most terminal commands.
    A good rule to remember is "If you do not know what something will do, do not do it."
    For information on diskutil, in a terminal enter
    man diskutil

  • Partitioning 1TB with Disk Utility

    I have 1TB external drive which I want to partition, but I have some questions regarding format, size, compatibility with both Snow Leopard and Windows (eugh, but necessary). Can someone help me out? I have a few gaps.
    _*Main Questions*_
    _*Partition A: for TimeMachine*_
    Format: Should it be Mac OS Extended Journaled...? is that right?
    _*Partition B: for Bootcamp*_
    Format: I don't know. Should it be FAT? or Mac OS Extended?
    Size: I don't know? Can someone recommend?
    _*Partition C: Everything else (Media etc)*_
    Format: I don't know? I need this to be compatible with 10.6 and Windows.
    _*Other questions*_
    a) Do I need to Erase first, re format, then create partition?
    b) What is RAID?
    c) Do I need to change something in Options? There's Master Boot - GUID - Apple Partition Map,
    What do I choose?
    Help.

    Ninda wrote:
    I have 1TB external drive which I want to partition, but I have some questions regarding format, size, compatibility with both Snow Leopard and Windows (eugh, but necessary). Can someone help me out? I have a few gaps.
    _*Main Questions*_
    _*Partition A: for TimeMachine*_
    Format: Should it be Mac OS Extended Journaled...? is that right?
    Yes
    _*Partition B: for Bootcamp*_
    Format: I don't know. Should it be FAT? or Mac OS Extended?
    Size: I don't know? Can someone recommend?
    I would make a bootable clone of my internal disk volume on partition B. The clone will provide a fail safe mechanism for disaster recovery. If you decide to do so, then the partition should be GUID.
    As far as I know, you cannot run Windows from an external drive even if using Boot Camp. I would put Boot Camp/Windows on a partition of your internal drive. When you want to set up you Boot Camp partition, just follow the instructions of the Boot Camp Assistant. Do not format FAT under any conditions. You want to use NTFS.
    _*Partition C: Everything else (Media etc)*_
    Format: I don't know? I need this to be compatible with 10.6 and Windows.
    I would not go this route. You do not want to use FAT. The best approach is to install MacDrive (mediafour.com) on you Windows system. If you do so then the 3rd partition can be Mac OS X extended (journaled), and both you Windows and OS X machines will be able to read and write the partition.
    _*Other questions*_
    a) Do I need to Erase first, re format, then create partition?
    Using Disk Utility, create 1 partition with partition table GUID. After doing so, your partition should be formatted Mac OS X extended (journaled). If it isn't, then format (i.e., erase) it this way. Change your partition to 3 GUID. Selecting the sizes you want.
    b) What is RAID?
    Of no importance to you
    c) Do I need to change something in Options? There's Master Boot - GUID - Apple Partition Map,
    What do I choose?
    See above
    Help.

  • My ipod touch 3rd gen will not sync to pc.itunes file menu sync my ipod is greyed out

    my ipod touch 3rd gen will not sync to pc.itunes file menu sync my ipod is greyed out.and i cant sync or put any new songs.please help me.

    I've gotten the iPod to sync after restoring it and not changing ANY of the music sync settings.  I didn't even click "sync music", I just have it on manual and clicked autofill. 
    After it synced all of the music successfully, I tried to sync a playlist (my recently added), and it's gone bonkers again, it won't sync the playlist's music, or any new music now. 

  • IPod appears on Desktop - enable disk use checked, greyed-out

    Each of my daughters has a video iPod--
    The "white" one - about 11 months old, now appears on the desktop when connected. iTunes opens, but the choice "enable disk use" is greyed-out, i.e. I cannot un-check this, and each time the iPod icon appears on the desktop.
    The "black" iPod-- just a few days old, but essentially the same video iPod-- it does NOT appear on the desktop, and the "enable disk use" writing is NOT greyed-out, i.e. we could "check" this if we wanted.
    How to get the "white" iPod to no longer appear on the desktop? I have tried resetting it, but that doesn't seem to change anything.
    Also-- is there a reason why this appears on the desktop, and is that a limiting factor for any reason-- or a problem? Really just trying to understand this!
    Thanks for any comments.
    Steve
    Wednesday 30 May 2007

    If the iPod is set to sync manually, the enable disk use checkbox will always be on, as iTunes doesn't know when you will be done transferring content to the iPod and ready to unplug it. The iPod will appear on a Mac's desktop while iTunes is syncing it or waiting for you to transfer content to it, or when disk use is explicitly enabled and the iPod is plugged in to the computer.
    (21931)

  • Setting Disk Utility to lock out bad sectors

    Setting Disk Utility to lock out bad sectors
    When my Leopard DVD arrives I'm planning on doing a clean install to my internal HD. I would like to format the drive to lock out bad sectors but I can't seem to find a setting to do that in Disk Utility or anything about it in Help.

    Hi Peggy Lynn;
    To the best of my knowledge there is no way to lock out bad sectors.
    What you can do is erase the disk and under security tab have zeros written to the disk. When you do this if any bad sectors are found, they will be mapped out so that will no longer be used.
    Disk drive always have some extra sector which can be mapped in to replace any that might go bad. The disk drive can continue doing this until the sectors are all used up then you will have to replace it.
    Allan

  • HT4718 No 1.    I can not activate Filevault : FileVault can't be turned on for the disk "Macintosh HD". Some disk formats don't support the recovery partition required by encryption. To use encryption, reinstall this version of Mac OS X on a reformatted

    I have TWO PROBLEMS
    No 1.  I can not activate FileVault. It displyas as follows :
    FileVault can’t be turned on for the disk “Macintosh HD”.
    Some disk formats don’t support the recovery partition required by encryption. To use encryption, reinstall this version of Mac OS X on a reformatted disk.
    No 2. I can not activate Find My Mac service. It displays as follows :
    Find My Mac requires a recovery partition
    Some configurations, such as software or hardware RAID, do not support a recovery partition and can't be used with find my mac

    Restart holding down the option/alt key and see if you have a Recovery Volume.
    Recovery Partition – Recreate Without Reinstalling
    Recovery Partition – Recreate Without Reinstalling (Requires Installer)
    Recovery Drive – Restore Missing
    Recovery Disk Assistant

  • How do I undo BC Partition repair in disk utility?

    Here's the summary:
    8-core MacPro2,1 running 10.6.8, Paragon NTFS for Mac, Bootcamp Win7.
    4 internal HDD drives: two 1.5TBs for data, one 1TB for MacOS, one 1.5TB for Win7 bootcamp.
    I mostly use the Mac side for music production (but rarely), and the Win side for business and everything else. Scores and scores of Win apps installed over the years. [4 monitor system], well over 500K files on the drive.
    I just backed up the data from the two data-only drives, and made a bootable clone of the MacOS drive (SuperDuper). I have never successfully been able to clone the Win7 Bootcamp NTFS drive (even with Winclone back in 2009) because of volume sizes (or something). I decided to try again, from WITHIN Windows this time (all other attempts were from the Mac OS side).
    I bought, downloaded, and installed Acronis True image from within the Win7 bootcamp system. [I obviously did not know that it was gonna modify my MBR, and I had no idea at the time that the GPT and MBR areas were somehow 'mingled' on a bootcamp drive.]
    So, when I performed the Acronis-requested reboot (my default boot is into the Bootcamp/Win7 drive), it failed to boot and requested some Windows recovery media or something. I was concerned that anything i put in the DVD drive would sabotage my priceless (in retrospect) stable/optimized Win7 bootcamp system. So, i just hard-powered down the Mac and tried to restart.
    I did the Alt/option key, and i was presented with the Mac or Win drive icons. I selected Win, and then I got a different boot error message--'no MBR found'.
    But this time i realized that Acronis had stepped where it shouldn't have, and I figured the Mac side could fix the boot problem (maybe with bootcamp assistant or something).
    If i had stopped THERE, and searched the forums i could have found how to fix THAT problem--that has been answered tons of times…
    But, instead, i went to Disk Utility and asked it to repair my Bootcamp partition (I have Paragon NTFS and it has worked for years, and so I did not have a reason to doubt Disk Utility's ability to Repair an NTFS volume--not that i have tried it before, of course).
    Disk Utility repair ran for about 10-15 minutes and said it fixed about 10-20 things.
    The drive information (in the side bar and below) still had the BOOTCAMP partition, reported that it was NTFS, said that there was 308 GB still available of the 1.5TB drive, and that it contained 1.19TB 'used'. Looked normal to me.
    I closed Disk Utility and then opened a Finder window to see if DU left any 'artifacts' of its 'fixes' on the BOOTCAMP partition, and all the files were gone! Even though DU said it had 1.19TB 'used', all of my files are gone. [I rebooted also, to verify that it was not some 'delayed reporting' issue.]
    When I enable 'hidden files' to show, what I get on the Bootcamp partition are these three entries:
    .DS_Store (16KB), .fseventsd folder (with a 1KB UUID file inside it), and a .Trashes folder with zero KB.
    At this point, I panic and assume the position of despair. There is no 'undo' key for the D/U that I can find. I do an orderly shut down of the system, physically remove the Win7 BC drive, and make/verify a sector-by-sector clone of the drive (on a Win7 laptop, using Acronis--22 hours).
    In Win7 Disk Management, the GPT partition (on the original drive) shows up and the BOOTCAMP partition shows up--with the proper size--but windows does NOT recognize the partition as being NTFS. It reports it as being RAW and 'urges' me to format it (yeah, right…).
    So, I place the sector-by-sector duplicate back into the Mac, boot up (only the Mac OS is given as an option), and am ready to 'work on' recovering the Win7 BC partition (if possible).
    I am avoiding trying to fix the booting problem, because recovery of the 1.2TB of a working system is much more critical for me.
    The clone HDD reports the same in DU, except now the GPT partition shows up as greyed-out 'disk1s1', right above the "BOOTCAMP" partition in the sidebar. [I understand from researching this that disk1s1 is somehow related to the bootloader for BC?]
    I used the demo version of Data Rescue 3 to scan for recoverable files from the drive, but it doesn't even report the .files. (I am running the deep scan now, but will take about another 9 hours to complete that).
    Has anybody got any suggestions on how to reclaim this partition and its system?
    Here are a couple of other details from diagnostic tools:
    Model Name:    Mac Pro
      Model Identifier:    MacPro2,1
      Processor Name:    Quad-Core Intel Xeon
      Processor Speed:    3 GHz
      Number Of Processors:    2
      Total Number Of Cores:    8
      L2 Cache (per processor):    8 MB
      Memory:    13 GB
      Bus Speed:    1.33 GHz
      Boot ROM Version:    MP21.007F.B06
    newmac:~ gmmx2$ sudo gpt -r show disk1
           start        size  index  contents
               0           1         PMBR
               1           1         Pri GPT header
               2          32         Pri GPT table
              34      262144      1  GPT part - E3C9E316-0B5C-4DB8-817D-F92DF00215AE
          262178        2014        
          264192      409600      2  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
          673792  2929602560      3  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
      2930276352         783        
      2930277135          32         Sec GPT table
      2930277167           1         Sec GPT header
    newmac:~ gmmx2$ diskutil list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *1.0 TB     disk0
       1:                        EFI                         209.7 MB   disk0s1
       2:                  Apple_HFS Macintosh HD            999.9 GB   disk0s2
    /dev/disk1
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *1.5 TB     disk1
       1:         Microsoft Reserved                         134.2 MB   disk1s1
       2:                        EFI                         209.7 MB   disk1s2
       3:       Microsoft Basic Data BOOTCAMP               1.5 TB     disk1s3
    /dev/disk2
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *1.5 TB     disk2
       1:                        EFI                         209.7 MB   disk2s1
       2:                  Apple_HFS D3                      750.0 GB   disk2s2
       3:       Microsoft Basic Data DATA3                  749.9 GB   disk2s3
    /dev/disk3
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:     FDisk_partition_scheme                        *1.5 TB     disk3
       1:               Windows_NTFS SSDSUB                 1.5 TB     disk3s1
    [Disk 1 is obviously the BC one]
    newmac:~ gmmx2$ sudo fdisk /dev/disk1
    Password:
    Disk: /dev/disk1    geometry: -5415437/4/63 [-1364690128 sectors]
    Signature: 0xAA55
             Starting       Ending
    #: id  cyl  hd sec -  cyl  hd sec [     start -       size]
    1: EE    0   0   2 - 1023 254  63 [         1 - -1364690129] <Unknown ID>
    2: 00    0   0   0 -    0   0   0 [         0 -          0] unused     
    3: 00    0   0   0 -    0   0   0 [         0 -          0] unused     
    4: 00    0   0   0 -    0   0   0 [         0 -          0] unused     
    I cannot be the only one who has much such a catastrophic error, so I am hoping that there is something I have overlooked (being only a part-time Mac user) or there is some utility somewhere which can fix this--
    Or if you need more data, let me know...
    thank you for your time--gmm

    Additional information: I found the DU Repair log for that session, in case it helps:
    2013-01-28 04:31:00 -0700: Disk Utility started.
    2013-01-28 04:31:30 -0700: Verify and Repair volume “BOOTCAMP2013-01-28 04:31:30 -0700: Starting repair tool:
    2013-01-28 04:31:30 -0700: Verifying files...                                                            
    2013-01-28 04:31:57 -0700: Adjusting instance tags to prevent rollover on file 0x606f0.                  
    2013-01-28 04:31:57 -0700: Adjusting instance tags to prevent rollover on file 0x606f2.                  
    2013-01-28 04:31:57 -0700: Adjusting instance tags to prevent rollover on file 0x606f4.                  
    2013-01-28 04:32:01 -0700: Files verification completed.                                                 
    2013-01-28 04:32:01 -0700: Verifying meta files...                                                       
    2013-01-28 04:32:01 -0700: Meta files verification completed.                                            
    2013-01-28 04:32:01 -0700: Veryfing $AttrDef.                                                            
    2013-01-28 04:32:01 -0700: Veryfing $Boot.                                                               
    2013-01-28 04:32:01 -0700: Verifying $UpCase.                                                            
    2013-01-28 04:32:01 -0700: Correcting $UpCase data.                                                      
    2013-01-28 04:32:01 -0700: Verifying $LogFile.                                                           
    2013-01-28 04:32:01 -0700: Verifying $Volume.                                                            
    2013-01-28 04:32:02 -0700: Verifying files with EAs...                                                   
    2013-01-28 04:32:02 -0700: EAs verification completed.                                                   
    2013-01-28 04:32:02 -0700: Verifying folders...                                                          
    2013-01-28 04:41:54 -0700: Folders verification completed.                                               
    2013-01-28 04:41:54 -0700: Minor inconsistencies are detected on the volume.                             
    2013-01-28 04:41:54 -0700: Creating root directory                                                       
    2013-01-28 04:41:54 -0700: Verifying security descriptors...                                             
    2013-01-28 04:41:54 -0700: Clearing invalid security descriptor 0x25e                                    
    2013-01-28 04:41:54 -0700: Clearing invalid security descriptor 0x260                                    
    2013-01-28 04:41:54 -0700: Clearing invalid security descriptor 0x797                                    
    2013-01-28 04:41:54 -0700: Clearing invalid security descriptor 0x1538                                   
    2013-01-28 04:41:54 -0700: Deleting orphan $Secure::$SII entry 0x25e                                     
    2013-01-28 04:41:54 -0700: Deleting orphan $Secure::$SII entry 0x260                                     
    2013-01-28 04:41:54 -0700: Deleting orphan $Secure::$SII entry 0x797                                     
    2013-01-28 04:41:54 -0700: Deleting orphan $Secure::$SII entry 0x1538                                    
    2013-01-28 04:41:54 -0700: Deleting orphan $Secure::$SDH entry Id=0x797                                  
    2013-01-28 04:41:54 -0700: Deleting orphan $Secure::$SDH entry Id=0x25e                                  
    2013-01-28 04:41:55 -0700: Deleting orphan $Secure::$SDH entry Id=0x260                                  
    2013-01-28 04:41:55 -0700: Deleting orphan $Secure::$SDH entry Id=0x1538                                 
    2013-01-28 04:41:55 -0700: Verifying files security...                                                   
    2013-01-28 04:41:55 -0700: Record 0x97c contains invalid security Id (0x260)                             
    2013-01-28 04:41:55 -0700: Record 0x99b contains invalid security Id (0x260)                             
    2013-01-28 04:41:55 -0700: Record 0xb88 contains invalid security Id (0x260)                             
    2013-01-28 04:41:55 -0700: Record 0xb91 contains invalid security Id (0x260)                             
    2013-01-28 04:41:55 -0700: Record 0xb92 contains invalid security Id (0x260)                             
    2013-01-28 04:41:55 -0700: Record 0x5633 contains invalid security Id (0x260)                            
    2013-01-28 04:41:55 -0700: Record 0x5635 contains invalid security Id (0x260)                            
    2013-01-28 04:41:55 -0700: Record 0x5637 contains invalid security Id (0x260)                            
    2013-01-28 04:41:57 -0700: Record 0xe1d4 contains invalid security Id (0x25e)                            
    2013-01-28 04:41:57 -0700: Record 0xe1d5 contains invalid security Id (0x25e)                            
    2013-01-28 04:41:57 -0700: Record 0xe1d6 contains invalid security Id (0x260)                            
    2013-01-28 04:41:58 -0700: Record 0x111c9 contains invalid security Id (0x260)                           
    2013-01-28 04:41:58 -0700: Record 0x111ca contains invalid security Id (0x260)                           
    2013-01-28 04:41:58 -0700: Record 0x111cb contains invalid security Id (0x260)                           
    2013-01-28 04:41:58 -0700: Record 0x111dc contains invalid security Id (0x260)                           
    2013-01-28 04:41:58 -0700: Record 0x11285 contains invalid security Id (0x260)                           
    2013-01-28 04:41:58 -0700: Record 0x11297 contains invalid security Id (0x260)                           
    2013-01-28 04:41:58 -0700: Record 0x113c4 contains invalid security Id (0x260)                           
    2013-01-28 04:41:58 -0700: Record 0x113c5 contains invalid security Id (0x260)                           
    2013-01-28 04:41:58 -0700: Record 0x12528 contains invalid security Id (0x260)                           
    2013-01-28 04:42:00 -0700: Record 0x1cfe2 contains invalid security Id (0x260)                           
    2013-01-28 04:42:00 -0700: Record 0x1dce1 contains invalid security Id (0x260)                           
    2013-01-28 04:42:00 -0700: Record 0x1f6a8 contains invalid security Id (0x260)                           
    2013-01-28 04:42:00 -0700: Record 0x1f6a9 contains invalid security Id (0x260)                           
    2013-01-28 04:42:00 -0700: Record 0x1f6c4 contains invalid security Id (0x260)                           
    2013-01-28 04:42:00 -0700: Record 0x21d57 contains invalid security Id (0x797)                           
    2013-01-28 04:42:03 -0700: Record 0x3220d contains invalid security Id (0x260)                           
    2013-01-28 04:42:06 -0700: Record 0x4bc2a contains invalid security Id (0x260)                           
    2013-01-28 04:42:10 -0700: Record 0x64ff9 contains invalid security Id (0x1538)                          
    2013-01-28 04:42:11 -0700: Can't read $SDS                                                               
    2013-01-28 04:42:12 -0700: Security verification completed                                               
    2013-01-28 04:42:12 -0700: Verifying $MFT.                                                               
    2013-01-28 04:42:12 -0700: Verifying $MFTMirr.                                                           
    2013-01-28 04:42:12 -0700: Verifying $Bitmap.                                                            
    2013-01-28 04:42:18 -0700: Volume repair complete.
    2013-01-28 04:42:18 -0700: Updating boot support partitions for the volume as required.
    2013-01-28 04:42:18 -0700: Repair tool completed: 2013-01-28 04:42:18 -0700:
    2013-01-28 04:42:18 -0700:

  • Disk Utility says of USB Drive - "This partition can't be modified" "This disk is not writeable and cannot be partitioned"

    Several months ago I bought a 64GB PNY USB memory stick to transpord data quickly.
    It seemed to work fine.  I could format it as a Mac partition and use it.  I hardly ever need
    it so I just put it away.
    Today I wanted to use it to put a file on and take it to the Kinko's/FedEx to print, and I
    find I cannot mount it on any of my computers, iMac, MacMini or MacBookPro.
    In Disk Utility virtually everything is greyed out.
    Disk Utility says: "This partition can't be modified" "This disk is not writeable and cannot be partitioned"
    If I try to mount it, it says "This disk cannot be mounted"
    There is no physical read-only switch or setting on the disk that I can see and it is very small.
    I has a Mac OS installed on it, so I wonder if that is a problem?  I should be able to write over that
    or reformat it I would think.

    Thanks for these replies. 
    I've got regular time machine backups and just backed up some of my data by copying some key folders to an external drive.  I'm bit paranoid about backup integrity and would ideally like to do another full backup to a different drive using a system other than time machine, in the event that something goes wrong with the time machine backup.  Any recommendations on good and affordable backup software to do a backup of my TM backup?
    One other question: I seem to encounter problems like this pretty frequently.  I'd say once a year or so, my drive fails completely or gets near enough to failing that I have to wipe and restore.  (I've never had a TM backup fail to work, though the last go around there were some hiccups which has led to my backup paranoia.)  I've had this happen on multiple computers, so I'm becoming pretty convinced that the problem lies somewhere in my data.  Is it possible (even likely) that there's something in my data causing this recurring problem?  If so, is there anything I might be able to do to try and pinpoint and address this problem?  I'd love to go one year without having to wipe/restore my machine!
    For a while I thought I just had bad luck.  But I think this is like the 4th or 5th time this has happened in the past 4 years and every time, I'm restoring from a backup, so I come back with the same data.  It's the one constant since I've had 3 different machines over this same time period. 

  • Disk utility wont resize/add/delete a partition (HD is part of a raid)

    I have two SSD set in a raid 0 in my MBP 15" late 2011 (Mountain Lion 10.8.2)
    256gb Samsung
    120gb Vertex 3
    My Vertex 3 is partitioned into 2 parts
    1.  70gb set in raid 0 with another 70gb partition in the Samsung
    2.  50gb dedicated to Windows 7
    My Samsung is partitioned in to 2 parts
    1.  70gb set in raid 0 with the other 70gb partition in the Vertex 3
    2.  The rest of the space in this SSD is just for data storage.
    The reason why I did it this way is a long story since it deals with issues in the optical bay SATA speed limitations so that's a different topic.
    So here is my problem:
    I have two 70gb partitions set in raid 0 between the two SSD's, the 50gb partition that was in the Vertex 3 dedicated to Windows.  After a while I realized I dont use windows that much and wanted to erase that partition.  Erasing it was easy, but now with the 50gb space left over I try to use disk utiility to divide the 50gb partition into 2 parts and it wont let me.  The satus bar says "preparing to partition disk" for 30 minutes and it doesnt budge. 
    To make matters worse, I deleted that partition by clicking the minus sign on the lower right corner, and now that partition is completely greyed out.  When I try to press the plus sign to add in the remaining free space in my Vertex 3, it wont let me.  The satus bar says "preparing to partition disk" for 30 minutes again and it doesnt budge. 
    Does the 70gb raid partition in the Vertex 3 prevent disk utility from making further changes to the Vertex SSD?  I am pretty familiar with disk utility and know my way around it but I have my hands tied in this situation.  Please help!

    Things I've tried:
    1.  Booting from an extenral HD with Moutain Lion and trying to use DIsk Utility to make changes to the Vertex 3 partition, same thing occurs (it hangs for 30 minutes with no progress).
    2.  After I deleted the 50gb partition from the Vertex 3, it is now greyed out.  Now when I try to press the add sign in disk utility to add back that 50gb empty greyed out space to make it for free storage (choosing Mac OS Extended, journaled), SAME THING HAPPENS.
    It seems as though once I deleted that partition from the Vertex 3, that 50gb space is now totally unuseable!
    By the way, I dont have filevault activated if that info helps at all to diagnose it.

  • How to get rid of hidden partitions display in Disk Utility?

    Running Snow Leopard I used the Terminal (defaults write com.apple.DiskUtility DUDebugMenuEnabled 1) to enable the Disk Utility Debug Menu. I then turned on the Show Every Partition so I could see the hidden partitions (but grayed out) in the disk/volume list. I then turned off Show Every Partition and they became hidden again.  I disabled the Debug Menu using the Terminal (defaults write com.apple.DiskUtility DUDebugMenuEnabled 0). The Debug menu went away, but the hidden partitions still show up again after quitting and restarting DU. Rebooting computer doesn't help either.
    It appears that display of all partitions is permanent. Does anyone have ideas on what to do to get back to the default display?

    I stumbled on the answer. When I just quit Disk Utility the hidden partitions come back on restarting DU. If I select Close from the File menu, the display of the hidden partitions goes away and doesn't come back after quitting and restarting DU.

Maybe you are looking for