-
All replies
-
Helpful answers
-
Nov 6, 2014 12:19 PM in response to MountainCyclerby Eric Root,Send Apple feedback. They won't answer, but at least will know there is a problem. If enough people send feedback, it may get the problem solved sooner.
-
-
Nov 6, 2014 1:46 PM in response to ksanganiby dataman,NOw both of my Mac Mini are exhibitng the same behavior. there is no oem memory or anything else in them. the only thing in common is they all have Yosemite on the,.
STill no reply from Apple..........reminds me of the reason I left the Microsoft OS behind......this is a similar issue that Vista had, I never got that one solved either
HOwever, turning off file vault security solves the problem on these as well.
-
Nov 6, 2014 2:10 PM in response to datamanby MountainCycler,I have 2 Crucial 256GB drives installed (removed the Superdrive and replaced it with a spare M4 Crucial SSD). The second SSD I encrypted (File Vault), but the boot SSD (another Crucial 256 SSD) is not. I could simply pull the secondary drive out and try that, just don't know if I am able to read it afterwards.
-
Nov 6, 2014 2:14 PM in response to MountainCyclerby dataman,I would just put the drives back in and keep restarting by holding down the power button for 15 seconds or so, it will eventually boot up long enough to turn off the file vault. Sometimes it takes up to ten tries but it will eventually come up if the drives are ok.
-
Nov 6, 2014 2:50 PM in response to MountainCyclerby Streeme,I'm kinda lucky, then, since I've got a TM from only 3 days ago. However it is hard to believe that I could be forced to lose those data: it is there and I guess readable by another Mac. I'm just not allowed to see its content, which is kinda frustrating. For someone the key was deactivating FV, which I'll try to do tomorrow.
I'm absolutely not happy with Apple this time. However, when I used to be only a Microsoft user I experienced similar issues once a week, while with the Mac it happened twice in 42 months.
-
Nov 12, 2014 2:04 PM in response to ksanganiby mac1994,vnav's suggestion on Unsigned Kernel Extension helped me solve my problem.
Boot into Safe Mode then fire up Terminal App.
$ system_profiler SPExtensionsDataType
You will get a list. Search (cmd+f) for Not Signed
In my case it was JMicronATA.kext
$ sudo mv /path/to/extension.kext ~/Desktop/
reboot and you should be able to continue.
I am now trying to figure what this JMicronATA does.
-
Nov 13, 2014 2:19 AM in response to mac1994by Fran Roig,I have exactly the same problem. Every morning I spend around 15 minutes trying to boot up my computer... This is very poor quality.
As @mac1994 said, I had JMicronATA kernel Not Signed, but his workaround didn't work for me. Unfortunately I'm still having the problem again and again.
-
Nov 13, 2014 2:35 AM in response to datamanby webbadger,Yep. So can I. "Once I deactivated my FileVault, my issue completely went away."
-
Nov 13, 2014 7:47 AM in response to ksanganiby MountainCycler,Finally got my issue resolved.
Mac Configuration:
Model Name: MacBook Pro
Model Identifier: MacBookPro6,2
Processor Name: Intel Core i7
Processor Speed: 2.8 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache (per Core): 256 KB
L3 Cache: 4 MB
Memory: 8 GB
Processor Interconnect Speed: 4.8 GT/s
Boot ROM Version: MBP61.0057.B0F
SMC Version (system): 1.58f17
Please note that Memory and SSD Drives are not Apple OEM, but Crucial M4's with Crucial memory. There are some threads that indicate that there are issues with Apple now checking for OEM RAM with Yosemite. While I went thru the effort of swapping, this was not an issue for me.
I had some issues with Flip camera install, made sure all references to uninstalled software was removed in /system/library/LaunchDaemons and LaunchAgents.
Next moved all my files off the 1 encrypted drive I had off to an external drive, reformatted it to a Mac OS Extended (journaled)
After all of this, machine would still boot really slowly with Status bar stuck. Performed forced shutdown and rebooted in Safe Mode.
Uninstalled McAfee AV software.
Rebooted and voila, the machine is working great.
Don't really know what root cause was, but McAfee was definitely a culprit.
Hope this will help someone else.
-
Nov 13, 2014 5:41 PM in response to ksanganiby johnmac_85,I'm having this issue. Tried EVERYTHING! Reinstalled Yosemite multiple times using cmd+R and I can't login in a safe mode or a guest account. When I type my password i just get the spinning ball and it continues spinning for hours. I can't get access to anything to make changes. Any idea?
-
Nov 13, 2014 8:43 PM in response to johnmac_85by mac1994,I had posted earlier that my problem got resolved with removing a .kext file. Truly not. I could get to the login screen and face the ever spinning beachball.
I started my Mac in Safe Mode and then 'downloaded' Yosemite to an external drive.
Rebooted my MBP while holding the Option key and selected the "Install Mac OS X" drive.
Once in used Disk Utility to erase my drive and perform a clean install.
I had a Time Machine backup to recover all my work barring a few files which I had manually copied to the external drive.
Clean install of Yosemite is working for me.
-
-
Nov 14, 2014 5:29 AM in response to ksanganiby uedf,Have the same issue on my MacBook also, everytime i enabled the FileVault the problem occured and the spinning wheel appears after login at around 30-50% of the progress bar.
But my colleage found a workaround for this, CTRL+SPACE+ENTER and the startup continued nice and smooth.
Has tried all other workarounds descibed in this thread(and a lot of other) but this was the only thin that realy worked for me.
Ps.
Don't ask me what happens when i press CTRL+SPACE+ENTER, because i don't know. -
Nov 14, 2014 6:56 AM in response to Cabimanby MineyMoe,My mac has this problem and I don't use FileVault. It's something else.....