Unable to Boot after upgrade to El Capitan Beta 6

App & System Services Core OS Beta macOS

Created Aug ’15

Replies 24

Boosts 0

Views 6.8k

Participants 3

Hi - I know many othere have has this problem, but the solutions that have been previously outlined to do seem to work for me.

Upon start up, the apple log shows, and the progress bar loads normally until it reaches the end and then stalls with out any other further activity. I have been trying to follow the steps outlined by Max in this post: https://forums.developer.apple.com/message/39869#39869 and a couple of others

- I intitially completed a time machine restore from internet recovery mode. The same issue remained after the restart.

- I am unable to start in safe mode

- I have resarted in recovery and completed repair and verify disk permission tasks. All fine.

- I have restarte in single user mode, using:

fsck -fy

This first displayed 'file system was modified' message but this cleared on when run again.

- Starting in verbose mode, the final message that I see (and that is displayed numerous times throughout) is 'Can't get kextd port'

- I have completed a NVRAM Reset.

- I have attempted to complete the following based on a nother forum:

Central Pane > Disk Utility > First Aid > Select internal drive / El Capitan partition.
Then go to the Utilities menu, open a Terminal and type the following:
- cd /Volumes/
- ls
- cd "partition_as_above"
  Identify your 10.11 partition - perhaps "Macintosh HD" unless you renamed it.
- sudo rm -Rf /Library/Extensions/VBox*
- sudo rm -Rf /Library/Application\ Support/VirtualBox/VBox*
- sudo rm -Rf /System/Library/Extensions/Eltima*
Quit Terminal
Reboot as normal.

My drive is called 'Samsung 500G SSD'

- I get stuck when tryng to run the sudo command. Each time, I get: sudo: command not found

I am going mad at this point as you can imagine! Any help would be really appreciated.

Thanks,

Darragh.

Boost

Max108 OP

Aug ’15

That's unusual... I might expect that from a Fusion Drive, but not from an SSD. It's still worth trying the

diskutil coreStorage revert A4D69B45-5A14-47A7-9D61-31923BE5A948

command anyway, but I don't hold out much hope. It's likely, I'm afraid, that you'll have to delete the partition (only the partition - not the disk) again using Disk Utility and reinstall 10.11 (both from the central Recovery menu). Depending on the version of RecoveryHD you have (the new one was only released a few days ago) you'll either be reinstalled to Beta 1 or Beta 7 - if it's Beta 1 then you're probably better off using your USB installer and wiping the whole SSD and starting again.

If you need FileVault security though, you might be better off downgrading to Yosemite for now. I don't think that FileVault is the cause - but it complicates diagnosis a little. There is an outside possiblilty, after both of these major issues you've had that cells in your SSD are begining to fail and that the SSD controller isn't compensating for them adequately. "Conversion Progress: Paused" from the output you posted above is unusual and makes me suspect the drive.

Assuming, for now, that the problem is not hardware related, your safest option would be to use Migration Assistant, after reinstalling Beta 7, to migrate only your user account(s). Your settings are probably safe to import in this instance too, but migrating applications and "other files and folders" runs the risk of re-importing a kernel extension (kext) that is somehow, in concert with Beta 6&7 security) causing the disk corruption you're seeing.

deadyd OP

Aug ’15

Hi Max - I actually got the "Error: -69666: This Core Storage operations is not allowed on a sparse logical volume" error on the revert command.

The unlock command advises that the disk has already been unlocked.

Looking at other forums, the issue is with file vault. I needed to let the encryption complete fully before shutting down, or not use FileVault at all.

I wipe and restore again and will let you know how I get on, this time not enabling file vault.

Max108 OP

Aug ’15

That makes a bit more sense - I understood from your previous reply that it was the unlockVolume command that threw the error. It does bode better for the health of the physical drive happily. I suspect that the advice to let FileVault complete before shutting down is sound and it seems that this recent issue is therefore unrelated to the original trouble that you asked about, which was probably answered above by creating the USB installer and using it, along with your backup, to recreate the system.

Max.

deadyd OP

Aug ’15

Hi Max,

The saga continues..!

So, I complete the reinstall procedure, this time not turing on FileVault. Worked perfectly and restored from time machine back up.

Working away all day until I completed a restart.

Again - upon restart I get the porgress bar and the Apple logo but it fails to boot. I am unable to navigate to cd /Volumes/Samsung SSD 500G to confirm what extensions are running. Returns error of command not found.

I run first aid and all come back fine. The disk is no longer locked or encrypted.

Running the diskutil corestorage list command brings back the following:

ize: 499248103424 B (499.2 GB)

Free Space: 18972672 B (19.0 MB)

+-< Physical Volume FFECE2FF-7B82-439A-A635-D4CD639BAA60

| ----------------------------------------------------

| Index: 0

| Disk: disk0s2

| Status: Online

| Size: 499248103424 B (499.2 GB)

+-> Logical Volume Family 1E49B267-5AA2-4CB6-91EB-E73DCFF62832

----------------------------------------------------------

Encryption Type: None

+-> Logical Volume CD05002B-20C7-4ADD-B78A-96A7EE70B6EA

---------------------------------------------------

Disk: disk1

Status: Online

Size (Total): 498876809216 B (498.9 GB)

Revertible: Yes (no decryption required)

LV Name: Samsung SSD 500G

Volume Name: Samsung SSD 500G

Content Hint: Apple_HFS

Max108 OP

Aug ’15

To rule out coreStorage being active on your volume as the cause of the issue, the first thing would be to boot into Recovery Mode and run this from Terminal (probably easiest to copy-paste from Safari as described above):

diskutil coreStorage revert CD05002B-20C7-4ADD-B78A-96A7EE70B6EA

If is still fails to boot, it would be useful to know if it is getting stuck at the same point in the progress bar and if you followed my advice above from two replies up to only migrate user data and not Applications and "other files and folders" etc.

Also, if you are still getting a bunch of "kernel[0]: Can't get kextd port" messages when you boot in Verbose Mode, then we're still looking for a kext.

deadyd OP

Aug ’15

Thanks Max.

That command rand successfully, but still not booting up.

It is stalling at the same stage since I did the resinstall, where I see the progress bar, but it does even being to load. This is separate from the orginal issue I reported, where it was getting stuck at the point where the progress bar has fully loaded.

I did restore Application data as part of the restore, but

In verbose mode, I am no longer seeing any kernel[0]: Can't get kextd port messages.

A couple of things that do stand out:

Kerel Extensions in backtrace:

com.eltima.SyncMate.ktext (0.25b15)

dependency: com.apple.iokit.IOSesrialfaily(11)

dependency: com.apple.iokit.IOUSBFamily

dependency: com.apple.iokit.NetworkingFamily

Also, This continues to appear:

Mac OS version:

Not Yet Set

I have also attempted the following from previous troubleshooting steps:

csrutil disable

It disables sucessfully but no change upon reboot.

Given that the SyncMate.ktest was present in verbose mode, I complete the following:

rm -Rf System/Library/Extensions/Eltima*

com.eltima.SyncMate.ktext (0.25b15) continues to remain in verbose mode after running the command.

Max108 OP

Aug ’15

Accepted Answer

These forums are about to be closed (OS X 10.11 Beta Forum Closing)

I should point out that I'm not affiliated with Apple in any way, but if you would like to request personal help, please contact me on MacMax108@gmail.com

-Max

deadyd OP

Aug ’15

Boom! Worked.

That did it. I was sure I had run cd /Volumes/Samsung\ SSD\ 500G but obviously not.

Will removing this kextd have any impact, or reappear in the future?

Thanks again for all your help and support.

Max108 OP

Aug ’15

Glad it's sorted for you 🙂

No, it will only incapacitate SyncMate - it won't affect anything else on your system. The only way it could reappear in the future is if you manually re-install SyncMate or restore Applications from a backup older than the ones you make from now on.