Mavericks/Disk Utility error msg:

Hi,
Started to have these problems:
Disk Utility msg:
Warning: SUID file “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent” has been modified and will not be repaired.
ACL found but not expected on “private/var/root/Library”
ACL found but not expected on “private/var/root/Library/Preferences”
Since upgrading to Mavericks my xhd is not seen when starting the iMac. I have to reboot it each time for the iMac to see it. It is also making sounds.

Hi,
Thanks for the reply.
I had problems with an update from DevonThink. That's why I ran Disk Utility.
I usually run it after I notice a problem. Then I do a restart.
The problem with the xhd-A is new. It started after the Mavericks install. During the install I also had a xhd-B plugged in, but no problem with that. I've run Disk Utility on xhd-A. Problem still exisits.
To recap when xhd-A is plugged in when I start my iMac everyday it isn't seen.
Then I unplug the xhd-A power cord, plug it back in, and it is seen.
To answer your question, I've already tried your idea. I ejected the xhd-A, shut down the iMac. Then restarted it, then plugged in the xhd-A and it is seen.
The specific problem is I can't leave xhd-A plugged in to the iMac. I have to remove the power cord, then plug in the power cord each time for it to be seen. Frustrating. This didn't happen in the past.

Similar Messages

  • 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 am in mavericks disk utility recovery mode as my mac book will not boot up & stays only on the grey apple screen. When I verify the disk I get open error5 :input /output error on Syst stuck on 1 minute pouring out over 50 error messages & still counting

    I am in Mavericks disk utility recovery mode as my mac book pro will not boot up & stays on the Apple grey screen . When I verify disk permissions I get
    Open error 5:"input/ output error" on syst with over 50 of this messages & still counting . Disk Utility says 1 minute
    But this has been going on for over 10 mins .
    I can not verify disk or repair disk .
    I have tried to reinstall mavericks operating system but it says my hard drive is locked which is very strange .
    Does anyone know what is going on here ?
    My system looks like it has been totally corrupted . Thanks Andrew

    Could be. The "lock" isn't actually looking for a password.
    WARNING: This will completely erase the ENTIRE hard drive.
    What you would need to do is boot to recovery > disk utility > select the MAIN drive on the left side > partition > change partition layout from CURRENT to 1 PARTITION > ensure on the right side it says Format : Mac OSX Extended (Journaled) then push APPLY.
    Then if it will allow us, close the windows until you see the 4 options popup again and select "Reinstall Mac OS X" select the Mac HD and you should be good to go!

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

  • Disk Utility error -206

    I am building a restorable image of 10.4.9 - or rather, trying to build an image, as I just ran into error -206 for the 2nd time.
    I add stuff to my source in logical groups, then make and test an image. The error occurs at the end of a block restore, when Disk Utility is comparing checksums (running in dutch, so this may not be the wording in english). There is no error message, aside from the number. The target volume is unmountable after this. File restore is OK, except for the odd invisible file turning visible. Block restore appears fine when I skip the checksum comparison.
    The 1st time it happened I made my 'install portions' smaller, and found that the error occurred after adding iTunes 7.1.1 to the image. However, now that it happened again with some 3rd party software I am really puzzled.
    My work volume runs 10.4.4, the source partition is on the internal drive, and my test partition is on a Lacie Porsche drive.
    So what's this error -206??
    Imac G5   Mac OS X (10.4.4)  
    Imacs G3 & G5   Mac OS X (10.4.4)  

    Cornelius,
    Both of your links seem to apply to OS 9.
    Yet, there may be something here, as they both indicate a problem with 'sound'; the msg itself claims a corrupt snd resource, and the app "Error codes" says it's a Sound Manager error.
    So I went looking in iTunes.
    In its Resources folder there's "Complete.aif".
    When I doubleclick this, it shows up in iTunes as "sappy.snd".
    Now I am really puzzled.
    FWIW: DiskWarrior 3 had a problem with the same aif file when Quicktime was updated to 7.0.x (forgot which one).
    I will see what happens when I remove this aif file, then post back.
    Another open point; I found I could block-restore an image with iTunes 7.1.1 if I checked 'skip checksum' in Disk Utility. The man page for asr calls this 'dangerous' but doesn't specify the dangers. Would you know anything about this?
    About my setup: I do not update my working volume. Instead, I start from scratch on a spare partition, then migrate when this turns out OK. I make and test images while building.
    Thanks (again) for your help.
    Imacs G3 & G5   Mac OS X (10.4.4)  
    Imacs G3 & G5   Mac OS X (10.4.4)  

  • Disk utility error message

    My daughter told me her Mac mini isn't booting up past the grey screen. I put in the install disk and started it up pressing "C" and used Disk Utility to attempt to figure out what's up. I got the following error message:
    Could not repair due to underlying task failure on exit (-9972)
    Does this mean the hard drive is toast? I don't have any HD repair software-with all my Macs I've never run across a problem that the boards here or Disk Utility couldn't fix for me. I don't know if she damaged the drive (she claims the cat chewed on the edge of the mini-sounds a bit like the "dog ate the homework"), or if it failed. It was purchased last year when Tiger was released, so it should still be under warranty. Any ideas about what I could try next?
    Thanks
    ~margaret
    17 iMac G4 1.25GHz 160GIG HD   Mac OS X (10.4.3)   G4 iBook, Mac mini, 10G iPod, iPod mini (pink!), Apple IIGS

    Dale, although the -9972 error is probably some serious data error on the drive, which can sometimes be solved by an Erase & Install of Mac OS X, the fact that the Hardware Test reports an issue probably means that the data error was caused by physical damage on the drive.
    I have to say that I find your post(s) most unhelpful. It' true that the informatin contained in them can be useful, however, you could have made the effort to sort it for iMargB. The fact that you didn't, plus your posting of the exact same post in two different threads, makes me feel that you are in a hurry, and that you sacrifice quality to quantity. Trying to help as many people as possible is a good thing, however, we are here to help (or to be helped), not to overwhelm people with information, hoping that they will figure it all out on their own.
    iMargB, the Hardware Test is not part of Mac OS X, it is a system-specific volume, which explains why it is included on your original disc rather than on the Tiger one. Your guess of using the latest OS's Install disc was a good one though, when it comes to using Disk Utility for example : attempting to repair a Tiger installation with a Panther disc is not a good idea, as it might damage it instead, because of the differences between Panther and Tiger.
    Although I know little about the Hardware Test's error messages, the "Master" part is not what would worry me, as it could just be the position of your hard drive's jumper (which could be Master, Slave, or Cable Select). However, if the Mass Storage test is failing, I would suspect a hardware issue with the drive itself. Hardware Test is known to miss a few things sometimes, but the reverse isn't true. Thus if it reports a bad drive, I think it is safer to assume that there is an issue than to assume that Hardware Test is wrong. Moreover, the "Invalid Node Structure" is very likely due to physical damage (as I already said), therefore, zeroing out all data and reisntalling Mac OS X or using Disk Warrior could be very temporary fixes.
    If you have a FireWire cable, I would suggest booting your Mini in FireWire Target Disk Mode to retrieve as much data as you can, with another Mac such as your iMac or iBook. Instructions can be found here. There may still be a chance that the other Mac could see the drive, so not all your data would be lost. Then, I would take it to Apple for repair, as the drive could be failing.

  • MacBook Pro Stuck in Recovery Loop; Disk Utility Error

    I am getting the error: Disk Utility Stopped Repairing "disk0s2" - says disk utility can't repair the disk and I will need to reformat the disk and restore my files. This appears to be the startup disk (could be wrong) - as I am currently in recovery mode and any time I reboot, I am taken back to recovery mode and there are no start-up disks available to be selected.
    When I run Disk Utility on my Internal HD (or what appears to be - this is 250 GB Hitachi) - I get the all clear that everything appears to be working correctly.
    I do have TMbackups saved to a NAS. My MacBook Pro has been running very slowly as of recent (slight boost after upgrading to Yosemite, but then returned to slow performance).
    I am running OS X Server on it - and have considered migrating that to a Mac Mini (yet to be purchased) - but want to get a better idea of options before I pull that trigger. I also want to make sure my MacBook Pro is recoverable and can still be used.
    1. What is the risk of reformatting just the startup disk "disk0s2"? Is that even possible?
    2. Is MacBook Pro in need of service at the apple store? Or can this be completed by me? (I have above average ability, but no wizard)
    3. My logic on best practice to recover MBP and then add Mac Mini, migrating OS X Server to it: (all recommendations/suggestions welcome)
    a. reformat MBP startup disk
    b. restore TMbackup
    c. use migration wizard to migrate OS X Server to Mac Mini
    d. reformat MBP again, starting from scratch and install fresh copy of Yosemite
    I had also considered just a fresh build of OS X Server on a new Mac Mini and starting fresh with the MBP. I don't use a ton of services on OS X Server so think my rebuild would be less time intensive than most.
    Appreciate all the feedback.

    Well, your hard drive (flash storage) is good, at least. Here's what I would try next (before making a trip to the Apple Store or an AASP):
    Boot into your Recovery partition and reinstall OS X. This won't damage or erase any of your user files, etc., just give you a fresh installation of Mountain Lion. Since your hardware seems to be OK, it could be that the system has just become corrupt and reinstalling it may 'fix' the problem.
    Call back if that doesn't work...
    Clinton

  • Disk Utility Error "no valid packages"

    Hi,
    I have a PowerBook G4 with 1GB RAM.
    I've noticed a significant system slowdown lately. Programs take longer to open and respond, and it's rather annoying. I came to the forums to seek some remedy, and tried to run a Disk Utility to check that everything there is at least okay. But when I click on verify permissions, I get an error that says "no valid packages." Does anyone know what this means and how to fix it (if it needs fixing; I'm assuming this isn't a good thing, whatever it is!).
    Thanks.
    Lori

    Hi librarygirl and Welcome to the Discussions!
    Mac OS X 10.3, 10.4: Disk Utility shows a "No Valid Packages" alert
    Disk Utility can't verify or repair permissions on the Mac OS X 10.3 or 10.4 volume if the "BaseSystem.pkg" file is not in /Library/Receipts.
    This alert appears when you try to repair permissions with Disk Utility:
    "First Aid failed
    "Disk Utility stopped repairing permissions on '(volume name)' because the following error was encountered: No valid packages"
    In the Disk Utility text window, this message appears in red text:
    "Error: No valid packages (-9997)"
    This happens when the BaseSystem.pkg file is not in /Library/Receipts.
    Solution
    If you've moved this file, move it back to /Library/Receipts. You shouldn't normally remove any files from /Library/Receipts.
    If the file has been deleted, replace it by copying it from a different computer that uses Mac OS X 10.3 or 10.4, or by reinstalling Mac OS X 10.3/10.4 from an installation disc.
    "Reinstall" means you can install 10.3 or 10.4 from a disc, if it's the same version of 10.3/10.4 (such as 10.3.3 on both the installation disc and computer). If the version of 10.3/10.4 on the computer is newer than what's on the install disc, then use the install disc to perform an Archive and Install installation instead, then update to a later version of Mac OS X.
    Joe

  • Disk Utility Error-Please Help

    I tried to repair my hard disk. I couldn't repair straight away as the repair button was greyed out so I varified the HD. The message came up:
    *Disk Utility*
    *First Aid*
    *Disk Utility stopped verifying “Macintosh HD” because the following error was encountered:*
    *The underlying task reported failure on exit*
    The result of the varifacation was:
    *Verifying volume “Macintosh HD”*
    *Checking HFS Plus volume.*
    *Checking Extents Overflow file.*
    *Checking Catalog file.*
    *Incorrect size for file objects.nib*
    *(It should be 0 instead of 4514)*
    4514
    *ng multi-linked files.",0)*
    *Checking Catalog hierarchy.*
    *Checking Extended Attributes file.*
    *Checking volume bitmap.*
    *Checking volume information.*
    *he volume %@ needs to be repaired.",1)*
    *Macintosh HD*
    *Error: The underlying task reported failure on exit*
    *1 HFS volume checked*
    * Volume needs repair*
    Could someone please advise me how to fix this.
    Thank you.
    Simon

    You can only Repair Disk from a different boot volume so boot from your Tiger installer disk, select your language and then from the menu>Utilities>Disk Utility. select your hard drive and then Repair Disk. If Disk Utility can't repair it you will need a stronger utility like DiskWarrior to rebuild the directory.

  • Disk utility error when erasing an external hard drive

    Hi,
    Not sure if this is the most appropriate fourm list to post this but I thought I'd give it a try.
    I am running snow leopard on my MBP and am trying to use disk utility to erase and format an ext. HD.  While the disk icon does not show up on the desktop when I connect it to my mac, Disk utility does show the ext. hd in the left column, but no matter what format I try, even just using one partition and selecting zero out all data, I get the following error: "disk erase failed with the error: POSIX reports: The operation couldn't be completed. Cannot allocate memory".
    Is the hd dead?  Are there other options?  I do have disk warrior, version 4.1.1 and it does not regonize the ext. hd.
    Please advise.
    Thanks,

    Thanks for the reply. Yes, I did select the ext hd as the one I wanted to erase (my internal hd is my start up drive). After I selected the ext hd, (there is no volume listed under it so the only thing I can select is the hd itself). that is when I selected erase and then Mac journaled, then named the hd and then after selecting erase, I got the error. Also as a matter of note, if I select firstaid, both the repair and verify permissions are dimmed, so I can't even try to repair the disk. That is when I tried disk warrior hoping that could examine the hd, but since it is not mounted on the d/t, it doesn't show as a drive to check. I don't understand why the ext hd shows up in disk utility, but not the d/t. Also of note is the fact that when I connect that ext had to my Mac with a fw cable, a window opens saying that the drive is not readable and do I want to initialize it or ignore. I choose to initialize and that is when I get the error. Also of note is that I have tried both security options of "don't erase data" and "zero out data" and still get the same error.
    Hope this clarifies things a bit.

  • Is my HD Dead? Reformat Disk Utility Error: secure disk erase failed with the error could not open disk.

    Hi,
    Fed up with seeing the spinning beach ball I decided to reformat my MacBook Pro...
    After backing up everything on an external hard drive I put in the OSX install DVD, restarted the machine and held down 'C'.
    I followed the install prcedure, clicking next a few times etc...
    I then went into Utilities > Disk Utility. I chose 7-Pass to erase the Macintosh HD and set it off erasing.
    I checked the process an hour in and message on screen read:
    Secure disk erase failed with the error:
    could not open disk
    The internal hard drive no longer exists in the disk utility so I cant retry erasing it.
    The only thing that appears in disk utility is the OSX install DVD.
    I can't even shut down the mac as everything under the apple tab is greyed out!
    I'm guessing this means my hard drive is broken right?
    If anyone has any other ideas of what to try I'd really appreciate that.
    How do I turn the machine off?
    If my hard drive is gone then should I consider getting an SSD drive?
    Any recommendations for such a drive would be great.
    Hope you can help!

    Did you partition the drive?
    Extended Hard Drive Preparation
    1. Open Disk Utility in your Utilities folder. If you need to reformat your startup volume, then you must boot from your OS X Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger or Leopard.)
    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. Click on the Options button, set the partition scheme to GUID (only required for Intel Macs) then click on the OK button. 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.) 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.) 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.
    Steps 4-6 are optional but should be used on a drive that has never been formatted before, if the format type is not Mac OS Extended, if the partition scheme has been changed, or if a different operating system (not OS X) has been installed on the drive.

  • Disk Utility Error 61 when attempting to create disk image on external driv

    I would like to make occasional archive backups of my three macintosh computers. I bought a new Western Digital 2TB drive for this purpose, and formatted it as Mac OS Extended. Trying to do a disk image backup using Disk Utility, I follow the directions:
    - Startup from an install DVD.
    - Start Disk Utilities and select "Restore"
    - Drag "Macintosh HD" into the Source box
    - Click on "New Image" and select compressed and 128-bit AES encryption
    This leads to the error message: Unable to create "....." (error -61)
    I have enocountered this problem both with my iMac G5 and a MacBook, both running Leopard.
    Does anyone know what this error means, what I am doing wrong, and/or if there is another way to create disk image backups? Help!

    1. For reasons I don't know disc images seem to become more fragile the larger they get. They also can be subject to file corruption that affects the entire disc image, whereas file corruption on a clone would only affect certain files.
    2. You cannot put multiple clones on the same volume. Each clone must be on a separate volume, but you can have multiple volumes on a single drive simply by partitioning the drive accordingly. Of course you need a drive large enough to accommodate each clone. Each clone should be to a space equal to the capacity of the cloned drive.
    3. I'm not a big fan of TM, although I must confess it has become more reliable since it's release, especially with Snow Leopard. However, there are many backup utilities that can create clones, perform incremental updates, and archive changed files. See the following:
    Backup Software Recommendations
    Carbon Copy Cloner
    Data Backup
    Deja Vu
    Silver Keeper
    MimMac
    Retrospect
    Super Flexible File Synchronizer
    SuperDuper!
    Synchronize Pro! X
    Synk Pro
    Synk Standard
    Tri-Backup
    Others may be found at VersionTracker or MacUpdate.
    Visit The XLab FAQs and read the FAQ on backup and restore. Also read How to Back Up and Restore Your Files.

  • Worrying Disk Utility Error Message

    When I click verify disk in Disk Utility, a worrying error message comes up saying " The underlying task did not complete on exit" giving the error message
    Verifying volume “Macintosh HD”
    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.
    Invalid volume free block count
    (It should be 24694657 instead of 24694833)
    The volume Macintosh HD needs to be repaired.
    Error: The underlying task reported failure on exit
    1 HFS volume checked
    Volume needs repair
    I can't repair the volume as it is greyed out.
    Help! This is a brand new MacBookPro, I've only had it a couple of days!

    So far I have never had any problems with them personally so I don't do an Erase & Install.
    I'm sure we're all happy for you although problems do happen. Problems with the installation and even hardware problems. Thing is, often these issues aren't apparent until some time later.
    The way I see it, the time and effort required to do an "Erase and Install" (which include a zero write to the drive) is a known… about 3 hours. To my mind, even there's a remote chance that this stops a potential problem in its tracks before it's a problem it's worth the time spent. 3 hours over the lifetime of a Mac OS X installation is not a lot to give up.
    Additionally, by zero writing to a drive, it does allow you to see if your drive is on one way performing correctly. All four of my 300GB drives in my Mac Pro wrote zeros within one minute of each other. I know these drives won't have issues when being told to write a ton of data. Whithout doing this I would never know.
    Now I did the same thing with my parents' 750GB drives and one finished in 3 hours and the other was still going at 5 hours. Now you can't tell me there's not something up there. So at what point would you like to have found that out?
    How much time, let alone money, does it cost to do something later on?
    Just like tools like Monolingual. How many issues with updates are caused by such tools? Again, how much time is lost to debug and maybe fix such issues? Thing is, we don't know although if you had a customised installation from the outset it wouldn't matter as you wouldn't be using such tools.
    But hey… everyone's got their own opinion. All I know is that my systems always seem to go better and faster than every other Mac owners I know.

  • Disk Utility Error Message-Bootable USB/ExternalHD

    I'm using Disk Utility at the moment to create a bootable USB/External HD ( I've tried both ) and nothing is working. It comes up with a error message. I have the retail Snow Leopard DMG and i'm doing everything correct user wise. It's just something is wrong with Disk Utility in my opinion..
    Error message (60) restore failure.
    So now my question is.. I's there a alternative for creating a bootable usb/external harddrive. CCC only allows for the copying of your Macintosh but I want to create a bootable drive. Please someone help fast.

    Hello, have you used Disk Utility to Repair the External Drive?
    Might try Carbon Copy Cloner...
    http://www.bombich.com/software/ccc.html

  • Disk Utility Error Message - Missing EFI + MediaKit

    Previously setup was with 2 partitions, one for normal use while the other had the Lion Install ESD on it, used when I installed some time ago. The other day my machine suddenly shutdown and when I started it, it stated that the Lion Install ESD partition was corrupted.
    I created a new Lion Install ESD partition and made a clean install (I was going to do so anyway).
    My machine is booting fine, but it acts funny in the Disk Utility. First, an overview of my disk:
    However if I attempts to "Verify Disk" on my disk (not on a specific partition) via the Disk Utility the following error is shown:
    Even more strange is when I attempt to let the "Macintosh HD" use maximum space on the disk. It is currently sized at 230GB, but if I use the Disk Utility to increase it to say 231GB it reports the following error:
    However, the space is clearly unused. And if I simply drag the partition down to use all the space the error will not prompt but nothing will happen.
    In the time between my first install of Lion and the recent shutdown I had installed rEFIt after attempting to run Ubuntu, however it was quickly uninstalled again with no issues in the following months.
    So, any clue what is going on with my disk?
    Thanks in advance!

    Maybe some added info will help. I have no problems starting the machine and using it. It's just that when I went to fix permissions and accessed disk utility from the hard drive to do it, I got the error message noted in my first post. I am wondering why that is, since it didn't happen before. I did use my 10.4 OS disk to start up just so I could fix permissions (that did fix permissions), but trying to repair the disk (to hopefully fix the problems I was having when I tried to access disk utility from my HD) didn't work. That's when I got the second error message. Is that because I've upgraded my OS to 10.4.11? I did that w/the Apple on line upgrades, so I don't have a 10.4.11 disk. Is that the problem? Also, do you know if there is a 10.4.3 upgrade? Thanks.

Maybe you are looking for

  • Can't open iDVD project

    Help needed I had account for my niece and she was playing with iDVD creating her own projects. After I have reinstalled everything, I created account for her with different name and none of her projects open anymore! The error is "Project locked by

  • FM to check if password fits SAP policy

    Hi, is there an FM/method to check if a password would fit the current sap password policy? e.g. it has to contain upper- and lower letters etc.. Thx a lot

  • Training and Events Workflow - Approval

    Hi, Whenever a course booking(request) is done we need to have it approved before finally booked. It looks like the course is always booked (not requested) if the employee has authorization for booking. Despite this, I've managed to trigger the workf

  • How to change the posting periods

    HI, could anyone tell me that how to change the posting periods in SD module regards, chary

  • [Fix Request] qt4-qtruby

    I've been trying to get qt4-qtruby to build, without much success. The error I get seems to be well documented, but nobody knows how to fix it as far as I can tell. [ 33%] Generating smokedata.cpp, x_1.cpp, x_2.cpp, x_3.cpp, x_4.cpp, x_5.cpp, x_6.cpp