OWC's Aura SSDs Not Working With macOS High Sierra, Fix Coming Soon

Discussion in 'Mac Blog Discussion' started by MacRumors, Sep 26, 2017.

  1. fairuz macrumors 68000

    fairuz

    Joined:
    Aug 27, 2017
    Location:
    San Jose and Berkeley, CA
    #26
    Ugh. I'm done with hardware RAID, especially when consumer-grade. It always looks great until something inevitably goes wrong that can't be fixed.
     
  2. dannyyankou macrumors 604

    dannyyankou

    Joined:
    Mar 2, 2012
    #27
    Oh, didn’t know that. Another reason I’m still spoiled with my 2012 MBP :D
     
  3. rtdunham macrumors 6502a

    rtdunham

    Joined:
    Jun 21, 2003
    Location:
    St. Petersburg, FL, Northern KY
    #28
    Ditto.
     
  4. macs4nw macrumors 601

    macs4nw

    #29
    This is a bit of an unexpected stain on an otherwise great Apple-centric business. Had they developed and released the planned new firmware in a timely fashion, this could have been totally prevented.
     
  5. iLilana macrumors 6502a

    iLilana

    Joined:
    May 5, 2003
    Location:
    Alberta, Canada
    #30
    just an FYI Transcend 512 ssd working just fine in my in my 2012 macbook air
     
  6. Pike R. Alpha, Sep 27, 2017
    Last edited: Sep 27, 2017

    Pike R. Alpha macrumors 6502

    Pike R. Alpha

    Joined:
    Oct 4, 2015
    Location:
    Spain
    #31
    Why OWC need Apple to resolve this is a mystery to me.

    Tip: simply repack the latest FirmwareUpdate.pkg that comes with macOS High Sierra as a stand alone installer and run it. That's how easy it is.

    FirmwareUpdateStandAlone-1.0.pkg

    md5 = 24a1731b514c633c7aff07b5d739828c

    You can make it yourself by running:

    ./installSeed.py -a update -f FirmwareUpdate.pkg -t / -u /tmp/FirmwareUpdate

    ./munkipkg.py --create /tmp/FirmwareUpdateStandalone

    cp /tmp/FirmwareUpdate/Scripts/postinstall_actions/update /tmp/FirmwareUpdateStandalone/scripts/postinstall

    cp -R /tmp/FirmwareUpdate/Scripts/Tools /tmp/FirmwareUpdateStandalone/scripts/

    ./munkipkg.py /tmp/FirmwareUpdateStandalone

    Used scripts:

    https://github.com/Piker-Alpha/HandyScripts/blob/master/installSeed.py
    https://github.com/munki/munki-pkg/blob/master/munkipkg
     
  7. Jody Hewell macrumors newbie

    Jody Hewell

    Joined:
    Jun 2, 2015
    Location:
    South Florida
    #32
    Thanks for clearing that up. There are lots of posts here that reflect unknowledgeable opinions.
     
  8. deley macrumors newbie

    deley

    Joined:
    Sep 27, 2017
    Location:
    London
    #33
    I tried this on a Mac Pro 6,1 and it didn't help.
     
  9. Chazzle macrumors 68000

    Chazzle

    Joined:
    Jul 17, 2015
    #34
    And you needed someone else’s post to educate you to deem them unknowledgeable.
     
  10. Glassed Silver macrumors 68020

    Glassed Silver

    Joined:
    Mar 10, 2007
    Location:
    Kassel, Germany
    #35
    They have technology to get 1TB of capacity out of 4 modules of 256 MB each?

    Well, this whole issue shall be forgotten then, let me get their magic controller whilst I go on a NAND shopping spree to replace some HDDs then...

    Glassed Silver:mac
     
  11. Weaselboy Moderator

    Weaselboy

    Staff Member

    Joined:
    Jan 23, 2005
    Location:
    California
    #36
    LOL... Glad you spotted that typo, because I linked to the wrong site. That quote (typo and all still there) is from the site SSDREVIEW.

    Anandtech has similar info:

     
  12. Glassed Silver macrumors 68020

    Glassed Silver

    Joined:
    Mar 10, 2007
    Location:
    Kassel, Germany
    #37
    No TRIM or SMART?

    Yuck!

    You blew the magic away, what do I do now with the NAND lot I just bought? :p

    Glassed Silver:mac
     
  13. hobbes3113 macrumors regular

    hobbes3113

    Joined:
    Oct 18, 2002
    Location:
    NYC
    #38
    Has anyone figured out a way to get this to work on the MP 6,1? I was pulling out my hair yesterday until I figured out what was happening...
     
  14. Pike R. Alpha macrumors 6502

    Pike R. Alpha

    Joined:
    Oct 4, 2015
    Location:
    Spain
    #39
    Please clarify. What didn't work? The installation of that package, or one self made, failed to install, or what?

    Did you check: /var/log/install.log for errors?
     
  15. deley, Sep 27, 2017
    Last edited by a moderator: Sep 27, 2017

    deley macrumors newbie

    deley

    Joined:
    Sep 27, 2017
    Location:
    London
    #40
    I ran this from the installer at first, it completed happily, but the 'firmware error' appeared again when I tried to install HS.

    This time I've extracted your installer into the cpio archive and have run the commands by hand. Note the final failure now. Any idea what this means? This is a 10.12 machine (MP 6,1)

    Code:
    19:37 mp01:~/Downloads/fw[] % sudo /usr/libexec/FirmwareUpdateLauncher -p Tools
    2017-09-27 19:37:08.354 FirmwareUpdateLauncher[4540:150074] Checking for MultiUpdater at Tools/MultiUpdater/MultiUpdater.efi
    2017-09-27 19:37:08.356 FirmwareUpdateLauncher[4540:150074] Running /usr/libexec/smcupdater (
        "-p",
        "Tools/SMCPayloads",
        "-s"
    )
    2017-09-27 19:37:08.362 smcupdater[4541:150078] path: Tools/SMCPayloads/Mac-F60DEB81FF30ACF6
    2017-09-27 19:37:08.363 smcupdater[4541:150078] SMC REV  Current version: 2.20f18
    2017-09-27 19:37:08.363 smcupdater[4541:150078] SMC REV  New     version: 2.20f18
    2017-09-27 19:37:08.363 smcupdater[4541:150078] No reason to update Tools/SMCPayloads/Mac-F60DEB81FF30ACF6/Mac-F60DEB81FF30ACF6.smc.
    2017-09-27 19:37:08.371 smcupdater[4541:150078] SMC RVBF Current version: 2.20f18
    2017-09-27 19:37:08.371 smcupdater[4541:150078] SMC RVBF New     version: 2.20f18
    2017-09-27 19:37:08.371 smcupdater[4541:150078] No reason to update Tools/SMCPayloads/Mac-F60DEB81FF30ACF6/flasher_base.smc.
    2017-09-27 19:37:08.380 smcupdater[4541:150078] SMC RVUF Current version: 2.20f18
    2017-09-27 19:37:08.380 smcupdater[4541:150078] SMC RVUF New     version: 2.20f18
    2017-09-27 19:37:08.380 smcupdater[4541:150078] No reason to update Tools/SMCPayloads/Mac-F60DEB81FF30ACF6/flasher_update.smc.
    Nothing to update.
    2017-09-27 19:37:08.444 FirmwareUpdateLauncher[4540:150074] smcupdater exited with status: 1
    2017-09-27 19:37:08.444 FirmwareUpdateLauncher[4540:150074] Running /usr/libexec/ssdupdater (
        "-p",
        Tools,
        "-s"
    )
    2017-09-27 19:37:08.514 FirmwareUpdateLauncher[4540:150074] ssdupdater exited with status: 255
    2017-09-27 19:37:08.514 FirmwareUpdateLauncher[4540:150074] Running /usr/libexec/usbcupdater (
        "-p",
        Tools,
        "-s"
    )
    2017-09-27 19:37:08.521 usbcupdater[4544:150092] Error reading plist: No files to support boardID: Mac-F60DEB81FF30ACF6
    2017-09-27 19:37:08.589 FirmwareUpdateLauncher[4540:150074] usbcupdater exited with status: 13
    19:37 mp01:~/Downloads/fw[] % sudo /usr/libexec/efiupdater -p Tools/EFIPayloads
    Raw EFI Version string: MP61.88Z.0116.B46.1706200309
    EFI currentVersion: [0000000001160046]
    EFI updateVersion:  [0000000001200000]
    EFI found at IODeviceTree:/efi
    Will need to copy 8523776 bytes to EFI system partition
    GPT detected
    No auxiliary booter partition required
    System partition found
    Returning booter information dictionary:
    <CFBasicHash 0x7ff6d1503330 [0x7fffaecb0da0]>{type = mutable dict, count = 3,
    entries =>
        0 : <CFString 0x106a76a60 [0x7fffaecb0da0]>{contents = "System Partitions"} = (
        disk0s1
    )
        1 : <CFString 0x106a77240 [0x7fffaecb0da0]>{contents = "Data Partitions"} = (
        disk0s2
    )
        2 : <CFString 0x106a77260 [0x7fffaecb0da0]>{contents = "Auxiliary Partitions"} = (
    )
    }
    
    ESP disk0s1 is not accessible as a recovery device
    Error while writing firmware updater for EFI
    
    19:37 mp01:~/Downloads/fw[] % sudo gpt -r show disk0
           start        size  index  contents
               0           1         PMBR
               1           1         Pri GPT header
               2          32         Pri GPT table
              34           6
              40      409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
          409640  3748477584      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
      3748887224     1269536      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
      3750156760           7
      3750156767          32         Sec GPT table
      3750156799           1         Sec GPT header
     
  16. Pike R. Alpha macrumors 6502

    Pike R. Alpha

    Joined:
    Oct 4, 2015
    Location:
    Spain
    #41
    The upgrade failed somehow, because it's still reporting an older version:

    EFI currentVersion: [0000000001160046]

    This is why you get the firmware error. Did you mount the volume before firing up:

    sudo /usr/libexec/efiupdater -p Tools/EFIPayloads

    By the way. I used:

    sudo /usr/libexec/efiupdater -p /tmp/FirmwareUpdate/Scripts/Tools/EFIPayloads

    Which failed with:

    Raw EFI Version string: IM191.88Z.0058.B00.1708081711
    EFI currentVersion: [0000000000580000]
    EFI updateVersion: [0000000000000000]

    Simply because there is no EFI update for it.
     
  17. deley macrumors newbie

    deley

    Joined:
    Sep 27, 2017
    Location:
    London
    #42
    Mount which volume, sorry? I am running it on HFS+ 10.12 on the root partition. Same disk etc.
     
  18. grundoon, Sep 27, 2017
    Last edited: Sep 27, 2017

    grundoon macrumors member

    grundoon

    Joined:
    Feb 2, 2013
    #43
    Same APFS conversion failure on an OWC Mercury Electra 6G (250GB, in a Mac mini) here, left unbootable.

    First thing I did was check the drive firmware version... it was not current, so jumped through the hoops to update that, and formatted fresh. A fresh High Sierra install went fine from there.

    (While not thrilled that I also needed to spend time recovering from backup, this is precisely why I hang a USB drive off every desktop and run a full bootable SuperDuper image to it nightly. Boot from external, fix internal, re-download installer and let Migration Assistant do its thing.)
     
  19. Pike R. Alpha macrumors 6502

    Pike R. Alpha

    Joined:
    Oct 4, 2015
    Location:
    Spain
    #44
    Look here: "Will need to copy 8523776 bytes to EFI system partition". That copy won't be done without the EFI partition being mounted.
    --- Post Merged, Sep 28, 2017 ---
    You don't necessarily need to use APFS.

    1.) Tun the installer (this creates the: /macOS Install Data/ folder).
    2.) Reboot.
    3.) Do not select the volume/drive with the /macOS Instal Data directory on it. Boot from another boot volume.
    4.) Download and run sudo checkAPFSSettings.sh (changes the APFS conversion settings) twice.
    5.) Reboot.
    6.) Let the installation process proceed.

    No. Now you won't have APFS, but that is highly overrated. The gains are very limited. Despite what Apple want us to believe. And when you want, the APFS conversion can always be done at a later time.
     
  20. deley macrumors newbie

    deley

    Joined:
    Sep 27, 2017
    Location:
    London
    #45
    That's a shame, it doesn't work with /dev/disk0s1 on /Volumes/EFI (msdos, local, nodev, nosuid, noowners) mounted either.

    ESP disk0s1 is not accessible as a recovery device

    I wonder if recreating it the hard way will work.
     
  21. deley macrumors newbie

    deley

    Joined:
    Sep 27, 2017
    Location:
    London
    #46
    OK I've gotten somewhere. I installed on the original SSD put back into the MP6,1: then was able to install on the OWC 2TB after moving the original SSD out again.

    The disk was not converted to APFS as OSX doesn't think it's an SSD. So MP 6,1 with OWC can do 10.13 with HFS+.
     
  22. code4fun macrumors newbie

    Joined:
    Jun 9, 2008
    #47
    Same here. I purchased the 1 TB version for my MacBook Air 2012 because I was living outside the US. The first two were the non pro versions and failed after 3 months of use. So, I purchased a Pro version thinking that would make a difference. It also failed after 3 months. I now have 3 non-functional SSDs. The MacBook Air will not recognize the SSD part. I put the original factory SSD back in the MacBook Air so I can still use it.

    Bad investment. Use to love OWC products, but not after this experience.
     
  23. axp4654 macrumors newbie

    Joined:
    Sep 14, 2016
    #48
    I don't understand what difference putting original SSD makes? You remove it anyways after. Is it maybe that you're doing fresh install after vs upgrade?
     
  24. elguille macrumors member

    elguille

    Joined:
    Jun 13, 2006
    Location:
    Venezuela & Spain
    #49
    I'm already using High Sierra on a OWC Aura SSD but I've not been able to convert the file system from HFS+ to APFS, I need that in order to use Time Machine because the HD in my Time capsule is formatted in APFS.

    You say that the conversion can be done at a later time but right now this is not possible or maybe I don't know how to do it.


    Any advice?

    Thanks
     
  25. Artstar, Oct 3, 2017
    Last edited: Oct 3, 2017

    Artstar macrumors newbie

    Joined:
    May 20, 2009
    #50
    In my case, I can see in the EFI partition that the firmware is loaded up in there, ready to go. It's just that upon boot-up, it's possibly not seeing that partition and loading the firmware. Unless you know of a way I can force this Mac to see my EFI partition upon boot up, I'm out of ideas (as is Dr. Google, it seems).

    EDIT: Also tried cloning the EFI partition to a USB drive. It booted but then ceased to continue past the BIOS screen, claiming it was a non-system disk. Oh well. I'll just have to wait and see for now.
     

Share This Page