OSX won't boot completely

When my MBP boots it stays at the following state:
The mouse works, the keyboard works, i can change the volume and brightness.
But it won't continue to the desktop, it should auto-login.
Before this happend i've shutdown my MBP by holding the powerbutton for 5 seconds.
Because none of the applications responded and the menubar didn't respond.
I've tried removing preferences & caches of the user. plist files for the loginitems,desktop & windowserver.
I've tried repairing the disk, it was ok, I fixed te permissions.

Reinstalling Mavericks, 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, Mavericks: Select Reinstall Lion/Mountain Lion, Mavericks 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.

Similar Messages

  • Mac OSx won't boot up after update to 10.6.7?

    Mac OSx won't boot up after update to 10.6.7?

    Hi Mike
    This is called a kernel panic, similar to s 'blue screen of death' on Windows. When you say you reinstalled 3 times, do you mean the OS or the Update?
    When does this kernel panic appear? You may have a hardware issue if it's happening on boot.
    Taylor

  • My Blackberry torch 9800 won't boot completely

    i have tried several times and have ejecting the battery several times but still not booting completely. it boots to about 99percent and then restarts again and again...

    Try booting in safe mode.
    Remove the battery.
    While holding down the back key, reinsert the battery and continue to hold the back key for another 20 seconds.
    if the device reboots then remove the last application or theme you installed.
    1. Please thank those who help you by clicking the "Like" button at the bottom of the post that helped you.
    2. If your issue has been solved, please resolve it by marking the post "Solution?" which solved it for you!

  • Created zone with defaults won't boot completely (Solaris 10, Update 1)

    If I create a zone with defaults, i.e. allowing the zone to inherit the typical package dirs, the resulting zone does not boot completely. When I attach to the zone via zlogin, the zone looks to be in an administrative state. It never boots to a point where one would typically enter in the initial configuration info, e.g. timezone and root password.
    However if I create the zone after first removing the inherited dirs, the zone boots to a state where it subsequently can be confiured and fully booted.
    Looks as if the SMF facilities are not fully initialized when the zone is configured to inherit its packages. This could be a red herring as I'm a newbie who's moved over from Linux and starting to understand SMF specifically and Solaris in general.
    I did not have this problem with Solaris 10. I've just installed Solaris 10 Update 1; the problem seems specific to that installation. I reinstalled and the problem persists.

    I snipped the output because there were some errors, which on retrospect seems to have been a silly decision. I repeated the process and captured the missing output:
    # zoneadm -z foo install
    Preparing to install zone <foo>.
    Creating list of files to copy from the global zone.
    Copying <5913> files to the zone.
    Initializing zone product registry.
    Determining zone package initialization order.
    Preparing to initialize <942> packages on the zone.
    Initialized <942> packages on zone.
    Zone <foo> is initialized.
    Installation of <1> packages was skipped.
    Installation of these packages generated warnings: <SUNWxwfnt
    SUNWxwplt SUNWxwcft SUNWjxmft SUNWxwpls SUNWpmowu
    SUNWxilrl SUNWolrte SUNWi13rf SUNWi15rf SUNWi2rf SUNWi5rf
    SUNWi7rf SUNWi9rf SUNWtxfnt SUNWdoc SUNWi1of SUNWi4rf
    SUNWi8rf SUNW1251f SUNWarrf SUNWxwoft SUNWxwxst
    SUNWkoi8f SUNWasu SUNWxrpcrt SUNWasac SUNWasdb
    SUNWasut>
    The file </zone/foo/root/var/sadm/system/logs/install_log> contains a log of the zone installation.The packages are related to App development and X11. I don't see any that might be related to SMF.
    The logfile is too large to post at over 37K lines. However there seemed to be a pattern to the package failures. Hopefully these greps highlight the important messages:
    # grep "partially failed" /zone/foo/root/var/sadm/system/logs/install_log
    Installation of <SUNWxwfnt> on zone <foo> partially failed.
    Installation of <SUNWxwplt> on zone <foo> partially failed.
    Installation of <SUNWxwcft> on zone <foo> partially failed.
    Installation of <SUNWjxmft> on zone <foo> partially failed.
    Installation of <SUNWxwpls> on zone <foo> partially failed.
    Installation of <SUNWpmowu> on zone <foo> partially failed.
    Installation of <SUNWxilrl> on zone <foo> partially failed.
    Installation of <SUNWolrte> on zone <foo> partially failed.
    Installation of <SUNWi13rf> on zone <foo> partially failed.
    Installation of <SUNWi15rf> on zone <foo> partially failed.
    Installation of <SUNWi2rf> on zone <foo> partially failed.
    Installation of <SUNWi5rf> on zone <foo> partially failed.
    Installation of <SUNWi7rf> on zone <foo> partially failed.
    Installation of <SUNWi9rf> on zone <foo> partially failed.
    Installation of <SUNWtxfnt> on zone <foo> partially failed.
    Installation of <SUNWdoc> on zone <foo> partially failed.
    Installation of <SUNWi1of> on zone <foo> partially failed.
    Installation of <SUNWi4rf> on zone <foo> partially failed.
    Installation of <SUNWi8rf> on zone <foo> partially failed.
    Installation of <SUNW1251f> on zone <foo> partially failed.
    Installation of <SUNWarrf> on zone <foo> partially failed.
    Installation of <SUNWxwoft> on zone <foo> partially failed.
    Installation of <SUNWxwxst> on zone <foo> partially failed.
    Installation of <SUNWkoi8f> on zone <foo> partially failed.
    Installation of <SUNWasu> on zone <foo> partially failed.
    Installation of <SUNWxrpcrt> on zone <foo> partially failed.
    Installation of <SUNWasac> on zone <foo> partially failed.
    Installation of <SUNWasdb> on zone <foo> partially failed.
    Installation of <SUNWasut> on zone <foo> partially failed.and# grep "not installed" /zone/foo/root/var/sadm/system/logs/install_log
    *** package <SPROmrdwf> was not installed:
    *** package <SPROdwrfb> was not installed:
    *** package <SPROlang> was not installed:
    *** package <SPROlangx> was not installed:
    *** package <SPROdwrfx> was not installed:
    *** package <SPROsbld> was not installed:
    *** package <SPROsbldx> was not installed:
    *** package <SPROrdbkb> was not installed:
    *** package <SPROrdbkx> was not installed:
    *** package <SPROcc> was not installed:
    *** package <SPROutool> was not installed:
    *** package <SPROmrcc> was not installed:
    *** package <SPROmrcom> was not installed:
    *** package <SPROmr3m> was not installed:
    *** package <SPROmrtcv> was not installed:
    *** package <SPROm9xs> was not installed:
    *** package <SPROsunms> was not installed:
    *** package <SPROsmsx> was not installed:
    *** package <SPROsmpx> was not installed:
    *** package <SPROmrsbe> was not installed:
    *** package <SPROsbe> was not installed:
    *** package <SPROpnsn> was not installed:
    *** package <SPROfd> was not installed:
    *** package <SPROupdck> was not installed:
    *** package <SPROcpl> was not installed:
    *** package <SPROcplx> was not installed:
    *** package <SPROcmpl> was not installed:
    *** package <SPROtlbn7> was not installed:
    *** package <SPROtll7> was not installed:
    *** package <SPROtl7x> was not installed:
    *** package <SPROtll7x> was not installed:
    *** package <SPROscl> was not installed:
    *** package <SPROsclx> was not installed:
    *** package <SPROmrstd> was not installed:
    *** package <SPROmrcpl> was not installed:
    *** package <SPROstl4h> was not installed:
    *** package <SPROstl4a> was not installed:
    *** package <SPROstl4o> was not installed:
    *** package <SPROstl4x> was not installed:
    *** package <SPROstl4y> was not installed:
    *** package <SPROftool> was not installed:
    *** package <SPROl90> was not installed:
    *** package <SPROl90x> was not installed:
    *** package <SPROl90s> was not installed:
    *** package <SPROl90sx> was not installed:
    *** package <SPROf90> was not installed:
    *** package <SPROmrftn> was not installed:
    *** package <SPROgc> was not installed:
    *** package <SPROlgc> was not installed:
    *** package <SPROgcx> was not installed:
    *** package <SPROlgcx> was not installed:
    *** package <SPROdbx> was not installed:
    *** package <SPROdbxx> was not installed:
    *** package <SPROjdbx> was not installed:
    *** package <SPROjdbxx> was not installed:
    *** package <SPROmrdbx> was not installed:
    *** package <SPROdemo> was not installed:
    *** package <SPROdmake> was not installed:
    *** package <SPROmrdmk> was not installed:
    *** package <SPROtdemo> was not installed:
    *** package <SPROmride> was not installed:
    *** package <SPROdbxui> was not installed:
    *** package <SPROsvc> was not installed:
    *** package <SPROxdplg> was not installed:
    *** package <SPROidext> was not installed:
    *** package <SPROjnsnb> was not installed:
    *** package <SPROjnsrt> was not installed:
    *** package <SPROjnsup> was not installed:
    *** package <SPROctags> was not installed:
    *** package <SUNWnbide> was not installed:
    *** package <SUNWnbcpp> was not installed:
    *** package <SUJAnbcpp> was not installed:
    *** package <SUZHnbcpp> was not installed:
    *** package <SUNWexted> was not installed:
    *** package <SUJAexted> was not installed:
    *** package <SUZHexted> was not installed:
    *** package <SPROnbreg> was not installed:
    *** package <SPROfdxd> was not installed:
    *** package <SPROmrxd> was not installed:
    *** package <SPROgvim> was not installed:
    *** package <SPROxmbin> was not installed:
    *** package <SPROxmshr> was not installed:
    *** package <SPROxmsrc> was not installed:
    *** package <SPROmrxm> was not installed:
    *** package <SPROprfan> was not installed:
    *** package <SPROmrpan> was not installed:
    *** package <SPROprfax> was not installed:
    *** package <SPROprflb> was not installed:
    *** package <SPROprflx> was not installed:
    *** package <SPROprfgn> was not installed:
    *** package <SPROmrpgn> was not installed:
    *** package <SPROhtbas> was not installed:
    *** package <SPROhttl7> was not installed:
    *** package <SPROhtstd> was not installed:
    *** package <SPROhtxd> was not installed:
    *** package <SPROdwrfs> was not installed:
    *** package <SPROrdbks> was not installed:
    *** package <SPROctsrc> was not installed:
    *** package <SPROplg> was not installed:
    *** package <SPROpl> was not installed:
    *** package <SPROplx> was not installed:
    *** package <SPROpls> was not installed:
    *** package <SPROplsx> was not installed:
    *** package <SPROmrpl> was not installed:These messages seem to be inline with the general output captured from the zone install itself.
    > What does "svcadm list -vc" give you when you started the zone ?
    I took that as a typo, instead using "zoneadm?"
    # zoneadm list -vc
      ID NAME             STATUS         PATH
       0 global           running        /
       7 foo              running        /zone/fooThe zone is not on its own slice, however "/zone" is mounted as a loopback from /export/zone. I don't think that's a problem since the zone install seems to work if I don't inherit packages. Unless perhaps its a nesting level of lofs's.
    FWIW,
    # mount |grep zone
    /zone on /export/zone read/write/setuid/devices/dev=1540000 on Fri Feb 24 16:10:55 2006
    /zone/foo/root/dev on /zone/foo/dev read/write/setuid/devices/zonedevfs/dev=4640007 on Tue Feb 28 13:13:03 2006
    /zone/foo/root/lib on /lib read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
    /zone/foo/root/platform on /platform read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
    /zone/foo/root/sbin on /sbin read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
    /zone/foo/root/usr on /usr read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
    /zone/foo/root/proc on proc read/write/setuid/nodevices/zone=foo/dev=4400007 on Tue Feb 28 13:13:06 2006
    /zone/foo/root/system/contract on ctfs read/write/setuid/nodevices/zone=foo/dev=43c0008 on Tue Feb 28 13:13:06 2006
    /zone/foo/root/etc/svc/volatile on swap read/write/setuid/nodevices/xattr/zone=foo/dev=448000e on Tue Feb 28 13:13:06 2006
    /zone/foo/root/etc/mnttab on mnttab read/write/setuid/nodevices/zone=foo/dev=4440008 on Tue Feb 28 13:13:06 2006

  • Mac G4 Won't Boot Completely After Restart

    I fired up my Mac G4 and ran software update and installed the 10.4.11 update. When I restarted to complete the install the computer gets hung up -- a blue screen with the gear icon turning and turning. It worked fine before I did the update.
    I've reset the PRAM to no avail. I've tried booting from the 10.4 install disc but that won'w work either?
    Any ideas on how to get this working again?
    Thanks!

    Open the service door and press the PMU reset button from about a second, then see if the computer starts. (Ref: http://support.apple.com/kb/HT1939)
    You can try a safe boot. Press and hold the SHIFT key until you see a message that the computer is starting in safe mode. When you see that message, t=you can let go of the key.
    If this gets you a workable desktop, don't try to use any apps--their extensions are temporarily disabled. Try a normal restart to see if everything works.
    I've found that by repairing permissions before and after doing a softare update, we've avoided update problems in all our OSX Macs.

  • Playbook won't boot - Completely unique problem

    Ok before anyone blasts me for posting before researching I would like to say that I have done my research and this post is my last hope.
    I recently bought a second hand Playbook that was advertised as not working for $20. Me being a BB freak and my Wife and I just having a new baby (so no ex tra $) I said to myself "oh they just don't know what they are doing" well apparently neither do I. 
    This PB was won at a Christmas party this past December and the woman who won it, was never able to get it to turn on.
    Now here's the weird part, this PB does not do what 99% of the other either bricked or drained PB's do. This one shows no signs of life at all if it is not plugged in, I will say here that I am only using the charger that came with the PB and no third party or uniusb's. Once I plug the PB in the red led comes on after about 5 seconds and stays on for exactly 10 minutes. From the hundreds of articles I could find I could not find one that showed the same symptoms.
    Here is what I have tried so far. 
    #1. Just letting it charge for 24 hours
    #2. Several different Stack methods (as a matter of fact, every single method that I came across)
    #3. Trying to get the computer to recognize the PB by hooking up the USB cable, and trying several different ways to get the DM to recognize the PB. No luck, not even for that glimmer of a second like others have reported.
    #4. Removing the back casing, after going online and making sure that there was no longer a warranty, and disconnecting the battery from the mother board for about an hour and then plugging the battery back in and hooking up the charger to see if there were any signs of life. NOTHING
    #5. Disconnecting all of the pin connections from the mother board, then once again after an hour replacing the connections and trying to charge. Nada
    #6. Removing the connections again and placing insulators between the mother board connections and the ribbon connections then placing the display with the batteries in a freezer bag, removing all of the air to stop condensation, then placing it in the freezer for about an hour and a half. Then letting it warm up to room temp and plugging in the charger. Nope
    #7. I saw a post about "jumping" the battery by Knotty Rope. Turns out he has a different version PB than this one because the battery connector is completely different than the one he had. Could not trace the circuit enough to find a valid place to apply a 5V source to trick the PB into thinking it has the proper voltage.
    Now after all of that I finally (don't ask me why I didn't start with this) tested the battery with my VOM and found that the battery only seems to have 0.91Vdc.....
    I know that 0.91V means that the batteries are stone dead and probably have to be replaced and I'm ready to give up.
    Update 1: After charging the battery again for about 12 hours I found that the battery has gone up to 0.98V. I just realized though that with the battery being this low the LED is probably using about 80% of the power being put into the unit, so I have disconnected the ribbon going to the LED indicator and I am going to try and charge it for the rest of the day and see if the battery can get a little more power.
    Update 2: Ok I finally gave up on trying to charge the battery using the USB port and I carefully exposed the main battery connections and found that the batteries actually had 1.7V. After watching a YouTube vid I then cut the end off of an only USB cord, found the + and - power leads and attached an aligator clip to each. I then hooked up the leads after making sure what the polarity was and began to manually charge the battery. I charged the battery up to 3V and then checked it 2 hours later. The battery was still at 3V so I took it up to 3.5V. I thought this was going to be the answer but apparently not. Still has the same symptoms described below and shows no signs of life. I think I'm going to have to call this unit FUBAR and wait until I can afford a new one 
    Update 3: I have tried a few more things to no avail but I figured I'd list them here. Since I charged the battery manually the battery has not discharged by more than .3V. So my problem doesn't seem to be a power issue. I have now tried to use a rapid charger and plugging in the USB cable to see if I could make the computer recognize the PB. That didn't work so I removed the mother board and carefully cleaned and dried it using alcohol and a blow drier. That also didn't work. Apparently I'm the only person to ever have this problem happen and even Blackberry themselves are at a loss as to what could be wrong. So I guess I have a shiny paper weight with a good charger for my 9810 and a new BB USB cable. I can't complain after spending $20 on it but I am really disappointed as I was really hopeful that I would finally be the proud owner of a Playbook.
    Update 4: As a complete "why not" effort I bought a dock charger for $15 and am trying to stack charge with it but after a few days it still hasn't done anything.

    Have you checked the power button on the top. I did see a post where the button was stuck in the down position and the PlayBook would not start. Eventually the poster fiddled with the button using something small until the button popped up again.

  • Osx won't boot

    Hi there. I'm new here and after googling around I thought it'd be best to ask here. I attempted to use a Fedora Core 6 live cd on my mini. To have it boot up from the CD I used the Startup Utility to select it and rebooted. After ejecting the CD (holding down left mouse button) and rebooting OSX will no longer boot, all I get is a blinking cursor. I suspect it is looking to boot off of the cd/dvd drive. It should be noted that I am using a Logitech wireless keyboard/mouse combo ( I don't know if that is an issue or not.
    Viral

    Insert your OSX system DVD. Start up while holding down the C key.
    Once booted off the DVD go to Apple/system preferences/start up disk.
    After you click on the HD icon select your HD as the start up disk.
    Reboot.

  • Ibook won't boot completely ! (stops at a blue screen)

    Hi...first time poster here, please be kind. Also, I'm not brilliant by any measure when it to computers.
    Yesterday I was installing updates (now, my ibook was out of use for at least 8 months, so I was bit back logged on updates) and after the second round (a safari update, a java update, and a security update) it said it needed to restart. Ok, easy enough, though apparently not it never booted up again. I get past the grey apple loading screen and to the blue screen that says "loading os x"...the progress bar finishes and then it disappears and all I get is a blue screen with a rotating "busy/working" symbol. A few times I got a black screen with white text asking for my login and password, but it always says it's wrong or it won't even let me type in a password before it freezes and goes on to the blue blank screen again. I did a PRAM cleaning and that ran correctly but did not help. It will not load in safe or verbose mode. Any one have any idea why my ibook is doing this or if there is anyway to fix it ? (also, I'm not sure eaxactly which os X I am running other than it os x 10.4) Help...
    Message was edited by: kurokaze83

    If you can't find the system discs that came with your computer, use fsck (a command-line utility that may be able to verify and repair a disk)
    To use fsck:
    1. Start up your computer in single-user mode to reach the command line.
    2. At the command-line prompt, type /sbin/fsck -fy
    3. Press Return. fsck will go through five "phases" and then return information about your disk's use and fragmentation. Once it finishes, it'll display this message if no issue is found:
    ** The volume (nameofvolume) appears to be OK
    If fsck found issues and has altered, repaired, or fixed anything, it will display this message:
    *** FILE SYSTEM WAS MODIFIED ***
    Important: If this message appears, repeat the fsck command you typed in step 2 until fsck tells you that your volume appears to be OK (first-pass repairs may uncover additional issues, so this is a normal thing to do).
    4. When fsck reports that your volume is OK, type reboot at the prompt and then press Return.

  • HELP! OSX won't boot?

    OSX 10.4
    Macbook Intel 2.0Ghz
    I am running boot camp w/ xp on a partition of the HD
    I downloaded/installed all the updates that were available. Allowed the computer to restart itself. Now when i try to boot to OSX it shows a folder with a question mark on it. Then it boots to windows instead.
    Please help, i have a paper to finish for school by tomorrow and the other 32 pages are on the Apple part of the HD.
    Thanks,
    Rob
    Rob

    Hi Rob,
    first of all: WELCOME TO THE DISCUSSIONS!
    Did you Repair permissions before and after the update?
    Insert the install DVD and reboot while holding down the c-key. Once the installer has started and you selected your language, select "Disk Utility" from the MENU. Repair the hard disk and repair permissions. Quit disk utility and reboot. Does the problem persist?
    If this answered your question please consider granting some stars: Why reward points?

  • OSX won't boot up

    Hey all,
    I'm hoping someone can help me with my MacBook Pro. My wife was running Power Point on it for a few hours yesterday and ever since then, I can't get it to boot in OSX. It just hangs on the grey screen and keeps spinning. I've tried the following:
    Reset PRAM
    Reset SMC
    Ran Repair Disk (disk shows up okay)
    Ran Repair Permissions (this always fails)
    Tried to start in safe mode (doesn't work)
    I did safe mode with a status and I get the following errors: Vnode_validate_compressed_file_type4 error: -1 and Disk0s2: I/O error.
    I tried reinstalling Snow Leopard, but it fails
    Not sure what else to do. I have Windows XP on here and that loads fine. The closest Apple Store is like 70 miles away and i would rather not make the trip. I can start it up as an external drive via FireWire and everything appears to be fine. Of course I haven't done a backup recently and I don't want to wipe it. Anyone have any ideas?
    Thanks,
    Jeff

    Hi Jeff
    I have fixed a similar problems in the past, most of them seem to happen when running Microsoft Office on a Mac. I have to agree with Linc, it is time to replace the hard drive, you can never trust it anymore. However, problems with bootloaders have the advantage, that if you don't have a recent backup, you can still easily get to your data on the hard disk for free.
    You might have already solved your problem by now, but just in case there are others out there experiencing the problem.
    First of all you need to start with the Laptop in the power down state. Hold the power button down until it goes silent.
    Press and hold the 'alt' key and turn the power back on. Hold the 'alt' key down until you get the 'Macintosh HD' and a 'Recovery HD' icon. If you have an OS X installation disc in the optical drive, you will also have an icon for this as well, but it will not help you, so ignore it. Just as a side comment, the 'alt' key is often referred to as the 'option' key. There are many postings on this, but to those of you who make rude comments when somebody asks this question, not all keyboards are the same!
    Getting back to more important things, select the 'Recovery HD' using the arrow keys and hit enter. The laptop will now boot from the recovery image.
    When you get the application 'Mac OS X ....' then you have the choice to restore from the latest backup on the time capsule. The '...' will be different, depending on the standard language' You can change this in the dropdown menu, if you are more comfortable working in a different language to the one given.
    Assuming you don't have a recent backup, then you need to go through the drop down menu items until you find one called 'Terminal'. Start the application and make the window bigger.
    For the next step, I am going to assume two things. You have an external hard drive, which is bigger that the amount of data you want to recover connected to the usb port. You are not afraid to type in a few unix command. If you feel uncomfortable, then ask some IT colleagues for help.
    First of all, you will need to use the 'cd' command. This enables you to change directory. Type in 'cd /Volumes' and hit enter.
    Next you will need to see what's in this directory, so you will need to use the second important unix command, namely 'ls'. Type in 'ls' and hit enter.
    What you get on the screen are different volumes. You will see the 'Macintosh HD' volume where your will find all your data and the external hard drive connected to the usb port. Obviously, this will show up depending on the label that you or the manufacturer gave it.
    You now need to navigate to the directoy where all your files are stored. to do this type in 'cd Macintosh HD/Users' and press enter. One tip here, press the tab button and it will autofill the rest of the text for you, so just keep typing until the volume name is unique.
    In the Users directory, you will need to do another directory listing. Type in 'ls' and you will get two folders, namely 'Shared' and the folder where all your data is stored. You can either stop here, or navigate into your personal directory, depending on how much you want to recover.
    The next and final command is to copy the files across to the external hard drive, e.g.
    cp -R -vp text1 /Volumes/text2
    where text1 is the name of folder where your data is stored.
    text2 is the label of the external hard drive.
    The '-R' is important for copying all sub-folders and files. The '-v' is important to make it verbose. This will give you confidence that the computer is doing something, as copying 750 GBytes will take several hours.
    When the computer has finished copying the files, you will get the '-bash-3.2#' and the cursor, or something similar.
    That's it, now you can close the terminal and restore from the latest backup on your time capsule. When your computer is up and running again, you can copy as many of the files as you need across from the external hard drive using the trusted drag and drop.
    Hope this helps.
    Cheers
    Huw
    Changed MByte to GByte. Sorry, I started when computers were fitted with 1 KByte.

  • Windows and OSX won't boot after partitioning

    Hi so I have a 2012 MacBook pro, it is running mountain lion and I also boot camped it and installed windows 7. I partitioned the hard drives correctly and it has been running great. Today I was on windows and used the disk manager to shrink my windows partition so that I could create another seperate 5gb partition for school. After I did this, my computer was running fine until I restarted it. When the windows logo appears while booting, it freezes and it flashes a blue screen and then shuts down. When I hold down the option key to boot into Mac OSX, the only option that comes up is windows, not even my recovery disk.
    How do I fix this? I need to boot into these because all of my school things are on these drives. Please help

    Never in my reply did I say I don't use Boot Camp or not to use boot camp. But I don't. And I don't have Windows installed in its own partition. I use a VM for Windows on my Mac for the few Windows programs I run on the Mac.
    I started to read that reply but then didn't finish it as that poster was talking about Win 8 and AFAIK right now neither Boot Camp or the driver package supplied by Apple for Windows supports Win 8. Even though it isn't much different then Win 7.
    It does create a Separate partition, as does Win 7, that is a hidden partition, just like Win 7 does, but it is different in some ways from Win 7. So that may of been the original problem that poster was having.
    In any event I don't think that post will help the OP of this thread. But I may be wrong. Only time will tell.
    The big reasons I don't use Boot Camp is I can't stand Dual Boot system and that I can't Re-Partition the BC partition without screwing the whole system up. Tried it, didn't care for it, then removed it and went VM.
    wjosten wrote:
    You read that thread I provided the OP a link for...don't you use Boot Camp? Got any better ideas?

  • Mac OSx won't boot up

    After a minute of that loading circle under the apple symbol in the middle of the screen, the apple symbol turns into a no entry sign, which I've never seen before. I know there's a button to hold down when you switch the computer on that can take me to a different screen and I can run some repairs, but I forgot what it is, any enlightenment would be great

    Hi Divus! and Welcome To Discussions!
    Is this the No Entry Sign you are seeing?
    What was the situation before this problem arose?
    Did you make any changes to your system?
    Exactly which model Mac do you have?
    What OS are you running?
    What size is your Hard Drive, and how much space is available?
    How much RAM is installed, and is it original or added?
    Under your login Alias, Divus, please click on My Settings, and enter your Mac specs.
    Computer Model:
    Operating System:
    Other Computer Informtion:.
    My Settings is located under your login Alias, Divus, on the right side of all Discussions pages.
    ali b

  • Macbook Pro won't boot OSX after Yosemite upgrade 10.10.3

    I downloaded the update to 10.10.3 this morning before driving my daughter to daycare. When I came back, my Macbook Pro had rebooted into Windows 7 (Boot Camp). I restarted it by telling it to reboot to OSX, but it boots Windows again. If I turn it off completely, and then turn it on again, there's no chime... just a black screen for about 30 seconds, followed by "Starting Windows". I'm about to reboot to try resetting NVRAM and SMC, but I don't know if that's going to work without the chime...
    I really need OSX to get going, so any help appreciated.

    If you don't already have a current backup, back up all data, then reinstall the OS.* You don't need to erase the startup volume, and you won't need the backup unless something goes wrong. If the system was upgraded from an older version of OS X, you may need the Apple ID and password you used.
    There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
    If you installed the Java runtime distributed by Apple and still need it, you'll have to reinstall it. The same goes for Xcode. All other data will be preserved.
    *The linked support article refers to OS X 10.10 ("Yosemite"), but the procedure is the same for OS X 10.7 ("Lion") and later.

  • Mac won't boot after updating to OSX 10.6.4

    I am on my 3rd Mac that won't boot after updating to OSX 10.6.4. One MacBook Pro and two iMacs. I fixed one but the last two are getting the better of me. HD is not fried. Have tried every keyboard shortcut on startup, Disk Warrior via. Target Disk, repairing permissions in single user mode. The machines will not boot off of a CD or DVD and it will not boot up in safe mode. Something in the startup files is preventing startup. I am suspecting Sophos antivirus. I tried to uninstall it and trash it but I think it's still blocking something. Any help would be appreciated.

    Got it! Not sure if removing Sophos had anything to do with it but here's what I did.
    1) boot dead machine in Target Disk Mode (iMac)
    2) boot good machine off Snow Leopard disk (MacBook)
    3) install OS to dead machine- I found this next part very curious. When the install was complete the MacBook restarted as the iMac.
    4) ran software updates
    5) shut down MacBook then shut down iMac
    6) rebooted iMac- all was good
    I actually did this twice because a co-worker had the exact same problem on her MacBook Pro. Got both fixed today.
    Thanks everyone for your help!

  • Reset PMU and Powerbook won't boot past the blue screen with "Mac OSX" box

    Hi-
    Problem: I tried to reset my PMU, and now when my computer restarts it won't go past the blue screen with the "Mac OSX" logo in the box (and progress bar, that never fills up). I then also tried to reset PRAM, but it still won't boot properly.
    Backstory--
    I've had my 12-inch Powerbook G4 for about 3.5 years already, so things are starting to get a bit out of whack. I replaced my battery about 3 months ago, which has been great, but recently my power-cord has been wonky (having to unplug it and replug it in to make sure it actually charges the computer, the light flickers on and off, etc). Today it actually started producing SPARKS at the place where the thin white wire meets the white plastic power brick, so I decided it was time to get a new one. Brought it home, plugged it in, and since it seemed like the battery indication icon on the menu bar was all out of sync with the powercord colored-light, I tried restarting it a few times, but still the same. Then, I decided to reset the PMU, which may have been a huge mistake. And now it won't boot past the blue screen... Any advice? I'm going to try restarting it in "safe" mode, but I'd be so grateful for any recommendations. Hope I haven't done something irreversibly stupid with the PMU reset.
    Thanks,
    Samantha

    Hello all,
    Thanks for all of your great suggestions and info-- here are a few responses.
    1) The disk I just borrowed from my friend appears to be the full retail version-- it looks just like the links that Ali B sent, and is in a large box saying "Mac OSX Tiger, version 10.4"... will this be the proper disk to do an Erase and Install? The only other disks I have came with my Powerbook when it was originally purchased, when it came Panther (I think, 10.3?). Would I use both sets of these disks to do erase and install? Or only the Tiger OSX disks?
    2) I get the sense that Disk Warrior or Tech Tool might be necessary, but does it make sense to TRY to do erase-install before buying them? Also, are there any downloadable (for pay) versions of this, or would I need to track down the actual physical disks in Hong Kong or wait for them to be shipped?
    3) I haven't yet tried the S.M.A.R.T. test, should I do that first? What is the procedure? Are there any results or ways to know if the drive is too far gone (so that I might instead replace the internal hard-drive) instead of pay 100 USD first to do the disk repair?
    4) Cornelius said: "An alternative would be to completely reformat and erase the entire HDD, then re-install and restore your data from backup. If your backup is in the form of a bootable clone of the entire HDD, you can just clone it back." I use Super-Duper to back-up and the most recent one copied the whole thing-- what would be the later procedure of "cloning it back"?
    5) As I'm able to use my computer pretty normally right now, but does it still mean that it might crash/die at any moment? Is there any way to tell?
    Thanks so much!

Maybe you are looking for