Unable to retrieve kernel symbols - Page 2

allenbd · ‎02-02-2015

My Mac was just updated to 10.10.2 Yosemite. All was well until that completed. After the reboot, this is all I get. I did the same thing that was mentioned in other threads and did the ls -l mdfind

sudo ls -l `mdfind -name mach_kernel`

ls: (August: No such file or directory

ls: /Volumes/My: No such file or directory

ls: 01/_CCC: No such file or directory

ls: 01/mach_kernel: No such file or directory

ls: 02): No such file or directory

ls: 13-15-18/mach_kernel: No such file or directory

ls: 2TB: No such file or directory

ls: Archives/2014-08-02: No such file or directory

ls: Book: No such file or directory

-rw-r--r--@ 1 root wheel 10618024 Feb 2 17:00 /mach_kernel

Any ideas? Beyond frustrated. I can boot into bootcamp but I want to be able to run it via a VM.

lynndylan · ‎02-04-2015

The first command gives me an error:

❯ sudo diskutil disableJournal /dev/disk0s3

Password:

An error occurred journaling the file system: Couldn't mount disk (-69842)

I'm not sure if this is useful, but here are the last 100 lines of /var/log/system.log:

Feb 4 16:56:08 tests-MacBook-Pro.local WindowServer[119]: WSGetSurfaceInWindow : Invalid surface 1174309725 for window 618

Feb 4 16:56:30 --- last message repeated 1 time ---

Feb 4 16:56:30 tests-MacBook-Pro kernel[0]: process VirtualBoxVM[18340] caught causing excessive wakeups. EXC_RESOURCE supressed due to audio playback

Feb 4 16:57:05 tests-MacBook-Pro.local WindowServer[119]: WSGetSurfaceInWindow : Invalid surface 1562041045 for window 616

Feb 4 16:57:06 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 16:57:39 --- last message repeated 4 times ---

Feb 4 16:57:47 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 16:57:57 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 16:58:27 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 16:59:02 --- last message repeated 1 time ---

Feb 4 16:59:07 tests-MacBook-Pro.local WindowServer[119]: WSGetSurfaceInWindow : Invalid surface 1176585671 for window 619

Feb 4 16:59:16 tests-MacBook-Pro.local WindowServer[119]: WSGetSurfaceInWindow : Invalid surface 1562036699 for window 620

Feb 4 16:59:27 tests-MacBook-Pro kernel[0]: Google Chrome He (map: 0xffffff80607a33c0) triggered DYLD shared region unnest for map: 0xffffff80607a33c0, region 0x7fff86c00000->0x7fff86e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

Feb 4 16:59:27 tests-MacBook-Pro kernel[0]: Google Chrome He (map: 0xffffff80607a3690) triggered DYLD shared region unnest for map: 0xffffff80607a3690, region 0x7fff86c00000->0x7fff86e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

Feb 4 16:59:48 tests-MacBook-Pro kernel[0]: process VirtualBoxVM[18340] caught causing excessive wakeups. EXC_RESOURCE supressed due to audio playback

Feb 4 17:00:04 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 17:00:44 --- last message repeated 1 time ---

Feb 4 17:01:18 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 17:01:48 --- last message repeated 35 times ---

Feb 4 17:01:48 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 17:02:18 --- last message repeated 88 times ---

Feb 4 17:02:25 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 17:02:38 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 17:03:03 --- last message repeated 7 times ---

Feb 4 17:03:03 tests-MacBook-Pro.local discoveryd[52]: Basic DNSResolver Re-Binding to random udp port 58644

Feb 4 17:03:03 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 17:03:36 --- last message repeated 3 times ---

Feb 4 17:03:36 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 17:03:40 tests-MacBook-Pro kernel[0]: process VirtualBoxVM[18340] caught causing excessive wakeups. EXC_RESOURCE supressed due to audio playback

Feb 4 17:03:40 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 17:04:11 --- last message repeated 8 times ---

Feb 4 17:04:11 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 17:04:43 --- last message repeated 4 times ---

Feb 4 17:04:49 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 17:05:21 --- last message repeated 3 times ---

Feb 4 17:05:21 tests-MacBook-Pro.local Airmail 2 Beta[15974]: [***ERROR***] ERROR IDLE lynn.dylan.hurley@gmail.com Error Domain=MCOErrorDomain Code=1 "A stable connection to the server could not be established." UserInfo=0x618000c75e00 {NSLocalizedDescription=A stable connection to the server could not be established.}

Feb 4 17:05:21 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 17:05:55 --- last message repeated 10 times ---

Feb 4 17:06:05 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 17:06:10 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 17:06:33 --- last message repeated 4 times ---

Feb 4 17:06:33 tests-MacBook-Pro kernel[0]: Google Chrome He (map: 0xffffff80607a33c0) triggered DYLD shared region unnest for map: 0xffffff80607a33c0, region 0x7fff86c00000->0x7fff86e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

Feb 4 17:06:33 tests-MacBook-Pro kernel[0]: Google Chrome He (map: 0xffffff80607a3690) triggered DYLD shared region unnest for map: 0xffffff80607a3690, region 0x7fff86c00000->0x7fff86e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

Feb 4 17:06:36 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 17:07:11 --- last message repeated 4 times ---

Feb 4 17:07:12 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 17:07:14 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 17:07:36 tests-MacBook-Pro kernel[0]: Google Chrome He (map: 0xffffff80607a33c0) triggered DYLD shared region unnest for map: 0xffffff80607a33c0, region 0x7fff86c00000->0x7fff86e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

Feb 4 17:07:36 tests-MacBook-Pro kernel[0]: Google Chrome He (map: 0xffffff80536c8f00) triggered DYLD shared region unnest for map: 0xffffff80536c8f00, region 0x7fff86c00000->0x7fff86e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

Feb 4 17:07:42 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 17:07:56 --- last message repeated 2 times ---

Feb 4 17:07:56 tests-MacBook-Pro.local sudo[18505]: lynn : TTY=ttys005 ; PWD=/Users/lynn ; USER=root ; COMMAND=/usr/sbin/diskutil disableJournal /dev/disk0s3

Feb 4 17:07:56 tests-MacBook-Pro kernel[0]: hfs: The journal file changed size! (was 0; is 8388608). Fixing up.

Feb 4 17:07:56 tests-MacBook-Pro kernel[0]: hfs: open_journal_dev: no available external journal partition found. waiting 10sec.

Feb 4 17:08:09 --- last message repeated 1 time ---

Feb 4 17:08:09 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 17:08:16 --- last message repeated 1 time ---

Feb 4 17:08:16 tests-MacBook-Pro kernel[0]: hfs: open_journal_dev: no available external journal partition found. waiting 10sec.

Feb 4 17:08:26 tests-MacBook-Pro kernel[0]: hfs: volume: disk0s3: did not find jnl device uuid: from machine serial number:

Feb 4 17:08:26 tests-MacBook-Pro kernel[0]: hfs_mounthfsplus: hfs_late_journal_init returned (30), maybe an external jnl?

Feb 4 17:08:26 tests-MacBook-Pro kernel[0]: hfs_mounthfsplus: encountered error (22)

Feb 4 17:08:26 tests-MacBook-Pro kernel[0]: hfs_mountfs: encountered failure 22

Feb 4 17:08:26 tests-MacBook-Pro kernel[0]: hfs_mount: hfs_mountfs returned error=22 for device disk0s3

Feb 4 17:08:26 tests-MacBook-Pro.local diskarbitrationd[42]: unable to mount /dev/disk0s3 (status code 0x00000001).

Feb 4 17:08:26 tests-MacBook-Pro.local diskmanagementd[18507]: Mount of disk0s3 blocked by dissenter PID=0 (unknown) status=0x0000c001 log=GenericBsdMountUmountProgramFailure message=(null)

Feb 4 17:08:38 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 17:09:08 --- last message repeated 2 times ---

Feb 4 17:09:08 tests-MacBook-Pro.local CalendarAgent[308]: [com.apple.calendar.store.log.caldav.coredav] [Refusing to parse response to PROPPATCH because of content-type: [text/html; charset=UTF-8].]

Feb 4 17:09:21 --- last message repeated 1 time ---

Feb 4 17:09:21 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 17:09:31 tests-MacBook-Pro.local WindowServer[119]: Surface testing disallowed updates for 10 sequential attempts...

Feb 4 17:09:31 tests-MacBook-Pro.local WindowServer[119]: Surface test allowed updates after 12 attempts

Feb 4 17:09:35 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 17:09:42 --- last message repeated 1 time ---

Feb 4 17:09:42 tests-MacBook-Pro.local sudo[18524]: lynn : TTY=ttys005 ; PWD=/Users/lynn ; USER=root ; COMMAND=/usr/sbin/diskutil disableJournal /dev/disk0s3

Feb 4 17:09:42 tests-MacBook-Pro kernel[0]: hfs: The journal file changed size! (was 0; is 8388608). Fixing up.

Feb 4 17:09:42 tests-MacBook-Pro kernel[0]: hfs: open_journal_dev: no available external journal partition found. waiting 10sec.

Feb 4 17:09:46 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 17:09:48 tests-MacBook-Pro kernel[0]: Google Chrome He (map: 0xffffff804996db40) triggered DYLD shared region unnest for map: 0xffffff804996db40, region 0x7fff86c00000->0x7fff86e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

Feb 4 17:09:48 tests-MacBook-Pro kernel[0]: Google Chrome He (map: 0xffffff804996d960) triggered DYLD shared region unnest for map: 0xffffff804996d960, region 0x7fff86c00000->0x7fff86e00000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

Feb 4 17:09:50 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 17:09:52 tests-MacBook-Pro kernel[0]: hfs: open_journal_dev: no available external journal partition found. waiting 10sec.

Feb 4 17:09:52 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 17:09:53 --- last message repeated 1 time ---

Feb 4 17:09:53 tests-MacBook-Pro.local WindowServer[119]: Surface testing disallowed updates for 10 sequential attempts...

Feb 4 17:09:53 tests-MacBook-Pro.local WindowServer[119]: Surface test allowed updates after 13 attempts

Feb 4 17:09:55 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

Feb 4 17:10:02 tests-MacBook-Pro kernel[0]: hfs: open_journal_dev: no available external journal partition found. waiting 10sec.

Feb 4 17:10:12 tests-MacBook-Pro kernel[0]: hfs: volume: disk0s3: did not find jnl device uuid: from machine serial number:

Feb 4 17:10:12 tests-MacBook-Pro kernel[0]: hfs_mounthfsplus: hfs_late_journal_init returned (30), maybe an external jnl?

Feb 4 17:10:12 tests-MacBook-Pro kernel[0]: hfs_mounthfsplus: encountered error (22)

Feb 4 17:10:12 tests-MacBook-Pro kernel[0]: hfs_mountfs: encountered failure 22

Feb 4 17:10:12 tests-MacBook-Pro kernel[0]: hfs_mount: hfs_mountfs returned error=22 for device disk0s3

Feb 4 17:10:12 tests-MacBook-Pro.local diskarbitrationd[42]: unable to mount /dev/disk0s3 (status code 0x00000001).

Feb 4 17:10:12 tests-MacBook-Pro.local diskmanagementd[18526]: Mount of disk0s3 blocked by dissenter PID=0 (unknown) status=0x0000c001 log=GenericBsdMountUmountProgramFailure message=(null)

Feb 4 17:10:15 tests-MacBook-Pro.local Google Chrome Helper[18452]: CoreText CopyFontsForRequest received mig IPC error (FFFFFFFFFFFFFECC) from font server

Feb 4 17:10:18 --- last message repeated 5 times ---

Feb 4 17:10:18 tests-MacBook-Pro kernel[0]: aio_queue_async_request(): too many in flight for proc: 16.

dariusd · ‎02-04-2015

You might need to restart your Mac and try again immediately after it's started. You might also try booting into the Recovery HD (restart and press Command+R before the Apple logo appears on screen) and then use the recovery environment.

I have to admit being a bit perplexed as to how this has happened. It looks like your Recovery HD is somewhat corrupted. It's a concern.

(By the way, please go easy on the copy-and-paste... There are lots of folks who get email notifications which include all the posts in this forum. We don't want to fill everyone's inboxes! I should have requested attachments for some of the earlier commands in the thread, had I known in advance how much output they were going to produce... Attachments are fine.)

Thanks,

--

Darius

lynndylan · ‎02-04-2015

By the way, please go easy on the copy-and-paste...

Sorry, I was just following the lead of other posts that I'd seen. It won't happen again!

I won't be able to restart my machine for a while, but I'll follow those steps and post back ASAP.

I'm not sure if I've mentioned this before, but this only started happening once I updated to Mac OS 10.10.2. Everything was fine on the previous release.

lynndylan · ‎02-04-2015

I just tried restarting and running the "diskutil disableJournal" command, and I saw the same result as before. I even tried rebooting into recovery mode and running the command, but the result was still the same.

Again, this was the error:

❯ sudo diskutil disableJournal /dev/disk0s3

Password:

An error occurred journaling the file system: Couldn't mount disk (-69842)

allenbd · ‎02-05-2015

I apologize I'm always lagging a day. I'm having to boot directly into bootcamp to work throughout the day and it's a bit inconvenient to shut everything down to log back into osx to run the terminal commands just to log back out and go in and do some work. With that said, I'm having all the same exact issues lynndylan. I'm going to try the command R but, last time I did that it wouldn't let me unmount the disk (I tried doing the repair from there). I did create that boot thumb drive - I might give that a shot....

allenbd · ‎02-05-2015

Ok...so I spent some time doing what I mentioned before. Booted off a USB install of Yosemite. I got to the terminal and tried all kinds of things using diskutil - the most interesting was a diskutil verifyVolume disk0s3...that gave me back "invalid b-tree node size"....so apparently there's a pretty big problem on my recovery disk. Any idea how to proceed from here? The crappy thing is I can log into Mac...I can log into Windows. But I can't use VMWare to run Windows. And apparently my recovery volume is jacked up and I really don't know what to do other than starting over, which at this point really isn't an option.

Thoughts?

lynndylan · ‎02-05-2015

And apparently my recovery volume is jacked up and I really don't know what to do other than starting over, which at this point really isn't an option.

It looks like we both have the same problem. What could have caused this issue? Everything was working for me before I updated to 10.10.2, and the update didn't report any errors.

Is there any way to repair the recovery volume? Disk Utility doesn't even list the volume at all, so I can't repair it from there.

allenbd · ‎02-05-2015

It looks like we both have the same problem. What could have caused this issue? Everything was working for me before I updated to 10.10.2, and the update didn't report any errors.

Is there any way to repair the recovery volume? Disk Utility doesn't even list the volume at all, so I can't repair it from there.

That's the incredibly frustrating thing to me - there was no indication that there was any kind of problem. And this most definitely happened immediately after the 10.10.2 update and a reboot. As soon as it loaded back up VMWare stopped working, and if not for all this digging in the logs and running these commands from the terminal, I wouldn't have even found out about the b-tree node size garbage. Also - same thing for me Disk Utility doesn't show the volumes in the UI - you have to use the command line...but when trying to do a repair from there, that's when I get the "Can't Mount" error.

Hopefully someone can give me a better answer than wipe and restart. At this point, VMWare software is doing nothing for me as I'm booting straight into bootcamp in order to do what I need to do.

dariusd · ‎02-06-2015

OS X 10.10.2 was the first in the 10.10.x series to provide a new kernel, and a new kernel necessitates updating the Recovery HD, so the problem could have occurred anytime since you originally installed OS X 10.10 and it would not have been apparent until now.

Random question for you, lynndylan: Are you also using Boot Camp to sometimes run Windows on the host?

Thanks,

--

Darius

dariusd · ‎02-06-2015

I would have thought that using the command-line tools would give the best chance of success. To be honest, I am not 100% sure that these tools are even telling us the truth anymore. Maybe the Recovery HD is fine but the mount/check tools are broken...?

I do not immediately know of any further tricks for fixing a Recovery HD. I can try to investigate further tomorrow, unless anyone else has any suggestions in the meantime.

Thanks,

--

Darius

lynndylan · ‎02-10-2015

Hi I just saw this - sorry for the late reply. I am not using Boot Camp.

I'm still having the same issue. I've been using VirtualBox for the past few days so I don't get fired, but I plan to re-install OS X tonight. I'll post the results ASAP.

wila · ‎02-10-2015

lynndylan wrote:

but I plan to re-install OS X tonight.

PMJI, this is kind of general knowledge (search the forum), but just to make sure you don't end up deeper down in the rabbit hole.

Do NOT depend on Time Machine for Virtual Machine backups.

Make a separate copy of any virtual machine you want to retain to an external disk before wiping and reinstall.

--

Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva

lynndylan · ‎02-10-2015

I just re-installed OS X and it solved the problem. The installer even left my data intact

I should note that I had to re-download the installer from the app store. I tried to re-install from within recovery mode, but it failed (twice).

dariusd · ‎02-10-2015

Good to know that you're back up and running. It doesn't surprise me that recovering from the Recovery HD failed given that there was a good chance it was really corrupted. It was worth a shot, though.

Thanks,

--

Darius

ourbenefactors · ‎07-05-2015

Wanted to extend thanks to dariusd for helping to resolve my issue. A nervewracking experience!