Tag Info

New answers tagged

1

Sometimes booting in Safe mode or in Verbose mode will ratify the boot log problems. Safe mode "Shift" Verbose Mode "cmd-v" or Press Option during startup Start up in Startup Manager, where you can select an OS X volume or network volume to start from.


1

I encountered the same problem after updating to 10.10.1. When I was booting through single user mode I noticed that fsck was reporting that the root file system didn't have journaling enabled. After booting into OS X Recovery and enabling journaling on the volume in Disk Utility the kernel panics stopped. I suspect that your problem will be solved by ...


0

Turns out resetting PRAM and NVRAM via pressing ⌘+⌥+P+R at boot (before the gray screen appears; hold until computer restarts and the startup chime has been heard twice). I have since successfully booted both OSX and Ubuntu via rEFInd without any excessive waiting.


0

Some days ago I discovered that installing an older version of mac is possible, but no one did it. The problem is in the EFI Bootloader Volume, if you have your mac from 2010 you have an EFI Controller Chip with version for example 1.6 (like BIOS in PCs) already installed in the logic board that supports an old System Drivers, but if you have a New Mac so ...


0

I used to run this exact configuration in a 2009 MacBook Pro. It works fine and never had any issues booting from a drive in the CD bay. I used the MCE Tech OptiBay drive bay kit for the second drive adaptor.


0

I was having problem with @Mark's answer exactly where he says - Install OS X.app purchased in Mac App Store. Turns out to get that, you need to open Mac AppStore, hold Alt, go to Purchased tab, select to download your older OS X, and release the key. (Tried to comment this on his answer but I don't have enough reputation to do that) Source: Where May I ...


0

What worked for me was that I got a USB enclosure, formatted the “Linux” partition, uninstalled rEFInd with this command: sudo rm -r /EFI/refind And everything came back to normal.


0

I had this happen with rEFInd before. I think rEFInd boatloader ended up in your efi partition. The excruciating long wait is rEFInd checking every device/partition to see if it's bootable. I have the debug menu in disk utility enabled, so I just selected show all partitions, mounted the efi partition from available partitions in the top left window, and ...


0

After reading the comments I would try to use Internet Recovery (Command + Option + R) and see if that works.


0

Finally I found a serious hardware error (failure of main board) was preventing installation of Yosomite. The reason I saw Virtual Box error was just a matter of chance, it printed out the lost error message before the computer crashed due to the main board error


1

Use this path instead: /Volumes/Untitled\ 2/ The backslash tells the terminal that the space is included in the path, otherwise it thinks your volume is called /Volumes/Untitled and that there is a random 2 argument in the command.


1

Change sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled 2 --applicationpath /Applications/Install\ OS\ X\ Yosemite.app --nointeraction to sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume "/Volumes/Untitled 2" --applicationpath ...


0

I also use a non-mac keyboard and have seen the issue where it skips the boot menu. The native keyboard works both from a cold boot and a soft reboot. The 3rd party keyboard only works from a cold boot and not from a reboot. You should be able to power down your Mac and power it back on and have the boot menu work with any keyboard. I've also read a few ...


0

I had the same problem. The dimmed screen happened during the reboot after turning on file vault. I was able to solve the problem by going into a darkroom. This allowed me to see the cursor and to log in to an account. Once I logged in the back light came on and everything was fine. I had first tried to solve the problem by zapping the pram. This had no ...


0

I had similar non bootable problem with a MBP 17 inch (early 2011). Saw all the online action, the lawsuits etc… Hopefully apple will do a recall as it was bought by me for graphic intense tasks like video editing. I followed these steps and got a workable fix: If you boot and get vertical stripes > apple logo > white grey screen, let it run hot as the ...


0

Update - i was able to solve this situation. The simplest solutions evade at times. In case someone else runs into this, what i did- In the grub menu i was trying to see if i could do something in the command line interface.. Just typed exit & immediately i was popped back onto refind. Immediately booted into OS X & reinstalled refind..


0

I have fixed the problem. I fixed it by mounting the hard drive on another MacBook and there i deleted the partition for "Montain Lion-Install"-partition. When i mounted the hard drive back to my MacBook it booted to the secound partition (Yosemite). But i have another problem, how do i make the boot loader work now from the OS X Yosemite?


0

You can set which account is automatically logged in under the "Login Options" section of the "Users & Groups" pane of System Preferences:


1

This is normal behaviour for Yosemite for users with FileVault enabled (i.e. Your Mac's primary disk is encrypted). The authentication process is done earlier because without authorisation from the user the OS cannot access the rest of the disk. This is a good thing, and I think you are (mostly) mistaken that it takes longer to boot up — since now you are ...


0

This should be either a kernel extension issue or bad memory. If you have replaced the RAM in this machine restore it to Apple Factory RAM and see if the issue persists. Alternatively if you are using factory RAM (or third party and don't have original or suspected good RAM) and have more than one SIMM try removing one or more of them to determine if one ...


1

If your EFI is not working, you will need to restore it. Download from here for your model. Then follow the procedure described here.


3

Looking at the tech specs for Apple's latest iMacs, all the 21.5" models seem to have 5400-rpm hard drives unless you specifically upgraded yours. (I can't find a 3.5 GHz model actually so I couldn't verify your model and I also couldn't comment to ask.) Based on the assumption that you do in fact have a model with a 5400-rpm dive, your boot time doesn't ...


0

Sorry, Tom -- this isn't an answer. I just have some questions--too many, in fact, to fit them all into a comment. The intent of my inquiries is to fire a shotgun at the likely initiators of your panics. (Disk Utility isn't (yet) capable of resolving the myriad of cs issues that pop up here and there, so it's not surprising that it reports all is well.) ...


1

Sounds about right to me. Mine would take that kind of time until I put an SSD in it. You could try starting in Safe Mode [hold shift after the chimes] & see if there is any significant difference.


1

Depending on your Macs you might use the FireWire/Thunderbolt target-disk mode. Apple-KB: If you have two Mac computers with FireWire or Thunderbolt ports, you can connect them so that one of them appears as an external hard disk on the other. This is called “target disk mode.” 1. Connect the two computers with a FireWire or Thunderbolt cable. ...


1

A clean install is not necessary, you simply need to reconfigure your NVRAM (nvram boot-args=kext-dev-mode=1) to disable the kext signing requirement for OS X. (After which, you can remove your TRIM enabler and reverse this change or leave it until the next time your NVRAM is changed/resets) A very clear explanation of OS X 10.10 Yosemite's new policy ...



Top 50 recent answers are included