Missing Partition after "Task reported failure on exit"

I have been getting this error on an external SATA drive
after power failure caused the system to go down. I erased
all the data and it went away. Then I partitioned the disc
into 2 parts using one part as half of a 2 disc mirrored RAID
the second disc being a firewire disc. After deciding that
this was not the ideal situation for the discs, I decided to
return the data to the original setup. During the process
of copying the data back to the firewire drive, I got an error
that one of my Apple Loops was unreadable. Running Disc
utility on the partition I got the 'failure on exit" again. Then
the patition which DU unmounted would not mount again.
I have tried repairing from the startup DVD but it did not work
This was before this current situation. Any suggestions?

Even though Disc Utility would not mount it on the desktop
it did know it was there. So I used it to erase and zero out
the disc, which allowed it to be mounted again.

Similar Messages

  • TS2570 After performing a "disk repair" a message in red indicates "Error: The underlying task reported failure on exit.

    Can someone help me with this issue. I can't install disk and restart my Mac it indicates verify permissions for Mac OSx install disc 1, the red error message states the underlying task reported failure on exit. I cannot start up my Mac and I am concerned that I lost my files.

    Just check the steps you are making are the same according to this help page.
    Resolve startup issues and perform disk maintenance with Disk Utility and fsck

  • Another  "Underlying task reported failure on exit " Disk Utility Problem

    So a Problem (at least for me)
    I've got an old Powerbook G3 266mhz (headless) acting as a server. It had been up for 258days, and then 2 days ago we had a lightning storm. No big deal, except the cable line got hit, flew through the line and fried my cable modem. In the process of pulling out the modem, I accidentially unplugged my 'server' Plugged it back in, think it crashed, tried again, and then nothing. Thats the story anyhow here's what I've done:
    1) managed to boot into the bootloader, did dev /hd .properties (or something like that) and it couldn't find my HD (oh boy)
    2) Got out my 10.3 Install disks, booted off them and ran disk Utility, One partition is fine, the other (my primariy) is showing up as disk0s9 instead of 'Nitrogen' not mounting, and when I 'repair disk' it starts okay, and then does this:
    -Checking catalog file
    -<red>Invalid Key Length</red>
    -<red>Volume Check Failed</red>
    -<red>Error: The underlying task reported failure on exit (-9972)</red>
    3) I checked through the forums and the mentioned 10 different possible reasons for the 'underlying task' error, 'Invalid key length' was not among them.
    I do have data on there I want to try to get off, (currently I am downloading ubuntu for PPC to see if I can boot off that, access the drive, and dump it to a networked drive.) As this is an old machine I don't actually have any computers with SCSI connections etc.
    Any suggestions would be GREATLY appreciated
    Thanks
    G3 Powerbook 266   Mac OS X (10.3.9)   (missing powerbook screen (it fell off long time ago)

    For what its worth, I went and purchased a copy of Disk Warrior, and was able to get it mostly cleared up Here is what I did do.
    -Tried to install Mac OSX 10.3 on the second partition: Said my mac was unable to install 10.3. Which is funny because I had 10.3.9 running on this computer.
    -Installed Mac OS 9 on the second paritition. This worked though sometimes had issues on booting.
    -Purchased DiskWarrior (download version): Tried to create 10.3 Startup disk, but for some reason couldn't get it to boot from it. The computer kept booting to OS 9. So I copied over the OS 9 Diskwarrior to the second parition.
    -I had to reboot in 'extensions-off' mode (hold shift after boot chime) in order to get DiskWarrior to work.
    -Disk Warrior recovered and fixed many issues, So I was able to reboot from OSX on the broken drive. However there still seem to be some remaining problems. I am currently in the process of trying to remove all important data and back up so that way I can wipe the HD and reinstall.
    Hope this helps anyone else

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

  • External Hard Drive: Error: The underlying task reported failure on exit

    I have a LACIE external drive (120GB/ firewire) which has had no problems. Recently, I reformatted to DOS so I could use with a PC. Now, when I plug into my MACBOOK Pro, the drive is not 'recognized. I've tried to repair with Disc Utility but I get the following messages:
    +Error: The underlying task reported failure on exit+
    and
    +1 volume could not be repaired+
    Reading up on the subject, seems I could purchase Disc Warrior but I've also read that there might be a problem with 10.4.10 which potentially could be alleviated by rolling back my OS.
    Before I shell out for DW; does anyone have any thoughts on rolling back the OS or perhaps other ways to resolve? What is the correct method for rolling back to a previous OS?
    Best,
    Rod

    Hi guys, I just received the same message on my G5 with a hard drive that I've been using for about two years. Today when I turned on my computer, I saw the icon for my second internal hard drive which is a Western Digital 250 Gb. When I clicked on the icon in finder, it didn't show me any files on my drive and soon after, the icon just vanished. I turned off my computer and made sure that all the connections where in properly and they were. I also tried other hard drive to make sure there was nothing wrong with the connectors, and they worked fine. When I go to disk utility, I see my hard drive but its not bolded, the title of the drive is faded and if I try to verify disk or repair, I get the Error: The underlying task reported failure on exit (-9972) 1 volume checked, 0 HFS volumes verified, 1 volume failed verification.
    I've had hard drives die on me before and I know where they are going to go due to the sound that it makes but today my computer was as quiet as can be. What is the problem here and is there something I can do to get the hard drive to work so I can retireve my data?
    Thanks

  • MacBook won't boot - Error: The underlying task reported failure on exit

    My wife's new MacBook won't start up. It crashed earlier today and when she tried to restart it, it got as far as the gray Apple logo and the spinning gear and then it reboots again. I booted it with the Leopard install disc and two strange things happened.
    1. When the installer first opens, it gives me an error that says I cannot install Mac OS X on this computer. This is a 3 month old MacBook that shipped with Leopard, but it's telling me that OS X can't be installed.
    2. When I run verify or repair permissions with Disk Utility from the Leopard disc, I almost immediately get an error stating "The underlying task reported failure on exit". When I try to verify or repair the disk, it says everything is fine.
    The HD appears to be fine. I can access it from Firewire Target Disk Mode and everything is still there. I can also boot into Single User Mode, but not Safe Mode.
    The night before the crash I made a change to the HD permissions via "Get Info". I copied the "Read/Write" settings to all enclosed folders because it was telling me that it couldn't install Flashplayer because I didn't have sufficient permission, even though she has an Admin account. After the change, Flashplayer installed just fine and everything was OK until this afternoon when she had a kernel panic while iChatting. iChat was the only program open at the time. She rebooted and hasn't gotten past the gray Apple logo since. I read in some other threads about people having the same issue after accidently setting HD permissions to "none". One suggestion was to use Firewire Target Disk Mode to open the drive with another computer and change the permissions back. I tried that, and the drive opened just fine, as I mentioned, but the permissions didn't appear to be set in a way that would cause problems. I set all of them to read/write and applied them to all enclosed folders just to be sure, but nothing changed when I rebooted.
    Any other suggestions will be much appreciated. Thanks!

    ndelc wrote:
    When I looked at the permissions for the HD in FW Target Disk mode, it was set to:
    System: Read/Write
    Admin: Read/Write
    Everyone: Read Only
    This is not your problem unless you have changed the r/w for special accounts elsewhere.
    I have the same on my HD. But it's the individual files that are important.
    Nothing there indicates that it should be locking her account out.
    How do you create a new admin account from the Leopard DVD? It wouldn't allow me to do much of anything except Disk Utility.
    I have not done it so I don't know, but there is a way to create a new administrator account using the DVD. Search these forums because I know others have done it.
    Would it be possible to attempt to change things back by booting into single user mode? If so, what do I need to do?
    I am not sure you can even boot into the Single User mode, or do you mean the Super User mode?
    You have taken write privs away from everyone so I believe only a Super User can fix it. I am not even sure the Sudo will work in your case.
    Thanks for your help!
    If you find out how to access your drive from the Leopard DVD, you need to invoke SU privileges and undo whatever it was you did.
    Were you using Time Machine? That would make fixing it a piece of cake. Just revert to the last backup before you made these changes.
    Message was edited by: nerowolfe

  • The underlying task reported failure on exit

    Hi All,
    I keep getting the following message when I try to verify disk and like to know if this is a known issue. Perhaps someone has solution for it, thanks for reading:
    Verifying volume “Macintosh HD”
    Checking HFS Plus volume.
    Checking Extents Overflow file.
    Checking Catalog file.
    Incorrect size for file temp536402
    (It should be 0 instead of 461405)
    Incorrect size for file temp539155
    (It should be 0 instead of 16128)
    Incorrect size for file temp539163
    (It should be 0 instead of 980)
    Incorrect size for file temp539983
    (It should be 0 instead of 93392)
    Incorrect size for file temp540015
    (It should be 0 instead of 4481)
    Incorrect size for file temp541051
    (It should be 0 instead of 4795)
    Incorrect size for file temp541091
    (It should be 0 instead of 4789)
    5 %)
    Checking multi-linked files.
    Checking Catalog hierarchy.
    Checking Extended Attributes file.
    Checking Extended Attributes file.
    e bitmap.",0)
    Checking volume information.
    The volume Macintosh HD needs to be repaired.
    Error: The underlying task reported failure on exit
    1 HFS volume checked
    Volume needs repair

    Just to be sure: are you checking using the DVD/CD? That is after having re-booted using the tiger DVD.
    If not, do so. Disk Utitlity's results are more accurate when stared from another disk than the one currently being checked.
    If the problem occurs using the DVD's DU and repair proves impossible then you have three options
    Buy a disk repair software such as DiskWarrior (a bit expensive)
    Clone your HD on an external drive, erase and install and then use the migration assistant to get most of the info back. (slow but safe)
    Clone your HD on an external drive making sure the clone is bootable. check the external HD with DU, startup with the external HD, see if everything works well and then erase the internal HD to clone back. (a bit faster but less safe: some subtle errors can get carried over)
    If you have any doubts don't hesitate to post back for more details and whatever you do: backup, backup, backup!

  • The underlying task reported failure on exit (-9972)

    my lacie has worked in the past
    now it will not show up on my osx desktop
    i can get to it in os9
    and it shows up in the disk utility as grey
    when i try to repair remissions it says
    "The underlying task reported failure on exit (-9972)"
    does anyone else know how i can get it back?

    Hello nooneever,
    You might find the following useful in dealing with your -9972 error (depending on the text which accompanies the error):
    The following was contributed by Fumiaki Kawashima. Edited by Kappy.
    The error message, "Error: The underlying task reported failure on exit (-9972)" is a serious filesystem error in the Mac OS X Core Foundation. The problem can also lead to other critical errors such as "Keys Out of Order," "Invalid node structure" and/or "Invalid sibling link." The causes and scenarios vary. Troubleshooting a solution may depend upon computer configuration and whether the -9972 error is accompanied by other critical errors. This issue can also lead up to a kernel panic. If the error occurs when an external FireWire device is connected, disconnect it until you verify the device's compatibility.
    Symptoms:
    In most cases, you are unable to restart from Mac OS X.
    * A volume is grayed out or not mounted with or without a kernel panic.
    * A folder with a flashing question mark may appear.
    * A bad partition map may be reported.
    * A target disk mode solution may not work.
    * Most likely, Disk Utility, TechTool and DiskWarrior cannot fix the issues.
    * The high level disk format (Standard format) may unable to perform.
    * You may unable to re-initialize the hard drive.
    * A disk physically malfunctions in the worst case.
    Example of an accompanied error message:
    DiskWarrior normally fixes 1 to 6, but cannot fix errors 7 to 10 if the symptoms are very bad. There is no definite case.
    01. Volume check failed
    02. Invalid B-tree Header
    03. Invalid map node
    04. Invalid extents entry
    05. Invalid clump size
    06. Incorrect block count file
    07. Invalid node structure
    08. Overlapped extent allocation
    09. Keys Out of Order
    10. Invalid sibling link
    Possible causes:
    * Third-party FireWire device or enclosure, or other peripheral devices.
    * Third-party mass storage drives or PCI card issues.
    * Incompatible third-party kernel extensions.
    * Mac OS X installer disc is improperly treated.
    HTH
    Jeff
    Mini 1.25, 512 AP/BT; 12 Al PB 1.5, 512 AP/BT   Mac OS X (10.3.8)   Wireless KB/Mouse, AEBS, 80 GB OWC FW HD

  • The underlying task reported failure on exit--what do I do?

    Long story short: Quicksilver G4 OS X 10.4.11 got stuck with the spinning color wheel using Eudora email, couldn't Force Quit, eventually it froze completely. I pulled the plug, restarted and ended with a blank blue screen (after the Apple logo and startup "wheel"). Reset the PMU, no difference. So I booted from the Tiger install DVD and got to Disk Utility. First, it didn't recognize any hard drive. So, I switched batteries, restarted, and the hard drive showed up. So I ran DU again, and came up with "the underlying task reported failure on exit" about 2/3 of the way through repairing the HD. Now I'm stuck.
    My questions:
    What difference did the battery make and why?
    What do I do to repair the HD now?
    Thanks!

    Odell:
    As roam indicated Disk Utility reports "Underlying task reported failure" when repairing a volume is a serious directory error that cannot be repaired by Disk Utility. The article linked suggests the use of a third party utility. Disk Warrior, recommended by roam, is one of the best utilities for this kind of work. Tech Tool Pro is the other utility of choice for this kind of work.
    If you do not have a current backup of your data, you should look to that immediately. If you have your data backed up, another approach would be to reinstall the OS choosing the Archive and Install option.
    Although this error is essentially a directory error, it can, and sometimes does, be rooted in a hardware issue, e.g. a failing/failed Hard Disk Drive. I suggest that you boot from the Apple Hardware Test disk and run all tests in a loop by holding down Command + L during the tests. It sometimes takes many many repetitions and several hours to detect intermittent issues, so leave it run and check on it occasionally.
    cornelius

  • The underlying task reported failure on exit - what do I do next?

    Hi,
    I recently decided to verify my internal drive using Disk Utility. The programme went through the motions then I got the following message:
    'First Aid failed
    Disk Utility stopped verifying “Internal Drive” because the following error was encountered:
    The underlying task reported failure on exit'
    In the progress window it read:
    Volume Header needs minor repair
    The volume The volume I Drive needs to be repaired.
    Error: The underlying task reported failure on exit
    1 HFS volume checked
    Volume needs repair
    I have no idea what this means or what actions I need to take next - can anyone help me out?
    By the way, everything seems to be working just fine otherwise apart from Front Row which hangs whenever I try to access media
    Your sincerely
    Very worried of London

    Hi there,
    You need to boot from your Install disk to actually repair it.
    "Try Disk Utility
    1. Insert the Mac OS X Tiger Install disc that came with your computer, then restart the computer while holding the C key.
    2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, you must select your language first.)
    *Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
    3. Click the First Aid tab.
    4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
    5. Select your Mac OS X volume.
    6. Click Repair. Disk Utility checks and repairs the disk."
    http://docs.info.apple.com/article.html?artnum=106214
    Then try a Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
    (Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.

  • Verify disk permissions: Error: The underlying task reported failure on exit.

    I need help. My iMac has been doing weird stuff for awhile but now it's just out of control. I did a system restore from a time maching backup and I thought things were okay, but then I rebooted in safe mode just to see if it would help with the "slow" problem I had after the restore. Well, all I could get after that was a black screen. So I booted up from my install disk and ran verify disk permissions and got this error code: Error: The underlying task reported failure on exit.
    I've also seen: Invalid node structure, etc.
    I hope someone can give me some good advice. I've thought about purchasing Disk Warrior but am trying to put it off as I don't want to spend $100.
    Thanks for any help.
    Vicky 

    Try this:
    Repair the Hard Drive
    Boot from your Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported, then quit DU and return to the installer.
    If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.

  • Repair Disk Permissions Error: The underlying task reported failure on exit

    Hi All...
    any idea about this error when trying to Repair Disk Permissions using "Disk Utility" :
    "Error: The underlying task reported failure on exit."
    No repair is made at all! It just stops right after being launched
    It happens either when booting on the Leopard CD or on external FW drive...
    Cheers guys!!

    riccopicco wrote:
    I've finally gave in, and bought an iMac.
    Transferred my old G4 to the new, fesh, Leopard installed iMac Intel chip....
    I've been getting the same thing just after 1 week with this new system!!!
    Someone help!!!
    It sounds as if you transferred the errors when you migrated your files from the G4. Something in that old filestructure that is not right. It might be the ownership of a single file somewhere.
    Have you considered DiskWarrior?

  • HELP! "Error: The underlying task reported failure on exit"

    Hello, I run the disk untility earlier today, and after I have done "verify disk permission, repair disk permissions and verify disk", the following message came up, however, the last option "repair disk" is shaded, I can't choose to repair the disk.
    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.
    Volume Header needs minor repair
    The volume Macintosh HD needs to be repaired.
    Error: The underlying task reported failure on exit
    1 HFS volume checked
    Volume needs repair
    Can anyone help with this error please? I just had my apple for a week, it's Macbook Pro.... Thanks a lot.
    Catherine

    Hi Catherine,
    Disk Utility can't repair a disk from which the system itself was booted.
    To do a repair of your "Macintosh HD" put the OSX Install-Disk in your optical drive, restart the MacBook and press and hold down the 'C'-Key.
    The system will boot from the OSX-DVD and will ask for the language.
    After that the Installation Programm will (no worry), but don't install anything just choose from the Top Menu "Utilities" the Disk Utility and then you can repair your HDD.
    Good Luck
    Stefan
    Please use the "Question Answered" and "Points Systems" (if appropriate) as it does indicate to others the need for help, or a possible answer for others with a similar problem.

  • More Permissions Error: The underlying task reported failure on exit

    PowerMac G5, OSX 1.5.1, 8.5 gig ram and MacBook Pro, 2.16 Ghz, 3 gig ram OSX 1.5.1
    The end result: G5 will not boot. It stops at the start up screen (i.e. apple logo with spinning icon) the MacBook lost all user accounts and required a complete erase and install.
    The preceding issues:
    1. I had wanted to connect my many macs at home over my LAN. I was having problems getting my G5 and my MacBook to connect with each other over network. The G5 logo would show up as a device, but would not open.
    2. The MacBook would allow some folders to be seen, but not others.
    3. On the folders I could see, some would allow me to transfer a file or doc into them and some would say I don't have the permission. Sometimes authorization was asked for and it would transfer a file, other times it would not. When I was not allowed to transfer a file, I found that if I removed the file that would be overwritten from the folder, I could then transfer the file.
    4. I tried to change the sharing and permission settings on these files with no success.
    5. The end result, as noted above was the MacBook would not boot. It showed the hard drive logo on the desktop with a red circle with a minus sign in the middle. I did a erase and install of OSX and reinstalled everything from the original sources.
    6. Now the G5 would see the MacBook, however 2 of the MacBook folders seen on the G5 had a circle with the minus sign. Everything else worked as expected.
    7. I repaired permissions on the MacBook. (incidentally, it takes forever). I also ran the disk repair which showed no problems. Still, the folders had the circle and the minus.
    8. I then ran permissions repair on the G5. Since, Leopard it takes hours on the G5, and went to bed. The next morning it was exactly as I left it an no progress had been made. I stopped the repair and restarted. The restart stopped at the apple logo.
    9. I started from the OSX disk and ran permission and disk repair. Disk repair showed no problems, but permissions stopped immediately reporting "the underlying task reported failure on exit"
    10. I have Time Machine set up, but it seem that all restoring the drive would accomplish would be to set it back to the state with faulty permissions.
    11. I've read through the posts regarding this problem and have found no solution, save reinstalling OSX. It looks like there is something wrong with the permissions and sharing functions in Leopard, that Time Machine in not a complete solution to backup and that I will be doing a erase and repair on the G5.
    LR

    Repair permissions always reports a bunch of stuff.  Ignore it if it says it completed successfully.
    Also note that is it usually a waste of time (except maybe after a system upgrade). 

  • Error: The underlying task reported failure on exit - PLEASE HELP

    After running Verify disc I keep getting the following message, What does it mean and how can I repair it? - the Repair disk option is always blanked out;
    "The volume Macintosh HD needs to be repaired.
    Error: The underlying task reported failure on exit
    1 HFS volume checked
    Volume needs repair"

    Maybe make a clone backup of the entire drive to an external FW drive that you can boot from.
    Cloning a drive with directory damage, or corrupt data will result in the exact same errors. If the original isn't able to boot, most likely, the clone won't be able to either.
    Backups are to protect your data when trouble strikes. After trouble rears it's ugly head, it's too late for clones. Manual (drag and drop) copying of the file can be accomplished, as long as the troubled drive mounts.
    Once the original has been repaired, then cloning is once again a good backup protocol.

Maybe you are looking for