HT5815: About the OS X Mountain Lion v10.8.5 Update
Learn about About the OS X Mountain Lion v10.8.5 UpdateQ: The update completely screwed up my computer! Now it won't start-up - it only goes into Terminal then shuts down. After three trie ... The update completely screwed up my computer! Now it won't start-up - it only goes into Terminal then shuts down. After three tries Techtool Pro opens in e-disk mode to repair the problem (which it can't find a solution). Great Apple - thanks ! more
-
All replies
-
Helpful answers
-
Sep 18, 2013 1:03 PM in response to arthurby Lesultan,Tech Tool Pro had nothing to do with the problem.
I took out the suspect disk - and all others except one clean 3TB disk. Booted in Target Mode and then downloaded and ran the installer from my laptop.
Exact same problem three times on three separate disks.
All of my diagnostics report all of the disks are fine. They all boot in Safe Mode but not in normal mode once the update has been applied.
I changed my updated graphics cards for the originals, nothing but monitors, keyboard and mouse are plugged in (yes, I tried another monitor without kbd and mouse).
I've changed the cables even - nothing works.
I'm beginning to think it's the processor.
Here is a pic of the screen.
-
Sep 18, 2013 4:40 PM in response to Lesultanby Barney-15E,All of my diagnostics report all of the disks are fine. They all boot in Safe Mode but not in normal mode once the update has been applied.
That means you have third-party software that is incompatible. You'll need to figure out what it is and uninstall it.
It could be related to a driver for some hardware, or it could just be standard crapware.
-
Sep 18, 2013 8:23 PM in response to Barney-15Eby Lesultan,Thanks Barney, but I erased the disk and took out all of the others, so how do you think third-party software or some unknown driver could be responsible ?
I had deduced that it may be some rogue software but with an empty disk that is impossible.
Thanks again
-
Sep 19, 2013 4:13 AM in response to Lesultanby Barney-15E,Lesultan wrote:
Thanks Barney, but I erased the disk and took out all of the others, so how do you think third-party software or some unknown driver could be responsible ?
I had deduced that it may be some rogue software but with an empty disk that is impossible.
Thanks again
If it boots into safe mode, then it is something non-native that is causing the crashes. Safe Mode disables all non-native startup items and kernel extensions.
-
Sep 19, 2013 4:27 AM in response to Lesultanby zhanklaa,The kernel panic seems to be pointing to USB, do you have any devices connected via USB besides maybe a Keyboard or Mouse? If so have you tried to boot with nothing connected?
-
-
Sep 19, 2013 4:39 AM in response to Barney-15Eby Lesultan,Again, Thanks Barney - Eltima software makes Foxl, a download assistant, which I have installed. I'm uninstalling it now to see if that works.
Thanks for the ideas, anything will help.
Cheers again ~
-
Sep 19, 2013 4:41 AM in response to zhanklaaby Lesultan,to zhanklaa,
I've rebooted with a different kybd and mouse - all USB and Ethernet cables are unplugged. Only kybd, mouse and monitors. I've even changed graphics cards.
Thx
-
Sep 19, 2013 5:10 AM in response to Lesultanby zhanklaa,Okay, since it will boot in to safe mode, and you think it might be software related there are several folders you can make a copy to the desktop of and remove the files within. These are folders that contain startup items.
/Library/Caches
/Library/LaunchAgents
/Library/LaunchDaemons
/Library/StartupItems
~/Library/Caches
~/Library/LaunchAgents
~/Library/Cookies <--- Since you are there anyway
Also go in to System Preferences>Users & Groups unlock if locked and click Login Items then remove all
Reboot normally and see if the problem persists.
~ denotes home
to get in to the home folder Library if you are running Lion or Mountain Lion you need to click Go then while holding the Option Key click Library
-
Sep 19, 2013 5:35 AM in response to Lesultanby R C-R,Lesultan wrote:
Again, Thanks Barney - Eltima software makes Foxl, a download assistant, which I have installed. I'm uninstalling it now to see if that works.
The com.eltima.eveusb.kext could not possibly have been installed along with the OS, which raises the question of how you installed the OS on the erased drive.
Earlier you said you "Booted in Target Mode and then downloaded and ran the installer from my laptop." Since there is no way for that to install the Eltima software, you must have done something to install it after running the OS X installer, unless you mean something other than using the Mountain Lion restore feature for the download.
If uninstalling the Eltima software doesn't solve your problem, first make sure you are using an uninstaller that removes the kext file & if you are sure that it did, please explain exactly how you reinstalled the OS & anything else you put on the erased drive. You may have done something that will cause you more problems, but without knowing all the details of what you did, it will be very tedious for us to try to help you.
-
Sep 19, 2013 5:49 AM in response to R C-Rby Lesultan,I have five (5) hard drive for a total of 9 TB.
On the original HD I still have the OS with all its problems. It is there that the Eltima software resides.
I completely erased a 3TB HD and did a new install from the App Store through running that computer in Target Mode from my laptop (this I already explained).
The clean HD with the new OS still gives me these problems (I've already explained this - which is making it a bit tedious for me to ask for help if people don't read what's already been explained)
I do appreciate your offer of assistance but I'm not a novice - after 22 years of using Macs this is the first time I've had a serious problem that I can neither understand nor fix.
I took out ALL other drives and unplugged ALL USB and Ethernet cabling, and then tried again to start up from the NEW DRIVE with NEW OSX.
Same problem.
It's folly for me to only use a new OS and forget what I have on the original HD. Therefore I ask for assistance in tracking down the culprit - which will also help prevent from making the same mistake in the future.
bests ~
-
Sep 19, 2013 5:52 AM in response to zhanklaaby Lesultan,Thanks again zhanklaa for suggesting "something to try"
I'm trying to track the culprit, so this type of assistance is very welcome ~ Wish I could drag all of you who have helped over to my patio for some fresh lemonade (HA!) and sunshine.
(I love lemonade but I live in Cognac country where there is a law that lemonade must be 'enhanced')
Cheers
-
Sep 19, 2013 6:36 AM in response to Lesultanby R C-R,Lesultan wrote:
The clean HD with the new OS still gives me these problems (I've already explained this - which is making it a bit tedious for me to ask for help if people don't read what's already been explained)
We have read what you said but the fact remains that if the Mac will boot into safe mode but not otherwise, then your "clean HD" isn't as clean as you think.
The most obvious conclusion from this is that either 1) you somehow managed to install third party software (like the com.eltima.eveusb kernel extension) on this HD or 2) using Target Mode to install the OS on a Mac different from the host one (the laptop) is for some reason not installing everything it should.
If you are absolutely certain that there is no third party software on this HD & that it is the one you are starting up from, then the second possibility above seems the most likely one. That in turn leads to asking why you chose this method instead of using the OS X Recovery feature to reinstall the OS on the Mac Pro.
Obviously, you can't boot from the Recovery partition if you have already completely erased the HD so in the future try to avoid doing that until you try that. However, if you still have a drive that you installed Mountain Lion on in the normal way (that is by downloading & installing Mountain Lion from the App Store from the Mac Pro), you may still be able to choose its Recovery partition at startup time & do the reinstall from that.
-
Sep 19, 2013 6:39 AM in response to Lesultanby John Galt,By "same problem" do you mean that your Mac is still booting to the same panic report shown in your screenshot?
-
Sep 19, 2013 6:41 AM in response to Lesultanby myfast,Yes....simmilar thing appeared on my screen*&^%$#@#$% was not able to fix this problem !
Had to go back to my Carbon Copy 10.8.4 backup ...
