Spinning Beach Ball Delay with "Look for Shared Photos" Checked

We installed iLife '06 on our school computers - all 500 of them - this fall. It is version 6.0.4. However, upon launch, there is a long delay of about 2-4 minutes with a spinning beach ball that we've determined takes place because iphoto is looking for shared libraries. We have one shared library on the network at this time, but sometimes teachers turn on sharing, or have in the past.
Last year, we were using iPhoto '04 and had no problems like this at all -shared libraries appeared immediately, just as quickly as shared libraries in itunes still do.
Has anyone experienced this - is there a known issue? Or should I look for a network problem.

Solved this problem myself. It was a dns issue. For some reason, when iphoto looks for shared photo's, it does a reverse lookup on the ip of any machine it finds that has sharing turned on. If there is no reverse lookup zone on your dns server running OS X then it locks up as it repeatedly sends the request. Simply creating a reverse zone for the ip address range of your clients makes the bug go away. Why it needs to do a reverse lookup is beyond me.

Similar Messages

  • Spinning beach ball delay.

    When I launch PS CC, after a 15 second-ish delay, I get the spinning beach ball. The ball spins, and PS CC is unresponsive for 1-2 minutes, then it works. I still have my PS C6 installed on the same computer, and it experiences no such problem. I woull appreciate any help.

    Thank you. I tried loading it with the shift key depressed. That did not alter the problem in any way that I noticed.
    I am running the program on a 12 core Mac Pro, 32 Gigs of Ram, OS 10.9.2. External e-Sata drives. nVidia Quadro 4000 video card, 2 NEC monitors (PA301W) and PA271W).
    I have both my CS6 Master Collection Installed, as well as a number of CC programs. I recently changed my CC subscription to Team (1 user) from individual (simply less expensive with current incentives). I would repeat that PS CS6 does not have this problem.
    I don't see what in settings could be causing the problem, but I admit to being well behind on the CC curve – I have not done much in the last couple of years, and need to re-learn a lot. I suppose that I could uninstall the program, then reinstall, and re-add my plug-ins. I have Nik, Perfect Photo, and added Snap Art 4 (but after the problem manifested). Please let me know what, if any, additional information might be helpful.
    Thanks

  • Power Mac G4 MDD 1.25GHz DP often completely locks up in the first few minutes after booting, sometimes with the spinning beach ball, normally with a very high pitched whining noise.

    Over the last few months my Mac has developed a worrying habit.
    Within the first few minutes of starting it up (perhaps on average about 50% of the time) it will completely lock up. This may happen at the Log In screen (if I start up the Mac & then leave it for a while) or during normal use.
    Often the first symptom is a very high pitched (but quiet) whining noise that seems to come from the loud speaker on the front of the Mac. The pointer may freeze at this point, or it may still be moveable for 5 or 10 seconds before it freezes. It sometimes turns into the spinning beach ball during this. Once locked up the only way I can restart the Mac is to hold down the power button on the front for a few seconds to completely reboot the machine.
    Once the Mac has restarted, it usually behaves normally, almost always for the rest of the day. The initial lock up & resulting restart only normally seem to happen the first time I use the Mac that day.
    The only peripherals attached to the Mac (apart from the display, keyboard & mouse) are an ADSL modem, a USB printer and a pair of Apple Pro speakers, and this setup hasn't changed since long before the problems started, so I'm confident that I can discount the peripherals causing problems. I doubt that unplugging the speakers, for example, would have any effect.
    I've run Disc Utility, OnyX and DiscWarrior without anything major cropping up. My instincts (I've been troubleshooting Mac problems for 16 years) tell me that I have a fundamental hardware problem, possibly with one of the 4 RAM DIMMs installed.
    The RAM configuration is shown in the attached screen grab.
    I'm considering removing one DIMM, running with 1.5GB of RAM rather than 2GB for a while, and repeating with a different DIMM removed each time until I can hopefully isolate the dodgy DIMM.
    Do people feel this is a sensible approach, or should I try something else first?
    Many thanks.

    Sometimes visual inpection will show bulging tops/sides., my guess is if it is it's most likely in the PSU.
    Possible cheap fix, You can convert an ATX PSU for use on a G4...
    http://atxg4.com/mdd.html
    http://atxg4.com/

  • Spinning beach ball appears at random for a radom period of time

    Hi,
    The spinning beach ball seems to appear at random: resizing crops, browsing through the lib, adjusting exposure. The frequency of appearance is pretty annoying. The ball spins for 10 to 60 seconds.
    Anyone experiencing the same?
    rgrds rgr

    I did installed MenuMeters. I just plugged in my camera and before I could click 'import' the ball was spinning. Later in the same session it spinned for some long periods while renaming a project and opening the file-menu.
    Every time the ball spins, the paging rate goes through the roof: 1k+/s with both a blue nand red arrow. At the same time, the free memory is 650 (also reported by MenuMeters). Why would Mac OS X page so much while there is lots of memory available?
    rgrds rgr

  • Spinning Beach Ball Freeze with HFS: err 5

    Ever since I upgraded to 10.5.x my iMac has been freezing more and more often. I noticed that every time the machine froze with the beach ball spinning so was the Time Machine indicator. I reformatted my LaCie HD that I was using to GUID and most (but not all) of the freezes have subsided. I have a second LaCie HD that I use for video (named Video HD)which along with my internal HD is part of my Time Machine back-up. Last evening my machine froze in the usual manner. I grabbed the console messages and saw:
    7/7/08 7:48:13 PM kernel disk1s2: I/O error.
    7/7/08 7:48:13 PM kernel HFS: err 5 reading VH blk (Video HD)
    7/7/08 7:49:43 PM kernel disk1s2: I/O error.
    7/7/08 7:52:13 PM kernel disk1s2: I/O error.
    7/7/08 7:52:13 PM /System/Library/CoreServices/backupd[4279] Starting standard backup
    7/7/08 7:56:43 PM kernel disk1s2: I/O error.
    7/7/08 7:56:43 PM kernel HFS: err 5 reading VH blk (Video HD)
    7/7/08 7:57:13 PM kernel disk1s2: I/O error.
    7/7/08 7:59:43 PM kernel disk1s2: I/O error.
    7/7/08 7:59:43 PM /System/Library/CoreServices/backupd[4279] Backing up to: /Volumes/TM HD/Backups.backupdb
    7/7/08 8:04:13 PM kernel disk1s2: I/O error.
    7/7/08 8:04:13 PM kernel HFS: err 5 reading VH blk (Video HD)
    7/7/08 8:04:43 PM kernel disk1s2: I/O error.
    7/7/08 8:07:13 PM kernel disk1s2: I/O error.
    7/7/08 8:09:43 PM kernel disk1s2: I/O error.
    7/7/08 8:12:13 PM kernel disk1s2: I/O error.
    7/7/08 8:16:43 PM kernel disk1s2: I/O error.
    7/7/08 8:16:43 PM kernel HFS: err 5 reading VH blk (Video HD)
    7/7/08 8:17:13 PM kernel disk1s2: I/O error.
    7/7/08 8:19:43 PM kernel disk1s2: I/O error.
    7/7/08 8:22:13 PM kernel disk1s2: I/O error.
    7/7/08 8:24:43 PM kernel disk1s2: I/O error.
    7/7/08 8:29:13 PM kernel disk1s2: I/O error.
    7/7/08 8:29:13 PM kernel HFS: err 5 reading VH blk (Video HD)
    7/7/08 8:29:43 PM kernel disk1s2: I/O error.
    7/7/08 8:32:13 PM kernel disk1s2: I/O error.
    7/7/08 8:32:13 PM /System/Library/CoreServices/backupd[4279] No pre-backup thinning needed: 614.0 MB requested (including padding), 136.86 GB available
    7/7/08 8:32:18 PM /System/Library/CoreServices/backupd[4279] Copied 2940 files (4.1 MB) from volume Shapiro HD.
    7/7/08 8:36:43 PM kernel disk1s2: I/O error.
    7/7/08 8:36:43 PM kernel HFS: err 5 reading VH blk (Video HD)
    7/7/08 8:37:13 PM kernel disk1s2: I/O error.
    7/7/08 8:39:43 PM kernel disk1s2: I/O error.
    7/7/08 8:39:43 PM /System/Library/CoreServices/backupd[4279] Error: (-36) copying /Volumes/Video HD to (null)
    7/7/08 8:39:43 PM /System/Library/CoreServices/backupd[4279] Copied 2941 files (4.1 MB) from volume Video HD.
    7/7/08 8:44:13 PM kernel disk1s2: I/O error.
    7/7/08 8:44:13 PM kernel HFS: err 5 reading VH blk (Video HD)
    7/7/08 8:44:43 PM kernel disk1s2: I/O error.
    Any help decoding HFS: err 5 would be greatly appreciated. Oh, I've updated to the latest system (using the Combo updater and have already run Disk Utility and Disk Warrior on the Video HD.
    Thanks

    Error 5 is an I/O error, which you're getting back from the filesystem after an attempted read (the reason you see explicit I/O errors and error 5's is that likely the driver is reporting one, and the filesystem is reporting the other). IMO, whatever is mounted at device disk1s2 is bad. Your reformats, repairs, etc may have remapped some bad sectors on that disk, but clearly hasn't repaired all of them (or, the disk is continuing to fail with new bad spots).
    I would suggest that you make a backup of your system somewhere other than whatever is on disk1s2. I'd then retire that disk...

  • Why do I get a spinning beach ball of death waiting for...

    When I open a window or select/search for a fhile I get the spinning beachball of death while one of the four hard drives spins up. Is there a way to get around this since I'm guessing Finder is spinning all available connected drives to do it's function?

    PS: also, add more RAM, 4 x 1GB should be minimum set. 4 x 2GB cost is only slightly more.
    Might want to 'upgrade' and move your system to a new drive as well.
    10.6.3 is from March 2010, over a year old and may as well stay current.
    Those MacPro1,1 are popular still go strong, and 5355s are cheap and popular way to improve performance and give it another 2-3 yrs.

  • Solution to iPhoto spinning beach ball for Book projects with too many unplaced photos

    A few days ago I discovered the solution to this problem for a client using iPhoto 9.5.1 in OS X Mavericks 10.9.4.
    =====
    TRIED ALL KNOWN SUGGESTIONS BUT NONE HELPED
    My client had already tried repairing, rebuilding etc. the iPhoto Library, and I tried OS X's Disk Verify and Repair Permissions plus emptied the cache folder in system Library and in the hidden user Library folder (option-key "Go" menu, Library). None of this helped.
    CLUE TO PROBLEM
    I noticed several of her iPhoto Book projects each had thousands of "unplaced" photos. In each of those cases, each Book project only had 10-50 "placed" photos used to order the book but thousands of "unplaced" photos. In a Book project, clicking on the bottom-right corner's "Photo" icon-button caused an extremely long lasting spinning beach ball making iPhoto unusable for long periods.
    I discovered the problem by clicking once on an existing Book project's name in the left column of iPhoto, then letting go of the mouse with its arrow cursor hovering over the selected Book project name. Within 1-7 seconds, a little pop-up appears listing the total number of photos (placed + unplaced) in that Book project. For many Book projects, the total number was just several more photos than the number of "placed" photos, e.g., a Book with 25 photos showed "(37)" in the pop-up info by the hovering stationary mouse, meaning 37 total photos (placed + unplaced) are associated with that Book project.
    BUT...
    ...some projects listed over 5,000 (five thousand) photos associated with a single Book project that had only placed 20-40 photos in the final printed book. One Book project had 6,070 and several other small book projects showed over 1,000 photos. In each Book project with a mass of unplaced photos, clicking the bottom-right "Photo" icon-button caused a very long-lasting spinning beach ball, almost certainly because iPhoto struggled to build a huge list of thumbnails for the mass of unplaced photos.
    My client didn't understand how to efficiently add photos to a new Book project and was clicking on the pull-down menu in the right column that appears after clicking the Photo icon-button within the Book project. From the menu she chose "Last import..." or other menu choice that added a mass of "unplaced" photos to the Book project.
    She didn't realize that after creating a new Book project, she could simply drag an individual photo or multi-selected group of photos or an event or "faces" group from its respective library section and drop it onto the Book project's name in the left column, thereby adding only a small group of "unplaced" photos.
    USER SOLUTIONS
    =====Delete mass of "unplaced photos" within a Book project
    This works best for cleaning up smaller number of unplaced photos from completed Book projects.
    Problems with solution:
    - if the number of unplaced photos is huge, e.g., 6,070, the list of unplaced photos won't appear for a long, long time if ever.
    - even if the list of unplaced photos finally appears, there's no way to select more than one thumbnail at a time, i.e., command-a for Select All doesn't work, nor do shift-clicks and command-clicks for multi-item selecting. You must click one photo then tap the "delete" key on your keyboard repeatedly and fast for this to be practical (note: delete key presses are cached here (meaning accumulated until it catches up processing them later); tapping the delete key like mad then waiting for iPhoto to catch up takes lots of patience.
    ====Delete an entire existing Book project containing a mass association of unplaced photos
    This is practical if you've already printed your Book project and no longer need it. My client chose this method for Book projects with a mega mass of unplaced photos.
    Problem with solution:
    - for incomplete Book projects in progress with a mass of unplaced photos, you'd have to start over after deleting the whole thing.
    NEED FOR IMPROVED IPHOTO FEATURE(S)
    (1) The existing "Clear Placed Photos" button within a Book project might be useful, but it'd be even better to also have a button to "Clear Unplaced Photos,” and this button should be available outside of the section that struggles to display thumbnails of large numbers of unplaced photos. Clicking "Clear Unplaced Photos" would do the trick.
    (2) An additional iPhoto behavior might help: iPhoto should warn with an option to cancel when adding a mass of photos to the "unplaced photo" section if the number of photos exceeds ??? (400??).
    (3) Add another choice to iPhoto’s special startup Administrative window (Repair, Rebuild, etc.): "Remove unplaced photos from existing projects. (Doesn't destroy any photos in Library)"
    Whew!

    Like I mentioned in the post, corruption was probably ruled out by running all the Admin features at iPhoto startup (e.g., Rebuild, etc.). I also stated in my post that I also ran a Disk Verify and Repaired Permissions in OSX (via Disk Utility). I also emptied system Library cache files as I stated in my post.
    I was paid to figure out the solution and am not getting paid to troubleshoot for Apple. The more unplaced photos there are in a Book project, the longer it takes to build thumbnails. It's an old general problem in computing when building lists on the fly.
    The delay happened for all Book projects with lots of unplaced photos (almost*** certainly more than Apple imagined a user would use), and the beach ball delay was proportional to the number unplaced photos, which super large numbers of photos.
    I very much doubt photos are corrupt. But Apple will probably figure it out. It was EASILY reproducible. Try it with different number of unplaced photos known not be corrupt (they display fine elsewhere and iPhoto's and Disk Utlity's admin Verify, Repair etc features show no problems).
    I'm done with this.
    My client's iPhoto works well now and she knows how avoid placing exorbitant numbers of unplaced photos into her project. I'm not getting paid to answer all this, so good night.
    =======
    ***"Science is the outcome of being prepared to live without certainty and therefore a mark of maturity. It embraces doubt and loose ends."
      — A. C. Grayling

  • Someone with two macs pls help with spinning beach ball

    Sometimes I download pictures to my MacBook from my camera and then transfer them to my main library on my G5 using photo sharing in iPhoto.
    If "look for shared photos" is enabled on the MacBook and "share my photos" is enabled on the G5, I get a long hang and a spinning beach-ball in when I launch iPhoto on the MacBook The hang seems subsequently affects the G5. They both hang for a good 15-30 seconds.
    While this is happening the Application Monitor shows a root process called "mds" using 99% of the MacBook CPU. Once the hang is over the mds process goes away. The G5 while still hanging simply shows iPhoto as not responding, no mds process.
    I've wiped the MacBook clean, set up new accounts. Nothing seems to fix it. The question is; am I alone? Can someone else go through the steps and get iPhoto to launch with iPhoto already running on another networked mac with photo sharing enabled and not get a spinning beach-ball.
    This was also a problem in iPhoto 06'. I was really hoping Apple got my feedback and fixed in 08' Maybe something is wrong with my MacBook.

    Hi.
    mds is the indexing process, usually run by Spotlight when looking for files, folders, servers, etc.
    that's the reason why you get the delay when seeking your images using the sharing function. Your mac is searching for the requested service (your photo sharing "server"...your other mac), and it cannot find it because of the firewall that's built in to the mac. Whether you're doing this via a wireless or an Ethernet connection, you'll need to assure that your firewalls on
    both computers are open to allow that type of sharing to take place.
    Take a look in your System Prefs, under the Sharing icon. Click on the "Firewall" button and, after authenticating with your password, scroll down and select the option for "iPhoto Bonjour Sharing". You'll need to do this on BOTH machines, as the port is used by each for communication.
    That should solve the problem..
    Cheers,
    Charlie

  • Spinning beach ball for 45-60 seconds, then fine

    For several months now, I've had the spinning beach ball issue on my Macbook Pro. Within the first 5 minutes after boot up, the spinning beach ball will occur, seemingly at random (no specific app or action), for 45-60 seconds. While this happens, the system becomes completely unresponsive. But after this occurrence within the first five minutes after startup, it never happens again and everything is fine - until I reboot of course.
    I am running Snow Leopard and this problem was happening before I installed Snow Leopard, so that's not it. But one thing I did do, which I am semi-convinced is the culprit, is I replaced my hard drive with a Seagate 500 mb Momentus drive. The actual model # is SEAST9500420AS. I don't know for sure, but that's around the time this issue first started. I know there is/was a spinning beach ball problem with the newer Macbook Pros and they were attributing it to the hard drive which just so happens to be the same hard drive I now have in my Macbook Pro. There was recently an EFI update that seemed to fix the problem for the newer models, but mine is the first generation right when they went to Intel chips (bought mine in April, 2006). Problem is, if it is my drive, this new EFI update that fixes the issue on the new models won't install on mine.
    I also did a verify disk and repair disk permissions, but that was no help. Another thing I found going through the discussion groups was that the problem could happen because both the Macbook Pro and the Seagate drive have anti-shock technology that could conflict with one another. So if you disabled the anti-shock on the Macbook Pro, it might solve the problem as it seemed to for some folks out there. But I did that and it didn't help either.
    I'm thinking it's my hard drive, but don't know how to fix it. But it could be something I haven't looked at yet or thought of. I've been trying everything the last several months with no luck and it's been driving me batty! What's really strange is it only happens once and always within the first 5 minutes after start up. Anybody have any suggestions? Thanks.

    I just finished doing lots of different tests to try to solve my problem. Didn't resolve it, but I did manage to eliminate some things and narrow it down further.
    First I removed all my login items and restarted my computer. That didn't fix the problem.
    So then I thought it might have something to do with Safari since that's one of the first things I open up when I start my computer and there are numerous reports in the discussions of spinning beach balls with Safari 4.0.3 which I have. So I purposely did not open Safari after startup. Problem still happened.
    So then I thought maybe it has something to do with my internet connection. So I disconnected my internet connection and rebooted. Then I only opened programs that don't use online access. I leisurely opened up a program, did a few things in it, closed it, and then did the same thing with another program. Did some things with Finder. Purposely did not rush things. Waited 4-5 seconds after every operation's completion before executing another task. Never had more than one program open at any given time to eliminate any issue with two many resources open. You guessed it - the problem STILL happened. Not that it matters, but it happened when I hit Command-I on my hard drive icon to get the info pane. A fairly innocuous task. Froze up with the spinning beach ball for at least 45-50 seconds. Tried clicking a few other things while this was happening, but nothing. Once it freed up, a few things I clicked on previously suddenly became active and everything was fine again. Tried Command-I for a lot of different things with no problem. Response was instantaneous.
    It pretty much happens 3-4 minutes into a session and then never happens again. And I think my test here eliminated several possibilities. Very frustrating. I hope this helps someone come up with a possible solution. Thanks.

  • Spinning Beach Ball on Start Up of iPhoto 09'

    I have suddenly started having problems with iPhoto '09.  I have about 4500 photos in my library. I have a late 2009 i7 iMac running mountain lion with 12 gb of RAM.
    When I start iPhoto, it opens quickly enough, but as soon as I move my cursor I get a spinning beach ball for about 20-30 seconds.  Then everything seems to work OK.  I have deleted my cache and plist files and rebuilt the thumbnails, etc. to no avail.  I also turned off sharing and unclicked look for shared photos.  I have "check for new published photos" set to manually. 
    Does anyone have any idea what the issue is or how to fix it? 
    Many thanks.

    I went into the Console and when I open iPhoto I get the following messages.  Does this mean anything to you? 
    Many thanks.
    5/25/13 12:26:37.927 PM iPhoto[407]: This process is attempting to exclude an item from Time Machine by path without administrator privileges. This is not supported.
    5/25/13 12:26:37.927 PM iPhoto[407]: This process is attempting to exclude an item from Time Machine by path without administrator privileges. This is not supported.
    5/25/13 12:26:37.928 PM iPhoto[407]: This process is attempting to exclude an item from Time Machine by path without administrator privileges. This is not supported.
    5/25/13 12:26:37.928 PM iPhoto[407]: This process is attempting to exclude an item from Time Machine by path without administrator privileges. This is not supported.
    5/25/13 12:26:38.161 PM iPhoto[407]: CFURLGetFSRef was passed this URL which has no scheme (the URL may not work with other CFURL routines): /Applications/iPhoto.app
    5/25/13 12:26:38.179 PM iPhoto[407]: CFURLGetFSRef was passed this URL which has no scheme (the URL may not work with other CFURL routines): /Applications/iPhoto.app
    5/25/13 12:26:38.181 PM iPhoto[407]: CFURLGetFSRef was passed this URL which has no scheme (the URL may not work with other CFURL routines): /Applications/iPhoto.app
    5/25/13 12:26:38.184 PM iPhoto[407]: CFURLGetFSRef was passed this URL which has no scheme (the URL may not work with other CFURL routines): /Applications/iPhoto.app

  • Print error - there was a problem connecting to the server - spinning beach ball

    This has happened pre-yosemite and since.  It used to only happen at home but now also happens at work.  Every time I try to print, I get a spinning beach ball and a long delay until I get an error message saying there was a problem connecting to the server. At home, after clicking OK, I get a second spinning beach ball session with same error.  Once I click OK second time, I get print window and can print.  At work, it's only one session of spinning beach ball.  The office problem occurred after upgrading to yosemite.  I've deleted and added the printers without resolution.  I've repaired permissions.  The home problem has been going on for at least a year, probably a couple.  Using a macbook pro.

    There are many possible causes for this issue, and it may be very hard to resolve without wiping your account clean of everything except documents as a last resort. Please take each of the following steps that you haven't already tried. Back up all data before making any changes.
    If you get the alert in the login screen before you log in, stop here and ask for instructions.
    Step 1
    If you get the alert as soon as you log in, it's probably caused by one of your login items or by software that otherwise loads at startup or login. Ask if you need help identifying it. Known offenders are "1Password" and "Adobe Resource Synchronizer."
    Step 2
    If there's an icon representing the server in the sidebar of a Finder window, hold down the command key and drag it out.
    Step 3
    In the Finder, press the key combination command-K or select
              Go ▹ Go to Server...
    from the menu bar. In the upper right corner of the window that opens is a Recent Servers popup menu represented by a clock icon. From that menu, select
              Clear Recent Servers…
    and confirm. Test.
    Step 4
    Open the Printers & Scanners pane in System Preferences and delete any network devices you no longer use. If in doubt, delete them all and add back the ones you want.
    Step 5
    Triple-click anywhere in the line below on this page to select it, then copy the text to the Clipboard by pressing  command-C:
    ~/Library/PDF Services
    In the Finder, select
              Go ▹ Go to Folder...
    from the menu bar and paste into the box that opens by pressing command-V. You won't see what you pasted because a line break is included. Press return. A folder may open. If it does, move the contents to the Desktop, or to a new folder on the Desktop. Log out and log back in. Test. If there's no change, put the items you moved back where they were and continue.
    Step 6
    Open the folder
    ~/Library/Preferences
    as in Step 5 and move the file named "loginwindow.plist" items in that folder to the Trash, if it exists (it may not.)
    Log out and back in again, and test.
    Step 7
    Other possible causes are references in the iPhoto, iTunes, or iMovie library pointing to the server, bookmarks in the Preview application, and PDF files created by Adobe Acrobat with embedded scripts.
    Try rebuilding the iPhoto library, if applicable.
    Step 8
    Resources such as images or sounds stored on the server may have been added to various applications. Examples would be pictures added to Contacts and custom sounds added to Mail. The range of possibilites here is practically infinite, so I can't be more specific. You might get a hint by launching the Console application and looking for error messages that appear at the same time as the alerts.
    Step 9
    Disconnect all wired peripherals except those needed to start up. Start up in safe mode. Test. After testing, restart as usual (not in safe mode) and verify that you still have the problem.
    Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Ask for further instructions.
    Step 10
    Triple-click the line below to select it:
    /System/Library/CoreServices/Directory Utility.app
    Rght-click or control-click the highlighted text and select
              Services ▹ Open
    from the contextual menu.* The application Directory Utility will open.
    In the Directory Utility window, select the Directory Editor tool in the toolbar. Select Mounts from the Viewing menu in the toolbar, and/Local/Default from the node menu, if not already selected. On the right is a list of names and values. By default, the list is empty. If it's not empty, post a screenshot of the window and stop here.
    *If you don't see the contextual menu item, copy the selected text to the Clipboard (command-C). Open a TextEdit window and paste into it (command-V). Select the line you just pasted and continue as above.
    Step 11
    Open the following file as you did in the last step:
    /etc/auto_master
    It will open in a TextEdit window. The contents should be exactly this:
    # Automounter master map
    +auto_master          # Use directory service
    /net               -hosts          -nobrowse,hidefromfinder,nosuid
    /home               auto_home     -nobrowse,hidefromfinder
    /Network/Servers     -fstab
    /-               -static
    If there are any other lines in the window, post them. Otherwise, close the window.

  • Spinning beach ball while wiping hard drive.

    I've been wiping the 80 GB hard drive on my eMac before passing it on to a friend. I opted for the 8 pass of writing random data, and it's taken 3 days! It reached the 'creating partition map' stage yesterday and I've got the spinning beach ball and what looks like no progress on the progress bar since then. Is it stuck? What do I do? I don't want to crash out and start the process again, I need to get on with my life
    Any help would be greatly appreciated.

    Crash it out, and do a quick reformat without erasing any data. That should only take a few minutes. And since your eMac has been overwriting for three days, your data is all safely gone now anyway.

  • Safari won't open... spinning beach ball

    Out of the blue this morning, Safari won't open. I click it, the icon bounces, and then I get the spinning beach ball. If I go to the Force Quit Applications window, it says it's not responding. Any ideas what may be causing this and how to fix it?
    -B

    What is the exact wording of the message you see, and what are you doing when you see it?
    These are the steps I took this morning, again, along with the wording.  Before these steps, I logged into my account through the Google browser, and verified that I had a purchase in October of OS X Lion: 
    1 - booted computer under recovery.
    2 - Disk Utility - Repair Disk  (Result: The Volume New Macbook appears to be okay)
    3 - Disk Utility - Repair Disk Permissions - (Result:0 Repaired - Permissions Repair Complete)
    4 - Reinstall Mac OS - "Your computer's eligibility will be verified with Apple - OK
    5 - "To Continue, you must agree to the terms and conditions" - Agree
    6 - Select New Macbook - Install
    7 - signing into Apple Store  (Result: This Apple ID has not purchased Lion)
    8 - rebooted and tried to launch App Store - back to spinning beach balls, along with all other internet apps; Safari, Mail, App Store, iTunes, etc. 
    Aps not affected: Google Chrome, Outlook (as long as I don't click on an email connected to an HTTPS server) and anything not on the internet.
    I hope this helps and thank you for your advice.  I wish I could use my Snow Leopard disks; my dvd drive is broken.

  • Spinning beach ball on desktop of macbook pro of 2013 is not stopping

    After downloading a .pdf file from the internet on the desktop, when I wanted to see the name of file, I am encountered with a spinning beach ball which is not stopping. It occured once more in this week. And immediate after 3 months of purchase of the MacBook Pro it appeared for the first time, which compelled me to reinstall OS X 10.9.1 and then, be updated.
    Why?
    I shall appreciate if anyone can help me out of this recurring problem of Spinning Beach Ball.

    Check out:  Troubleshoot the spinning beach ball/freezing & crashing
    Troubleshoot the spinning beach ball
    Have you read for possible solutions over in the "More Like This" thread over here?----------------------->
    =================
    If you are still under warranty and/or have AppleCare, call them.  Let them deal w/it.
    OOW:  Take your Mac to your local Apple Store or an AASP.  Diagnostic testing is FREE!

  • MacBook Pro - incessant spinning beach ball

    My MacBook Pro is running really slow. The spinning beach ball keeps coming up for almost everything I try to do.
    For instance I can't type more than about 4 words in MS word before it stalls out and the beach ball pops up. It's almost like there's some big program running in the background sucking up processing power.
    I ran disk utility repair from the OSX Recovery and it didn't show any problems.
    Is it possible I caught some kind of virus? Anyone have any thoughts on how to remedy this? Any help would be greatly appreciated!
    Here's the system overview...
    <Edited by Host>

    Here's mine.  Or should I start a new thread?
    9/25/14 11:07:14.124 PM AppleSpell[389]: *** -[NSMachPort handlePortMessage:]: dropping incoming DO message because the connection is invalid
    9/25/14 11:07:27.142 PM com.apple.IconServicesAgent[25101]: IconServicesAgent launched.
    9/25/14 11:07:37.000 PM kernel[0]: memorystatus_thread: idle exiting pid 25014 [WiFiKeychainProx]
    9/25/14 11:07:37.163 PM com.apple.launchd.peruser.502[173]: (com.apple.wifi.WiFiKeychainProxy[25014]) Idle-exit job was jettisoned. Will bypass throttle interval for next on-demand launch.
    9/25/14 11:07:37.163 PM com.apple.launchd.peruser.502[173]: (com.apple.wifi.WiFiKeychainProxy[25014]) assertion failed: 13E28: launchd + 43321 [364E35A7-9FA7-3950-8494-40B49A2E7250]: 0x9
    9/25/14 11:07:37.000 PM kernel[0]: memorystatus_thread: idle exiting pid 25019 [aosnotifyd]
    9/25/14 11:07:37.413 PM com.apple.launchd[1]: (com.apple.AOSNotification[25019]) Idle-exit job was jettisoned. Will bypass throttle interval for next on-demand launch.
    9/25/14 11:07:37.413 PM com.apple.launchd[1]: (com.apple.AOSNotification[25019]) assertion failed: 13E28: launchd + 43321 [364E35A7-9FA7-3950-8494-40B49A2E7250]: 0x9
    9/25/14 11:07:37.000 PM kernel[0]: memorystatus_thread: idle exiting pid 25034 [CloudKeychainPro]
    9/25/14 11:07:37.663 PM secd[25029]:  handle_xpc_event >>>>> handle_connection_event via event_handler <<<<<, ***?
    9/25/14 11:07:37.664 PM com.apple.launchd.peruser.502[173]: (com.apple.security.cloudkeychainproxy3[25034]) Idle-exit job was jettisoned. Will bypass throttle interval for next on-demand launch.
    9/25/14 11:07:37.664 PM com.apple.launchd.peruser.502[173]: (com.apple.security.cloudkeychainproxy3[25034]) assertion failed: 13E28: launchd + 43321 [364E35A7-9FA7-3950-8494-40B49A2E7250]: 0x9
    9/25/14 11:07:37.000 PM kernel[0]: memorystatus_thread: idle exiting pid 25061 [com.apple.CodeSi]
    9/25/14 11:07:37.915 PM com.apple.launchd[1]: (com.apple.CodeSigningHelper[25061]) Exited: Killed: 9
    9/25/14 11:07:38.000 PM kernel[0]: memorystatus_thread: idle exiting pid 25064 [xpcd]
    9/25/14 11:07:38.166 PM com.apple.launchd[1]: (com.apple.xpcd.00000000-0000-0000-0000-000000000000[25064]) Exited: Killed: 9
    9/25/14 11:07:38.000 PM kernel[0]: memorystatus_thread: idle exiting pid 25079 [com.apple.InputM]
    9/25/14 11:07:38.467 PM com.apple.launchd[1]: (com.apple.InputMethodKit.UserDictionary[25079]) Exited: Killed: 9
    9/25/14 11:07:38.635 PM WiFiKeychainProxy[25102]: [NO client logger] <Nov 10 2013 18:30:13> WIFICLOUDSYNC WiFiCloudSyncEngineCreate: created...
    9/25/14 11:07:38.637 PM WiFiKeychainProxy[25102]: [NO client logger] <Nov 10 2013 18:30:13> WIFICLOUDSYNC WiFiCloudSyncEngineRegisterCallbacks: WiFiCloudSyncEngineCallbacks version - 0, bundle id - com.apple.wifi.WiFiKeychainProxy
    9/25/14 11:07:38.639 PM secd[25029]:  SecErrorGetOSStatus unknown error domain: com.apple.security.sos.error for error: The operation couldn’t be completed. (com.apple.security.sos.error error 2 - Public Key not available - failed to register before call)
    9/25/14 11:07:38.639 PM secd[25029]:  securityd_xpc_dictionary_handler WiFiKeychainProx[25102] DeviceInCircle The operation couldn’t be completed. (com.apple.security.sos.error error 2 - Public Key not available - failed to register before call)
    9/25/14 11:07:38.000 PM kernel[0]: memorystatus_thread: idle exiting pid 25008 [periodic-wrapper]
    9/25/14 11:07:38.671 PM com.apple.launchd[1]: (com.apple.periodic-daily[25008]) Idle-exit job was jettisoned. Will bypass throttle interval for next on-demand launch.
    9/25/14 11:07:38.671 PM com.apple.launchd[1]: (com.apple.periodic-daily[25008]) assertion failed: 13E28: launchd + 43321 [364E35A7-9FA7-3950-8494-40B49A2E7250]: 0x9
    9/25/14 11:07:38.000 PM kernel[0]: memorystatus_thread: idle exiting pid 25097 [systemstatsd]
    9/25/14 11:07:38.921 PM com.apple.launchd[1]: (com.apple.systemstatsd[25097]) Idle-exit job was jettisoned. Will bypass throttle interval for next on-demand launch.
    9/25/14 11:07:38.921 PM com.apple.launchd[1]: (com.apple.systemstatsd[25097]) assertion failed: 13E28: launchd + 43321 [364E35A7-9FA7-3950-8494-40B49A2E7250]: 0x9
    9/25/14 11:07:39.000 PM kernel[0]: memorystatus_thread: idle exiting pid 25049 [tccd]
    9/25/14 11:07:39.174 PM com.apple.launchd.peruser.502[173]: (com.apple.tccd[25049]) Idle-exit job was jettisoned. Will bypass throttle interval for next on-demand launch.
    9/25/14 11:07:39.174 PM com.apple.launchd.peruser.502[173]: (com.apple.tccd[25049]) assertion failed: 13E28: launchd + 43321 [364E35A7-9FA7-3950-8494-40B49A2E7250]: 0x9
    9/25/14 11:07:39.000 PM kernel[0]: memorystatus_thread: idle exiting pid 25099 [com.apple.NotesM]
    9/25/14 11:07:39.428 PM com.apple.launchd[1]: (com.apple.NotesMigratorService[25099]) Exited: Killed: 9
    9/25/14 11:07:39.000 PM kernel[0]: memorystatus_thread: idle exiting pid 25100 [accountsd]
    9/25/14 11:07:39.830 PM com.apple.internetaccounts[25052]: /SourceCache/Accounts/Accounts-336.9/ACAccountStore.m - __60-[ACAccountStore _connectToRemoteAccountStoreUsingEndpoint:]_block_invoke - 130 - The connection to ACDAccountStore was interrupted.
    9/25/14 11:07:39.831 PM com.apple.launchd.peruser.502[173]: (com.apple.accountsd[25100]) Idle-exit job was jettisoned. Will bypass throttle interval for next on-demand launch.
    9/25/14 11:07:39.831 PM com.apple.launchd.peruser.502[173]: (com.apple.accountsd[25100]) assertion failed: 13E28: launchd + 43321 [364E35A7-9FA7-3950-8494-40B49A2E7250]: 0x9
    9/25/14 11:07:39.000 PM kernel[0]: memorystatus_thread: idle exiting pid 25022 [com.apple.iCloud]
    9/25/14 11:07:39.992 PM com.apple.launchd[1]: (com.apple.iCloudHelper[25022]) Exited: Killed: 9
    9/25/14 11:07:40.000 PM kernel[0]: memorystatus_thread: idle exiting pid 25095 [pbs]
    9/25/14 11:07:40.183 PM com.apple.launchd.peruser.502[173]: (com.apple.pbs[25095]) Idle-exit job was jettisoned. Will bypass throttle interval for next on-demand launch.
    9/25/14 11:07:40.183 PM com.apple.launchd.peruser.502[173]: (com.apple.pbs[25095]) assertion failed: 13E28: launchd + 43321 [364E35A7-9FA7-3950-8494-40B49A2E7250]: 0x9
    9/25/14 11:07:40.000 PM kernel[0]: memorystatus_thread: idle exiting pid 25052 [com.apple.intern]
    9/25/14 11:07:40.439 PM com.apple.launchd[1]: (com.apple.internetaccounts[25052]) Exited: Killed: 9
    9/25/14 11:07:40.000 PM kernel[0]: memorystatus_thread: idle exiting pid 25027 [xpcd]
    9/25/14 11:07:40.687 PM com.apple.launchd[1]: (com.apple.xpcd.F6010000-0000-0000-0000-000000000000[25027]) Exited: Killed: 9
    9/25/14 11:07:40.000 PM kernel[0]: memorystatus_thread: idle exiting pid 25101 [com.apple.IconSe]
    9/25/14 11:07:40.938 PM com.apple.launchd[1]: (com.apple.IconServicesAgent[25101]) Exited: Killed: 9
    9/25/14 11:07:40.972 PM Safari[1883]: XPC error messaging com.apple.IconServicesAgent: Connection interrupted
    9/25/14 11:07:40.972 PM Safari[1883]: XPC error messaging com.apple.IconServicesAgent: Connection invalid
    9/25/14 11:07:41.000 PM kernel[0]: memorystatus_thread: idle exiting pid 25026 [cfprefsd]
    9/25/14 11:07:41.193 PM com.apple.launchd[1]: (com.apple.cfprefsd.xpc.daemon[25026]) Idle-exit job was jettisoned. Will bypass throttle interval for next on-demand launch.
    9/25/14 11:07:41.193 PM com.apple.launchd[1]: (com.apple.cfprefsd.xpc.daemon[25026]) assertion failed: 13E28: launchd + 43321 [364E35A7-9FA7-3950-8494-40B49A2E7250]: 0x9
    9/25/14 11:07:41.000 PM kernel[0]: memorystatus_thread: idle exiting pid 25029 [secd]
    9/25/14 11:07:41.443 PM WiFiKeychainProxy[25102]: xpc __securityd_create_connection_block_invoke got event: Connection interrupted
    9/25/14 11:07:41.497 PM com.apple.launchd.peruser.502[173]: (com.apple.secd[25029]) Idle-exit job was jettisoned. Will bypass throttle interval for next on-demand launch.
    9/25/14 11:07:41.497 PM com.apple.launchd.peruser.502[173]: (com.apple.secd[25029]) assertion failed: 13E28: launchd + 43321 [364E35A7-9FA7-3950-8494-40B49A2E7250]: 0x9
    9/25/14 11:07:41.000 PM kernel[0]: memorystatus_thread: idle exiting pid 24908 [cfprefsd]
    9/25/14 11:07:41.697 PM com.apple.launchd.peruser.502[173]: (com.apple.cfprefsd.xpc.agent[24908]) Idle-exit job was jettisoned. Will bypass throttle interval for next on-demand launch.
    9/25/14 11:07:41.697 PM com.apple.launchd.peruser.502[173]: (com.apple.cfprefsd.xpc.agent[24908]) assertion failed: 13E28: launchd + 43321 [364E35A7-9FA7-3950-8494-40B49A2E7250]: 0x9
    9/25/14 11:07:47.615 PM gkbisd[168]: Unable to collect cdhash for /Applications/Utilities/Console.app (error code 100024)
    9/25/14 11:07:49.609 PM Console[25104]: setPresentationOptions called with NSApplicationPresentationFullScreen when there is no visible fullscreen window; this call will be ignored.
    9/25/14 11:07:59.281 PM WindowServer[107]: disable_update_timeout: UI updates were forcibly disabled by application "Console" for over 1.00 seconds. Server has re-enabled them.
    9/25/14 11:08:11.384 PM com.apple.IconServicesAgent[25113]: IconServicesAgent launched.
    9/25/14 11:08:11.947 PM WindowServer[107]: common_reenable_update: UI updates were finally reenabled by application "Console" after 13.67 seconds (server forcibly re-enabled them after 1.00 seconds)

Maybe you are looking for