Disk Utility resize results in corrupt BootCamp partition

Hello,
  Yesterday I decided that I wanted to put Linux on my system: taking what was already a fully working boot camp partitioned drive, resizing the main mac partition to free up some space, and then install debian on that. I went into Disk Utility and resized the drive and that worked just fine, except that when the process was complete my boot camp partition was no longer bootable. It is also no longer labeled BOOTCAMP in the diskutility (though it is when I use diskutil list on the command line), but instead named after its block device (disk0s4 in this case).
I've tried everything I can think of. Disk Utility quickly became useless (repair disk? can't repair disk!), and any sort of attempt to mount the disk on the command line just gives me an "Input/output error," so no dice there. I really need the data off this partition and from what I can tell it seems that the partition is intact, its just the partition map that has been corrupted. I also tried rEFIt's gptsync utility which also did not work. Any suggestions would be very welcome, it's very important that I get the data off this partition.

Honestly, had this process even gotten to a point at which I was on my way to a triple boot I would be much more inclined to agree with you. Yes, I did make a mistake of not backing up before the resize, totally willing to admit that. Of course, that course of discussion leads nowhere in terms of solving this problem. We all know to back things up, most of us do, some don't, nothing new here..
Having said that, this problem has nothing to do with a triple booting. This problem stemmed completely from a simple resize of a HFS+ partition in Disk Utility (a partition, I might add, that was extremely large and mostly free, so overwriting data in the shrink was also not a concern). As far as I'm concerned, if Disk Utility can't resize the partition without destroying/corrupting data, then they shouldn't offer it as a feature. At very least display some sort of message. Maybe: "Hey there! This process USUALLY works, caveat emptor!" I might have been inclined to use _any_ other product.
I'm in the process of using Data Rescue 3 to analyze the drive, and hopefully retreive most of the files. As I previously stated, the actual problem here appears to be completely with a corrupt partition map (Data Recue is having no problem accessing the files so far), but I just don't have the time to dig too deeply into how that all works to solve the problem.

Similar Messages

  • 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

  • Disk Utility - Resize Partition

    I'm using Snow Leopard on my Macbook Pro (i7, 2.7 GHz). I have a 500 GB HD that is divided into two partitions of 300 and 200 GB each.
    I want to resize them in order to obtain two equal partition. Using Disk Utility, I was able to reduce the size of the top one (the one with the OS) but I cannot find a way to enlarge the bottom one to fill the blank space in between. In fact, I cannot drag the separator upwards, but only downwards (see the picture).
    Any clue on how I might solve this without erasing all the data and create a band new partition? Thanks in advance.

    Hmmm, not sure what you did to get what you have, but you cannot enlarge the bottom partition. You can only enlarge the top partition. My suggestion:
    Delete that bottom partition. Drag the sizing gadget on the top partition all the way to the bottom. Click on the Apply button. When this is finished click in the resulting single partition then click on the Add [-] button which should automatically divide into two equally sized partitions. Click on the Apply button.
    Now, this will erase whatever is on the lower partition you now have, but not the upper partition on which you have OS X installed. Be sure you have backups of your data before proceeding as a precaution.

  • Disk Utility - Resizing partition

    I'm currently in the middle of resizing an external disk partition. It's a 250 gig partition on a 500 gig drive. Disk Utility progress bar indicates "Shrinking disk" and it's been doing this for the past 12 hours uninterrupted.
    Is this normal? How long should I continue to wait? Is there any way I can safely abort the procedure? How can I tell if it's still working normally?

    Ok, I aborted the procedure. It had been running about 32 hours until then. Thought I'd post an update in case this happens to anyone else.
    Disk Utility was still responsive -- I told it to quit, and it warned me it was in the middle of the operation. Finder crashed in shutdown and after waiting a few minutes I killed the power by holding in the power button. Unplugged the external drive's power and the firewire cable to my mac, powered back up, plugged it in, and ... all files, folders are still there. Disk Utility shows no changes were made to partition.
    I have no idea what the cause of this may have been. I captured sample processes from the Disk Utility.app and diskmanagementd. Someone knowledgeable about that this process might be make a determination.
    I'm taking this as a lesson not to modify partition sizes of external drives. Backing up the entire drive and completely repartitioning the drive is the only safe way to go.

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

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

  • Disk Utility no longer restores to smaller partitions

    Up until today, I've been using Disk Utility to clone my Macbook Pro HD to an external HD. The MBP drive is 750GB, with about 300GB in use. The external 1TB drive has two equally sized partitions of ~500GB. I alternate between the two partitions each time I make a back up. I've been doing this regularly for many years now, and it's saved me on a couple of occasions. My last clone was made on June 2nd. However, today I got this message when trying to make a clone:
    Restore Failure
    Not enough space on /dev/disk1s4 to restore
    This is the first time I've ever had this message pop up. I even tried repartitioning and reformatting the external drive, but it didn't help. The only way I can successfully clone my drive now is by making the external drive one large partition, which results in "Copying blocks. Estimated time: 8 hours". Previously, it took slightly less than 3 hours to clone my drive.
    Was there a recent update that changed something with Disk Utility? Is anyone else having this problem?

    I seem to remember reading somewhere that Disk Utility will only restore to a smaller partition if you un-select the "Erase destination" check-box. This option does not seem to exist any more in the latest version of Disk Utility (13 (450)). Have you updated to Mountain Lion recently?
    A better approach may be to use Time Machine with your external HD. This works nicely with USB disks. You don't need to buy the TimeCapsule hardware. I assume the reason you alternate backups between two partitions is in case it fails during one of the backups. That is less of an issue with Time Machine as it does incremental backups. However, if you want multiple backup disks, Time Machine will automatically alternate backups between them. You can even do the same thing with two partitions on the same disk, but it is safer to use two separate disks in case of a complete disk failure.

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

  • Time Machine, Disk Utility, and clearing out corrupted snapshots

    Hi, all. I've been having some troubling issues with Time Machine and could use your collective insight.
    I have a 500GiB external USB2 disk that I've been using for Time Machine since December (the oldest snapshot in Backups.backupdb is named 2007-12-13-222250). Everything worked fine until sometime in late January, when Time Machine decided to ax 2/3 of my Applications directory. Time Machine's logging is terse, so I wasn't able to determine what caused the corruption. The fact that this error wasn't caught and flagged by Time Machine bothers me.
    Especially because I discovered this in the process of needing to recover from a crash on my laptop's hard drive -- I had to roll back to a previous, complete snapshot to get all my applications back.
    After that I had to engage in some jiggery-pokery to get Time Machine to re-snapshot everything, but things proceeded normally until I received my new copy of DiskWarrior 4.1 last night (although DiskWarrior is an innocent bystander here). I tried to use DiskWarrior to rebuild the directory on the Time Machine disk, but it failed before trying to write anything.
    (For those who care: after some back and forth with Alsoft tech support, we determined this was likely because my Time Machine volume has 6.2GB of catalog data, and DiskWarrior works by rebuilding the directory in memory, so it has to be able to fit the whole catalog into virtual memory.)
    I was a little paranoid that something might be wrong with the disk after that, so I fired up Disk Utility and told it to repair the disk. It churned for about 6 hours and repaired an extraordinarily large number of hardlink reference count errors, but completed by claiming that the disk had been repaired.
    When I next told Time Machine to run, instead of copying over a couple GB of data like it usually does, it started copying 38GB! ***? I took a look at the previous Time Machine snapshots, and discovered that Disk Utility had totally corrupted every snapshot I'd made since last month's fandango. Most of the root-level directories in the snapshots now look like this:
    $ ls -al /Volumes/Time\ Machine\ Backups/Backups.backupdb/xxx.net/2008-03-13-025640/Euphrosyne/
    total 128
    drwxrwxr-t@ 16 root admin 1020 Feb 15 00:17 ./
    drwxr-xr-x@ 3 root ogd 204 Mar 13 02:56 ../
    -r--r--r--@ 9151 root 20051003 0 Feb 11 23:13 .DRM_Data
    -r--r--r--@ 50574 root 20051004 0 Feb 11 23:13 .DS_Store
    -r--r--r--@ 9154 root 20051006 0 Feb 11 23:13 .SymAVQSFile
    -r--r--r--@ 9155 root 20051007 0 Feb 11 23:13 .VolumeIcon.icns.candybarbackup
    drwxr-xr-x@ 2 ogd admin 68 Feb 29 2004 .buildinstaller1.tmp/
    -r--r--r--@ 9149 root 20051001 0 Feb 11 23:13 .com.apple.timemachine.supported
    -r--r--r--@ 9150 root 20051002 0 Feb 11 23:13 .com.apple.timemachine.supported (from old Mac)
    -r--r--r--@ 9153 root 20051005 0 Feb 11 23:13 .redethist
    -r--r--r--@ 58730 root 20051009 0 Feb 11 23:13 Applications
    -r--r--r--@ 37526 root 20051012 0 Feb 11 23:13 Desktop Folder
    -r--r--r--@ 13328 root 20051013 0 Feb 11 23:13 Developer
    -r--r--r--@ 64211 root wheel 0 Feb 11 23:13 Library
    -r--r--r--@ 49886 root 20051080 0 Feb 11 23:13 Network
    -r--r--r--@ 5643 root 20051120 0 Feb 11 23:13 System
    lrwxr-xr-x 1 root ogd 60 Mar 13 02:56 User Guides And Information@ -> /Library/Documentation/User Guides and Information.localized
    drwxr-xr-x@ 5 root admin 204 Dec 6 02:07 Users/
    -r--r--r--@ 2554 root wheel 0 Feb 11 23:13 Volumes
    -r--r--r--@ 37448 root 20051010 0 Feb 11 23:13 bin
    -r--r--r--@ 37525 root 20051011 0 Feb 11 23:13 cores
    lrwxr-xr-x@ 1 root ogd 11 Mar 13 02:56 etc@ -> private/etc
    -r--r--r--@ 26309 root 20051078 0 Feb 11 23:13 mach_kernel
    -r--r--r--@ 26310 root 20051079 0 Feb 11 23:13 mach_kernel.ctfsys
    lrwxr-xr-x 1 root ogd 12 Mar 13 02:56 opt@ -> /private/opt
    drwxr-xr-x@ 8 root wheel 272 Dec 6 02:31 private/
    -r--r--r--@ 52664 root 20051119 0 Feb 11 23:13 sbin
    lrwxr-xr-x@ 1 root ogd 11 Mar 13 02:56 tmp@ -> private/tmp
    -r--r--r--@ 41668 root 20052660 0 Feb 11 23:13 usr
    lrwxr-xr-x@ 1 root ogd 11 Mar 13 02:56 var@ -> private/var
    That is clearly, completely wrong, and it alarms me that Disk Utility could cause so much damage to a Time Machine volume.
    Since I also use SuperDuper! to regularly clone this disk, it's not as big a nightmare as it could be, but this means that I'm going to have to clear out every snapshot for the last month by hand, both because I obviously can't trust them anymore, and because I keep getting messages like this in the logs:
    2008/03/13 7:25:35 PM /System/Library/CoreServices/backupd[1229] Error: (-36) copying /.com.apple.timemachine.supported to /Volumes/Time Machine Backups/Backups.backupdb/xxx.net/2008-03-13-192246.inProgress/70254508-90E3-4FF A-AE46-9E8210095DAE/Euphrosyne
    2008/03/13 7:25:35 PM /System/Library/CoreServices/backupd[1229] Error: (-36) copying /.com.apple.timemachine.supported (from old Mac) to /Volumes/Time Machine Backups/Backups.backupdb/xxx.net/2008-03-13-192246.inProgress/70254508-90E3-4FF A-AE46-9E8210095DAE/Euphrosyne
    2008/03/13 7:25:35 PM /System/Library/CoreServices/backupd[1229] Error: (-36) copying /.DRM_Data to /Volumes/Time Machine Backups/Backups.backupdb/xxx.net/2008-03-13-192246.inProgress/70254508-90E3-4FF A-AE46-9E8210095DAE/Euphrosyne
    2008/03/13 7:25:35 PM /System/Library/CoreServices/backupd[1229] Error: (-36) copying /.DS_Store to /Volumes/Time Machine Backups/Backups.backupdb/xxx.net/2008-03-13-192246.inProgress/70254508-90E3-4FF A-AE46-9E8210095DAE/Euphrosyne
    2008/03/13 7:25:35 PM /System/Library/CoreServices/backupd[1229] Error: (-36) copying /.redethist to /Volumes/Time Machine Backups/Backups.backupdb/xxx.net/2008-03-13-192246.inProgress/70254508-90E3-4FF A-AE46-9E8210095DAE/Euphrosyne
    2008/03/13 7:25:35 PM /System/Library/CoreServices/backupd[1229] Error: (-36) copying /.SymAVQSFile to /Volumes/Time Machine Backups/Backups.backupdb/xxx.net/2008-03-13-192246.inProgress/70254508-90E3-4FF A-AE46-9E8210095DAE/Euphrosyne
    2008/03/13 7:25:35 PM /System/Library/CoreServices/backupd[1229] Error: (-36) copying /.VolumeIcon.icns.candybarbackup to /Volumes/Time Machine Backups/Backups.backupdb/xxx.net/2008-03-13-192246.inProgress/70254508-90E3-4FF A-AE46-9E8210095DAE/Euphrosyne
    I'd like to keep the old snapshots if I can. What's likely to happen if I just go and clear out the b0rked backup sessions by hand?
    (Hmm... it appears yes, because I just deleted them all and the disk didn't recover the freed space.)
    Here's the important question: has anyone else had issues using Disk Utility on a Time Machine volume, and does anyone at Apple have any plans to add integrity checking to Time Machine? As it stands, I don't really feel like I can trust it in its present form, as convenient as it is...

    I have trouble with disk utility on my new (1 TB Lacie) as well as on my old (500 GB WD) drive. After doing a backup, du tells me a never ending list of errors like
    HasFolderCount flag needs to be set (id = 599567)
    (it should be 0x10 instead of 0)
    Everything was O.K. before doing the backup; so is the disk to be backupped, according to du.
    Up to now, no other problem occurred, but I´d like to clear this issue before my trust in time machine is restored.

  • Disk Utility can't repair and refuse Partition to work

    Hi,
    Is there any ways to solve this message appearing in the Disk Utility?
    When i click repair disk on Disk Utility, message shown;
    Repairing permissions for “Macintosh HD”
    Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/Deploy.bundle/ Contents/Resources/JavaPluginCocoa.bundle/Contents/Resources/Java/deploy.jar", should be lrwxr-xr-x , they are lrw-r--r-- .
    Repaired "System/Library/Frameworks/JavaVM.framework/Versions/A/Resources/Deploy.bundle/ Contents/Resources/JavaPluginCocoa.bundle/Contents/Resources/Java/deploy.jar".
    Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/readconf ig" has been modified and will not be repaired.
    Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/writecon fig" has been modified and will not be repaired.
    Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/deploy.jar", should be -rw-r--r-- , they are lrwxr-xr-x .
    Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/deploy.jar".
    Permissions differ on "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/libdeploy.jnilib", should be -rwxr-xr-x , they are lrwxr-xr-x .
    Repaired "System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Resources/JavaPlugin Cocoa.bundle/Contents/Resources/Java/libdeploy.jnilib".
    Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.
    Permissions repair complete
    Then i thought its might not be repair just by one repair.
    After that i try repair again however this message still appear.
    I ever try restarting and shutting down my MacBook but the message still appear.
    I do some research and find that one of the message in the list can be safety ignore
    http://support.apple.com/kb/ts1448
    Hence i just ignore the message.
    Meanwhile i try to partition my hard disk and message shown;
    Partition failed
    Partition failed with the error:
    Could not modify partition map because filesystem verification failed
    I getting too frustrated about this problem.... ARRRGGGGHHHH!!!!
    Any solutions are welcome. Thanks

    You can find an extensive discussion of the permissions repair messages you can ignore at Topic: Permissions Snow Leopard 10.6.4. Nothing on your list of permissions messages is unusual or indicates an issue that needs correction.
    However, the partition failed message indicates that you need to run Disk Utility's Repair Disk function on the disk volume. Note that if this is your normal startup volume, you will have to start up from some other disk, such as your installer disc, & run the Repair Disk step from it.
    If Disk Utility is unable to repair the HD, you can try more powerful (& costly) utilities like Disk Warrior, but there are no guarantees that any of them will be able to fix all possible problems the HD may have.

  • DIsk Utility doesn't allow creating a partition

    Hi all,
    I just bought a new MacBookPro and installed Mountain Lion yesterday. I decided to use a encrypted file system (File Vault). So far everything worked fine.
    This morning I decided to do a clean install, as Migration Assistent carried over some data I do not need.
    So I booted into Recovery Mode, selected the harddisk and chose "Erase". As I wanted an encrypted volume again, Disk utility asked me for a password which I specified. Immediately after clicking ok, Disk Utility said "Not enough RAM to complete this request". After clicking OK, my partition went and since then I am strugglign to find out how to activate it (data not important, as everythign backed up).
    Apple Care also doesn't knwo what to recommend anymore.
    Here's what I tried:
    1) Command+R boot and Disk Utility
    2) Boot from external HD and Disk Utility
    3) Internet Recovery (ends with error)
    4) Delete PR
    The strange thing is that Disk Utility shows Macintosh HD on the top level with the option to partition (it doesn't show any indended partitions) but all options are grayed out. It's like Disk Utility somehow confused Parttion with physical drive and now gets confused.
    Any other idea other than sending the macbookPro back to Apple?
    Thanks
    Matt

    You should of taken the encryption off before you started that proccess. That is one thing they don't tell you. Never try to modify an encrypted partition.
    You may have to boot to the Internet (Online) Recovery HD system lto Re-Partition the drive as one partition.
    Hold down Command+Option+r keys at boot and keep them held down until you see a spinning globe in the center of the screen, then you can let them up. Have the computer WIRED to your unternet router.
    Once that loads open disk utility and select the Drive Name (Not volume name, IE Macintosh HD) and then the partition tab and select One partition from the Partition Layout drop down.
    If that doesn't work then the drive is FUBAR.

  • Disk Utility can't create a new partition

    Hello,
    I'm trying to create a new partition to install Windows 7 on, but I am unable to do so.
    At first I tried to do this with Boot Camp Assistant, but it didn't work.
    Then I tried to create a FAT partition with Disk Utility, which didn't work either.
    So I verified and repaired the disk, tried to create the partition again, yet it still didn't work.
    I verified and repaired the disk and tried to create the partition while running the OS, in Safe Mode and from the Mac OSX Install DVD.
    Neither of them worked.
    I noticed while running the OS, the info of the HD said the capacity is 749.81 GB, while checking that from the Mac OSX Install DVD it only says about 700 GB (I mentioned 698.6 GB).
    Strange..
    It might also be important to mention that I recently (2 days ago) I installed a new HD: Western Digital Scorpio Black 750 GB, and today I swapped my 2x 2GB RAM for 2x 4GB RAM (Samsung).
    On my previous HD, the Fujitsu 250GB, this proces was no problem at all. I installed W7 on that drive just a week ago.
    I made a clone of the Fujitsu HD and "back-upped" it to my new WD HD. The W7 partition on the Fujitsu HD was 50GB, which is the difference in capacity mentioned above. I'm not sure if there's a link here..
    I've got a MacBook Pro from mid 2009.
    I'm not sure what to do next... I'm stuck!
    Any help is greatly appreciated!

    Good thing to mention that, I forgot to do that.
    Unfortunately it did not help.. The screen to remove the existing Boot Camp partition does not pop up, it just tries to create the new Boot Camp partition.
    The partition I'm trying to create it 150GB. The 50GB mentioned above was on the stock Fujitsu 250GB disk.
    Edit:
    I'm actually trying to avoid using Boot Camp Assistant.. I became to dislike the utility due to problems creating a partition on my previous HD.
    I would like to create a partition using Disk Utility and then install Windows 7 by selecting that DVD to boot from.
    Thank you for the tip though, I'll post it there as well!

  • Disk Utility Hangs When Creating a New Partition

    Hello,
    I recently purchased a Late 2005 Power Mac G5. My problem is, that the hard drive is 250 MB and only one partition appears in the disk utility of 37 GB. I try to add a new partition, but it hangs on "modifying partition map". Any Help?
    Additional info -
    Main Disk
    Name : WDC WD2500JD-41HBC0
    Type : Disk
    Partition Map Scheme : Apple Partition Map
    Disk Identifier : disk0
    Media Name : WDC WD2500JD-41HBC0 WDC WD2500JD-41HBC0
    Media Type : Generic
    Connection Bus : Serial ATA
    Connection ID : Device 0, "A (upper)"
    Device Tree : first-boot/@0:0
    Bay : "A (upper)"
    Writable : Yes
    Ejectable : No
    Mac OS 9 Drivers Installed : No
    Location : Internal
    Total Capacity : 232.9 GB (250,059,350,016 Bytes)
    S.M.A.R.T. Status : Verified
    Disk Number : 0
    Partition Number : 0
    Partition -
    Name : Mac OSX 10.5
    Type : Volume
    Disk Identifier : disk0s3
    Mount Point : /
    File System : Mac OS Extended (Journaled)
    Connection Bus : ATA
    Device Tree : first-boot/@0:3
    Writable : Yes
    Universal Unique Identifier : 989D8CCE-3C5D-3ECC-9A12-C025D2DF23F2
    Capacity : 37.1 GB (39,873,503,232 Bytes)
    Free Space : 24.5 GB (26,274,824,192 Bytes)
    Used : 12.7 GB (13,598,679,040 Bytes)
    Number of Files : 484,775
    Number of Folders : 110,579
    Owners Enabled : Yes
    Can Turn Owners Off : Yes
    Can Repair Permissions : Yes
    Can Be Verified : Yes
    Can Be Repaired : Yes
    Can Be Formatted : Yes
    Bootable : Yes
    Supports Journaling : Yes
    Journaled : Yes
    Disk Number : 0
    Partition Number : 3
    Thanks

    Have you tried doing this first:
    Repair the Hard Drive and Permissions
    Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the 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. Now restart normally.
    If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
    If there are no errors reported then try the routine I suggested rather than trying to expand the existing partition just try to Add a second partition as you have tried before.
    If this still gets you nowhere, then I'm afraid you're left with having to repartition from scratch. You'll want to backup the existing files if you don't wish to lose them. I would then do this:
    Drive Preparation
    1. Boot from your OS X Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu.
    2. 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.
    3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID (for Intel Macs) or APM (for PPC Macs) then click on the OK button. Click on the Partition button and wait until the process has completed.
    4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
    5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
    6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
    When the above is completed quit DU and return to the installer. Complete the OS X installation.

  • Disk Utility stuck on "updating boot support partitions for the volume as required"

    Tonight when I mounted my Time Machine drive (a WD My Passport drive), it failed to mount properly, and I received a warning from Drive Genius that it needed repair. But when I launched Drive Genius, the disk would not show up.
    Through a series of mounts, unmounts, and sleeping the computer, I managed to get it to show up in Disk Utility, so I seleted "Time Machine Backups" under the main listing for the drive ("319.37GB WD My Passort..."), and clicked Repair.
    The detail window showed "Volume repair complete" almost immediately. But for almost four hours now, it's been stuck on "Updating boot support partitions for the volume as required."
    Meanwhile, Activity Monitor has been showing fsku_hfs taking 30%-85% of the CPU the whole time.
    Anyone have advice?

    Apparently not:
    Error: 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.
    But when I ran Disk Utility again this morning, not on the Time Machine Backup, but up the hierarcy on the level labeled "319.37GB WD My Passort...," I got...
    The volume Time Machine Backups appears to be OK.
    And now the drive seem to be OK.
    I think I'll still offload everything and reformat it.

  • Why wont my Disk Utility allow me to Reformat and Partition Seagate?

    When I plug in my new Seagate HD, via USB 2.0 cable to my Mac, the Seagate HD mounts on my desk top. When I open disk utility and select the Seagate HD in the left hand colomn, and then select the Erase tab in the right hand colomn to begin the process of Reformatting and Partitioning, none of the Volume Format selections high light. Everything remains dimmed and I am unable to move forward. I am able to use Disk Utility to Repair Disk Permissions for my Macintosh HD but nothing else!
    I am unable to find any kind of 'lock' or 'preference' for Disk Utility. The Disk Utility info under file >get info high lights Owner and Group with pull down options but it is not clear to me what pull down items I should select and if I am even in the right place.

    Not knowing exactly what you did, I'll describe what should be done:
    1. Open Disk Utility in the Utilities folder of your Applications folder.
    2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
    3. Set the number of partitions from the dropdown menu (use 1 partition unless you wish to make more.) Set the format type to Mac OS Extended (Journaled, if supported.) Click on the Partition button and wait until the volume(s) mount on the Desktop.
    4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
    5. Set the format type to Mac OS Extended (Journaled, if supported.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
    6. Click on the Erase button. The format process will take 30 minutes to an hour or more depending upon the drive size.

Maybe you are looking for