D3rR4lf

Q: OSX 10.11.1 El Capitan crashes when using filevault encrypted external drive

Here is my problem:

 

the upgrade of my mac mini late 2012 from 10.11.0 to 10.11.1 went fine.

I have two external permanently attached. One of the drive is encrypted with filevault.

 

Latest after 5 minutes of accessing the encrypted drive, the mac mini crashes.

Until I figured this out, it crashed at least 10 times.

 

Now with the encrypted drive removed the system runs stable.

 

After I figured out, what caused the crash, I went to the Appstore and downloaded a fresh copy of 10.11.1 and installed it again on top of the current installation. But that hasn't helped.

 

The problem is not only with this one drive, but all encrypted drives I have.

The drives work great on my other macs with 10.11.0.

 

Is there a bug in 10.11.1?

 

Any idea, what might fix the problem?

 

Ralf

Mac mini, OS X El Capitan (10.11.1)

Posted on Oct 27, 2015 1:09 AM

Close

Q: OSX 10.11.1 El Capitan crashes when using filevault encrypted external drive

  • All replies
  • Helpful answers

  • by Linc Davis,

    Linc Davis Linc Davis Oct 27, 2015 5:47 PM in response to D3rR4lf
    Level 10 (208,037 points)
    Applications
    Oct 27, 2015 5:47 PM in response to D3rR4lf

    These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.

    Launch the Console application in any of the following ways:

    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

    ☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

    ☞ Open LaunchPad and start typing the name.

    In the Console window, select

              DIAGNOSTIC AND USAGE INFORMATION System Diagnostic Reports

    (not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select

              View Show Log List

    from the menu bar.

    There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A panic report has a name that begins with "Kernel" and ends in ".panic". Select the most recent one. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.

    If you don't see any reports listed, but you know there was a panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.

    In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)

    Please don’t post other kinds of diagnostic report.

    I know the report is long, maybe several hundred lines. Please post all of it anyway.

    When you post the report, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the text on Pastebin, then post a link here to the page you created.

  • by D3rR4lf,

    D3rR4lf D3rR4lf Oct 28, 2015 2:27 PM in response to Linc Davis
    Level 1 (0 points)
    Oct 28, 2015 2:27 PM in response to Linc Davis

    Thanks for your detailed description, to submit a kernel panic report.

     

    Unfortunately, it seems there was no kernel panic. since I see only 11 entries there, but none is a kernel panic.

    Most of them are from iTunes. One from ImageCapture and two mds_stores. But all ending with .diag

     

    Maybe I explain a little more in detail, what the system does, in case it "crashes".

    The system removes ALL windows and just shows my blue background color.

    It even removes ALL icons from the menu bar except the search icon.

    The mouse is still moving, but no click or key stroke works anymore.

    The only option I have is press the power button for several seconds until the system is off.

     

    Any other suggestion?

  • by D3rR4lf,

    D3rR4lf D3rR4lf Oct 28, 2015 2:30 PM in response to Linc Davis
    Level 1 (0 points)
    Oct 28, 2015 2:30 PM in response to Linc Davis

    one more piece of information:

    Not every time, but two or three times, the system asked me to submit a crash report to Apple, once the system rebooted.

    I agreed and send the report to Apple...

  • by Linc Davis,

    Linc Davis Linc Davis Oct 28, 2015 6:40 PM in response to D3rR4lf
    Level 10 (208,037 points)
    Applications
    Oct 28, 2015 6:40 PM in response to D3rR4lf

    Please post one of those reports.

  • by D3rR4lf,

    D3rR4lf D3rR4lf Oct 28, 2015 11:05 PM in response to Linc Davis
    Level 1 (0 points)
    Oct 28, 2015 11:05 PM in response to Linc Davis

    Here is what happened last night:

     

    I attached the encrypted drive and started a copy of some big files (total of 100 GB) and went to sleep.

    This morning the mac mini was off!

     

    and the following system report shall be sent to apple after the reboot:

     

     

     

    Thu Oct 29 06:58:51 2015

     

     

    *** Panic Report ***

    panic(cpu 1 caller 0xffffff8009b9ed64): launchd exited (signal 11, exit status 0 )

     

     

    uuid info:

    0x7fff6775d000 uuid = <03673b53-b8b7-34d1-adce-f449e78e39cc>

    0x1035d4000 uuid = <13d08717-b23a-38be-85a6-085b051f8322>

     

     

    Thread 4 crashed

     

     

    RAX: 0x00007fff67794e48, RBX: 0x00007fff6779c5f8, RCX: 0x0000000000000000, RDX: 0x00007fff67795568

    RSP: 0x00007000000801c8, RBP: 0x0000700000080250, RSI: 0x0000000000000265, RDI: 0x00007fff6779c5f8

    R8:  0x0000000000000000, R9:  0x00007000000805c0, R10: 0x0000700000080b01, R11: 0x0000000103613170

    R12: 0x0000000000000000, R13: 0x000000010401f340, R14: 0x0000000000000265, R15: 0x0000000000000000

    RFL: 0x0000000000010202, RIP: 0x00007fff5fc1168a, CS:  0x000000000000002b, SS:  0x0000000000000023

     

     

    Thread 0: 0xffffff80167de000

      0x00007fff8a373d85

      0x0000000000000000

     

     

    Thread 1: 0xffffff80168476d0

      0x00007fff8a3827b4

      0x0000000000000000

     

     

    Thread 2: 0xffffff8016847240

       Could not read LR from frame at 0x000070000021cd48

     

     

    Thread 3: 0xffffff801828d920

      0x00007fff8a37e674

      0x00007fff8a372a3b

      0x00007fff8a3731b8

      0x00007fff8a3796bf

      0x00007fff8a371d0b

      0x00007fff8a371ab8

      0x00007fff968fa4f2

      0x00007fff968f8375

      0x0000000000000000

     

     

    Thread 4: 0xffffff801b81f6d0

      0x00007fff67761063

      0x00007fff92230262

      0x0000000103613170

      0x00007fff85b6f52a

      0x0000000000000000

      0x00007fff8a372a3b

      0x00007fff8a3731b8

      0x00007fff8a3796bf

      0x00007fff8a371d0b

      0x00007fff8a371ab8

      0x00007fff968fa4f2

      0x00007fff968f8375

      0x0000000000000000

     

     

    Thread 5: 0xffffff801afa46d0

      0x00007fff85b701f3

      0x00007fff85b700af

      0x00000001035fe4bd

      0x00007fff8a386324

      0x00007fff8a36e3c3

      0x00007fff8a372ff3

      0x00007fff8a3796bf

      0x00007fff8a371d0b

      0x00007fff8a371ab8

      0x00007fff968fa4f2

      0x00007fff968f8375

      0x0000000000000000

     

     

    Mac OS version: 15B42

    Kernel version: Darwin Kernel Version 15.0.0: Sat Sep 19 15:53:46 PDT 2015; root:xnu-3247.10.11~1/RELEASE_X86_64

    Kernel UUID: AB5FC1B4-12E7-311E-8E6F-9023985D8C1D

    System model name: Macmini6,1 (Mac-031AEE4D24BFF0B1)

    Model: Macmini6,1, BootROM MM61.0106.B0A, 2 processors, Intel Core i5, 2,5 GHz, 4 GB, SMC 2.7f0

    Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In

    Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333235533643465238432D50422020

    Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333235533643465238432D50422020

    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x10E), Broadcom BCM43xx 1.0 (7.21.94.29.1a4)

    Bluetooth: Version 4.4.2f1 16391, 3 services, 27 devices, 1 incoming serial ports

    Network Service: Ethernet, Ethernet, en0

    Network Service: Wi-Fi, AirPort, en1

    Serial ATA Device: Samsung SSD 840 EVO 250GB, 250,06 GB

    Serial ATA Device: ST2000LM003 HN-M201RAD, 2 TB

    USB Device: USB 2.0 Bus

    USB Device: Hub

    USB Device: Hub

    USB Device: IR Receiver

    USB Device: BRCM20702 Hub

    USB Device: Bluetooth USB Host Controller

    USB Device: USB 2.0 Bus

    USB Device: Hub

    USB Device: USB 3.0 Bus

    USB Device: My Book 1130

    USB Device: My Passport 0748

    Thunderbolt Bus: Mac mini, Apple Inc., 23.4

  • by Linc Davis,

    Linc Davis Linc Davis Oct 29, 2015 5:53 AM in response to D3rR4lf
    Level 10 (208,037 points)
    Applications
    Oct 29, 2015 5:53 AM in response to D3rR4lf

    If the panics happen only when one particular external drive is connected, I suggest you first test the drive with another USB cable, and if there's no change, replace the drive.

  • by D3rR4lf,

    D3rR4lf D3rR4lf Oct 31, 2015 1:43 AM in response to Linc Davis
    Level 1 (0 points)
    Oct 31, 2015 1:43 AM in response to Linc Davis

    No, the panic happens, with all encrypted drives. But only with my system which has 10.11.1.

    My other macs are still on 10.11.0 and there the drives work like a charm.

     

    I went back with Time Machine to 10.11.0 on my mac mini now, and everything is working stable .

     

    I am using OS X since 10.5 and this was the first time I had to use Time Machine to revert to an older version.

    OS X isn't as reliable as it used to be...

     

    I will try again, when 10.11.2 comes out.

  • by Muzzypat,

    Muzzypat Muzzypat Nov 2, 2015 10:02 AM in response to D3rR4lf
    Level 1 (10 points)
    Nov 2, 2015 10:02 AM in response to D3rR4lf

    This "update" totally crashed my Mac. Called AppleCare support, we tried about six attempts to get the CPU to respond and "nothing". So now I have an appointment with Memphis Apple Store on Saturday. That's a four hour drive. There needs to be 1.) and Apple store here in Mountain Home, AR and Apple needs to pull this "update". It's bad.

  • by D3rR4lf,

    D3rR4lf D3rR4lf Nov 5, 2015 2:14 PM in response to D3rR4lf
    Level 1 (0 points)
    Nov 5, 2015 2:14 PM in response to D3rR4lf

    sorry, wrong conclusion.

    It turned out that the hard drive of my fusion drive stopped working after writing couple of GB on it, which crashed the system.

     

    Not El capitans fault.

    Only strange that the hard drive failure happened at the moment the upgrade was installed.

    But thats life