"verify disk permissions" and "Underlying task reported failure on exit"

This is more of a "How I fixed this problem, so others can benefit" posting than a current problem.
I put my MBP to sleep yesterday, and then when I tried to come out, it just sat there. After about 15 minutes, I figured I'd just force it quit and then restart.
After hitting the power button, it came up with the gray screen and apple logo with spinning gear and basically sat there for 20 minutes. Several reboot attempts were failures; sometimes I got a blue screen with spinning gears, but basically not much else.
I tried rebooting with the install disk, holding down the C key, but it gave me nothing, tried rebooting in verbose mode, tried doing CommandOption+PR, nothing, etc. So, I tried rebooting while holding down the option key, and I could see the Disk Utility.
I ran the Disk Utility to verify the disk, and that all came back fine. So, I ran Verify Disk Permissions, and i spit out "Underlying Task Reported Failure on Exit". The phone support people suggested I try reinstall with archive.
So, I tried running install with Archiving, and that failed as soon as it verified the DVD was ok - basically it couldn't access the HD.
So, I rooted around and did the following. From the Install disk, I selected "Terminal". Then, I did:
cd /Volumes
ls -lt
There I noticed that for some odd reason, Macintosh HD was listed as the following permissions:
rwxrwx---
So, admin and group had read-write-exec access to the Mac HD, but others had nothing, which I thought odd. It seems like you should at least be able to boot the computer to the login screen, and if a user is not admin or admin group, you cannot login, but I guess that's not the way it's set up.
So, I tried:
chmod o+r Macintosh HD
Then, I reran verify disk permissions. Again, I got the same "Underlying..." error. So I tried
chmod o+x Macintish HD
I then reran verify disk permissions, and it ran fine and the suggested that the Macintosh HD volume permissions should be set to:
rwxrwxr-t
So, I had the Disk Utility repair it to the way it should be, and now it all seems fine.
This suggestion basically did not come from any Apple Support people or any forums, and it seemed like such an easy fix that I'm surprised nobody (at least nobody I've found) has had the same problem or needed the same fix.
Further, I think figured out what happened. I took my computer to my local tech support guys because I wanted to turn off sharing for this MBP. So, under Macintosh HD, somebody changed the permissions under "Everyone" from "Read Only" to "No Access".
It turns out that doing this basically creates the whole problem above by making the Macintosh HD unmountable or inaccessible.
I find it truly odd that it would be so easy to remove access to the computer for mounting purposes, but this is the only thing I can think of. The tech guy realized his error and apologized and was also surprised it was so easy to hose the computer.
Anyway, this is partially a warning to everyone as well as a possible fix for the blue screen problem, especially since it was a solution I could not find anywhere.
Maybe Apple Support will see this and for its next update at least make a warning box when people try to remove "Read Only" access for "Everyone".
Good luck.

If your Mac still boots and runs most applications correctly, but applying Software Update packages fails and you decide to run Disk Utility to Verify Permissions and it fails almost immediately with the "underlying task reported failure on exit" explore this posting. If you see other errors, have slow/varied disk performance, or hear nasty grinding/clicking sounds you have a much more serious problem this solution isn't for you.
Use Applications, Utility, Console and check the messages appearing there each time you try Disk Utility. If you see:
Failed to open database on '/'. Error 14, 13, Permission denied.
You may have had your permissions reset on the receipts db. Which is found in
/Library/Receipts/db/a.receiptdb
At this point you have to enter the dark world of the Terminal and use a unix shell (command line).
If you are not comfortable doing find a Unix/Linux power user.
The simple fix for me was to open Applications, Utilities, Terminal and do
sudo chmod 755 /Library/Receipts/db/a.receiptdb
This allowed Disk Utility to read the file and move on to repairing permissions.
When things generate error messages in the GUI part of Mac OS X ...always go check the messages in the logs via the Console in Utilities. These messages are 'down a level' and get you much closer to the real problem.
Note that I did follow the instructions in Apple kb TS1901
http://support.apple.com/kb/TS1901
which did not help at all. Same problem each time:
xxxx-imac:Volumes user$ diskutil verifyPermissions /
Started verify/repair permissions on disk disk0s2 Macintosh HD
$<3>Error -9972: The underlying task reported failure on exit
$<3>[ + 0%..10%..20%..30%..40%..50%..60%..70%..80%..90%..100% ]
Finished verify/repair permissions on disk disk0s2 Macintosh HD
Error detected while verifying/repairing permissions on disk0s2 Macintosh HD: The underlying task reported failure on exit (-9972)
Now I wonder what changed the permissions on the receipts database file? I am off to use find and date fields to see what changed the permissions file last (my is dated sometime in November!).
flatiswhereitsat

Similar Messages

  • Disk Utility will not verify disk because, "The underlying task reported failure on exit."  Now what?

    Disk utility will not verify disk because, " The underlying task reported failure on exit."  The "repair disk" button does not light up.  The report says that repairs need to be made to the hard drive.  I have already checked permissions.  What do I do next to get the repair process started?  Also, I cannot find a defragmenting drive option in Disk Utility.  Doesn't it exist?

    You need to boot from the install DVD (or a clone of your internal) to run Repair Disk. Repair Disk will be grayed out, dimmed, because you can't repair from the same volume you are booted from.
    EDIT: No, you do not yet need to use Disk Warrior or Tech Tool or do any reformatting. These steps might become necessary only if Repair Disk fails.
    Unless you have very large video files, for example, there is no need to run any defragmenting utility. OS X does it all by itself on the fly.
    Try Disk Utility
    Start from your Mac OS X Install disc: Insert the installation disc, then restart the computer while holding the C key.
    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.
    Click the First Aid tab.
    Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
    Select your Mac OS X volume.
    Click Repair. Disk Utility checks and repairs the disk.
    If you don't have the install DVD, try a Safe Boot. Hold the Shift key down at startup and give it much more time to boot than usual. It's trying to repair the drive directory.
    Message was edited by: WZZZ

  • Disk Utility Error - "Underlying task reported failure on exit"

    I've been having a problem opening Logic 7.1 (it will crash at startup every time) and I got the advice to repair disk permissions. Both 'verify disk permissions' and 'repair disk permissions' work, but when I go to 'verify disk' I get the following readout/error:
    Verifying volume “Macintosh HD”
    Checking HFS Plus volume.
    Checking Extents Overflow file.
    Checking Catalog file.
    Incorrect block count for file 5AD8D6E5d01
    (It should be 92 instead of 0)
    hecking multi-linked files.",0)
    Checking Catalog hierarchy.
    Checking Extended Attributes file.
    Checking volume bitmap.
    Checking volume bitmap.
    ,0)
    Checking volume information.
    Invalid volume free block count
    (It should be 2859750 instead of 2859751)
    The volume Macintosh HD needs to be repaired.
    Error: The underlying task reported failure on exit
    1 HFS volume checked
    Volume needs repair
    So I can't complete a rapair because it has this error. I'm wondering how I can fix this and if it could be the cause of the error that I get every time I open Logic. Thank you all in advance for your help!

    Al
    Disk Utility cannot repair this type of error.Not sure this is always the case, Al. I've had "incorrect block count" errors repaired in the past, so it must be worth a try before spending money (although I regard money spent on DiskWarrior as good insurance!)
    Cam
    It has to be worth you at least trying to Repair the error.
    I think the first thing you should try is a Safe Boot, which will automatically run the disk checking and repair routines: Mac OS X: Starting up in Safe Mode. If the check during Safe Boot is unable to repair the disk, your system will shut down rather than continuing, otherwise it will have successfully repaired the disk.
    If this doesn't work, you should try Disk Utility from the Install Disk. First read these articles: Mac OS X 10.4 Help: About testing and repairing a disk, and Using Disk Utility and fsck to resolve startup issues or perform disk maintenance.
    Let us know how this goes.

  • Disk Utility: "The underlying task reported failure on exit"

    Hi there,
    I've just lost the use of my second HD (non-bootable) in my G4. I was backing up my iTunes folder from it to an external HD, then left for work. When I got home the machine had frozen. I rebooted and then the drive was unavailable. I ran Disk Utility and received the following error:
    http://www.jowie.net/images/du_error.png
    Please tell me it's fixable, because the backup of my iTunes folder didn't finish
    thanks...
    :-Joe

    All very good points.
    A friend very nicely lent me a copy of Disk Warrior after a panicky phone call... It looks like it's doing the trick now as it appears to have generated a "preview volume" which I am using to copy from to an external drive... phew
    I have not had any issues like this for a long time, so I guess I became quite blasé. I have backed up my iTunes before, but had been meaning to do so now for a couple of months... Ironic that it decided to fall over as I was doing a new backup. But as you pointed out, I should have kept a backup offline.
    Now this has been a wake-up call and I will be investing in two new things - a new internal HD to replace the dodgy one, and an extra external HD which I can keep swapping with the one I already have - as you say if I alternate those then I will always have an offline backup.
    Luckily for me this all happened on a second non-bootable drive and as such was much easier to restore from.
    Thanks again for the help. It's nice to keep calm in a crisis

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

  • I ran a disk verify & disk repair on my macbook.. both said my system was fine. I keep getting the underlying task reported failure on exit when trying to do disk permission or repair permissions. Also get cant install files in "/applications error. Help

    m was fine. I keep getting the underlying task reported failure on exit when trying to do disk permission or repair permissions. Also get cant install files in "/applications error when ever trying to install a driver or update. Help

    Hi,
    Here's an article for that:
    http://support.apple.com/kb/ts1901

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

  • 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

  • Can't boot up and error "The underlying task reported failure on exit"

    I've spent some time searching the forums and internet for my problem to no avail, so hopefully this isn't something that was posted before.
    I recently upgraded my internal drive on my Macbook. Everything has been fine for a week or so, and Leopard ran smoothly. Yesterday, the machine got hung up on backing up to Time Machine. For whatever reason, it got hung up and now all I get when I try to reboot is a gray screen, the Apple logo, and a spinning progress disc.
    I can boot from another external drive just fine, and the data on the disk is all there. I just cannot boot from my master internal drive.
    I ran Disk Utility from the other external drive (also runs Leopard), and when I try to repair the disk, Mac OS X says everything is fine.
    However, when I try to repair permissions, I get the following error:
    Verify permissions for “John HD”
    Error: The underlying task reported failure on exit.
    Permissions verification complete
    That's it...nothing else to it. I cannot seem to get over this error no matter what.
    Also, I'm a bit nervous because my Time Machine folder has a folder labeled "Update in Progress" that is all white. Will I be able to backup from Time Macine, or is that data now corrupted?
    Thanks, and any help will do!
    John
    Macbook Core 2 Duo 2.0 Ghz
    2 Gig of RAM
    Note...I have the same thread in the Time Machine section, since I didn't know where to post this.

    By the way, this is the information that Disk Utility gives me when I try to repair the disk and then repair the permissions:
    Verify and Repair volume “John HD”
    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 John HD appears to be OK.
    Repairing permissions for “John HD”
    Error: The underlying task reported failure on exit.
    Permissions repair complete
    Like I said, the drive seems healthy enough. I just cannot get it to boot.
    John

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

    When I run Disk Utility on the hard drive( repair permissions/verify disk), I see an "illegal name" message and the following error message and DU will not complete the "verify disk" function.
    -Error: The underlying task reported failure on exit
    What does this mean and how do I fix it?
    Thanks, Pete
    iMac 17 G5 Mac OS X (10.4.3) Igb ddr ram and winning attitude

    Thanks, I have deleted the legal and legal. files but DU is erroring with this message now;
    Volume Header needs minor repair
    The volume Macintosh HD needs to be repaired.
    Error: The underlying task reported failure on exit

  • Error: The underlying task reported failure on exit and (~)file on root

    following is error i'm getting while i run disk utility verify disk permissions
    "Verify permissions for “Macintosh HD”
    Reading permissions database.
    Reading the permissions database can take several minutes.
    Error: The underlying task reported failure on exit.
    Permissions verification complete"
    so i tried booting from leopard disk, i'm getting the same error there also
    and i have a (~) file on my macintosh HD
    somebody plz help

    ..."Error: The underlying task reported failure on exit."...
    One reason this error can appear is if "repair permissions" is unable to read the permissions database at "/Library/Receipts/db/a.receiptdb" of the affected volume, due to incorrect permissions.
    Yes, you read that correctly - "repair permissions", the procedure to correct incorrect permissions, can fail to work if permissions are incorrect. This is a ridiculous shortcoming of the new (in my opinion "beta"-quality) Leopard versions of "repair permissions" that goes out of its way to drop its privileges to a level that is insufficient to complete its job.
    If you are able to manually adjust the permissions (eg. using 'chown', or 'chmod' -- I would recommend against using "Get Info" unless you are very careful since it also is "beta" quality in Leopard) of all of the folders along the path to the "a.receiptdb", and of the file itself, to ensure that the user '_installer' has at least "read" permissions, that should allow "repair permissions" to function...

  • Help -- "The underlying task reported failure on exit" And no boot up

    I've spent some time searching the forums and internet for my problem to no avail, so hopefully this isn't something that was posted before.
    I recently upgraded my internal drive on my Macbook. Everything has been fine for a week or so, and Leopard ran smoothly. Yesterday, the machine got hung up on backing up to Time Machine. For whatever reason, it got hung up and now all I get when I try to reboot is a gray screen, the Apple logo, and a spinning progress disc.
    I can boot from another external drive just fine, and the data on the disk is all there. I just cannot boot from my master internal drive.
    I ran Disk Utility from the other external drive (also runs Leopard), and when I try to repair the disk, Mac OS X says everything is fine.
    However, when I try to repair permissions, I get the following error:
    Verify permissions for “John HD”
    Error: The underlying task reported failure on exit.
    Permissions verification complete
    That's it...nothing else to it. I cannot seem to get over this error no matter what.
    Also, I'm a bit nervous because my Time Machine folder has a folder labeled "Update in Progress" that is all white. Will I be able to backup from Time Macine, or is that data now corrupted?
    Thanks, and any help will do!
    John
    Macbook Core 2 Duo 2.0 Ghz
    2 Gig of RAM

    Before you do anything it would be worth checking very, very carefully to make sure that you installed your new disk correctly and that all connections are absolutely solid.
    Also, you might want to try booting from safe mode. Hold the shift key down on startup until you see the spinning gear. It takes a long time. If that works disable all your non-apple startup items in System Preferences and add them back in one by one until you find the troublemaker.
    If a previously completed backup shows up in your Time Machine browser you should be able to choose that one from the Utilities menu from the Leopard install disk. It might not be a bad idea to zero out the drive before reinstalling from Time Machine even though DU is reporting no errors.
    Also, since there seems to be an interrupted Time Machine backup make sure than any of your critical data has been backed up by another method before erasing your internal drive.

  • Disk Utility - First Aid - The underlying task reported failure on exit

    Disk Utility -> First Aid -> Repair Disk Permissions provides in red
    Error: The underlying task reported failure on exit'
    This was a nightmare for me to fix, but after I learned how it was easy. If you get this error and you have not already restarted your computer, open you sharing preferences and make sure you ahve not set the everyone group to 'no access'. If you have change it and retry to run the permissions repair. If you have already restarted you will need to startup using your install DVD and then open terminal. In terminal type the following to fix your permissions.
    chmod 775 /Volumes/'Macintosh HD'
    This will change your permissions and you should be able then to get past the grey screen.
    Hope this helps someone.

    Hi everyone, I believe my permissions are the problem.
    I let someone change permission settings to share music files on their hard drive and mine and another mac (3 in total) yesterday. I seemed to work. I can't remember if I then shut down my mac or just closed it. Anyway last night I was trying to organise the music files and burn them to dvd. I also tried change the permissions as some of the files were read only. I though it worked. It seemed to be burning and the screen saver came up, I clicked to exit screen saver and it just went to black and back to screen saver and i couldn't go any further. I had to hold down the power button to turn if off.
    I tried to turn it on and now it's stuck on start up gray screen with the loading wheel thing? just loading forever.
    I used disk utility, verified volume and repair disk are ok, but verify permissions and repair permissions, I get an Error message "the underlying task reported failure on exit"
    I opened terminal and typed in what tryjezus1 said,"chmod 775 /Volumes/'Macintosh HD'" and pressed return. Not sure if I should have pressed return or if I should have just closed the window?. Anyway I'm still stuck.
    I only have the mac since march so I believe I still have phone support, but if anyone can help I'd like to try and sort this out myself.

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

    So I decide to play around with Bootcamp for the first time, and I go through the install but it kicks me out, telling me there was some kind of HDD error. It points me to Disk Utility, and I click on Verify Disk, and then I get the following error:
    Verifying volume “MacBook”
    Checking HFS Plus volume.
    Checking Extents Overflow file.
    Checking Catalog file.
    Illegal name
    Illegal name
    Checking multi-linked files.
    Checking multi-linked files.
    g Catalog hierarchy.",0)
    Checking Extended Attributes file.
    Checking volume bitmap.
    Checking volume information.
    Volume Header needs minor repair
    Volume Header needs minor repair
    0 %)
    The volume MacBook needs to be repaired.
    Error: The underlying task reported failure on exit
    1 HFS volume checked
    Volume needs repair
    So I do some searching, and Apple tells me that I need to reformat! ***?! There is nothing wrong with my HDD, or at least so I thought. No clicks, no shutdowns, nothing. Does this mean that soon my HDD might die? And if not, how the **** do I go about installing Bootcamp now?
    Here's Apple's support document:
    http://docs.info.apple.com/article.html?artnum=302411
    Thanks much.
    MacBook   Mac OS X (10.4.8)  

    You don't need to reformat.
    Put your first installation disk in and reboot, holding down the C key when you hear the chimes. When the installation program starts, start Disk Utility from the menu and select your system drive, then do a verify/repair from there.
    The reason it can't repair it is because Disk Utility won't do a low level repair on the system drive in case important system files are moved. When you boot off the CD, your system drive isn't in use and can be repaired easily.

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

Maybe you are looking for

  • Can I tell if I have activated any tracking software on my Macbook that will help me find it.

    My Macbook Pro was stolen today.  I know that I have logged into iCloud from this laptop before but I am not sure that I have specifically activated any tracking software.  Can anyone suggest any ideas for tracking this down - unlikely I think.

  • I have verified an email address but iMessage keeps saying it is not verified. How do I fix?

    I Have verified the address multiple times and my account show that it is verified. But on iMessage it keeps telling me its uncertified. Help!! 

  • Validation issues with XSD

    I'm trying to validate a xml file with this schema: <?xml version="1.0" encoding="UTF-8"?> <xsd:schema     xmlns:xsd="http://www.w3.org/2001/XMLSchema"                xmlns="http://www.jeromedroz.org/etc/lexicon.xsd"                targetNamespace="h

  • Transport customizations in ERMS

    Hi Experts, We are configuring ERMS (SAP CRM2007). We have a few question with regards to transporting customization from development system to Quality and then futher to production: Q1: We have different servers for development and quality. Hence we

  • 0x61011bed error code

    Error code 0x6011bed appears after the printer completes a print and to enable the printer to print again requires many button pushes on the message display of  "OK."   I have powered down the Officejet 7500,  unplugged the power, waited a minute,  r