My MBP won't boot anymore after "repair disk" and "repair disk permission"

My 2011 MBP 15 with Lion stopped working after I attempted to use Disk Utility to "repair disk" and "repair disk permission". 
It was having weird issues before I attempted the repairs, it was freezing every few seconds no matter what I am doing, the whole thing would freeze with only the mouse movable. then after a few seconds it goes back to normal again. This happened after I downloaded and installed some updates from Apple. I don't know if the updates would cause this or it's something else.
In Disk Utility, "Repair Disk Permission" took 5 hours.  While "Repair Disk" resulted in "Disk utility can't repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed up files".
Now when it boots, there's a loading bar under the Apple logo, it loads half way and shuts down itself. 
I can still get into CMD+R Utilities though.
Any idea how I can extract the data out of the disk?  I'm going to format and do a clean install.

mike2016 wrote:
 This happened after I downloaded and installed some updates from Apple. I don't know if the updates would cause this or it's something else. Now when it boots, there's a loading bar under the Apple logo, it loads half way and shuts down itself.
A stopped loading bar is indicative of a failed firmware install that didn't complete, it's trying to install and is failing.
Do a PRAM reset
https://support.apple.com/kb/HT1379
Reboot into Safe Mode, (shift key down) then reboot normally and see if that fixes the issue.
https://support.apple.com/kb/TS2570
You may have to try to reinstall your firmware manually, you'll need another disk burning Mac
Find your exact firmware(s) here (or on Apple Downloads page)
https://support.apple.com/kb/HT1237
Apply instructions here
https://support.apple.com/kb/HT2213
Lastly it could be your boot drive is failing or something wrong happened with the update and accounting for all the to the other issues.
A OS X "overwrite" may solve the issue, may not.
See 10.5, 106. 10.7 OS X "overwrite" here
https://discussions.apple.com/message/16276201#16276201

Similar Messages

  • Won't boot anymore after nvidia-xconfig

    Hey Guys,
    Got a problem with my Arch Linux here, hope you can help.
    Today I tried to install the official Nvidia Driver and BumbleBee following along the great Wiki on this topic.
    Everything worked just fine and I also could run optirun gfxgear or somemthing like this.
    I wanted to switch to the Nvidia Settings in the settings menu and it told me to configure my xconfig and restart x so I typed nvidia-xconfig in the terminal and it gave me an success output.
    I restarted my system and now it hangs on the graphical thing I think. It won't boot anymore.
    Hope you can help me out.
    Thanks alot
    Edit: My Nvidia Card is a Nvidia GT 740M if this matters
    Last edited by Whitz (2015-02-09 11:02:41)

    No, I have a laptop with 2 graphic cards an intel hd4000 and a nvidia gt 740m.
    I ran the Arch Linux installation well until I tried to get the nvidia gt working with bumblebee.
    I followed the wiki of the bumblebee topic and it worked well. I wanted to switch into the nvidia settings and it told me my x isnt configured properly and I should type nvidia-xconfig and restart X.
    After the restart it won't boot to the graphical interface anymore.
    Hope this cleared up the things
    Also I dont get any errors but it just wont load..
    Last edited by Whitz (2015-02-09 12:08:49)

  • IMac won't boot anymore after power cut

    Thanks to the great storms in New Jersey, my iMac does not boot anymore after a power cut. Does not get past the apple logo screen with the spinning wheel and keeps rebooting every 2 minutes.
    I was able to mount the HD via Firewire on a host machine and the disk seemed fine.
    I booted from the Install disk and ran Disk Utility - seemed fine though I could not verify the disk permissions ?
    One other thing - I seemed to remember the white light (front bottom right) was blinking before during start-up. Now it goes and stays black after couple of seconds.
    Help please,
    Philippe

    HI Phillipe and Welcome to Apple Discussions...
    If you haven't done so, try running the Apple Hardware Test.
    http://support.apple.com/kb/HT1509
    I doubt repairing disk permissions can't help this problem. It sounds like a hardware issue.
    *"I booted from the Install disk and ran Disk Utility - seemed fine though I could not verify the disk permissions ?"*
    When you ran Disk Utility via Firewire, did you actually Verify the hard disk for errors?
    Carolyn

  • Btrfs: System won't boot anymore after unclean shutdown

    Hi,
    I have a problem with my ArchLinux (kernel 3.19.2-1-ARCH).
    I have my root partition as BTRFS and no /boot partition.
    After an unclean shutdown the system won't boot anymore.
    GRUB loads the kernel and the kernel starts but it hangs saying: Mounted /dev/sda3 on real root.
    Then, I have to start a Live CD and do:
    btrfsck /dev/sda3
    After that the system boots correctly.
    I've tried adding fsck to the HOOKS in the mkinitcpio.conf file and in fact it tries to fsck the filesystem (but with BTRFS, fsck.btrfs doesn't work...)
    What can I do?
    Thanks

    I'm also having this problem. I tried booting up the netinstall image to debug it, but I can't mount my btrfs volume from there either: mount just hangs. After a while, the kernel goes:
    [...] INFO: task mount:612 blocked for more than 120 seconds.
    [...] Not tainted 3.19.2-1-ARCH #1
    [...] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    [...] INFO: task btrfs-transacti:636 blocked for more than 120 seconds.
    [...] Not tainted 3.19.2-1-ARCH #1
    [...] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    From this post I guessed that I might just need to wait so that I could defrag the volume once it was mounted, but it's been hanging for over 15min now (the message above continues to come up periodically).
    Like the OP in the thread I linked to above, my btrfs volume is inside an LVM volume (which is on dm-crypt). Don't know whether that's relevant.
    Output of btrfs-check:
    Checking filesystem on /dev/pixie/btrfs
    UUID: e04cc661-e31a-4dbf-870d-664bc913e34a
    found 76855677062 bytes used err is 1
    total csum bytes: 72928436
    total tree bytes: 2092515328
    total fs tree bytes: 1888452608
    total extent tree bytes: 104644608
    btree space waste bytes: 357251032
    file data blocks allocated: 181197139968
    referenced 109440282624
    btrfs-progs v3.19
    dmesg output:
    [ 36.824998] Btrfs loaded
    [ 36.826713] BTRFS: device fsid e04cc661-e31a-4dbf-870d-664bc913e34a devid 1 transid 98618 /dev/dm-3
    [ 46.219014] BTRFS info (device dm-3): disk space caching is enabled
    [ 46.259830] BTRFS: detected SSD devices, enabling SSD mode
    [ 240.333313] INFO: task mount:539 blocked for more than 120 seconds.
    [ 240.335542] Not tainted 3.19.2-1-ARCH #1
    [ 240.337795] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    [ 240.340263] mount D ffff8800cf2837f8 0 539 453 0x00000000
    [ 240.340277] ffff8800cf2837f8 ffff8800cf2331b0 0000000000013f00 ffff8800cf283fd8
    [ 240.340286] 0000000000013f00 ffffffff81818540 ffff8800cf2331b0 ffff8802094f67a8
    [ 240.340291] 0000000000000004 ffff8800cf283758 ffffffffa0a2fc91 ffff8802094f67a8
    [ 240.340298] Call Trace:
    [ 240.340335] [<ffffffffa0a2fc91>] ? set_extent_buffer_dirty+0x71/0xc0 [btrfs]
    [ 240.340357] [<ffffffffa0a05796>] ? btrfs_buffer_uptodate+0x56/0x80 [btrfs]
    [ 240.340366] [<ffffffff8155e999>] schedule+0x29/0x70
    [ 240.340389] [<ffffffffa0a47745>] btrfs_tree_lock+0x65/0x200 [btrfs]
    [ 240.340396] [<ffffffff810b4380>] ? wait_woken+0x90/0x90
    [ 240.340410] [<ffffffffa09e5cd9>] btrfs_search_slot+0x799/0xaa0 [btrfs]
    [ 240.340425] [<ffffffffa09e79f5>] btrfs_insert_empty_items+0x75/0xd0 [btrfs]
    [ 240.340446] [<ffffffffa0a47a37>] btrfs_insert_orphan_item+0x67/0xa0 [btrfs]
    [ 240.340465] [<ffffffffa0a4a12e>] insert_orphan_item+0x5e/0x90 [btrfs]
    [ 240.340482] [<ffffffffa0a4c531>] replay_one_buffer+0x361/0x380 [btrfs]
    [ 240.340504] [<ffffffffa0a2f244>] ? alloc_extent_buffer+0x34/0x370 [btrfs]
    [ 240.340523] [<ffffffffa0a488f3>] walk_down_log_tree+0x1d3/0x410 [btrfs]
    [ 240.340540] [<ffffffffa0a48bfb>] walk_log_tree+0xcb/0x1d0 [btrfs]
    [ 240.340558] [<ffffffffa0a507f7>] btrfs_recover_log_trees+0x1e7/0x490 [btrfs]
    [ 240.340575] [<ffffffffa0a4c1d0>] ? replay_one_dir_item+0xf0/0xf0 [btrfs]
    [ 240.340596] [<ffffffffa0a08b3e>] open_ctree+0x17ae/0x2030 [btrfs]
    [ 240.340609] [<ffffffffa09dd633>] btrfs_mount+0x843/0x920 [btrfs]
    [ 240.340618] [<ffffffff8117b7aa>] ? pcpu_alloc+0x35a/0x680
    [ 240.340628] [<ffffffff811d5d68>] mount_fs+0x38/0x1c0
    [ 240.340634] [<ffffffff8117bb05>] ? __alloc_percpu+0x15/0x20
    [ 240.340641] [<ffffffff811f116b>] vfs_kern_mount+0x6b/0x120
    [ 240.340647] [<ffffffff811f4184>] do_mount+0x224/0xb40
    [ 240.340653] [<ffffffff811f4dae>] SyS_mount+0x7e/0xe0
    [ 240.340661] [<ffffffff81562809>] system_call_fastpath+0x12/0x17
    [ 240.340671] INFO: task btrfs-transacti:561 blocked for more than 120 seconds.
    [ 240.342927] Not tainted 3.19.2-1-ARCH #1
    [ 240.345175] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    [ 240.348473] btrfs-transacti D ffff88020b88bd98 0 561 2 0x00000000
    [ 240.348483] ffff88020b88bd98 ffff880211edc590 0000000000013f00 ffff88020b88bfd8
    [ 240.348491] 0000000000013f00 ffff8802162289f0 ffff880211edc590 ffff8802094a70c8
    [ 240.348496] ffff8802094d8000 ffff880200000000 ffff8802094d8000 ffff880200000033
    [ 240.348501] Call Trace:
    [ 240.348511] [<ffffffff811b5d1a>] ? kmem_cache_alloc+0x16a/0x180
    [ 240.348525] [<ffffffffa09e07ca>] ? btrfs_free_path+0x2a/0x40 [btrfs]
    [ 240.348543] [<ffffffffa0a64213>] ? __btrfs_run_delayed_items+0xf3/0x1d0 [btrfs]
    [ 240.348550] [<ffffffff8155e999>] schedule+0x29/0x70
    [ 240.348568] [<ffffffffa0a0b555>] btrfs_commit_transaction+0x2a5/0xbe0 [btrfs]
    [ 240.348573] [<ffffffff810b4380>] ? wait_woken+0x90/0x90
    [ 240.348590] [<ffffffffa0a06fc5>] transaction_kthread+0x1d5/0x240 [btrfs]
    [ 240.348605] [<ffffffffa0a06df0>] ? btrfs_cleanup_transaction+0x5a0/0x5a0 [btrfs]
    [ 240.348611] [<ffffffff81091748>] kthread+0xd8/0xf0
    [ 240.348617] [<ffffffff81091670>] ? kthread_create_on_node+0x1c0/0x1c0
    [ 240.348624] [<ffffffff81562758>] ret_from_fork+0x58/0x90
    [ 240.348629] [<ffffffff81091670>] ? kthread_create_on_node+0x1c0/0x1c0
    Last edited by ouroboros8 (2015-04-02 12:37:25)

  • MBP won't boot up after Battery update

    I downloaded the update this afternoon on my MBP. I restarted my machine but it would not load OSX. It keeps going to grey screen with the apple logo and waits there for 6-7 minutes and restarts itself. It keeps doing this over and over. I've tried holding down the keys to reset memory, I've restarted it plugged in, and unplugged. I inserted Disc Warrior. Nothing has worked. Any ideas?

    Try this
    Boot holding down Apple/S and don't let go until you see scrolling text.
    When that stops and you see a root#: prompt enter
    fsck -fy
    Let it run through all the checks and repairs.
    If it fails first time, at any time, or finds and fixes a fault - run the command again and keep doing so (some fixes can take several passes) until it says "Appears to be OK" then enter
    reboot

  • MBP won't boot up after Onyx maintenance

    Did a complete automation on the latest version of Onyx for Lion since my mac was running a little slow.. And now my MBP doesn't boot at all! Just gets stuck on the apple logo. What do I do?

    THere are a few things to try.
      Start in safe mode
      Reset PRAM
       Hold down command-R to start in the lion recovery volume then run disk utility to repair the disk
       Do an SMC reset.
    You can try one of these methods then move on if that does not work.
    Jay

  • Sol10 won't boot anymore after patching

    Hi,
    I tried patching (Recommended patches of 1/1/2008) an old Netra T1 running Sol10 while running in multi-user mode (yes, I'm that stupid). Unfortunately when I rebooted the server it won't come up again all I get is:
    Netra T1 200 (UltraSPARC-IIe 500MHz), No Keyboard
    OpenBoot 4.0, 512 MB memory installed, Serial #51796331.
    Ethernet address 0:3:ba:16:59:6b, Host ID: 8316596b.
    Executing last command: boot disk
    Boot device: /pci@1f,0/pci@1/scsi@8/disk@0,0 File and args:
    SunOS Release 5.10 Version Generic_127111-05 64-bit
    Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    /kernel/fs/sparcv9/specfs: undefined symbol 'stralloctty'
    WARNING: mod_load: cannot load module 'specfs'
    (Can't load specfs) Program terminated
    ok
    Trying a 'boot disk -s' or 'boot disk -r' doesn't make any difference.
    Unfortunately the server is located in another country so booting from cdrom is not an option. I only have serial and network access (limited by a firewall that I don't control so remote booting is not an option either).
    Anybody any idea how I can boot my server?
    Thanks in advance,
    Nico

    I think a call to Sun is in order... however I do have a long shot you could try (at your own risk or course :) )
    I checked a Solaris 10 system and confirmed that stralloctty is used by specfs (sparcv9)
    I then check the 32-bit version on specfs and it doesn't use stralloctty...
    You could trying booting the server in 32-bit mode instead of 64-bit while this wont solve the problem is may let you boot so you can fix it....
    "........To get the image to install switch the machine to 32bit mode (not supported for newer machines). To set the mode, halt the machine and at the ok prompt type setenv boot-file kernel/unix
    To change the machine back to 64bit mode type the following at the ok prompt: setenv boot-file kernel/sparcv9/unix........"
    NOTE: I have not ever tried this so I would test it on a machine you have locally first!!!
    BTW: I don't think patching in multi user is stupid, I think if you do it (and I do) you need to quiesce the system and make sure you have a backout plan e.g. detached mirror.
    I am guessing something went amiss in the patching and the kernel is stuffed i.e. half applied patch

  • Powermac G5 1.8Ghz June 2004 won't boot anymore

    Hi all,
    Past week i've bought a second hand PM G5. At first it seems to be all ok, but right now its not working anymore.
    I've managed to install the OSX on the first evening i've had the PM G5. After installing evrything seemed to be fine. But after 30 minutes surfing on the internet, it froze. I had to give it an hard reset by holding down the power button.
    After turning it of, it won't boot anymore. after a few times trying with 10 secconds between it, i unpluged the powercabel for 2 minutes. Wile turning it on after 2 minutes, it was booting , but it stopped booting after 1,5 minute and froze.. after hard resetting it, i've managed to boot it right. The OS seemed to be ok again, but after 5 till 10 minutes it froze again.
    Right now it won't boot anymore... it starts (without the front light, this light only blinks fast once i turn it on, but after that no more. Sometimes it won''t even flash.
    I've been buzzy replacing some components to get to know if it was a hardware fail. I've first replaced the PSU with two other PSU's from the PM G5, but won't do a thing.
    The i've replaced the memory with 4 kind of difrent pairs, but won't do a thing either. At last i replaced the Logic Board, this won't even do a thing about it.
    Of course i replaced the PRAM battery first, but also this won't help me.
    I've tested it in AHT, but evrything was working well, according to AHT. I've managed to get the system log, but nothing scarry though here also, only some 122 errors some times. (download the system log here: http://www.mijnbestand.nl/Bestand-F4DDN66WLRCI.log )
    I've reset al things possible like PRAM reset, PMU reset. Nothing seem to be working.
    What can i do next to get this thing work?? I'm getting nut's here..
    Please help..
    Thanks a Lot
    MArtijn Snoek

    Hi martijnsnoek, and a warm welcome to the forums!
    Can you count the beeps or flashes?
    1 beep = no RAM installed
    2 beeps = incompatible RAM types
    3 beeps = no good banks
    4 beeps = no good boot images in the boot ROM (and/or bad sys config block)
    5 beeps = processor is not usable
    In addition to the beeps, on some computers the power LED will flash a corresponding number of times plus one. The LED will repeat the sequence after approximately a 5-second pause. The tones are only played once.
    Note: In this case, a flash is considered to be 1/4 second or 250 ms or greater in length.
    http://support.apple.com/kb/HT1547
    So, with the info you given, two things come to mind...
    Bad solder joints around the RAM slots, try heating that area with a Hair Dryer for 3 to 5 minutes, then see if it starts.
    If you can get it running, Get Temperature Monitor to see if it's heat related...
    http://www.macupdate.com/info.php/id/12381/temperature-monitor
    And/or iStat Pro...
    http://www.islayer.com/apps/istatpro/
    If you have any temps in the 70°C/160°F range, that's likely it.
    BTW, have you blown the dust out of it since you got it?

  • MBP won't boot - "GRUB_" - tried installing ubuntu on an external drive

    so i tried installing ubuntu netbook remix onto an external drive, and upon restarting my MBP won't boot to my internal HDD, once it displayed "GRUB_" with a blinking cursor, but is otherwise unresponsive.
    now i just get the folder with the ? on it.
    I've run disk util, repair permission, repair disk and still no luck.
    i can boot the MBP into target disk mode and see the HDD on my other system and all appears to be good, and if i boot to the install dvd, the HDD shows up under the "startup disk" menu, but it just doesn't boot.
    any thoughts on how to fix this?

    So I have an imac that I have had for about 3yrs. About several months ago, it started acting a little strange, it wouldnt pick up the mouse or the keyboard at times even thought they were plugged in properly to the usb port, sometimes both would work sometimes one or the other would work and other times they worked fine. About a month or 2 ago, I went to turn my imac on and it got to the screen where the little circular icon pops up implying it is loading, stayed that way for 2-3min then turned of and turned itself back on and did the same thing, made the apple sound got to the load screen turned of after 2-3min then turned back on, it has been doing that for the past month. What do I do?

  • Won't boot anymore but in safe mode

    My laptop won't boot anymore. I get a gray screen with a prohibition sign. Here's what I found so far:
    If I boot in the verbose mode it gets stuck on something like Looking for boot device.
    I zapped the PRAM. Didn't help.
    I can boot in safe mode.
    I used Disk Utility to check the drive and permisions. Everything ok.
    I can't boot from the original Snow Leopard DVD. I press C, the drive spins then stops.
    I reinstalled Snow Leopard from the safe mode. Didn't help.
    In safe mode Safari is crazy slow. Firefox runs full speed.
    Any idea?

    Reinstall OS X without erasing the drive
    Do the following:
    1. Repair the Hard Drive and Permissions
    Boot from your Snow 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 click on the Repair Permissions button. Wait until the operation completes, 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.
    2. Reinstall Snow Leopard
    If the drive is OK then quit DU and return to the installer.  Proceed with reinstalling OS X.  Note that the Snow Leopard installer will not erase your drive or disturb your files.  After installing a fresh copy of OS X the installer will move your Home folder, third-party applications, support items, and network preferences into the newly installed system.
    Download and install the Combo Updater for the version you prefer from support.apple.com/downloads/.
    Unless you can boot from your installer DVD there's nothing you can do to reinstall OS X, so I'm not sure how you did reinstall as you said.
    Booting From An OS X Installer Disc
    1. Insert OS X Installer Disc into the optical drive.
    2. Restart the computer.
    3. Immediately after the chime press and hold down the "C" key.
    4. Release the key when the spinning gear below the dark gray Apple logo appears.
    5. Wait for installer to finish loading.

  • Mac mini won't boot anymore

    My Mac mini won't boot anymore. It's been running fine for months.
    It's running Leopard Server 10.5.2 Build 9C31
    It starts to boot, I get the first spinning gear with the gray screen, then the blue desktop blinks, then a second spinning gear on a gray screen and it appears to hang (the gear stops spinning).
    I booted off the install DVD, ran disk utility, repaired the HD, repaired the permissions: the behavior is the same.
    Safe mode doesn't work (same hang as above).
    Single user mode does work.
    I can connect to it via Server Admin while it appears hung.
    The last few lines of the system log are:
    May 15 18:38:58 server emond[67]: SetUpLogs: uid = 0 gid = 0
    May 15 18:38:58 server emond[67]: SetUpLogs: opening /Library/Logs/EventMonitor/EventMonitor.error.log
    May 15 18:38:59 server kextd[23]: writing kernel link data to /var/run/mach.sym
    May 15 18:39:09 server KernelEventAgent[59]: tid 00000000 received unknown event (12)
    May 15 18:39:20 server kernel[0]: display: Not usable
    May 15 18:39:20 server com.apple.KerberosAutoConfig[126]: Kerberos configuration is up to date
    May 15 18:39:20 server com.apple.ATSServer[125]: FODBCheck: New annex file created
    May 15 18:39:21 server ARDAgent [130]: ******ARDAgent Launched******
    May 15 18:39:21 server com.apple.KerberosAutoConfig[132]: Kerberos configuration is up to date
    May 15 18:39:22 server ARDAgent [130]: call logout from LoginLogoutProxyCallBackFunction
    May 15 18:39:22 server com.apple.launchd[1] (com.apple.RemoteDesktop.agent): Throttling respawn: Will start in 9 seconds
    May 15 18:39:24 server loginwindow[58]: Login Window Started Security Agent
    May 15 18:39:29 server servermgrd[53]: servermgr_calendar: created default calendar virtual host
    May 15 18:39:31 server ARDAgent [146]: ******ARDAgent Launched******
    May 15 18:39:32 server ARDAgent [146]: ******ARDAgent Ready******
    May 15 18:39:33 server mdworker[109]: (Error) SyncInfo: Boot-cache avoidance timed out!
    May 15 18:39:54 server Python[47]: CGImageSourceCreateWithData data parameter is nil
    May 15 18:39:54 server com.apple.wikid[47]: Thu May 15 18:39:54 server.jeff.carpenter.name Python[47] <Error>: CGImageSourceCreateWithData data parameter is nil\n
    May 15 18:39:56 server kernel[0]: AppleYukon2 - bad packet received. length: 1440, packet status bits: MII error
    May 15 18:39:56 server kernel[0]: AppleYukon2: 00000000,00000001 sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
    May 15 18:49:54 server kernel[0]: serialnumberd 194 FSWRITEDATA SBF /dev/dtracehelper 13 (seatbelt)
    May 15 18:49:54 server kernel[0]: serialnumberd 194 FSREADDATA SBF /dev/autofs_nowait 13 (seatbelt)
    May 15 18:49:54 server kernel[0]: serialnumberd 194 FSREADDATA SBF /usr/sbin 13 (seatbelt)
    May 15 18:55:12 server kernel[0]: AppleYukon2 - bad packet received. length: 23, packet status bits: MII error
    Any ideas?

    Yes, it's been running Server since I purchased it.
    I doubt the serial number is in use elsewhere: I purchased the 10-user version at a retail store in a sealed package and I've only installed it once.

  • My 2006 iMac running Snow Leopard won't boot even after erasing and re-installing Snow Leopard (via my MacBookPro), either from the HD or DVD drive.  Can't get it to run Hardware Test.  Disk Utility says disk OK - files are there. What can I do?

    My 2006 iMac running Snow Leopard won't boot even after erasing and re-installing Snow Leopard.   I erased and re-installed by putting the iMac in Target Disk mode and usin my MacBookPro as the host.  But after numerous attempts I still can't get it to boot either from the HD or DVD drive. I just get the white screen after the wheel stops spinning.  I can't get it to run Hardware Test - just get the white screen.  If I use Disk Utility via my MBP it says the disk appears OK. All the Snow Leopad files appear to have been installed. What can I do?

    Hi-NRG Bwoy wrote:
    I erased and re-installed by putting the iMac in Target Disk mode and using my MacBookPro as the host.
    Reet the SMC and the PRAM
     Cheat sheet to help diagnose and fix your Mac
    Perhaps you installed the wrong version OS X onto the iMac, you can't use the disk from another Mac.
    clean the disk.
    If it's not working then use this method to create a bootable 10.6 USB from the iMac machine specific 10.6 disk or the 10.6.3 retail disk on your other Mac, use it to boot the iMac with.
    http://www.maciverse.com/install-os-x-snow-leopard-from-usb-flash-drive.html
    How to erase and install Snow Leopard 10.6

  • 2011 15" MBP won't boot past grey screen

    I came to turn on my 15" 2011 MBP OSX10.9.5 today, which had been left in sleep mode for a few days. The battery was flat, so I connected to the power supply and left it for a couple of hours. I then turned it on (no longer connected to power) and it made the familiar bong and showed the apple logo; the screen then went grey, changed a few shades of grey and then stayed there, with a cursor on  screen, but nothing else. I powered off and retried.
    I then booted successfully into the bootcamp partition, did my work in Windows and then tried rebooting into the OSX partition, with the same outcome as before.
    I booted to the recovery console and did a repair permissions and repair disk on the OSX partition; it didn't indicate any particular problems. Still didn't boot though. The OSX and Windows partitions are on the same physical hard disk, which is an SSD which I fitted myself about a year ago (no problems till now).
    These symptoms seem to indicate that there is not a problem with the hardware, as Windows boots and runs just fine. I am surmising that the problem might lie with the OSX partition.
    Any suggestions?
    Also, I should confess at this point that the disk has not been backed up fully, so there is some data I would like to recover ideally.....

    OS X- Gray screen appears during startup
    Question (?) Mark, Blinking Folder, or Gray Screen at Startup
    These are related but not identical issues. Their causes are outlined in Intel-based Mac- Startup sequence and error codes, symbols. Solutions may be found in:
    A flashing question mark appears when you start your Mac
    Mac OS X- Gray screen appears during startup
    In most cases the problems may be caused by one or more of these:
    a. Problem with the computer's PRAM - See Resetting your Mac's PRAM and NVRAM.
    b. Boot drive's directory has been corrupted - Repair with Disk Utility.
    c. Critical system files are damaged or deleted - Reinstall OS X.
    d. The disk drive is physically non-functional - Replace the hard drive.
    Note that the information I have provided is what Apple recommends, If other users suggest different solutions than found here, then be sure what they recommend does not impact on your warranty, if any, or ability to get continuing Apple service.
    Please don't start removing drives or changing cables unless you know what you are doing and have exhausted other non-invasive alternatives outlined here. If you perform any work yourself that is unapproved by Apple, then you will void any warranty you may have and lose all further Apple Support.
    Repair the Hard Drive and Permissions
    Boot from your Snow 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 click on the Repair Permissions button. Wait until the operation completes, 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.
    The main difference if you are using Lion or Mountain Lion is that you must first boot from the Recovery HD. Simply boot from the Recovery HD to perform the above.
    Reinstall Snow Leopard Without Erasing The drive
    1. Repair the Hard Drive and Permissions
    Boot from your Snow 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 click on the Repair Permissions button. Wait until the operation completes, 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.
    2. Reinstall Snow Leopard
    If the drive is OK then quit DU and return to the installer.  Proceed with reinstalling OS X.  Note that the Snow Leopard installer will not erase your drive or disturb your files.  After installing a fresh copy of OS X the installer will move your Home folder, third-party applications, support items, and network preferences into the newly installed system.
    Download and install Mac OS X 10.6.8 Update Combo v1.1.
    Reinstalling Lion/Mountain Lion 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.
    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. 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 click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu.
    Reinstall Lion/Mountain Lion: Select Reinstall Lion/Mountain Lion 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.

  • My MBP won't boot!

    When I try to start it up it opens the load screen. I get the apple pic followed by a rotating dotted line circle (that means its thinking) and the progress meter. When the meter is 2/3 full it disappears and I'm left with a dotted circle and the apple. It stays as such until I turn it off.
    I booted MBP from the CD to try to repair the disk with Disk Utilities but DU couldn't find my HD. I rebooted, this time running the Apple Hardware test. It said my HD was hunky-dory. I rebooted again from the CD and DU still couldn't see my HD. I rebooted in single-user mode and ran the file system check (fsck). THAT said that it found minor errors, and that it successfully repaired them. Upon a second run, fsck found no problems. I tried starting normally again, but was greeted by my initial problem.
    Booting from the CD, DU could now find my elusive hard disk, so I first had it "repair disk permissions". It found many instances of something's value being 80 when it was supposed to be 0. It reset them, and I ran disk repair. It found some more minor problems and "fixed" them. It then had the audacity to tell me that everything is now OK. From there, neither running startup disk and selecting my HD nor giving the MBP a full reboot yields any deviation from the foremost scenario.
    I still have no idea what could be wrong with it. What else can I try? I need some answers from this machine! I won't be denied!

    when you say "low-level" reformat what exactly do you
    When booted from your install DVD and have Disk Utility open, select "Zero out data" under Security Options. Note: This may take hours to complete before you can start the install.
    Here is a video on it: http://macosg.me/2/4y
    Check out the new remodeled MacOSG website! 24-hour Apple-related news & support.
     MacOSG: An Apple User Group  iTunes: MacOSG Podcast  Follow us on Twitter: MacOSG

  • Re: Satellite C850 won't boot anymore - broken HDD

    Hello Folks,
    I bought a *Toshiba Satellite C850 - 1F2* with *+Windows 8+*.
    After installing, upgrading to *+Windows 8.1+* and setting up everything, the whole machine worked pretty fine.
    BUT since yesterday the laptop won't boot anymore!
    When I turn it on, the HDD makes click and click and the system tries to boot from DVD, from USB, from HDD, from IPV4, from IPV6 and then it says, that there is no bootable device.
    Unfortunately I wanted to make the +Windows 8 Restoration-/Rescue-DVDs+ this weekend!
    Huh!!!
    Well, I still have an *+original Windows-7-DVD and license+*, which would be good as well (I used it the last years).
    *YET*, I cannot install *+Windows 7+*.
    It says something like that, that +this system is not available for Secure Boot+.
    I read about "Secure Boot".
    So I pressed F2, turned the laptop on and could with this reach the BIOS.
    It is a *+InsydeH20 Rev. 3.7+*.
    *BUT*, when I go to "Boot Mode" I can only see, that this option is greyed and I cannot change from +UEFI Boot+ to +CSM Boot+.
    Even the change of the HDD made no difference.
    I put in my old HDD with Windows 7 installed (wich works in the other laptop), but the system won't boot, for it is +not suitable for Secure Boot+.
    *So, WHAT NOW?*
    I mean, it cannot really be the Toshiba politics, that you need to throw away your laptop, if the HDD breaks, can it?
    For I didn't create the Rescue-DVD, I have just my Windows 7 DVD and another HDD with installed Windows 7.
    Do I need to buy another Windows 8 licence and another HDD, to install Windows 8 (suitable for Secure Boot) again?
    Would it even work like that?
    Or is there any chance to upgrade the BIOS, for that I can then change from UEFI Boot to CSM Boot?
    Or is there any other chance, to use my other HDD with Windows 7, or at least a new clean HDD, on wich I then can install my Windows 7 OS?
    I hope, that someone can give me any good advice, what to do now ... without throwing the Toshiba laptop away ;)
    Thanks in advance!

    If the HDD died, in needs to be replaced.
    If notebook is still covered by warranty, the HDD will be replaced free of charge. If warranty isnt valid, you will need to pay for the new HDD.
    I think this understandable.
    _Now some facts about the Recovery disk._
    If you did not create a recovery disk in the past, you could order the recovery medium on this page: http://backupmedia.toshiba.eu/landing.aspx
    The recovery disk would install the Toshiba image and would set the notebook back to the same state like at the first day of purchase.
    _Regarding the Win 7 installation:_
    Usually to install the non UEFI capable system, the secure boot needs to be disabled and boot mode needs to be set to CSM mode.
    If this isnt possible you should update the BIOS but to do that you need an running Windows system (Win 8).

Maybe you are looking for