Mavericks slow booting up

[evam]

Can I use this with Mac Os X 10.7 as well?

Clear the kext caches:

sudo chown root:admin (enter password)

sudo kextcache -system-prelinked-kernel
sudo kextcache -system-caches


Do in terminal and reboot. make sure your start up disk is still selected correctly in preferences.

Hi, I have Mac Os X 10.7. Can I use this trick to speed up my computer? If not, can you tell me how to do it?

I would appreciate any help.

Thanks.

 

[Washac]

Tried this but cannot complete the second part, I get this.

xxxxx-xxxxx-Mac-Pro:~ xxxxxx$ sudo kextcache -system-caches
Can't create kext cache under / - owner not root.

XXXX = Just removed my information.

 

[xgman]

Hi, I have Mac Os X 10.7. Can I use this trick to speed up my computer? If not, can you tell me how to do it?

I would appreciate any help.

Thanks.

I believe so.

----------

Tried this but cannot complete the second part, I get this.

xxxxx-xxxxx-Mac-Pro:~ xxxxxx$ sudo kextcache -system-caches
Can't create kext cache under / - owner not root.

XXXX = Just removed my information.

not sure exactly. maybe a terminal guru can help. does the first sudo chown command line prompt you for your admin password?

 

[iPhoneczar]

I'm having the same issue on Mavericks on a brand new [Late 2013 Edition] 15" MacBook Pro Retina.

It usually [9 times out of 10] takes roughly 2 to 3 minutes to get me to a log-in screen.

If I boot into safe mode and then shut down and boot normal it boots in a few seconds [very quick].

If I shut down from 'normal' mode and boot back up it takes 2 to 3 minutes to boot.

From the logs it looks to me like the boot cache is failing on every boot and being rebuilt [and loaded] which takes time - every time.

Have done a format/erase + fresh install twice now - issue persists.

Have an open ticket with Apple and it's in their Engineering department now. I believe this to be a bug with Mavericks but can't confirm this 100%. They do not believe it's hardware failure nor do they believe it's a software issue. Disk Utility tools all ran - etc.

For me the solution is simply to use sleep [and turn off power nap] until the system boots quickly every time as I'm used to.

Perhaps a reboot every couple of days to keep things 'fresh' when I'm not in a hurry to use the system.

I imagine with all of the changes in Mavericks they're probably being slammed with bug reports. I just hope 2 to 3 minute boot time on a machine that should take seconds will be prioritized if it is a bug.

My issue has very similar symptoms and I've found a straightforward cause/effect and apparent fix that I'll offer FWIW. I bought my MBPr in Dec 2013. It has 1TB SSD and is the top of the line model. So I was worried when it started occasionally taking 5-6 minutes to boot. Turning on verbose mode via the NVRAM settings I noticed that when it "hung" this way it had started an FSCK of the boot drive. That pointed me to the fsck_hfs logs in the console app and I could then clearly see that it was the 5-6 minute FSCK check of the 1TB SSD that was the culprit on boot. That led to a call to Apple Care and they had me run the hardware diagnostics (boot, hold "D" key) and all was well so that was a relief. In running DiskUtility after the boot I would sometimes get a message about certain files having wrong block counts and that the disk needed repair. But not always. When I did and when I repaired the disk it would always complete. I thought the corruption might be a bad OS install so I did the nuke and pave, reinstall from scratch, restore from time machine thing. Issue was still there. Then I did a Find from the command prompt from the root to see where the troublesome files (reported in fsck log) were. It turns out they were part of BackBlaze, my cloud backup service.

Bingo! Now it all made sense. Occasionally when doing a shutdown, the shutdown would "pull the rug" out from under BackBlaze and that would cause the "dirty shutdown" flag to be set on the partition and sometimes cause actual corruption in the open files. Now apps are supposed to interact with the OS to prevent that (i.e. like the Mail app will sometimes cause a shutdown to "time out") But not all apps use all of the API's for that sort of thing. When machines took longer to shutdown, you can get away with that as an app developer but these new machines are so fast on boot and shutdown that you literally only have seconds. Also, Apple has dramatically changed the way apps start and stop. The old RC and INIT.D processes have been replaced by LAUNCHCTL and LAUNCH.D. This has put more burden on app developers to ensure the appropriate interactions with the OS in starting and stopping.

As a test of this, I've been manually starting and stopping BackBlaze BEFORE doing a shutdown. I verify that their processes have stopped with the Activity Monitor before I do the Mac shutdown. I haven't had the long boot/FSCK issue since then. Now there COULD be other apps that haven't caught up with Apple yet in terms of the recent OS changes in the way things are done. Your mileage may vary. So even if you don't use BackBlaze you could have this same thing happen if ANY app inadvertently causes a "dirty" shutdown which results in an FSCK run on the following boot. That will significantly delay your boot by the amount of time it takes FSCK to run.

BTW, I have reported this to BackBlaze. They'll fix it no doubt. That is a great service.

 

[camdenmaine]

Syntax Error on clearing kext caches

Clear the kext caches:

sudo chown root:admin (enter password)

sudo kextcache -system-prelinked-kernel
sudo kextcache -system-caches


Do in terminal and reboot. make sure your start up disk is still selected correctly in preferences.

I get errors when I try to do this:
Can't read info dictionary for HotSync Classic Seize.kext: IOCFUnserialize: syntax error near line 1.
Can't read info dictionary for HotSync Classic Seize.kext: IOCFUnserialize: syntax error near line 1.
Can't read info dictionary for HotSync Classic Seize.kext: IOCFUnserialize: syntax error near line 1.
Can't read info dictionary for HotSync Classic Seize.kext: IOCFUnserialize: syntax error near line 1.
kext com.maudio.usb.mobilepre.boot.driver 108019000 is in exception list, allowing to load
kext com.jmicron.JMicronATA 101069000 is in exception list, allowing to load
kext com.ATTO.driver.ATTOExpressSASRAID 307029000 is in exception list, allowing to load
kext com.ATTO.driver.ATTOExpressSASHBA3 100059000 is in exception list, allowing to load
kext com.ATTO.driver.ATTOExpressSASHBA 200009000 is in exception list, allowing to load
kext com.ATTO.driver.ATTOExpressPCIUl4 404029000 is in exception list, allowing to load
kext com.ATTO.driver.ATTOCelerityFC 304089000 is in exception list, allowing to load
kext com.AmbrosiaSW.AudioSupport 401029000 is in exception list, allowing to load
kext com.Accusys.driver.Acxxx 300029000 is in exception list, allowing to load
kext com.AmbrosiaSW.AudioSupport 401029000 is in exception list, allowing to load

 

[glad95]

i tried this but unable to text my password their in the field... pls tell my what to do...no text is appearing in the field while typing the password

----------

i hope xgman will help me...please tell me a way..