Disk Utility error "Mediakit reports partition map too small. 3TB

So I have a Mac Pro with a 3TB inside, but Snow Leopard won't recognize the whole 3TB. I can format it, but it only allows 801.23 GB. The remaining space is left as Free Space. When I try to resize the Volume, I get this:
I get this error: " Partition failed with an error." MediaKit reports partition (map) too small.
Can someone help me find a way to utilize the 3TB as it was intended to?
My setup:
MacPro1,1
10.6.8
ST3000DM001-1CH166:
  Capacity:          3 TB (3,000,592,982,016 bytes)
  Model:          ST3000DM001-1CH166 
Removable Media:          No
  Detachable Drive:          No
  BSD Name:          disk0
  Rotational Rate:          7200
  Medium Type:          Rotational
  Bay Name:          Bay 1
  Partition Map Type:          GPT (GUID Partition Table)
  S.M.A.R.T. status:          Verified
  Volumes:
  Capacity:          209.7 MB (209,715,200 bytes)
  Writable:          Yes
  BSD Name:          disk0s1
BK:
  Capacity:          801.23 GB (801,225,752,576 bytes)
  Available:          737.7 GB (737,702,121,472 bytes)
  Writable:          Yes
  File System:          Journaled HFS+
  BSD Name:          disk0s2
  Mount Point:          /

Anyways, i've made it work. My process was this:
Problem:
1. I put MacPro into Target Disk Mode to mount to my 2011 MacBook Pro. Disk Utility on MBP would only see 800GB.
Solution:
2. Booted the SL CD on the MacPro and ran Disk Utility from there. In the partitions tab, I chose 1 partition, and hit apply.
3. "could not unmount disk."
4. So I tried to partition it again, and it worked this time. 3TB Available.
5. I then booted the MacPro using an external HD with OSX on it to run CarbonCopyCloner to reimage my backup.
I hope this helps anyone else with the same problem.

Similar Messages

  • Disk Utility gives error "Partition failed with the error:  MediaKit reports partition (map) too small" when trying to repartition

    I recently un partitioned my mac book pro with bootcamp in order to gain more space for my mac side.  Now it will neither increse the space on the mac side nor will it re-partition again.  What should I do?

    Hi Rachel,
    Your best bet would be to clone uour present OSX Install to an external Drive, Boot from that & erse the Internal drive, clone back to the Internal drive.

  • Install error : disk cannot be used to start up your computer [or] MediaKit reports partition (Map) too small

    Greetings,
    I am aware that this problem has been discussed, but in long and vague discussions that I had to sift deeply to find an answer. Therefore I am posting a clear message, as this problem can be very troublesome for someone who just received a Mac OS installation disk and cannot install it.
    Situation : you cannot install/update your new system because the installer does not consider your volume.
    Error message : this disk cannot be used to start up your computer.
    Version française : Ce disque ne peut pas être configuré pour démarrer votre ordinateur.
    Also discussed below error: "MediaKit reports partition (Map) too small"
    Note : although this occurred with a Snow Leopard (10.6) install DVD, it can alo occur with Lion (10.7) according to discussions on Apple web site.
    IF YOUR CONDITIONS ARE AS FOLLOWS :
    - You are using an official Apple installation DVD of Mac OS 10.6 (Snow Leopard) [or 10.7 Lion] or an official download/upgrade of those systems.
    - Your main Mac partition scheme is in GUID as it should be (check with Disk Utility). That partition contains a Mac system that can start-up.
    - Your volume format is: Mac OS Extended (journaled) [the format should not be Case Sensitive.]
    - You have the hardware requirements to install Mac OS 10.6 (Intel processor; internal or external DVD drive or a linked DVD drive; 1 GB of RAM; a screen controlled by your computer graphics card; at least 5 GB space on the hard disk or 7 GB if you install all components).
    - Using Disk Utility, you of course tried the disk Repair Tool and the Repair Permissions tool.
    - Your hard disk does not have a file called Backups.backupdb (if it does, this means Time Machine has once used this hard disk for its back-ups). Anyhow, if it were the case, the installation would give a different error message (with the word TimeMachine). This file may block the installation: Apple Support suggest to place it in the garbage, *without* deleting it, and placing it back on the disk later. Mind you, if you do not use this hard disk as such to save your Time Machine back-ups, you can simply delete this file.
    HOW TO FIX :
    1. Boot with the 10.6 install DVD (Tip: you can either select Mac 10.6 as the boot DVD in your Start-up Preferences or simply press down c during the start-up).
    2. Above the install screen, you have a Utilities tab from where you can run Disk Utility. Select your hard disk and select the Partition tab. Resize the primary Mac partition (don't add a new one) by decreasing it by about 5 GB.
    It will look like this http://i.imgur.com/jHTbr.jpg
    ( That image shows only one partition, but the same principle applies even if you have two or more partitions on your disk.)
    Also see the official Apple how to: http://support.apple.com/kb/TS3926
    Version française: http://support.apple.com/kb/TS3926?viewlocale=fr_FR
    3. Commit the change by hitting "Apply"
    3.b. If you get the error "MediaKit reports partition (Map) too small", this is a rare error where the partition that follows (for example Bootcamp) is slightly overlapping your main Mac partition. You will need to reduce that other following partition. Once you have reduced the other partition, you will probably need to return to step 2 and 3 and try again.
    [ For example, in my case, I had resized my Bootcamp with CampTune software and it would seem that the file system ended-up somehow larger than the actual partition container. I simply asked CampTune to reduce the partition a bit (barely 2 GB) and that fixed it.]
    4. Reboot, again into the 10.6 install DVD.
    5. You can then install 10.6.
    6. Once 10.6 is installed, use the Disk Utility on the desktop (you can boot into the primary HD at this point) to resize the primary partition back to its original or maximum size.
    SOURCE (main fix): http://forums.macrumors.com/showthread.php?t=774410 [and] http://support.apple.com/kb/TS3926
    SOURCE (explaination for MediaKit error): some Apple discussion post.
    nb: in my case, it was on a MacBook Pro (late 2008).

    GasMan4932 wrote:
    When I click on the icon for this drive, the warning message below states "Mac OS X cannot be installed on 'iMac HD', because this disk cannot be used to start up your computer." Obviously that's not true, since that's where the OS is installed.
    How did you partition this drive, if you did that? Does it contain start up or utility partitions for any other OS (for instance Linux)? There have been reports that the "cannot be used to start up your computer" message will appear if a third party utility was used to create a 'triple boot' system or such, apparently because SL is picky about the format GUID partition scheme table info & how partitions are allocated space on the drive by other formatting/partition methods.
    For some users with these partitions, the fix has been as simple as "tickling" (slightly changing) the partition size of some partition with Disk Utility, which apparently updates the GUID partition scheme table info so that the SL installer accepts it as safe to use with SL.( In this sense, the message may be trying to say the installer thinks the disk can't be used to reliably start up your computer with SL, not in general.)
    See the discussions topic Cannot install Snow Leopard over 10.5.8 for more about this.

  • MediaKit reports partition (map) too small

    I recently needed to upgrade my 320GB Hard Drive, in doing so I used a stand alone HDD cloner to copy my data to my new 750GB drive. Now, all seemed well and good until launching my computer after the switch, I still had a 320GB hard drive according to Mac OS X. I later figured it was just a partition of my 750 disk that needed to be expanded.
    Trying to expand my partition to utilize the full 750GBs of my hard drive leaves me with this error message:
    I don't know what to do, I've verified and repaired disk permissions and the disk itself. Does anyone have a solution for this? 

    Disk Utility is not very adventurous about taking over a partition table created by other programs. That is probably a good thing, because one false move could trash your entire drive.
    You should have at least one full backup of your User data before proceeding. (The system can be re-installed form DVDs in  an hour or so.) Sometimes Bad Stuff happens.
    As I see it, there are two paths:
    1) go back to the utility that did the cloning, and see if it can adjust the partition table to add another Volume.
    2) Erase the drive and re-partition with Disk Utility. This erases all your data, which you will then have to restore from your backups.
    The second approach sounds draconian, but if/when you upgrade to 10.7, Disk Utility wants to create an additional "hidden" partition for System Recovery. If you do not get your partition table into a form Disk Utility likes now, you WILL have to do it later to upgrade.

  • MediaKit Reports Partition {Map} To Small

    At the moment I have a partition on my hard drive which has a size of 249.99 gb
    the toal size of the hrad drive is 500gb
    Two issues are nedded help with:
    When I drog the the drive in disk utilities from 249 .99 to the full extebt of 500gb
    click on the partition without erasing any data I get the error
    MediaKit reports partition {map} to small
    If I go into a terminal and type df I get this:
    Filesystem 512-blocks Used Available Capacity Mounted on
    /dev/disk0s2 488253464 480241864 7499600 99% /
    devfs 357 357 0 100% /dev
    map -hosts 0 0 0 100% /net
    map auto_home 0 0 0 100% /home
    /dev/disk1s0 776 776 0 100% /Volumes/Bluebirds
    which I do not understand as accoring to the disk utility there is i untitled disk 249.99gb is a blue colour below that it is gray.
    what i do is to drag the unitiled 1 so it fills the whole box now the first half is blue the second halfis white . I click on apply and partition but get the Mediakit message.
    What I do not understand is why the ds in the terminal thinks I have used all the space - very strange
    thanks for any feedback
    Message was edited by: symm108

    I have Solved my problem.
    I booted with a Linux Live CD (Backtrack 4.R1) run GParted and found a little invisible partition, then I deleted it, and reboot into MAC again and now I could use the full disk.

  • Hello, I am trying to upgrade to yosemite, but I get the "disk cannot be used to startup your computer" error. Resizing the partition does not work, I get the error "MediaKit reports no such partition" probably because I installed linux in dual boot

    Hello, I am trying to upgrade my macbook pro to yosemite, but I get the "disk cannot be used to startup your computer" error.
    Resizing the partition does not work for me and I get the error "MediaKit reports no such partition" probably because I installed linux in dual boot and the disk manager is lost.
    Anyway to tell the yosemite installer that it should not pay attention whether the disk is bootable or not ?
    If I am doomed, any way to delete the installer and downloaded OS from my hard drive ?
    Thanks for your help

    As usual, the Linux installer wrecked the partition table. You would have to boot from your OS X installation disc and repartition. Doing so will of course remove all data from the drive, so you must back up first if you haven't already done so.

  • Disk Utility Error: The underlying task reported failure on exit 1

        #!/bin/bash
          # Author : Bill Hernandez
        # Location : Plano, Texas
        # Updated : Saturday, June 6, 2009 (1:48 PM)
        # script name : setdisk_ownerenabled
        # make sure to set permissions to execute
        <hr>
        # Description :
        <hr>
        # I've noticed that sometimes when using disk utility I cannot repair permissions, or I might get :
        # ERROR: The underlying task reported failure on exit 1
        # This shell script seems to have solved the problem.
        # It worked very well for me,
        # IF YOU USE THIS SCRIPT, IT IS AT YOUR OWN RISK...
        # DO NOT USE IT UNLESS YOU UNDERSTAND WHAT IT DOES
        # After running it, it is best to restart before using Disk Utility again
        <hr>
        # Details :
        <hr>
        # After partitioning a disk using "Disk Utility", and then begin using it, at some point I would get
        # an arror message when trying to save to one of the partitions, yet when I looked at the permissions
        # everything looked fine. I would then try to use Disk Utility to repair permissions and end up with a
        # cryptic error that pretty much told me nothing.
        # I noticed that while in Disk Utility, if I selected a partition the lower LH corner of the dialog
        # showed : Owners Enabled : No
        # I tried selecting the partitions at the Desktop and doing a (CMD-I) and at the very bottom of each
        # info dialog there was a checkbox :
        # [ ] ignore ownership of this volume
        # which I would check, even after logging in as root, and I couldn't seem to get a consistent way
        # to get rid of the permissions dialog failure, so I found the vsdbutil command which can be used
        # as follows to get partition, or disk info :
        # $ vsdbutil -c /Volumes/driveor_partitionname
        # ----> Permissions on '/Volumes/driveor_partitionname' are enabled.
        # if it is not enabled you can enable the disk or partition using :
        # $ vsdbutil -a /Volumes/driveor_partitionname
        # It will set "Owners Enabled : Yes"
        # This below script loops through the mounted disks, partitions, etc. and gives you information.
        # You can leave the three flags below all set to TRUE, or selectively use what you want and change
        # the rest to false...
        <hr>
        # CHOOSE {"TRUE", "FALSE"}
        <hr>
        getvolumestatus="TRUE"         # get "Owners Enabled : (Yes|No)" status
        setvolumestatus="TRUE"         # set "Owners Enabled : Yes"
        list_volumes="TRUE"                   # show volume names
        <hr>
        # DO NOT CHANGE ANYTHING BELOW HERE
        <hr>
        if [ $getvolumestatus == "TRUE" ]; then
         echo '============================='
         echo '$getvolumestatus'
         echo '============================='
         # get "Owners Enabled : (Yes|No)" status
         for i in $( df -l | sort -u | awk '{print $6}' | grep '/' ); do
         vsdbutil -c $i
         done
        fi
        <hr>
        if [ $setvolumestatus == "TRUE" ]; then
         echo '============================='
         echo '$setvolumestatus'
         echo '============================='
         sudo echo -n
         # set "Owners Enabled : Yes"
         for i in $( df -l | sort -u | awk '{print $6}' | grep '/' ); do
         sudo vsdbutil -a "$i"
         echo "setting Owners Enabled : Yes for ---> $i"
         done
        fi
        <hr>
        if [ $list_volumes == "TRUE" ]; then
         echo '============================='
         echo '$list_volumes'
         echo '============================='
         for i in $( df -l | sort -u | awk '{print $6}' | grep '/' ); do
         echo $i
         done
        fi
        <hr>
        

    As it turns out, this didn't completely solve the problem, it solved part of the problem.
    Here is a summary to the root cause of the problem.
    SUCCESS...
    Problem Summary : The system crashed and would hangup during boot, tried many things, until I eventually erased the disk and started over again.
    iMacG5 24 GHZ Intel with One internal disk partitioned into 3 logical drives
    Cub_1 OS X 10.5.7
    Cub_2 OS X 10.5.7 (Carbon Copy Cloner backup of Cub_1)
    Cub_3 OS X Server 10.5.7 (standard os x server setup)
    At some point after setting up standard preferences, OS X Server crashed.
    When I tried to restart, the machine would hang up during boot.
    Finally after several attempts, ran Disk Utility from install dvd and repaired Cub_3
    When I tried to run "Repair Permissions" on Cub_3 from install dvd, I got an error
    Disk Utility Error: The underlying task reported failure on exit 1.
    Rebooted, and started in single user mode (CMD-S) during boot until I saw the unix commands on the screen
    RAN : root # fsck -fy
    Then I began seeing the same command filling the screen :
    posix_spawnp("/usr/sbin/mDNSResponder") could not find file or directory
    Called Enterprise Support and spoke to Frank Alcorn, he said this was most likely a permissions problem and asked me to try repairing permissions from the install dvd. I told him about the error, but nevertheless I tried it again and got the same Disk Utility Error: The underlying task reported failure on exit 1..
    He asked me to try booting into single user mode again, and to try
    root # chmod 775 /
    root # reboot
    During the reboot process the machine got hung up again, and could not get the single user mode to work at all.
    Frank said the command needed to be :
    root # chmod 1775 /
    Frank asked me if I had changed anything in file sharing, and I told him I had. He asked me what I had shared, and I said the entire drive Cub_3. He asked me what I had done for permissions, if I had denied permissions to anyone. I told him that I had set myself up as the only user that could have access to it, and when he said that's where the problem was the lightbulb went off, and it made sense.
    Shortly after I set the sharing preferences is when the server crashed. It all makes sense now...
    Frank said not to share the entire disk, only portions (share points) of it. I had done this in Panther Server, and Tiger Server and it worked fine, but apparently Leopard Server works a little differently, maybe more secure.
    It seems to me that if sharing the entire disk, which is what I needed would cause such a problem there should have been some sort of warning from the operating system, but there wasn't. I had run into this problem several times over the past three weeks since I had started working with Leopard Server, but in each case I ended up re-installing OS X Server and starting over again.
    I told him I would try to reboot from the OS X partition (Cub_1) and try it from there.
    He asked me to let him know if it worked, and I said I would...
    Problem FIX :
    I booted back into the partition containing OS X (Cub_1) and did the following via the Terminal.
    $ su - root
    $ chmod 1775 /
    $ reboot
    During the reboot process I held down the (OPTION) key, and selected Cub_3 (the os x server partition) and sure enough after a few minutes of holding my breath the login window magically appeared. So I logged in, and did not have to re-install the server. Hallellujah....
    This solved the boot hang problem. It is great to finally have an answer. In retrospect it makes sense, but that's why its hindsight...
    The reason for sharing the entire disk in my mind was that since I was the only user on the system, it was easier to have one disk mounted on my workstation rather than several folders. It made sense to me, it still does. I don't need a bunch of folders, just one disk is easier...

  • Can't install OSX Mountain Lion, on the disk selection screen i cant select the Macintosh HD to install OSX giving a message (This disk cannot be used to start up your computer).only have one disk to select and my partition map scheme is GUID partition

    just bough OSX Mountain Lion, my laptop operating with v10.6.8.  Can't install OSX Mountain Lion, on the disk selection screen i cant select the Macintosh HD to install OSX giving a message (This disk cannot be used to start up your computer).only have one disk to select and my partition map scheme is GUID partition table. 24.44gb disk available.

    Verify your computer can run Mountain Lion:
    Upgrading to Mountain Lion
    To upgrade to Mountain Lion you must have Snow Leopard 10.6.8 or Lion installed. Purchase and download Mountain Lion from the App Store. Sign in using your Apple ID. Mountain Lion is $19.99 plus tax. The file is quite large, over 4 GBs, so allow some time to download. It would be preferable to use Ethernet because it is nearly four times faster than wireless.
         OS X Mountain Lion - System Requirements
           Macs that can be upgraded to OS X Mountain Lion
             1. iMac (Mid 2007 or newer) - Model Identifier 7,1 or later
             2. MacBook (Late 2008 Aluminum, or Early 2009 or newer) - Model Identifier 5,1 or later
             3. MacBook Pro (Mid/Late 2007 or newer) - Model Identifier 3,1 or later
             4. MacBook Air (Late 2008 or newer) - Model Identifier 2,1 or later
             5. Mac mini (Early 2009 or newer) - Model Identifier 3,1 or later
             6. Mac Pro (Early 2008 or newer) - Model Identifier 3,1 or later
             7. Xserve (Early 2009) - Model Identifier 3,1 or later
    To find the model identifier open System Profiler in the Utilities folder. It's displayed in the panel on the right.
    Open Disk Utility and verify the drive is partitioned using GUID and formatted Mac OS Extended, Journaled. If it is then do this:
    Repair the Hard Drive and Permissions
    Boot from your Snow Leopard 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 Utilities menu. 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 are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
    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.
    Now try installing Mountain Lion.

  • Disk Utility and Time machine partition

    Ran a Disk Utility check on my Time Machine volume (internal drive - and yes I stopped Time Machine first).
    It Came back with error messages something like this:
    Verifying volume “Leopard_2”
    Checking Journaled HFS Plus volume.
    Checking Extents Overflow file.
    Checking Catalog file.
    Checking multi-linked files.
    Incorrect number of file hard links
    Checking Catalog hierarchy.
    Checking Extended Attributes file.
    Checking multi-linked directories.
    Incorrect owner flags for directory hard link (id = 998962)
    (It should be 0x2 instead of 0x0)
    Incorrect owner flags for directory hard link (id = 998964)
    (It should be 0x2 instead of 0x0)
    Incorrect owner flags for directory hard link (id = 998966)
    (It should be 0x2 instead of 0x0)
    Incorrect owner flags for directory hard link (id = 998970)
    (It should be 0x2 instead of 0x0)
    Incorrect owner flags for directory hard link (id = 998972)
    (It should be 0x2 instead of 0x0)
    Incorrect owner flags for directory hard link (id = 998974)
    (It should be 0x2 instead of 0x0)
    Incorrect owner flags for directory hard link (id = 998976)
    (It should be 0x2 instead of 0x0)
    Incorrect owner flags for directory hard link (id = 998978)
    (It should be 0x2 instead of 0x0)
    Incorrect owner flags for directory hard link (id = 998980)
    (It should be 0x2 instead of 0x0)
    Incorrect owner flags for directory hard link (id = 998982)
    (It should be 0x2 instead of 0x0)
    Incorrect owner flags for directory hard link (id = 998986)
    (It should be 0x2 instead of 0x0)
    Incorrect owner flags for directory hard link (id = 998988)
    (It should be 0x2 instead of 0x0)
    { Edited for Brevity }
    Stopped by user
    Well, the first time I Used repair mode and it wrecked my backup. I had to reformat the partition. Even disk warrior couldn't undo the directory damage Leopard's disk utility reeked on my partition. The irony of it is, I doubt very seriously that anything was wrong with the backup partition before Disk Utility assaulted it.
    I ran time machine again and checked (verified this time) the partition after it completed and Leopard's DU reported the same errors as before.
    Then I checked the backup partition with Tiger's DU:
    Verifying volume “Leopard_2”
    Checking 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 Leopard_2 appears to be OK.
    Mounting Disk
    1 HFS volume checked
    Volume passed verification
    Tiger found no problems.
    I also checked the partition with Disk Warrior and got a good report.
    If I'm not the only one that has this problem then it looks like Leopards DU is an accident waiting to happen when someone uses it to "repair" their Time Machine partition.
    Has anyone else experienced this?

    FYI, I have a TM partition sharing an internal HD with a FAT32 formatted partition. Here's my Verify output. I did not stop TM while running Verify
    Verifying volume “MacTimeMachine”
    Checking Journaled HFS Plus volume.
    Checking Extents Overflow file.
    Checking Catalog file.
    Checking multi-linked files.
    Checking Catalog hierarchy.
    Checking Extended Attributes file.
    Checking multi-linked directories.
    Checking volume bitmap.
    Checking volume information.
    The volume MacTimeMachine appears to be OK.

  • I tried partitioning my HD to install linux, the installion was not successful and now I can't boot my mac, I tried internet recovery, it was not helpfull as the disk utility cannot delete the partition I created.

    I tried partitioning my HD to install linux, the installion was not successful and now I can't boot my mac, I tried internet recovery, it was not helpfull as the disk utility cannot delete the partition I created. It was only showing me an error message "EFI files are missing", I realized that it is trying to boot from the new partition I created for the installation of the linux I intended to do.

    It sounds like you may have multiple problems, but none of them are likely to be caused by malware.
    First, the internet-related issues may be related to adware or a network compromise. I tend to lean more towards the latter, based on your description of the problem. See:
    http://www.adwaremedic.com/kb/baddns.php
    http://www.adwaremedic.com/kb/hackedrouter.php
    If investigation shows that this is not a network-specific issue, then it's probably adware. See my Adware Removal Guide for help finding and removing it. Note that you mention AdBlock as if it should have prevented this, but it's important to understand that ad blockers do not protect you against adware in any way. Neither would any kind of anti-virus software, which often doesn't detect adware.
    As for the other issues, it sounds like you've got some serious corruption. I would be inclined to say it sounds like a failing drive, except it sounds like you just got it replaced. How did you get all your files back after the new drive was installed?
    (Fair disclosure: I may receive compensation from links to my sites, TheSafeMac.com and AdwareMedic.com, in the form of buttons allowing for donations. Donations are not required to use my site or software.)

  • Disk Utility error msg:  Filesystem verify or repair failed!!!

    Ok so after erasing my partitioned HD I wanted to use the rest of my HD on my start up HD, So I pulled the expander in the partition window to resize the volume of the HD. Then I clicked apply to resize the HD and ended up with a Partition Failed message that stated
    Partition failed with the error:
    Filesystem verify or repair failed.
    What do I do from here to get my current HD at full capacity?
    The current size is 19.9 GB and it should be at 60 GB.

    Ok, so I had a partitioned hard drive, and I wanted to expand the start up drive and delete the unnecessary partition. So in disk utility I clicked on partition and deleted the partition I didn't want.
    Then I used the expander thing in the bottom corner of the start up hard drive box and clicked apply to enlarge it, but filesystem verify or repair failed message appeared.

  • I accidently used Disk Utility to fix a partition. I cant boot in with any USB drive. Help.

    I accidentally used Disk Utility to fix a partition.  It erased it.  I desperately need to restore it.
    I have an imac without a cdrom.  How do I create a bootable usb with testdisk as for some bizarre reason it seems impossible to create a bootable usb drive for osx.  I tried GParted and the ultimate boot disk that both have test disk.
    I am stumped.  Why can't I boot into my imac with a usb?  I have a mac air that I just cant seem to create a usb drive with testdrive thats bootable.  I even tried rEFit but no luck. 
    Anyone have an idea? How do I fix my system ?

    I have an imac OSX 10.8.
    I tried creating a usb drive of testdisk on my mac air so that I could use it to boot into the iMAC and restore the partition table. 
    I created it using:
    hdiutil convert -format UDRW -o target.img ~/Desktop/ubcd530.iso
    dd if=./target.img.dmg of=/dev/rdisk1 bs=1m
    It did not work.  It would not boot.  I also tried Gnome Partition tool and that did not boot either.  I need my old system as it has important data
    Any tips? Thanks!

  • After i bought mac os x lion from web then download , after that to install but when they ask me to choose disk to install i can not choose, it say this disk does not use the GUID partiton table scheme. use disk utility to change the partition scheme. but

    after i bought mac os x lion from web then download , after that to install but when they ask me to choose disk to install i can not choose, it say this disk does not use the GUID partiton table scheme. use disk utility to change the partition scheme. but

    after i bought mac os x lion from web then download , after that to install but when they ask me to choose disk to install i can not choose, it say this disk does not use the GUID partiton table scheme. use disk utility to change the partition scheme. but

  • DISK UTILITY Error: Partition map repair failed...

    Hi all,
    I purchased a new SEAGATE BACKUP PLUS 3T USB3.0 drive - and formatted GUID 1 partition - then ran repair disk and it showed with = "Error: Partition map repair failed while adjusting structures to fit current whole disk size"
    And I also tried 4 partitions but no help
    And I also tried formatting same on older 10.6 mac with no errors - then came back to 10.8 and error shows there...
    Can some folks please try this on there own setups to see how widespread this is...
    Criteria...
    1 - ML 10.8.2
    2 - Large external drive 2T or greater
    Q: Has anyone experienced this and has a possible solution?
    Thanks

    HI all,
    This issue has been in discussion (actively) since last August here:
    https://discussions.apple.com/thread/4218970?start=0&tstart=0
    After months and months of new reports, it's pretty clear that this is an Apple Mountain Lion problem and one that Apple needs to address.  As one frustrated user noted :
    >>There is no consistent solution for a user.  Apple has to supply it.  All you can do is submit a bug report to
    >> http://www.apple.com/feedback    
    Please, if you are encountering this problem you will save yourself a lot of wasted time and energy simply by joining me and others in asking Apple to fix this problem: Make a bug report.
    Thanks!

  • Mediakit reports that the partition is too small

    Hi everyone,
    I have a NAS (QNAP TS-239ProII+) connected to my network. I have created a iscsi target and a LUN attached to that target (let's say 1GB - it's a test).
    That target is mounted on the iMac using GlobalSAN. So, that drive is seen like a local harddrive. The first time I try to access it, macosx reports that the volume need to be initialize --> the disk utility launches and I can format the disk --> everything is fine.
    Now, I decide to modifiy the LUN's size from 1GB to 2GB (it's done through the admin console of the NAS) --> the imac stills view a 1GB size HD (which is normal). So I launch Disk Utility in order to resize the partition of the target iscsi : DU show me that the drive has 2 GB drive and there is one partition of 1GB.
    When I try the modify the partition size (the idea is to avoid formatting the existing partition of course ), I get a message "Partition failed : Mediakit reports that the partition (card) is too small"
    Why? How to solve this issue?
    Thank and regards,
    Fabrice

    hi montadorwatt, when you go into the firefox menu, you'll find a zoom bar at the top which allows you to change the size of a website.

Maybe you are looking for

  • Connection error when trying to start a i chat video

    this is the message it posted when it said error: Date/Time: 2008-07-06 13:31:32.223 -0400 OS Version: 10.5.4 (Build 9E17) Report Version: 4 iChat Connection Log: 2008-07-06 13:30:47 -0400: AVChat started with ID 3868979663. 2008-07-06 13:30:47 -0400

  • Problem in answerMachine  pls help me

    Hi All my problem is exactly when u detect dtmf char can not stop playying wav file the code is below import java.net.*; import javax.telephony.*; import javax.telephony.events.*; import javax.telephony.media.*; import javax.telephony.media.events.*;

  • File location dialog has started defaulting to specific server folder

    A problem has recently arisen on one of our G5's with Tiger. It occurs during the actions of saving files, or navigating within apps to place, import or export files. When the primary work folder on our server is selected as the destination, or path

  • Search for a program

    Hello How can i check whether a specified application is installed in a machine. If yes how can i get the path (I use windows as operating syatem) e.g; I want to get the installation path of windows media player Thanks in advance

  • Can we connect 4R/3 and 4BI Systems to single Portal?

    Hi, Can we Connect 4 R/3 Servers and 4 Bi Servers to Single Portal and I Want Retrieve data from these Servers.is it Possible .If so Reply ASAP. Thanks and Regards Kiran