Mdworker deny mach-lookup. But macbook won't boot in safe mode

I have a common problem, I get theese messages every now and then in console:
2/8/13 6:38:24.000 PM kernel[0]: Sandbox: sandboxd(793) deny mach-lookup com.apple.coresymbolicationd
2/8/13 6:38:24.534 PM sandboxd[793]: ([791]) mdworker(791) deny mach-lookup com.apple.ls.boxd
2/8/13 6:38:24.556 PM sandboxd[793]: ([792]) mdworker(792) deny mach-lookup com.apple.ls.boxd
There is a solution, which should resolve it, like here https://discussions.apple.com/message/19750564?searchText=mach-lookup%20com.appl e.ls.boxd#19750564
I have just boot in safe mode. (holding Shift during boot)
but my macbook won't boot in Safe mode. It just freeses with a grey screen for hours and wont boot.
I tried to leave it overnight to boot, but it didn't.
Please help me make my macbook to boot in SafeMode.
my configuration is the following:
MacBookPro8,1
OSX 10.8.2

There is a bug in fsck_hfs that is affecting a bunch of people.  Basically as your comptuer starts in safe mode, it runs a file system check (fsck) against your hard drive, it gets to a certain point and... just sits there.  No one knows why outside of apple.
Lots of info here, including a way to get around it by tricking the system to think fsck had been run, though the fsck will not be complete so it is not a good solution.
https://discussions.apple.com/message/21389737?ac_cid=tw123456#21389737

Similar Messages

  • Mdworker deny mach-lookup com.intego.mig_hook (pre-ls-info fstype:hfs

    I made a clean insatlle of Mouatin Lion and my HD is  is filled with many files every day.
    I looked in the console, I get this message that reproduces to infinity
    Here you have an example :
    mdworker(2557) deny mach-lookup com.intego.mig_hook (pre-plugin fstype:hfs fsflag:480D000 flags:240000004C diag:0 uti:com.apple.property-list plugin:internalPlainTextImporter - find suspect file using: sudo mdutil -t 1387774)
    Process:         mdworker [2557]
    Path:            /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker
    Load Address:    0x10e999000
    Identifier:      mdworker
    Version:         ??? (???)
    Code Type:       x86_64 (Native)
    Parent Process:  launchd [305]
    Date/Time:       2012-10-06 13:27:46.816 +0200
    OS Version:      Mac OS X 10.8.2 (12C60)
    Report Version:  8
    Thread 0:
    0   libsystem_kernel.dylib                  0x00007fff82cec686 mach_msg_trap + 10
    1   CoreFoundation                          0x00007fff8bb05803 __CFRunLoopServiceMachPort + 195
    2   CoreFoundation                          0x00007fff8bb0aee6 __CFRunLoopRun + 1078
    3   CoreFoundation                          0x00007fff8bb0a6b2 CFRunLoopRunSpecific + 290
    4   CoreFoundation                          0x00007fff8bb19371 CFRunLoopRun + 97
    5   mdworker                                0x000000010e9a1ba9
    6   libdyld.dylib                           0x00007fff889777e1 start + 0
    Thread 1:
    0   libsystem_kernel.dylib                  0x00007fff82ceed16 kevent + 10
    1   libdispatch.dylib                       0x00007fff8ac139ee _dispatch_mgr_thread + 54
    Thread 2:
    0   libsystem_kernel.dylib                  0x00007fff82cec686 mach_msg_trap + 10
    1   liblaunch.dylib                         0x00007fff861ac7c4
    2   liblaunch.dylib                         0x00007fff861ab4d9 bootstrap_look_up3 + 69
    3   liblaunch.dylib                         0x00007fff861ab591 bootstrap_look_up + 37
    4                                           0x000000010ea1eb40
    5                                           0x000000010ea1f098
    6   mdworker                                0x000000010e9a6282
    7   mdworker                                0x000000010e9a6027
    8   mdworker                                0x000000010e9a34f2
    9   libsystem_c.dylib                       0x00007fff828b8742 _pthread_start + 327
    10  libsystem_c.dylib                       0x00007fff828a5181 thread_start + 13
    Thread 3:
    0   libsystem_kernel.dylib                  0x00007fff82cec686 mach_msg_trap + 10
    1   mdworker                                0x000000010e9b5df9
    2   libsystem_c.dylib                       0x00007fff828b8742 _pthread_start + 327
    3   libsystem_c.dylib                       0x00007fff828a5181 thread_start + 13
    Thread 4:
    0   libsystem_kernel.dylib                  0x00007fff82cee6d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff828bacb3 _pthread_wqthread + 412
    2   libsystem_c.dylib                       0x00007fff828a5171 start_wqthread + 13
    Binary Images:
           0x10e999000 -        0x10e9f2ff7  mdworker (707.3) <105316D8-F5DF-3079-96EF-0EF0986EB053> /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker
        0x7fff828a4000 -     0x7fff82970fe7  libsystem_c.dylib (825.25) <8CBCF9B9-EBB7-365E-A3FF-2F3850763C6B> /usr/lib/system/libsystem_c.dylib
        0x7fff82cdc000 -     0x7fff82cf7ff7  libsystem_kernel.dylib (2050.18.24) <C0535565-35D1-31A7-A744-63D9F10F12A4> /usr/lib/system/libsystem_kernel.dylib
        0x7fff861a9000 -     0x7fff861b1fff  liblaunch.dylib (442.26.2) <2F71CAF8-6524-329E-AC56-C506658B4C0C> /usr/lib/system/liblaunch.dylib
        0x7fff88975000 -     0x7fff88978ff7  libdyld.dylib (210.2.3) <F59367C9-C110-382B-A695-9035A6DD387E> /usr/lib/system/libdyld.dylib
        0x7fff8ac0f000 -     0x7fff8ac24ff7  libdispatch.dylib (228.23) <D26996BF-FC57-39EB-8829-F63585561E09> /usr/lib/system/libdispatch.dylib
        0x7fff8bad6000 -     0x7fff8bcbffff  com.apple.CoreFoundation (6.8 - 744.12) <EF002794-DAEF-31C6-866C-E3E3AC387A9F> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    I contacted intego France, who told me that they were not aware of this

    I contacted Intego opened a ticket (no response), but I think Version 6 must have a big bug  with ML
    you can see this url :
    https://www.facebook.com/Intego/posts/311468278907535
    dam Wallace I am getting exactly the same thing in Mountain Lion. My System Log is full of hundreds of messages repeating exactly the same thing, around 20 times per second. Macintosh.local sandboxd[7781] ([7307]): mdworker(7307) deny mach-lookup com.intego.mig_hook (pre-plugin fstype:hfs fsflag:480D000 flags:250000005E diag:0 uti:com.apple.application-bundle plugin:/Library/Spotlight/Application.mdimporter - find suspect file using: sudo mdutil -t 1029605)
    I think this might explain why I have been getting system freezes & kernel panics. A fix for this would be much appreciated.
    Mike Dever mdworker(2315) deny mach-lookup com.intego.mig_hook (pre-plugin fstype:hfs fsflag:480D000 flags:240000004C diag:0 uti:com.apple.property-list plugin:internalPlainTextImporter - find suspect file using: sudo mdutil -t 64324970)

  • What's this sandboxd mdworker deny mach-lookup thing about?

    My newer iMac keeps locking up over many months. It seems to be getting more frequent. All updated are made and I'm running OS10.8.2.
    Each time I've looked at the console log one of the last entries has been related to mdworker and sandboxd.
    This is the console immediatly surrounding the latest lockup and restart (having to use the powerbutton.)
    3/10/13 7:48:27.128 PM com.apple.backupd[20992]: Backup completed successfully.
    3/10/13 7:48:27.000 PM kernel[0]: Sandbox: sandboxd(21005) deny mach-lookup com.apple.coresymbolicationd
    3/10/13 7:50:27.573 PM mdworker[21015]: Unable to talk to lsboxd
    3/10/13 7:50:27.577 PM mdworker[21014]: Unable to talk to lsboxd
    3/10/13 7:50:27.622 PM sandboxd[21016]: ([21015]) mdworker(21015) deny mach-lookup com.apple.ls.boxd
    3/10/13 7:50:27.626 PM sandboxd[21016]: ([21014]) mdworker(21014) deny mach-lookup com.apple.ls.boxd
    3/10/13 7:50:27.000 PM kernel[0]: Sandbox: sandboxd(21016) deny mach-lookup com.apple.coresymbolicationd
    3/10/13 7:52:28.404 PM mdworker[21026]: Unable to talk to lsboxd
    3/10/13 7:52:28.408 PM mdworker[21027]: Unable to talk to lsboxd
    3/10/13 7:52:28.457 PM sandboxd[21028]: ([21026]) mdworker(21026) deny mach-lookup com.apple.ls.boxd
    3/10/13 7:52:28.461 PM sandboxd[21028]: ([21027]) mdworker(21027) deny mach-lookup com.apple.ls.boxd
    3/10/13 7:52:28.000 PM kernel[0]: Sandbox: sandboxd(21028) deny mach-lookup com.apple.coresymbolicationd
    3/10/13 10:04:58.000 PM bootlog[0]: BOOT_TIME 1362978298 0
    3/10/13 10:05:24.000 PM kernel[0]: Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64
    3/10/13 10:05:24.000 PM kernel[0]: vm_page_bootstrap: 3994120 free pages and 167416 wired pages
    3/10/13 10:05:24.000 PM kernel[0]: kext submap [0xffffff7f80741000 - 0xffffff8000000000], kernel text [0xffffff8000200000 - 0xffffff8000741000]
    3/10/13 10:05:24.000 PM kernel[0]: zone leak detection enabled
    3/10/13 10:05:24.000 PM kernel[0]: standard timeslicing quantum is 10000 us
    3/10/13 10:05:24.000 PM kernel[0]: standard background quantum is 2500 us
    3/10/13 10:05:24.000 PM kernel[0]: mig_table_max_displ = 74
    3/10/13 10:05:24.000 PM kernel[0]: corecrypto kext started!
    3/10/13 10:05:24.000 PM kernel[0]: Running kernel space in FIPS MODE
    Below is the full report from the line in red above --
    mdworker(21027) deny mach-lookup com.apple.ls.boxd
    Process:         mdworker [21027]
    Path:            /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker
    Load Address:    0x107e3e000
    Identifier:      mdworker
    Version:         ??? (???)
    Code Type:       x86_64 (Native)
    Parent Process:  launchd [285]
    Date/Time:       2013-03-10 19:52:28.457 -0700
    OS Version:      Mac OS X 10.8.2 (12C60)
    Report Version:  8
    Thread 0:
    0   libsystem_kernel.dylib                  0x00007fff8ca62686 mach_msg_trap + 10
    1   CoreFoundation                          0x00007fff93f47803 __CFRunLoopServiceMachPort + 195
    2   CoreFoundation                          0x00007fff93f4cee6 __CFRunLoopRun + 1078
    3   CoreFoundation                          0x00007fff93f4c6b2 CFRunLoopRunSpecific + 290
    4   CoreFoundation                          0x00007fff93f5b371 CFRunLoopRun + 97
    5   mdworker                                0x0000000107e46ba9
    6   libdyld.dylib                           0x00007fff94edb7e1 start + 0
    Thread 1:
    0   libsystem_kernel.dylib                  0x00007fff8ca64d16 kevent + 10
    1   libdispatch.dylib                       0x00007fff94d8c9ee _dispatch_mgr_thread + 54
    Thread 2:
    0   libsystem_kernel.dylib                  0x00007fff8ca626c2 semaphore_wait_trap + 10
    1   libxpc.dylib                            0x00007fff94f48e1f xpc_connection_send_message_with_reply_sync + 127
    2   LaunchServices                          0x00007fff8e8ec3ce send(LSBoxMessage&, LSBoxMessage&) + 28
    3   LaunchServices                          0x00007fff8e96cd4b lsbox_preflightAppLaunch + 84
    4   LaunchServices                          0x00007fff8e8f7341 _LSFindOrRegisterBundleNode + 857
    5   LaunchServices                          0x00007fff8e953b02 _LSRegisterNode + 75
    6   LaunchServices                          0x00007fff8e8ffa0f _LSBundleCopyOrCheckNode + 1047
    7   LaunchServices                          0x00007fff8e8e75b6 _LSCopyLibraryItemURLs + 486
    8   mdworker                                0x0000000107e6e014
    9   libdispatch.dylib                       0x00007fff94d8df01 _dispatch_call_block_and_release + 15
    10  libdispatch.dylib                       0x00007fff94d8a0b6 _dispatch_client_callout + 8
    11  libdispatch.dylib                       0x00007fff94d8b47f _dispatch_queue_drain + 235
    12  libdispatch.dylib                       0x00007fff94d8b2f1 _dispatch_queue_invoke + 52
    13  libdispatch.dylib                       0x00007fff94d8b1c3 _dispatch_worker_thread2 + 249
    14  libsystem_c.dylib                       0x00007fff89e9ccab _pthread_wqthread + 404
    15  libsystem_c.dylib                       0x00007fff89e87171 start_wqthread + 13
    Thread 3:
    0   libsystem_kernel.dylib                  0x00007fff8ca646d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff89e9ccb3 _pthread_wqthread + 412
    2   libsystem_c.dylib                       0x00007fff89e87171 start_wqthread + 13
    Thread 4:
    0   libsystem_kernel.dylib                  0x00007fff8ca646d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff89e9ccb3 _pthread_wqthread + 412
    2   libsystem_c.dylib                       0x00007fff89e87171 start_wqthread + 13
    Thread 5:
    0   libsystem_kernel.dylib                  0x00007fff8ca62686 mach_msg_trap + 10
    1   liblaunch.dylib                         0x00007fff918217c4
    2   liblaunch.dylib                         0x00007fff918204d9 bootstrap_look_up3 + 69
    3   libxpc.dylib                            0x00007fff94f46c21 _xpc_connection_bootstrap_look_up_slow + 371
    4   libxpc.dylib                            0x00007fff94f45c82 _xpc_connection_init + 1062
    5   libdispatch.dylib                       0x00007fff94d8a0b6 _dispatch_client_callout + 8
    6   libdispatch.dylib                       0x00007fff94d8b47f _dispatch_queue_drain + 235
    7   libdispatch.dylib                       0x00007fff94d8b2f1 _dispatch_queue_invoke + 52
    8   libdispatch.dylib                       0x00007fff94d8b448 _dispatch_queue_drain + 180
    9   libdispatch.dylib                       0x00007fff94d8b2f1 _dispatch_queue_invoke + 52
    10  libdispatch.dylib                       0x00007fff94d8b1c3 _dispatch_worker_thread2 + 249
    11  libsystem_c.dylib                       0x00007fff89e9ccab _pthread_wqthread + 404
    12  libsystem_c.dylib                       0x00007fff89e87171 start_wqthread + 13
    Binary Images:
           0x107e3e000 -        0x107e97ff7  mdworker (707.3) <105316D8-F5DF-3079-96EF-0EF0986EB053> /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker
        0x7fff89e86000 -     0x7fff89f52fe7  libsystem_c.dylib (825.25) <8CBCF9B9-EBB7-365E-A3FF-2F3850763C6B> /usr/lib/system/libsystem_c.dylib
        0x7fff8ca52000 -     0x7fff8ca6dff7  libsystem_kernel.dylib (2050.18.24) <C0535565-35D1-31A7-A744-63D9F10F12A4> /usr/lib/system/libsystem_kernel.dylib
        0x7fff8e8e3000 -     0x7fff8e994fff  com.apple.LaunchServices (539.7 - 539.7) <DA7C602E-5E01-31B8-925D-B45360CA089F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
        0x7fff9181e000 -     0x7fff91826fff  liblaunch.dylib (442.26.2) <2F71CAF8-6524-329E-AC56-C506658B4C0C> /usr/lib/system/liblaunch.dylib
        0x7fff93f18000 -     0x7fff94101fff  com.apple.CoreFoundation (6.8 - 744.12) <EF002794-DAEF-31C6-866C-E3E3AC387A9F> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
        0x7fff94d88000 -     0x7fff94d9dff7  libdispatch.dylib (228.23) <D26996BF-FC57-39EB-8829-F63585561E09> /usr/lib/system/libdispatch.dylib
        0x7fff94ed9000 -     0x7fff94edcff7  libdyld.dylib (210.2.3) <F59367C9-C110-382B-A695-9035A6DD387E> /usr/lib/system/libdyld.dylib
        0x7fff94f3d000 -     0x7fff94f5fff7  libxpc.dylib (140.41) <FAC04D8B-680E-325F-8F0C-DD69859D0E01> /usr/lib/system/libxpc.dylib
    Any suggestions and help apprecieated.
    --Dan

    Dan Bratten wrote:
    3/10/13 7:48:27.128 PM com.apple.backupd[20992]: Backup completed successfully.
    3/10/13 7:48:27.000 PM kernel[0]: Sandbox: sandboxd(21005) deny mach-lookup com.apple.coresymbolicationd
    3/10/13 7:50:27.573 PM mdworker[21015]: Unable to talk to lsboxd
    3/10/13 7:50:27.577 PM mdworker[21014]: Unable to talk to lsboxd
    3/10/13 7:50:27.622 PM sandboxd[21016]: ([21015]) mdworker(21015) deny mach-lookup com.apple.ls.boxd
    3/10/13 7:50:27.626 PM sandboxd[21016]: ([21014]) mdworker(21014) deny mach-lookup com.apple.ls.boxd
    3/10/13 7:50:27.000 PM kernel[0]: Sandbox: sandboxd(21016) deny mach-lookup com.apple.coresymbolicationd
    3/10/13 7:52:28.404 PM mdworker[21026]: Unable to talk to lsboxd
    3/10/13 7:52:28.408 PM mdworker[21027]: Unable to talk to lsboxd
    3/10/13 7:52:28.457 PM sandboxd[21028]: ([21026]) mdworker(21026) deny mach-lookup com.apple.ls.boxd
    3/10/13 7:52:28.461 PM sandboxd[21028]: ([21027]) mdworker(21027) deny mach-lookup com.apple.ls.boxd
    3/10/13 7:52:28.000 PM kernel[0]: Sandbox: sandboxd(21028) deny mach-lookup com.apple.coresymbolicationd
    3/10/13 10:04:58.000 PM bootlog[0]: BOOT_TIME 1362978298 0
    3/10/13 10:05:24.000 PM kernel[0]: Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64
    3/10/13 10:05:24.000 PM kernel[0]: vm_page_bootstrap: 3994120 free pages and 167416 wired pages
    3/10/13 10:05:24.000 PM kernel[0]: kext submap [0xffffff7f80741000 - 0xffffff8000000000], kernel text [0xffffff8000200000 - 0xffffff8000741000]
    3/10/13 10:05:24.000 PM kernel[0]: zone leak detection enabled
    3/10/13 10:05:24.000 PM kernel[0]: standard timeslicing quantum is 10000 us
    3/10/13 10:05:24.000 PM kernel[0]: standard background quantum is 2500 us
    3/10/13 10:05:24.000 PM kernel[0]: mig_table_max_displ = 74
    3/10/13 10:05:24.000 PM kernel[0]: corecrypto kext started!
    3/10/13 10:05:24.000 PM kernel[0]: Running kernel space in FIPS MODE
    You have a common problem with OS X 10.8.2, the "unable to talk to lsboxd" message. First of all, try to fix this. It's fixed just starting your Mac in safe mode, holding the Shift key while your computer is starting. Then, just after starting in safe mode, restart, and that message will disappear. Finally, see if your red message appears

  • MacBook Pro won't boot - tried safe mode but it went to black screen after trying.

    my MacBook Pro froze after the fan was running very loudly. I turned it off and try to reboot but just got a gray screen. I tried to boot in safe mode but that did not work.any other thoughts on what might help?

    Reinstalling OS X Without Erasing the Drive
    Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
    Reinstalling OS X Without Erasing the Drive
    Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
    When the recovery menu appears select Disk Utility and press the Continue button. After Disk Utility loads select the Macintosh HD entry from the the left side list.  Click on the First Aid tab, then click on the Repair Disk button. If Disk Utility reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit Disk Utility and return to the main menu.
    Reinstall OS X: Select Reinstall OS X and click on the Continue button.
    Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.
    Alternatively, see:
    Reinstall OS X Without Erasing the Drive
    Choose the version you have installed now:
    OS X Yosemite- Reinstall OS X
    OS X Mavericks- Reinstall OS X
    OS X Mountain Lion- Reinstall OS X
    OS X Lion- Reinstall Mac OS X
         Note: You will need an active Internet connection. I suggest using Ethernet
                     if possible because it is three times faster than wireless.

  • Macbook won't boot in any mode

    It started playing up last week but I booted it with command s and it's been fine, today it's done the same and I've tried rebooting it with every different key combination I have seen on discussions online and it either just keeps thinking on the apple logo page or goes blue. If I try to boot in safe mode the progress bar never fully finished, it stops halfway and goes to the blues screen. I've not made any changes or updates to the macbook? Model is a1181. Can I get a recovery disk or software disk to reboot it as I don't have one of those either? This is my first mac so I don't know much about them? All I know is I'm deployed in afghan with a broken laptop lol. Ta for your help

    He  tried booting it in safe mode and from an external drive, neither of which worked. He said that he could hear the hard drive spinning and it didn't sound right (when I held my ear next to it, I couldn't hear anything).
    He spent most of the time working in the back room and didn't give me much information. He simply said that I needed to swap out the internal drive and that should fix the problem.
    Obviously it didn't, so I have no idea where the problem could really be.
    I do know that my drive is bad, because I put it in my mom's macbook (we have the same kind) and it didn't boot in there.
    However, I cloned my mom's working drive on my blank ssd and tried putting it in my macbook, but that didn't work either.
    The computer won't respond to any commands - it won't even eject the install disk I put in.
    I am at a loss as to what to try next, and I can't find a similar situation addressed on any forums.

  • Macbook Pro won't boot into safe mode or via bootable USB key

    Hi,
    Am running OSX Lion latest version on my Macbook Pro 4,1 and can't get the thing to boot from any source.  Always get's stuck at the grey screen with apple logo.  Have tried all the following...
    - Straight Boot (power on)
    - Boot via Recovery HD (hold option on bootup then select)
    - Boot via Safe Mode (Holding Shift on bootup)
    - Boot via Safe Mode Verbose (Shift, Command, V)
    - Boot via bootable Lion USB Key (Hold option, and choose the USB drive - not the same USB key works on my other macbook pro)
    On every one (except verbose) it just get's stuck on the grey screen with spinning timer thingie.
    I have done PVRAM reset, SMC reset and have reseated the RAM and all to no avail.  I'm pretty sure the problem was caused by removing battery at wrong time (device not responding after sleep mode started and I plugged in power - should have been more patient!)
    I have a Time Machine backup but it's a bit older than I thought and very much want to get my newer photos off it before rebuilding - not that Time Machine would work in current state anyway. 
    So what are my remaining options?  Will I have to open it up and remove the HD as next step or is there anything else left to try?  Can I remove the HD and connect it via a USB caddy to my existing Mac to recover info (hardrive spins and sounds ok to me)?
    Any advice appreciated...

    ds store wrote:
    Yes, once the data is off you can use Disk Utility to Erase the entire drive (Lion + Recovery) with the Zero option (one selection below 7x) then use the Lion USB to install it fresh and stick it back into the machine.
    Thanks for the info - I removed the HD and data is all ok on there so very happy about that.  Before I wipe the data (all backed up now) I thought I would try booting the mac without any harddrive installed - using a OSX Lion bootable USB.  However, still can't get past the grey apple screen and circle icon whirling away.   I know the USB works ok, as tried it in my 2011 Macbook Pro and it boots absolutely fine. 
    I am happy to wipe the HD now and start again, but seeing as the DVD Drive is broken I'll probably need a USB drive boot to install OSX onto the wiped HD anyway.  I'm a bit lost as to what to try now. 

  • Macbook Pro Won't Boot in Safe Mode...it also won't stop trying to boot in safe mode

    I was having an issue with Finder crashing on my Macbook Pro.  After startup Finder would give me the spinning wheel of death if I clicked "about this Mac."  To try to resolve this issue, I attempted to boot in Safe Mode, but it basically died each time when the progress bar reached around 20%.  I was able to get into the Disk Utility and attempt to repair, but I learned that I need to back up and restore.  (I tried this twice.)  However, my machine will now only attempt to boot in Safe Mode (at which point it reverts to dying at around 20%).  How can I back up my machine if I can't boot into either safe mode or regular mode?
    (P.S., If you can't tell, I'm not hyper computer literate, so simple explanations will be most helpful.  Thanks!)

    dullman82,
    as you’ve discovered, the option to back up is currently unavailable to you with your disk in its current condition. You can try these two possibilities:
    Install OS X onto an external disk, boot from your external disk, run Software Update to get it up-to-date in its version, and try backing up your internal disk when booted from your external disk;
    Boot into Recovery mode, and select Reïnstall Mac OS X to reïnstall OS X on your internal disk (which should leave your other files there untouched) to see if that will fix your Finder problem.

  • My MacBook won't boot into recovery mode after new hard drive installation. Please help!

    I just installed a new hard drive. On boot it keeps on going to the flashing folder with a question mark inside.
    I was able to format the new hard drive but am unable to boot into recovery mode to install the operating system over the air.
    When I hold down Command -R it keeps on taking me to the flashing folder.
    Please help!

    A new hard drive doesn't have a recovery partition. It's totally blank.You're going to need either your original install discs or a Snow Leopard retail disc from which partition, format and install OS X.

  • How do I stop my MacBook from ONLY booting in Safe Mode

    I have a new Intel MacBook with 512 Mhz of Memory. My granddaughter loaded about 8 programs from the dock all at the same time. Now, the computer will only boot up in safe maode. Does anyone know how I can get the machine to boot up properly? And yes, I have turned it off and on normally to see if this would fix the problem - but no luck. Help!!
    MacBook   Mac OS X (10.4.8)  

    "Now, the computer will only boot up in safe
    mode."
    In my earlier response I assumed that you booted into
    safe mode by holding down the Shift key during
    startup.
    Upon reconsideration, I'm wondering if you meant
    instead that the computer boots into safe mode by
    itself, without your holding down the shift key. If
    so, this would indicate that the computer suspected
    some inconsistency in the filesystem and is booting
    into safe mode in an attempt to repair the damage.
    This repair can take some time. Are you allowing it
    10-20 minutes to finish the task?
    If so, and it still won't reboot into regular mode,
    then you probably should start the computer from the
    Installation Disc by inserting the Disc before
    shutdown and then holding down the C key during
    startup.
    Don't actually install anything, but use the menu at
    the top to run DiskUtility on the hard drive. Tell it
    to "Repair Disk".
    Sorry I didn't see this post before I responded to your first one. Yes, this is exactly what is happening. I am not holding down any key to force it into safe mode - it's doing that all by itself. I will try the 10 - 20 minute repair time as you suggested. What will I see happening after this period of time has elapsed? Does it matter if my screen goes into "sleep mode" before the 10-20 minute time is up? And then, if this doesn't work, I'll try your other suggestion using my installation disc.
    Thank you!!!!

  • MacBook Pro only boots in safe mode with pink vertical stripes across screen.

    So on Friday night I was using Chrome on my MacBook Pro, when all of a sudden little squares of light flashed randomly across the whole screen and everything but the mouse froze. I thought that was weird, so after a few minutes I forced my computer to shutdown. I waited a little and then turned it back on, and opened Chrome again. The same thing happened again, so I forced shut down, backed up Time Machine and ran a virus scan. Nothing came up, so I put it to sleep and and went to bed.  Then Saturday morning I went to open my laptop and it was off, which was weird, so I went to turn it on. After the apple logo and spinning gear went away, it booted to a light blue screen and stayed there. Again I waited and nothing happened, so I held the power button down until it turned off. I tried again but the same thing happened, so I booted in Safe Mode.
    This time there were inch long vertical bars of horizontal lines, kind of confusing but here are two pictures I took of the screen that hopefully help. http://imgur.com/oj2WbZL and http://imgur.com/O1hwJ1B . When it finally loaded I had another issue, I had 6 pink vertical bars across the screen and a box of pink horizontal stripes around my pointer, http://imgur.com/BJBzu74 . I performed an extended Apple Hardware Test and after 17 minutes it found no issues, and as it performed the test the lines got whiter and made the screen harder to see http://imgur.com/XahBD3s .
    I got my laptop June 2011, so it's not that old. I just want to know what this problem could be. I don't know if it's the connection from the screen to the computer, the hard drive, the logic board or something else. I'm really worried that it's something major, so any help is greatly appreciated.
    Thank you in advance!

    This is a GPU problem. It's normal that you see that the problem is random, but the fact that your Mac is only starting up in safe mode indicates that your Mac can only start up if the VGA driver is used. Moreover, if you open Console, you should start seeing "GPU Debug Info Start", which indicates a GPU failure.
    As you have a backup, take the MacBook to an Apple Store or reseller. In the case of the MacBook Pro, the GPU is soldered onto the logic board, so the whole logic board has to be replaced, being a very expensive repair.
    If a post solved your question or helped you, mark it as solved or helpful before posting a reply. Doing this, you will avoid that your own post is marked as solved or helpful. You won’t receive any point if you mark your own post as solved or helpful. Also, you won’t be rewarding the user who solved your question and you will help other users find the answer if you mark the correct reply

  • Macbook Pro only boots in Safe Mode

    Hello,
    I've read a few discussions about MacBooks only booting in Safe Mode, but my circumstances are a bit different.
    Yesterday I installed a new piece of RAM. The installation was careful and went well. When I went to restart the computer, however, it would not load after the gray screen with the apple appeared. So I restarted it in Safe Mode and it worked fine (abeit there is no sound, can't use the disc drive, etc.)
    The interesting part is that while in safe mode I clicked on the apple in the top left corner, clicked "About This Mac," and it appears that the computer accepted the new ram (I originally had two 2-gig sticks [4 gigs total], and I swapped out one of the sticks for the new 4-gig stick [therefore I have 6 gigs total]). So the computer recognizes the new RAM, which is good news, but I've still got a problem.
    I've tried rebooting several times, and have even tried the Apple Hardware Test, but it froze shortly after I started the test (the same thing happened about 4 times).
    Any help would be greatly appreciated!
    Here's the specs of my Macbook:
    MacBook Pro, mid-2010 edition
    Mac OS X, version 10.6.8
    2.4 GHz Intel Core i5 Processor
    6 GB 1067 MHz DDR3 Memory

    The RAM you received was bad, return it. That brand of RAM seems to pop up a lot here as a problem for Mac's.
    According to MacTracker the Mid 2010 models with i5 processors can accept 8GB of RAM.
    Maximum Memory
    8.0 GB
    Memory Slots
    2 - 204-pin PC3-8500 (1066 MHz) DDR3 SO-DIMM
    Amazon and eBay are not good sources of top tier reliable and tested RAM, your just going to be spending more money returning it.
    Crucial.com or OtherWorld Computing will make sure the RAM they sell you works correctly in your model/year of machine.

  • Win2003 SP2 VM won't boot to safe mode

    I have a Windows Server 2003 SP2 VM set up in Hyper-V on my Windows Server 2008 R2 server.  The VM was created as an export from AppAssure 5 export to Hyper-V Virtual Standby.  This particular server won't complete the boot but "sits"
    at the Windows splash screen indefinitely (I've let it run for two hours with no change).  I specifically use the work "sits" vs. "hangs" because the progress bar continues to move and the CPU usage fluctuates between 20 and 30%.
    AppAssure T3 support want me to try to boot into safe mode but I'm unable to do so.  I'm connecting to the VM through Hyper-V manager on my local Windows 7 PC.  I have inserted the integration services disk in the vmguest and it shows that keyboard
    input is being captured but it doesn't seem to recognize the F8 keystroke.
    Before I try to run startup recovery from install I was hoping someone here might be able to offer insight into why I'm unable to boot to safe mode.  I do have one other VM server created through the AppAssure export and I can boot normally or into
    safe mode with that one.
    Thanks in advance for any insight provided.

    Thanks for the reply.  I'm currently into the 5th hour of the boot process and no joy yet.  I'll let it go for a little bit longer before stopping to so I can re-enable my protection of the server.
    Yesterday, I tried mounting the drive to see if any errors were being registered in the event log that might not be causing a bsod or other start up error but kept getting an error when trying to read the event logs through my win 7 pc.  It said
    it wanted to convert them to .evtx and I said ok then would get an error that the log was corrupt or unreadable.

  • Won't boot into safe mode

    My 2012 iMac 27" was randomly rebooting itself, while in Sleep. I assumed this was due to the cheap 32 GB memory I bought, but before I could change it back to the original memory, to test, the Mac booted into Safe Mode (I assume - a progress bar showing at the bottom of the boot screen, below the Apple logo), and did not get further than a half the way, and then shut down. I swapped the memory to the original 8GB. I tried booting again, no buttons held down, as then it wouldn't get further than a quarter of the way. Further attempts to boot do not work, even when holding down Option to choose the boot disk, pressing Shift for Safe Mode, or Option-S for Single User Mode. I assume it's trying to boot in Safe Mode, but failing?
    I also tried using a good Mac with the bad Mac as the Target Disk boot mode - the good Mac does not see the bad Mac...
    I have an external DVD drive, but that isn't an option as I can't go into boot drive select mode. What are my options, apart from sending the iMac back?

    Booting into the Recovery HD should allow you to effect repairs - that's the point of it, so it's a bit concerning that it won't allow you to. The Recovery HD is a partition on the internal drive that should allow you to effect repairs to the Macintosh HD, albeit part of the same physical disk.
    I'm no expert, but I'd be concerned that the hard disk is on the way out. Do you have backup of everything - Time Machine or a bootable clone, perhaps?
    Maybe have another try with Command+r. If it fails I'm not sure what would be the best next step - it depends if you have a full and up-to-date backup of your disk so that you can restore.
    One of the options of the Recovery HD is to allow you to re-install the OS, which won't delete your data.
    The more extreme step would be Internet Recovery which would involve erasing everything and re-installing via the internet.
    Worth reading this carefully before proceeding: http://support.apple.com/kb/HT4718
    Disk Warrior from Alsoft (not cheap) is another possibility for recovering damaged disks, although it's not a guaranteed solution.

  • Help! MacBook Pro only boots in Safe Mode and runs extremely slow (bonus: happened in Brazil and there are no Apple stores here - I need you guys!)

    It's a MBP mid 2010. Last year it had some problems and an Apple authorised shop changed the HD and upgraded the OS from Snow Leopard to Lion. After that it seemed fine. Recently it started getting very slow and apps (e.g. Chrome, Flash) would crash. At some point it seemed stuck so I gave it a hard shutdown - bad idea. After that it would only boot in Safe Mode. I ran repar disk and repair permissions from the Disk Utility and it booted normally again but extremely slow. I upgraded to OS X 10.8.2, but didn't solve it. I tried booting with Command D to have a hardware diagnostic - it wouldn't boot and now it only boots in Safe Mode.
    All data is backed and I have an external HD (but not an OS X Disc). Ready to anything. Help please!
    Utility Disk Logs
    Repairing permissions for “Macintosh HD”
    Group differs on “Library/Java”; should be 0; group is 80.
    Permissions differ on “Library/Java”; should be drwxr-xr-x ; they are drwxrwxr-x .
    Repaired “Library/Java”
    Warning: SUID file “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent” has been modified and will not be repaired.
    Permissions differ on “System/Library/Frameworks/CoreGraphics.framework/CoreGraphics”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
    Repaired “System/Library/Frameworks/CoreGraphics.framework/CoreGraphics”
    Permissions differ on “System/Library/Frameworks/CoreGraphics.framework/Resources”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
    Repaired “System/Library/Frameworks/CoreGraphics.framework/Resources”
    Permissions differ on “System/Library/Frameworks/CoreGraphics.framework/Versions/Current”; should be lrwxrwxrwx ; they are lrwxr-xr-x .
    Repaired “System/Library/Frameworks/CoreGraphics.framework/Versions/Current”
    Permissions repair complete
    Verifying volume “Macintosh HD”
    Checking file systemPerforming live verification.
    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 Macintosh HD appears to be OK.
    Verifying and repairing partition map for “ST9500325AS Media”
    Checking prerequisites
    Checking the partition list
    Adjusting partition map to fit whole disk as required
    Checking for an EFI system partition
    Checking the EFI system partition’s size
    Checking the EFI system partition’s file system
    Checking all HFS data partition loader spaces
    Reviewing boot support loaders
    Checking Core Storage Physical Volume partitions
    Updating Windows boot.ini files as required
    The partition map appears to be OK

    See this for incompatible log in items
    https://support.apple.com/kb/TS4348
    Also you can perform #1 and #2 as these occur before Safe Mode, so you just reboot again with Shift key if you need to enter Safe Mode again.
    At this point it sounds like your hard drive is dying or some sort of other hardware issue which I can only advise this.
    Try to install OS X on a external drive and boot from it, if it's fine then you know your internal boot drive is dying.
    Create a data recovery/undelete external boot drive
    You can replace your internal drive yourself.
    OtherWorld Computing is pretty good about providing drives and tool kits to perform that function yourself.
    Install/upgrade RAM or storage drive in Mac's

  • Won't boot in safe mode

    Hi,
    I can't get my PowerBook to boot in safe mode. I hold the shift key after the startup chime, then release it when I see the gray apple and progress spinner; but the spinner spins for a while and eventually the computer shuts off. I can boot up normally, but I'm trying to boot in safe mode to rectify a problem I have updating Office 2004. I tried zapping the PRAM, but that didn't make a difference.
    Thanks,
    Michael

    Well, according to DiskWarrior my news isn't good: "DiskWarrior has successfully built a new directory for the disk named “Macintosh HD.” The new directory cannot replace the original directory because of a disk malfunction. A disk malfunction is a failure of or damage to any mechanical component of the disk device, or any component connected to it."
    So I suppose my HD is on its way out, although it's not exhibiting much in the way of problems yet, and the S.M.A.R.T. status is still verified. And, rather interestingly, I can no longer use Disk Utility to Verify or Repair disk when I'm booted up from an external drive. I get this message:
    Repairing disk failed with error Could not unmount disk
    Which just seems weird, since this is the same way I'm running DiskWarrior.
    I love this PowerBook but I'm not sure I want to invest the time or expense in replacing the HD in a PowerPC-based machine. I assume new apps will soon be demanding more than that chip can handle. Does this message of doom from DiskWarrior generally reliably indicate the drive is beyond repair?
    Thanks, Carolyn, and to anyone who wants to chime in.
    Michael

Maybe you are looking for

  • MC.9 Stock value not correct

    Dear Friends In  mc.9 stock value is showing different than MMBE stock. What will be the reason? Regards,

  • Excise details in MIGO

    Dear Guru's, I am creating Goods receipt for STO process. In this transaction, after filling the excise invoice and date the system will pick excise amounts automatically. But that was not happening. Pls tell me wat are the other settings to be  main

  • Can't MOVE images from one project to another: must not understand

    Greetings, I have two questions as a result of aperture not working the way that I have read on forums etc. and am wondering what i am doing wrong 1) How do I MOVE images from project to project without duplicating masters or versions 2) how do I del

  • Credit deduction even when no usage?

    I have edge activated in my iPhone. Even when my iPhone is on standby , my iPhone is still using data , even though all push notifications are turned off! Why is it consuming data while there is no usage?

  • SPOOL with the right record length

    I have implemented a SQL script to download a "package" and "package body" definition into a file, in a windows environment. To avoid "truncate" lines (split in two lines) in the file , I use the "SET LINESIZE v_max_length", where v_max_length is the