Disk Utility: MediaKit reports no such partition

What is up with my disk?
On my brand new mac mini, I played around with resizing partitions in Disk Utility, it worked fine, and I eventually returned it to the original single-partition state.
Then, I ran boot camp, and told it to create a 10 GB partition.
Then, I installed Linux (64-bit Ubuntu) -- from the Linux installer I deleted the windows partition, and a zero-size partition before it, and put Linux swap and ext3 partitions in that space.
Now, from the mac side, if I try to shrink the boot partition again, I get the error "MediaKit reports no such partition".
Help? One potentially related anomaly is that Disk Utility shows my Linux ext3 partition format as "MS-DOS (FAT)" but the "fdisk" command correctly lists it as "Linux files*"
Another disturbing thing is that if I type "sudo pdisk" on the Macintosh command line, and give the 'L' command to list partitions on all disks, pdisk exits with the error "Floating point exception"
Here's the log from Disk Utility:
2007-11-04 00:09:19 -0400: Disk Utility started.
2007-11-04 00:09:40 -0400: Preparing to partition disk: “Hitachi HTS541612J9SA00 Media”
2007-11-04 00:09:40 -0400: Partition Scheme: GUID Partition Table
2007-11-04 00:09:40 -0400: 3 volumes will be created
2007-11-04 00:09:40 -0400:
2007-11-04 00:09:40 -0400: Partition 1
2007-11-04 00:09:40 -0400: Name : “Macintosh HD”
2007-11-04 00:09:40 -0400: Size : 90.1 GB
2007-11-04 00:09:40 -0400: Filesystem : Mac OS Extended (Journaled)
2007-11-04 00:09:40 -0400: Do not erase contents
2007-11-04 00:09:40 -0400:
2007-11-04 00:09:40 -0400: Partition 2
2007-11-04 00:09:40 -0400: Name : “Linux Swap”
2007-11-04 00:09:40 -0400: Size : 488.3 MB
2007-11-04 00:09:40 -0400: Filesystem : Mac OS Extended (Journaled)
2007-11-04 00:09:40 -0400: Do not erase contents
2007-11-04 00:09:40 -0400:
2007-11-04 00:09:40 -0400: Partition 3
2007-11-04 00:09:40 -0400: Name : “DISK0S4”
2007-11-04 00:09:40 -0400: Size : 10.2 GB
2007-11-04 00:09:40 -0400: Filesystem : MS-DOS (FAT32)
2007-11-04 00:09:40 -0400: Do not erase contents
2007-11-04 00:09:40 -0400:
2007-11-04 00:09:40 -0400: Modifying partition map.
2007-11-04 00:09:40 -0400: Partition failed for disk Hitachi HTS541612J9SA00 Media MediaKit reports no such partition.
2007-11-04 00:09:41 -0400: Partition complete.
2007-11-04 00:09:41 -0400:
2007-11-04 00:09:41 -0400: Error with partition: MediaKit reports no such partition.

It doesn't sound like you've actually tried reformatting the entire drive, just resizing partitions. There is absolutely no reason why mountability should enter into the picture at all since you can't format a drive if any volumes are mounted.

Similar Messages

  • 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.

  • Mediakit reports no such partition

    I have Leopard and Ubuntu installed side by side on my MacBook. I am running out of space on Leopard and wanted to free up some space.
    So I loaded the Live version of Ubuntu and made the native Ubuntu partition smaller.
    I then restarted and loaded the Disk Utility from the Leopard installation CD and tried to make my Leopard partition larger, however after I click 'Apply', a message comes up saying: Mediakit reports no such partition.
    Anyone know what the issue could be? Why can I not add the free space to the Leopard partition?
    Thank you!

    It is possible that Ubuntu is holding onto the partition, or it is formatted in a way that won't let Disk Utility handle it. Try looking on some Ubuntu forums as there are probably not that many people here with any experience with Ubuntu.

  • Disk Utility won't add new partition

    I have an external 250GB hard drive connected via USB to my Mac Mini (Early 2009) computer. The drive has a GUID partition table that was created using Windows Vista SP 1. The first partition on the disk is a 128MB Microsoft Reserved partition. The second partition is a 120GB NTFS partition. When I try to use Disk Utility to partition the remaining 112GB of space as a Mac OS Extended Journaled partition I keep getting an error message stating "MediaKit reports no such partition". How do I get around this bug in Apple's Disk Utility application?

    techguy378,
    As they always do, Microsoft has undoubtedly created "their own" proprietary implementation of the GUID partition table. The effect, in this particular case, is that Disk Utility cannot see that unused space. That doesn't mean this is a Disk Utility "bug."
    If one were to do the same thing with Disk Utility- create 2 partitions on a drive that do not fill the drive- that empty space would be included in the partition map. Simple. In your case, however, it appears that Vista has just excluded that empty space from the map entirely. Neat trick, huh?
    I think your only solution will be to add a partition in Vista, if that is possible without destroying the current volumes. You can then reformat the new partition in Disk Utility.
    Scott

  • Disk Utility Not Letting Me Resize Partition

    Hi people,
    I had used boot camp to install Ubuntu as dual boot but it wasn't working properly so I decided to delete the partition that Ubuntu was on. This worked fine.
    However when I tried to resize my Macintosh HD to its original size I get the error message:
    Partition failed with the error:
    MediaKit reports no such partition.
    Also there is a partition called "Linux Swap" that I can't erase or reformat.
    Any suggestions?

    That definitely has to do with the encryption on the disk.  Thats what that message CoreStorage Physical volume is referring to.
    Sorry I don;t have a solution, if you google for that CoreStorage message you'll get some ideas. One thing I can tell you make sure you have this disk backed up if you start messing around with this. The chances of messing up is sort of high.
    regards

  • 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.

  • Disk utility can't repair a partition on external hard drive

    I have a 1TB Western Digital external FW drive that's only a couple years old (2 or 3, probably). I have it split into partitions, one of which I'm using for Time Machine. The non-Time Machine partition checked out fine with DIsk Utility, but when I ran Disk Utility on the Time Machine partition, I received this message:
    Disk Utility stopped reparing "Time Machine." Disk Utility can't repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
    Does this mean the drive itself is failing? I erased the Time Machine partition and recreated it through Disk Utility, and then I verified it. Everything checked out okay, but I want to make sure, especially since I'm hosting my iTunes music in the other partition (it's backed up to a 2nd external drive, so if the drive does die, at least I don't lose everything).
    Before this problem happened, both partitions dropped off the Finder and the light on the drive went off. I unplugged the drive and plugged it back in again a couple times, but nothing happened. Finally, the light went back on after plugging it back in for the 3rd or 4th time, but I'm wondering if the drive could be going bad, which would surprise me since it isn't very old.

    Brad Cook wrote:
    Disk Utility stopped reparing "Time Machine." Disk Utility can't repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
    Does this mean the drive itself is failing?
    Possibly, but not necessarily.  The File System on the disk was so badly corrupted that Disk Utility couldn't fix it.  That might indicate a problem with the drive.  It's not unusual for consumer-quality (ie, inexpensive) drives to fail after 2-3 years, although many will run for several years.  It's a bit of a crapshoot.
    Before this problem happened, both partitions dropped off the Finder and the light on the drive went off.
    Whatever caused that is another good possibility -- if a drive is improperly disconnected, OSX can't "close it out" properly, and that can cause damage to the file system.  Sometimes Disk Utility can fix it, sometimes it can't.  And sometimes heavy-duty 3rd-party disk repair apps like DiskWarrior can fix things Disk Utility can't.
    A power dip or spike could have caused it, or an overheated electronic component, etc.  If it has it's own power supply, be sure it's on a good (ie, not cheap) surge protector or U.P.S. system.
    Otherwise, keep an eye on it.  If you don't have "secondary" backups, this would be an excellent time to get another drive for that purpose.  See #27 in Time Machine - Frequently Asked Questions for some suggestions.
    Bottom line:  personally, I'd not trust my only backups to that drive.
    (But then, I'd never trust my backups to any single drive, no matter how new or high-quality.)

  • Disk Utility is reporting a fatal hardware error-S.M.A.R.T. status failing. Is there hope?

    OS 10.5.8 on a 1.8 GHz Power PC G5. Installed Western Digital WD1002FAEX as a second internal hard drive. I also installd the jumper needed to slow HD down for this computer. Initialized and formated the HD was able to back up a large iPhoto file and am still able to acceass the file from the new HD. Now Disk Utility is reporting a fatal hardware error-S.M.A.R.T. status failing. Is there hope?

    Is that on your first drive or the new one???
    Only experience I had with SMART warning was that in less than 48 hrs it was dead for good.

  • Can I use the Leopard Disk Utility to repair a Tiger partition?

    I have a multi-partition external disk, one partition has Tiger installed on it, while others have Leopard. (I used Leopard to partition the drive and then used SuperDuper! to copy my earlier Tiger backup from another disk to this disk.) Now I find I have errors on the partition with Tiger. Can I use the Disk Utility tool from my Leopard install to repair the Tiger partition? Earlier today I tried to boot from my Tiger install DVD and use the Disk Utility there to repair the partition, but it just hangs up and won't go forward.
    thanks,
    Chris Altwegg

    You could use it, but if Tiger's Disk Utility couldn't fix it, it's doubtful Leopard's would fix it as well. You're better off using Disk Warrior from Alsoft.com.

  • Disk Utility will not format/erase/partition an unformatted scsi disk

    Well, I'm back with a RAID problem again. This time the powers that be sent me a Sun Microsystems StorEDGE A5200 RAID box (22 33gig disks). It's a fibre channel system, and is full of Seagate FC disks. The box only hooks up to my G5 Quad via the Apple Fibre channel card that I have hooked up. It's a dual channel card and both are plugged into the back of the RAID array.
    Now, here's what I have.....
    The Drives show up in both Disk Utility and Anubis
    The is only one drive formatted and it works fine.
    All the rest of the drives are unformatted (not just blank, but without any operating system on them, just like they were fresh out of the box)
    Attempting to Erase a disk results in the message
    Disk erase failed
    Disk erase failed with the error:
    Invalid Argument
    Attempting to Partition a disk results in the message
    Partition failed with the error:
    Invalid Argument
    Attempting to create a RAID set results in the message
    Creating RAID set failed with the error:
    Could not add a RAID disk to a RAID. (note there was no other RAID set)
    Only one disk in the array is formatted and it will respond to all of the functions in Disk Utility.
    I was told that I needed to do something using the command line, but that was pretty vague as to what I needed to do. Apparently I need some sort of superuser authority to get these drives formatted, and that's it's not documented any where.
    So folks, I leave it up to you again, what do I do?

    OK, I have found out much in the last few weeks.
    1 - Apple no longer supports SCSI, you may not format disks in any way using OS X. OS 9 also does not work on any of the G5 machines at least.
    2 - You can use Linux to do most of the work with SCSI, it is still supported, although there is little clear documentation on how to get it done. Linux is free and works very well with my G5 Quad. But it has a steep learning curve and it's not worth it for just formatting SCSI drives.
    What I found out about my SCSI drives turned out to be the core of all the problems I have had, and it was Linux that found the problem. Seems all of the drives I have but one have been formatted in such a way that only the proprietary operating system that formatted them would read them. 520k data blocks. I reformatted several of the drives to 256k blocks and they work fine now.
    Before I go out and start going though this for a few hundred more of these drives, my academic supplier found just as many drives that were specifically formatted for use in Sun RAIDs and are properly recognized by OS X, and with twice the drive space (current is 36gig, new ones are 73gig). He is sending me 44 of them (and a second RAID box)
    I'm hoping that this finally solves the problem and hope all will be working soon.

  • Disk Utility won't resize a partition

    Disk Utility won't resize (eliminate smaller partition from a 2-partitioned internal) Hard Drive. This is the message I get:
    "Partition failed
    Partition failed with the error:
    Filesystem resize support required, such as HFS+ with Journaling enabled."
    Help files offer no information on this error. I followed the Help instructions to do this operation, but the resize doesn't work. The older, smaller partition shows up in Disk Utility but is dimmed out. It will activate at highlight, but is not recognized on the desktop.
    Any suggestions as to how to fix this problem?

    Intel based Macs use a different partition scheme called GPL or GUID rather than what PowerPC used, APL.
    You could try reformatting, or get a new system, and run BootCamp and Windows even.
    Even if you've used Macs for years, there is always a place on my book shelf for this one, David Pogue's "Mac OS X: The Missing Manual (Leopard Edition)"
    http://books.slashdot.org/books/08/02/27/1551206.shtml

  • Disk utility intermittently reports corrupt disk

    As a matter of routine maintenance I like to "Verify Disk" in disk utility from time to time.
    The issue I am having is that disc utility intermittently identifies that the Server drive is corrupt and needs to be repaired. Here is a typical sequence:
    1) Run verify disk and it reports a corrupt disk.
    2) Boot up off a different disk and re-run verify / repair disk on the problematic disk and it reports that the disk is fine.
    3) Boot up on the original (problematic) disk and re-run verify disk and it reports the disk as fine.
    4) Checking again the next day the original problem resurfaces - disk is corrupt.
    The server appears to be running fine, but I am loathe to have an issue like this potentially simmering in the background. I am also averse to upgrades until this issue is resolved. Any pointers on getting this resolved would be much appreciated.
    Coincidentally, I have run disk warrior and it reports no issues.

    Here is the typical disk utility log when reporting the error:
    Verifying volume “Server”
    Verifying volume when it is mounted with write access.
    Checking Journaled HFS Plus volume.
    Checking extents overflow file.
    Checking catalog file.
    Incorrect block count for file kdc.log
    (It should be 91 instead of 92)
    Incorrect number of thread records
    Invalid leaf record count
    (It should be 1567637 instead of 1567636)
    Checking multi-linked files.
    Checking catalog hierarchy.
    Checking extended attributes file.
    Checking volume bitmap.
    Volume bitmap needs minor repair for under-allocation
    Checking volume information.
    Invalid volume file count
    (It should be 684309 instead of 684308)
    Invalid volume free block count
    (It should be 47746895 instead of 47747031)
    Volume header needs minor repair
    The volume Server 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.

  • Disk Utility: MediaKit?

    Hello! Long story short, I tried to partition my disk and I got this error:
    http://www.cakeman.biz/what_happened.png
    Any help?
    Zack

    HI Zack,
    Boot from your install disk (the one that came with your Mac).
    Run Disk Utilitly to verify and if necessary, repair any errors.
    Insert Installer disk and Restart, holding down the "C" key until grey Apple appears.
    Go to Installer menu (Panther and earlier) or Utilities menu (Tiger and later) and launch Disk Utility.
    Select your HDD (manufacturer ID) in the left panel.
    Select First Aid in the Main panel.
    (Check S.M.A.R.T Status of HDD at the bottom of right panel. It should say: Verified)
    Click Repair Disk on the bottom right.
    If DU reports disk does not need repairs quit DU and restart.
    If DU reports errors Repair again and again until DU reports disk is repaired.
    When you are finished with DU, from the Menu Bar, select Utilities/Startup Manager.
    Select your start up disk and click Restart
    While you have the Disk Utility window open, look at the bottom of the window. Where you see Capacity and Available. Make sure there is always 10% to 15% free disk space
    If you can't boot from your install disk, try booting in Safe Mode
    What is Safe Mode
    Carolyn

  • Disk utility can't verify/repair partition map.

    When trying to verify/repair my hdd it gives me the error: "Error: Couldn’t find the target disk for this operation."

    You should already have a Recovery HD that was created when you installed Lion or came with the computer pre-installed. The Recovery Disk Assistant simply makes a Recovery HD you can use if one is missing from the hard drive.
    However, repartitioning will destroy all the data on the drive so you will have to reinstall Lion. It will also remove the Recovery HD from the drive, so you will need to use your flash drive Recovery HD to boot the computer and get to the recovery main menu. The essential process:
    Install or Reinstall Lion from Scratch
    If possible backup your files to an external drive or second internal drive.
    Boot to the Recovery HD:
    Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
    You will need to use the OPTION boot method to select your recovery flash drive as the boot volume.
    Repartition the hard drive:
    Select Disk Utility from the main menu and click on the Continue button.
    After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area.  If it does not say "Verified" then the drive is failing or has failed and will need replacing.  SMART info will not be reported  on external drives. Otherwise, click on the Partition tab in the DU main window.
    Select one partition from the Partition Scheme dropdown menu. Click on the Options button and set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the process has completed.
    Quit DU and return to the main menu.
    Reinstall Lion: Select Reinstall Lion and click on the Continue button.
    When the destination drive is displayed click on the Display Other Drives button and select your internal hard drive as the target.

  • Partitioned with Disk Utility, during XP inst. desired partition N/A

    Basic computer info: Macbook Pro 3,1 Leopard 1.5.1
    I partitioned my computer into 4 separate partitions:
    MacSys - 25gb, journaled, extended
    LinSys - 12gb, journaled, extended
    WINSYS - 14.86gb, fat32
    HdaSys - 59.35gb, journaled, extended
    So, 1 partition per OS, and a commonly accessible partition.
    I used Disk Utility to do all this.
    The problem is that with my XP Home SP2 disk, the WINSYS drive does not show up. Instead, it shows 1 large conglomerate partition, I believe as unpartitioned space (Don't write that last bit in stone, this is from retrospect)
    What have I done wrong? I need some insight.
    Thanks in advance.

    lilwing wrote:
    Ahh thanks, now I understand.
    However, how can I have another partition for file storage/archiving which can be mountable from all other partitions? The njHdaSys would have problems, I would assume.
    Due to the GUID/MBR Hybrid issues, you need to change your GPT disk setup/cration to this:
    1: MacSys - 25gb, journaled, extended
    2: HdaSys - 59.35gb, FAT32
    3: WINSYS - 14.86gb, FAT32
    4: LinSys - 12gb, FAT32
    Then after using a tool that creates a hybrid MBR on your GPT disk (such as gptsync included with rEFIt or maybe some version of OSX's Disk Utility), your hybrid MBR (what Windows ONLY sees) will be:
    1: EFI Protected
    2: MacSys - 25gb, journaled, extended
    3: HdaSys - 59.35gb, FAT32
    4: WINSYS - 14.86gb, FAT32
    (with LinSys not accessible (to Windows) and showing up as 'unallocated space', which you can't ever touch under Windows or you'll trash it.)
    Now, with this setup:
    1) your OSX HFS+ system partition has an MBR entry, so you'll be able to see and read it under Windows with the BootCamp 3.0 HFS+ file-system drivers.
    2) your HdaSys storage partition has an MBR entry, so you'll be able to see and read it under Windows
    3) your WINSYS volume with be the last partition which Bootcamp demands (or else you get the hall.sys error.)
    Then, you can install Windows into WINSYS, reformating to NTFS during install.
    Then, since Linux is GPT aware, you can install it into LinSys which doesn't have an MBR entry and is only GPT. (Depending upon your RAM, you might also want to have a SWAP partition after LinSys.) However, since Linux does require a BIOS/MBR boot in order to get full video support, during your Linux install, you need to install GRUB to the start of the HdaSys STORAGE partition -- then GRUB will boot off a BIOS/MBR partition, gaining video support, but can still point to the rest of the Linux install on the GPT partition.
    Now, since the Mac startup selector will only give you a choice between OSX GPT volumes and 1 BIOS/MBR choice, you'll need to either setup Windows or GRUB to be your secondary OS chooser (between Windows and Linux), or use rEFIt to be the single startup chooser between OSX, Windows, and Linux instead.

Maybe you are looking for