beta 6 won't install

Question

cjgross OP

Created Aug ’15

Replies 4

Boosts 0

Views 1.3k

Participants 2

Hey,

i just wanted to update from beta 5 to beta 6 yesterday.

The macbook started the installation and come to the point, where it has to restart. After the Restart it didnt made progress in 2 hours, so i tried restarting. nothing happend. I cant do safeboot or single user. Verbose and single user give me kernel panic or cpu panic something likr this. Here is the last part of installation log.

Aug  5 01:36:29 MacBook-Pro OSInstaller[456]: Attempting to make install media (r/w) for unbless.
Aug  5 01:36:30 MacBook-Pro OSInstaller[456]: Cleaning up non-target install media.
Aug  5 01:36:30 MacBook-Pro OSInstaller[456]: Reblessing orginal system on source media.
Aug  5 01:36:30 MacBook-Pro storagekitd[457]: Blessed disk: Bless disk operation for disk: SKDisk { BSD Name: disk2s2 Mount point: /Volumes/Install OS X El Capitan Public Beta Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }
Aug  5 01:36:30 MacBook-Pro OSInstaller[456]: InstallType cookie file was successfully written for Setup Assistant to pick up.
Aug  5 01:36:30 MacBook-Pro OSInstaller[456]: TAL state restore path:/Volumes/Macintosh HD/.TALRestoreApps
Aug  5 01:36:30 MacBook-Pro OSInstaller[456]: No TAL state to restore
Aug  5 01:36:30 MacBook-Pro OSInstaller[456]: Boot chime muted
Aug  5 01:36:30 MacBook-Pro OSInstaller[456]: Evaluating 1 disks
Aug  5 01:36:30 MacBook-Pro OSInstaller[456]: Evaluating SKCSDisk { CSLV UUID: D7071350-CCCB-409E-80EE-97A338CA892A CSLVG UUID: 75302EC1-3FE2-44FE-9FBC-2F378C71FFCF BSD Name: disk1 Mount point: /Volumes/Macintosh HD Role: kSKDiskRoleMacSystem Type: kSKDiskTypeCSLV }
Aug  5 01:36:30 MacBook-Pro OSInstaller[456]: Macintosh HD is a valid target.
Aug  5 01:36:31 MacBook-Pro storagekitd[457]: Blessed disk: Bless disk operation for disk: SKCSDisk { CSLV UUID: D7071350-CCCB-409E-80EE-97A338CA892A CSLVG UUID: 75302EC1-3FE2-44FE-9FBC-2F378C71FFCF BSD Name: disk1 Mount point: /Volumes/Macintosh HD Role: kSKDiskRoleMacSystem Type: kSKDiskTypeCSLV }
Aug  5 01:36:31 MacBook-Pro storagekitd[457]: Updating boot≠root for: /Volumes/Macintosh HD
Aug  5 01:36:31 MacBook-Pro OSInstaller[456]: Source is not target, not cleaning up IA
Aug  5 01:36:31 MacBook-Pro OSInstaller[456]: Removed mutable product
Aug  5 01:36:31 MacBook-Pro OSInstaller[456]: Deleted mutable product.
Aug  5 01:36:31 MacBook-Pro OSInstaller[456]: Running /usr/libexec/smcupdater using payload /Volumes/Mac OS X Install DVD/Packages/SMCPayloads
Aug  5 01:36:31 MacBook-Pro Unknown[437]: path: /Volumes/Mac OS X Install DVD/Packages/SMCPayloads/Mac-C3EC7CD22292981F
Aug  5 01:36:31 MacBook-Pro Unknown[437]: Failed dir stat
Aug  5 01:36:32 MacBook-Pro OSInstaller[456]: /usr/libexec/smcupdater finished with status: 11
Aug  5 01:36:32 MacBook-Pro OSInstaller[456]: Running /usr/libexec/efiupdater using payload /Volumes/Mac OS X Install DVD/Packages/EFIPayloads
Aug  5 01:36:32 MacBook-Pro Unknown[437]: EFI currentVersion: [00EE0009]
Aug  5 01:36:32 MacBook-Pro Unknown[437]: EFI updateVersion:  [00EE0009]
Aug  5 01:36:32 MacBook-Pro OSInstaller[456]: /usr/libexec/efiupdater preflight finished with status: 1
Aug  5 01:36:32 MacBook-Pro OSInstaller[456]: ------- Install Complete -------
Aug  5 01:36:32 MacBook-Pro OSInstaller[456]: User data migration: 331 seconds
Aug  5 01:36:32 MacBook-Pro OSInstaller[456]: Run SMC updater tool: 0 seconds
Aug  5 01:36:32 MacBook-Pro OSInstaller[456]: Install packages: 657 seconds
Aug  5 01:36:32 MacBook-Pro OSInstaller[456]: Ensure recovery system: 26 seconds
Aug  5 01:36:32 MacBook-Pro OSInstaller[456]: Remove previous system: 360 seconds
Aug  5 01:36:32 MacBook-Pro OSInstaller[456]: Post install cleanup: 1 seconds
Aug  5 01:36:32 MacBook-Pro OSInstaller[456]: Attaching the install log: 0 seconds
Aug  5 01:36:32 MacBook-Pro OSInstaller[456]: Run EFI updater tool: 0 seconds
Aug  5 01:36:32 MacBook-Pro OSInstaller[456]: Preparing disk for install: 2 seconds
Aug  5 01:36:32 MacBook-Pro OSInstaller[456]: Verify and repair disk: 140 seconds
Aug  5 01:36:32 MacBook-Pro OSInstaller[456]: Enabling system idle sleep.
Aug  5 01:36:42 MacBook-Pro OSInstaller[456]: Can't save principal user cookie, path /Volumes/Macintosh HD/private/var/db/.AppleUpgrade is invalid
Aug  5 01:36:42 MacBook-Pro OSInstaller[456]: Could not find next pane.

only thing i could do was reverse by backup or install beta 1 again in the recovery. so but after i red her about virtualbox i tried this, but hat nothing to do with it, stuck at the same point again. Macbook retina 15 mid 2012

Thanks

Boost

Answer 1

Max108 OP

Aug ’15

Hi cj,

Do you have a DVD drive attached? If so, remove any DVD or drive and try again.

Your log also mentions an SMC update so maybe an SMC reset will help:

Shut down the computer.
Plug in the MagSafe power adapter to a power source and to your computer.
On the built-in keyboard, press the (left side) Shift, Control, and Option keys and the power button at the same time.
Release all the keys and the power button at the same time.
Press the power button to turn on the computer

Max.

0

Answer 2

cjgross OP

Aug ’15

yeah i've got smc problems all the time. Apple support cant find failure and thinks its on me and not the hardware. But tried to reset before install doesnt bring me to beta 6.

0

Answer 3

Max108 OP

Aug ’15

Accepted Answer

Your Reply from earlier:

I used the tools by syncmate and blackberry suite to uninstall the kext, which i couldnt find anywhere [kexts tend to be either in /Library/Extensions or /System/Library/Extensions]

Before updating, i did NVram reset and smc reset. and beta 6 is now running [except for your SMC problems, the resets are generally not necessary if you remove the kexts before updating].

First i had a problem with audio and microphone, i had to turn of dictation and restart. Now all is back to normal and i can do a backup.

0

Answer 4

Max108 OP

Aug ’15

Anyway, I'm glad it's sorted for you 🙂

As for your battery issue - that seems like a seperate problem - If you create it's own thread, I'll try to address it there (although it sounds like a tricky one).

To mark your question as answered (it goes green so that others can easily see there is a solution for it) you have to log in to these Developer Forums first (top left of this page) and then come back to this thread. Also, If a reply was helpful, use the Actions menu under it to "Mark as Helpful"

0