Wahrscheinlich bin ich der letzte Mensch im Bundesgebiet, der seinem Macbook Pro endlich macOS Sierra gegönnt hat.
Aber wie sich herausstellt, hat sich meine Säumigkeit ausgezahlt.
Denn gleich nach der Installation stellte ich fest, dass mein USB-Ethernet-Adapter entweder nicht mehr erkannt wurde oder
aber zumindest keine Netzwerkverbindung mehr zustande brachte. In meinem Adapter steckt der Ethernet-Controller
. Unter diesem Stichwort fanden sich
wie die unter https://forums.developer.apple.com/thread/48775
, und so war schnell klar, dass eine
Neuinstallation des zugehörigen Treibers fällig war. Und da ich so lange gewartet hatte, war zum Glück auch schon
eine Treiberversion vorrätig, die mein Problem schnell löste:
Ausserdem musste ich feststellen, daß Paintbrush
nicht mehr starten will.
Offenbar gibt es dazu auch keine neuere Version, und so bin ich jetzt auf der Suche nach gleichwertigem oder besseren Ersatz.
In more than two years of owning a Macbook, I never faced a single issue upgrading the OS. Until today when, after installing the
OS X 10.11.1, the Macbook would just hang after rebooting.
More precisely, the progress bar on the boot screen would stop at roughly two thirds of the way. So today, finally, I had to figure
out what kind of diagnosis and recovery options OS X actually provides.
The two most important tools were:
- ⌘+V during reboot: Boot in verbose mode, showing the boot messages instead of the Apple logo and progress bar. I noticed
that the boot process hung after a message saying pci pause: SDXC.
- ⌘+R during reboot: Boots into recovery mode,
which offers tools for disk and networking diagnosis, as well as
the option to open a terminal as a superuser.
Things I tried:
I was dangerously close to reinstalling the OS now, with only two aces left up my sleeves: Single-user mode
and kernel extensions.
I had seen references to startup issues related to kernel extensions in some articles, but knew very little about them.
The first thing I tried was to temporarily disable kernel extension signing (nvram boot-args=kext-dev-mode=1
), with no
discernible effect. Fortunately, at this point I came across
Justin Silver's blog article "OS X El Capitan 10.11.1 Hanging on Boot"
in which he describes a startup issue which looks a lot
like mine. His excellent summary contains
instructions on disabling kernel extensions using recovery mode - which helped me solve my problem!
I booted into recovery mode, opened a terminal window, and then:
$ mount -rw /
$ cd /Volumes/Macintosh\ HD
$ cd Library/Extensions
Following Justin's advice, I moved all kernel extensions out of
to disable them temporarily, and
then rebooted. Lo and behold, the login screen appeared! After a few such rounds of moving kernel extensions back to
and rebooting, the root cause of my startup issues turned out to be those HP printer extensions.
The HP kernel extensions had been on my system for quite some time, of course, and had never caused any problems like this before.
So there are still open questions about what exactly had happened here. To be solved on a rainy day.
Other related links:
Update January 2nd, 2016: Today it happened again - the MacBook hung at the same point during reboot. I remember
I installed an HP scanner driver roughly a week ago, and I probably did not reboot since then. The above recipe
worked for me this time again.
Update November 2016: Apparently, the printer driver reinstalls itself automatically:
See also https://support.apple.com/en-us/HT201465
. Which explains the many times I have had to re-apply the workaround described above.
I guess it is about time to look for and eliminate the root cause of all this.
I had seen that pesky message every now and then before, but today I finally got fed up with it, as I was pretty
sure that no application was running which had a legitimate business touching the external drive - at least
none of the applications I had started myself. So I set out on a quest to find the culprit.
The weapon of choice in such a case is lsof
sudo lsof | grep /Volumes/FOO
In my case, this produced a list of files opened by a process called
which, apparently, is used
to produce the Spotlight search index:
mds_store 42059 root txt REG 1,6 3277 8832664
mds_store 42059 root txt REG 1,6 32768 8832663
mds_store 42059 root txt REG 1,6 8192 8832666
mds_store 42059 root txt REG 1,6 8192 8832668
mds_store 42059 root txt REG 1,6 8224 8832669
mds_store 42059 root txt REG 1,6 1024 8832670
mds_store 42059 root txt REG 1,6 65536 8832671
mds_store 42059 root 5r DIR 1,6 2074 8832643
mds_store 42059 root 11r DIR 1,6 2074 8832643
mds_store 42059 root 47u REG 1,6 28 8832650
mds_store 42059 root 49u REG 1,6 118784 8832674
backupd 42148 root 4w REG 1,6 1300 8832803
The fun part was that I had explicitly configured Spotlight to ignore that particular external disk
- and yet,
it was still trying to index it!
Turns out that I am not alone with this.
"Disable Spotlight on a FAT32 external drive"
provides the best summary I could find. Apparently, the type of file system on the external drive plays a role.
I was somewhat skeptical about this claim, but then, all my external drives had FAT32 file systems on them,
and so I followed the instructions in the article. I was still somewhat incredulous, as this seemed to be such a basic issue and the article is rather old.
But then, following the instructions indeed seemed to be successful, at least initially.
The magic ingredient in the sauce was to create a top-level file called
the affected drive:
I was too impatient to wait for existing instances of
to finish their work,
and did not care about the consistency of the Spotlight index on the external drive anyway.
So I killed the
process right away, then unplugged the drive and plugged it in again.
From there, indeed I had no issues anymore with ejecting the external disk. Hmmm...
Other related articles and discussions:
Whenever I connect an external monitor to my MacBook Pro via a Thunderbolt/DVI adapter, the Mac
loses its wifi connection. Huh?
My setup: A MacBook Pro 2013 model with Retina display, a Thunderbolt/DVI adapter hooked up to an
external old Dell monitor. The Mac has a stable wifi connection - until I plug in the DVI adapter.
This problem annoyed me for quite some time, up to the point I did not even use the external monitor
anymore. Today, it happened to me again, and I decided to finally try and tackle the issue.
I found this discussion
titled "My wifi drops when I plug in an external monitor through the thunderbolt port". In this discussion,
a workaround is suggested - which is changing the wifi channel!
And indeed, this helped! Before, my router was using channel 4. I reconfigured the router
to select an appropriate channel automatically, and now it is on channel 1, as confirmed by the
Wireless Diagnostics tool