Tag Info

New answers tagged

2

Personally, I installed rEFInd on my computer to its own partition. This prevents the problems you are encountering. Everything ./install.sh installed went to this partition. If I want to remove rEFInd, I can simply erase or remove the partition. Of course both are unnecessary, because I can turn rEFInd on and off at will. I just go to the Startup window in ...


1

There is a partition on your hard drive called EFI. At boot up your system looks for the EFI as very first step. EFI is responsible for the booting process, and if it is broken for some reason the computer wont boot at all. Using your hard drive on another computer wont tell you if the EFI is still intact since it is not used in that set up. EFI is about ...


0

AFIK....Some steps of the Installation process require heavy CPU usage. That is why is it required to have full battery and charger plugged in. System will be consuming a lots of power. In you case "without battery" there is not enough juice to continue with the installation. It is well published fact that Macs will automatically cut the CPU power in 1/2 ...


0

Apple has steps to isolate the failure documented at : Mac OS X: Gray screen appears during startup Remove everything you can to make a minimal system. (remove all external devices, the SSD/HDD and all but one memory stick). Alternately, you could try placing that Mac into target disk mode and installing the OS from another Mac. To run a minimal install ...


0

Folder showing ? means, that there is no bootable system found on your hard disk. Booting in Recovery Mode means, that your HDD is still working. Disk Utility not showing HDD means, that there is no formatted HDD. To recover your data try following step: Shut down computer Turn on again pressing "T"-Key down till Firewire Icon is shown. Take another Mac ...


0

I rang Apple in the end, they didn't know either without seeing it. 8-) Suggested I take it in for a free diagnosis. Before I did that I tried taking the heatsink sensors connected off and replacing it. Bingo, all fixed. So the answer must be that this error is the heatsink sensor.


1

Download BootChamp. You get a shortcut that reboots into Windows, but it doesn't change the default OS. Seems to work really well.


1

Boot holding the option key and select the SSD to boot. You can also use system preferences to set it as the default boot drive. Once the machine will restart (or power on from off) and boot to the SSD, use Disk Utility to erase the HDD and enjoy your new Mac.


1

First, you need to isolate the problem. Put the internal hardrive in a casing and connect it to your laptop through USB. Then boot up the OS X in this configuration by holding down OPTION key. If everything is smooth after a couple of hours, the problem is definitely SATA cable. I have a 2011 13' MBP (A1278) and the cable broke a year ago. From what I read, ...


0

Way by Terminal.. Use diskutil list in a Terminal instance to list all volumes and find yours. Then do hdiutil eject disk? Replace the ? with your disk number, making sure you are not trying to eject the main hard drive :) It is probably called "Disk1" Here is a Sample when I insert a USB stick and run diskutil list disk0 is my hard drive and I can ...


0

Apparently RAM I installed months ago didn't want to play nice with the new SDD. Switching back to the old ram got the computer to boot no problem. (Weird, because I previously had no issues with the RAM before upgrading the SDD)


0

Yosemite is not supported on the Early 2006 iMac - it can only go up to Snow Leopard v10.6. You will either need to order a set of restore discs for this particular system (as discs do not necessarily work between models, make sure to get the right ones) or find a retail copy of either Tiger (Make sure it is newer than 10.4.6), Leopard or Snow Leopard. You ...


0

MacBooks like yours are artificially prohibited by Apple from booting the 64 bit kernel. This restriction is in the boot.efi. To bypass this restriction in the current 10.10.3 boot.efi you must do the following. 1) Create a copy of the boot.efi file and name it boot64.efi (boot.efi is usually located in /System/Library/CoreServices/ or on your esp ...


-1

My guess is that something is wrong with your hard drive. You should check if it is working correctly (or get someone else to check for you.)



Top 50 recent answers are included