Catandcamera
Level 1 (4 points)
Desktops

Q: Help!!Upgraded to Sierra, now boots up to black screen with nothing on it.

My Mac Mini, bought as a brand new, late 2014 model, bought last year.

Iris graphic card, i7.

 

Was on Capitan before, and everything works perfect, never had any problem. Last night, I upgraded to Sierra, and then problem comes!  

 

The Mac will boot up to a black screen, a complete black screen with nothing on it. I can hear that normal startup sound after I pressed the power button, but nothing shows up. I also waited for quite a while on this black screen to see if anything will show up eventually, the result is No.

 

I Googled and tried the "Command+Alt+R+P" method, Yes, it works. Then I restart the Mac, it will come back without any problem. I also tried Sleep mode, it can wake up also without problem. And when the Mac is on, everything seems working well, no error, no warning, no strange things show up. All the softwares I use all work without issues.

 

The problem happens when I completely turn off the Mac and turn back on. I have to use that "Commend+Alt+R+P" method to turn the Mac on and even this method not working all the time. And when this method is not working, the screen stays on black screen forever.

 

Anyone has similar experiece?

Mac mini, null

Posted on Oct 3, 2016 6:20 PM

Close
Catandcamera

Q: Help!!Upgraded to Sierra, now boots up to black screen with nothing on it.

  • All replies
  • Helpful answers

  • by trevoz,

    trevoz trevoz Oct 3, 2016 6:33 PM in response to Catandcamera
    Level 4 (1,646 points)
    Mac OS X
    Oct 3, 2016 6:33 PM in response to Catandcamera

    Open a Terminal window and type/paste the following command:

     

    nvram -p | fgrep -i efi-boot-device

     

    and paste the result here.

     

    Also in a Terminal window, type/paste the following command:

     

    df

     

    and paste the result here.

  • by Catandcamera,

    Catandcamera Catandcamera Oct 3, 2016 6:49 PM in response to trevoz
    Level 1 (4 points)
    Desktops
    Oct 3, 2016 6:49 PM in response to trevoz

    The "nvram -p | fgrep -i efi-boot-device" returns nothing.

     

    The "df" returns:

    Filesystem    512-blocks      Used  Available Capacity iused      ifree %iused  Mounted on

    /dev/disk2    2176716032 223218216 1952985816    11%  794598 4294172681    0%   /

    devfs                369       369          0   100%     639          0  100%   /dev

    map -hosts             0         0          0   100%       0          0  100%   /net

    map auto_home          0         0          0   100%       0          0  100%   /home

  • by trevoz,

    trevoz trevoz Oct 3, 2016 7:01 PM in response to Catandcamera
    Level 4 (1,646 points)
    Mac OS X
    Oct 3, 2016 7:01 PM in response to Catandcamera

    Does:

     

    nvram -p

     

    return anything?

  • by Catandcamera,

    Catandcamera Catandcamera Oct 3, 2016 7:02 PM in response to trevoz
    Level 1 (4 points)
    Desktops
    Oct 3, 2016 7:02 PM in response to trevoz

    Yes.

     

    BootCampProcessorPstates %0c%00

    fmm-computer-name Cocoa%e2%80%99s Mac mini

    bluetoothActiveControllerInfo %89%82%ac%05%00%00%00%003%14%ac%bc2%ed%b3D

    SystemAudioVolumeDB %f6

    bluetoothInternalControllerInfo %89%82%ac%05%00%003%14%ac%bc2%ed%b3D

    SystemAudioVolume k

  • by trevoz,

    trevoz trevoz Oct 3, 2016 7:12 PM in response to Catandcamera
    Level 4 (1,646 points)
    Mac OS X
    Oct 3, 2016 7:12 PM in response to Catandcamera

    Hmmm. What's missing is the efi-boot-device variable.

     

    And looking back at your df output, what happened to disks 0 and 1? You are booting from "disk2" and that doesn't resemble a BSD slice (it's normally something like disk0s2 for the internal boot disk).

     

    In a terminal window, what is the output of:

     

    diskutil list

  • by Catandcamera,

    Catandcamera Catandcamera Oct 3, 2016 7:18 PM in response to trevoz
    Level 1 (4 points)
    Desktops
    Oct 3, 2016 7:18 PM in response to trevoz

    I really don't know what happened. All I do is the normal upgrade process, really cannot do anything else.

     

    Here is the output:

     

    /dev/disk0 (internal, physical):

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *121.3 GB   disk0

       1:                        EFI EFI                     209.7 MB   disk0s1

       2:          Apple_CoreStorage Macintosh HD            121.0 GB   disk0s2

       3:                 Apple_Boot Boot OS X               134.2 MB   disk0s3

     

    /dev/disk1 (internal, physical):

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:      GUID_partition_scheme                        *1.0 TB     disk1

       1:                        EFI EFI                     209.7 MB   disk1s1

       2:          Apple_CoreStorage Macintosh HD            999.3 GB   disk1s2

       3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3

     

    /dev/disk2 (internal, virtual):

       #:                       TYPE NAME                    SIZE       IDENTIFIER

       0:                            Macintosh HD           +1.1 TB     disk2

                                     Logical Volume on disk0s2, disk1s2

                                     3734FA3A-C0FC-41CB-9F87-B8E3BDDC146E

                                     Unencrypted Fusion Drive

  • by trevoz,

    trevoz trevoz Oct 3, 2016 7:41 PM in response to Catandcamera
    Level 4 (1,646 points)
    Mac OS X
    Oct 3, 2016 7:41 PM in response to Catandcamera

    Ah, ok, it's a fusion drive. That explains the mysterious disk2 - I was wondering how you got three disks into a Mac Mini

     

    Unfortunately I'm not familiar with the fusion drive boot process as I kept the SSD in my Mac Mini separate.

     

    If you got to Preferences > Startup Disk and select it, then reboot, does it boot?

  • by Catandcamera,

    Catandcamera Catandcamera Oct 3, 2016 7:45 PM in response to trevoz
    Level 1 (4 points)
    Desktops
    Oct 3, 2016 7:45 PM in response to trevoz

    It is okay. I will go to Apple store tomorrow to have them fix it. I already made my appointment.

     

    I was trying to see if anyone here can help me out before I go because I really need this computer right now.

     

    I don't want to mess around the computer. I am not a computer person and don't want to damage my equipment too quickly.

     

    Thanks again and again for your help on this!

  • by trevoz,

    trevoz trevoz Oct 3, 2016 8:04 PM in response to Catandcamera
    Level 4 (1,646 points)
    Mac OS X
    Oct 3, 2016 8:04 PM in response to Catandcamera

    Not that I was much help. Do let us know what happens after your store visit.