-
All replies
-
Helpful answers
-
Dec 9, 2015 3:50 AM in response to Peachtree55by tommeketommeke,Hi peachtree55
I just found my HD in the /Volumes folder. Although I did not have to that, I also read somewhere you may first need to mount your drive with "Disk Utility".
HTH
-
Dec 9, 2015 4:03 AM in response to tommeketommekeby Peachtree55,Thanks for getting back to me. I was stuck in the 100% bar but nothing happens point so could not look at Volumes - Terminal did not want to know about the name I typed, so now I am restoring from Time Machine. Then I will delete all those old Kext things.
Unbelievable that Apple do not at least put them aside & let us know. They are too caught up in looking after kids buying iPhones IMHO :-(
-
Dec 9, 2015 9:25 AM in response to urquhartpsby pizdecseventyseven,solution
1. use cmd + R to boot into Recovery Mode
2. in terminal type:
cd /Volumes/<your harddrive>/System/Library/Extensions
example: cd /Volumes/Macintosh\ HD/System/Library/Extensions
rm -rf *
reboot
3. use cmd + R to boot into Recovery Mode
4. Reinstall OS X
enjoy
-
Dec 9, 2015 10:25 AM in response to pizdecseventysevenby Peachtree55,Thanlks - I will try this after the weekend (Need the Computer from Tomorrow early AM to be definitely working)
Where the heck is the backward slash on the keyboard, by the way?
Never mind - found it :-)
-
Dec 9, 2015 11:20 AM in response to urquhartpsby dwhinkl,I have this same issue on a 27" iMac 2012 version. I am restoring from a clone drive and will not try this update again until this issue is resolved.
-
Dec 9, 2015 2:33 PM in response to urquhartpsby javidaboo,Same thing - half way thru the status bar - my iMac hung. I was able to compete the process by booting into safe mode. I actually had to complete the process a few times.
-
Dec 30, 2015 10:05 PM in response to dominicperryby davidfromhindhead,El Capitan won't boot on my MacBook Pro either. It gets to the end of the bar, but won't open. Tried Disk-Aid to check and repair without success. Tried to re-download El Capitan 3 times with the same result. No use. There do not appear to be any simple fixes on this forum. Now kicking myself for not making a backup first.
Worse...our local Apple authorised dealer is closed over Xmas and New Year.
Frustrated from Hindhead!
-
Mar 1, 2016 12:26 PM in response to BertoShipby BlazeKrypton,I have this exact same problem!! Reinstalled twice with no luck! Did you manage to sort it out???
-
Mar 1, 2016 2:59 PM in response to BlazeKryptonby Mambaman68,I Have just experienced this (again) with the latest El Capitan upgrade. I've had to reboot from my Time Machine. Often with this it pays to wait a few weeks before uploading the latest upgrade as for various reasons (add ons etc) it hangs the computer
-
Apr 13, 2016 10:14 AM in response to urquhartpsby unaMelaAlGiorno,Hello,
it is definitively a problem with the extensions in /System/Library/Extensions/
As suggested in some posts, I have firstly erased all extensions but then the reboot gets stuck in "resetting IOcatalogue".
Then I have erased only those extensions that seemed to me not related to my mac (probably not signed), or to devices that I am not using anymore. In my case these were the Huawei extensions (Huawei*.kext).
So here's what to do:
1. Use cmd + R to boot into Recovery Mode
2. From utilities menu, open the terminal
3. In terminal type:
cd /Volumes/<your harddrive>/System/Library/
example: cd /Volumes/Macintosh\ HD/System/Library/
4. create a directory to store the extensions you think are not supported (better move them than erase them .. in case they are actually supported)
mkdir Unsupported
5. Go to the extension directory
cd Extensions
6. Move the extensions you think are not related to your mac or are not supported (and probably non signed) to the Unsupported directory
mv <the extension>.kext ../Unsupportedexample: mv Huawei*.kext ../Unsupported
7. Reboot in verbose mode (by pressing cmd+v+power)
8. If it still get stuck then you might need to remove more undesired extension
-
Jul 15, 2016 2:51 PM in response to urquhartpsby EddieQB,Just to add to all the comments towards the end, I've just fixed this problem in the same way by removing all extensions. In fact there was only one extension in there from something to do with HP. Moved it out of extensions, rebooted, waited a bit and then it was sorted.
Thanks for all the efforts of everyone here to work this one out!