Hey guys, so I did a clean install of Mavericks from the final public release on the Mac App Store which I downloaded yesterday, and did Migration Assistant without copying over System settings.
Now, my MBPr is taking on average about 5+ minutes to boot up (I'm getting the spinning loading wheel with the Apple logo). I've booted into Safe mode to clear the dynamic loader shared cache, and sometimes it will reboot again rather quickly (around 5 seconds) and others it's back again to 5+ minutes. I then rebuilt the kernel extension caches, and this doesn't seem to actually do anything strangely (as this has been cited as a fix to slow boot times to much success.)
I've tried all sorts of different permutations of restarts, cold starts after a shutdown, and it almost seems like it's random. I then decided on turning on File Vault 2 to see if this might affect it somehow, and it doesn't: it's exactly the same. Getting to the File Vault login window is quick, but once it starts loading the OS, it goes back to the long load times. I've also repaired disk permissions, and still the same behavior.
Any ideas what this could be? I appreciate any help or suggestions on the manner. Thank you.
Now, my MBPr is taking on average about 5+ minutes to boot up (I'm getting the spinning loading wheel with the Apple logo). I've booted into Safe mode to clear the dynamic loader shared cache, and sometimes it will reboot again rather quickly (around 5 seconds) and others it's back again to 5+ minutes. I then rebuilt the kernel extension caches, and this doesn't seem to actually do anything strangely (as this has been cited as a fix to slow boot times to much success.)
I've tried all sorts of different permutations of restarts, cold starts after a shutdown, and it almost seems like it's random. I then decided on turning on File Vault 2 to see if this might affect it somehow, and it doesn't: it's exactly the same. Getting to the File Vault login window is quick, but once it starts loading the OS, it goes back to the long load times. I've also repaired disk permissions, and still the same behavior.
Any ideas what this could be? I appreciate any help or suggestions on the manner. Thank you.
Last edited: