SSD Unrepairable in Mojave

Discussion in 'macOS Mojave (10.14)' started by Mac Hammer Fan, Apr 26, 2019.

  1. Mac Hammer Fan, Apr 26, 2019
    Last edited: Apr 26, 2019

    Mac Hammer Fan macrumors 6502a

    Mac Hammer Fan

    Joined:
    Jul 13, 2004
    Location:
    Belgium
    #1
    I updated my MacPro 5,1 with firmware 141.0.0.0.0 from High Sierra 10.13.6 to Mojave 10.14.4 a few days ago. My Samsung EVO 850 SSD installed in an OWC SATA PCI card was converted from HFS+ to APFS. After a few days I have disk problems.
    When I ran disk utilty I got this message:
    warning: inode_val: object (oid0X111a3) invalid internal-flags (a lot of these)
    too many warnings generated: suppressing subsequent ones
    I tried to repair in the recovery mode but was unable to unmount the startup SSD.
    The I booted from another SSD under High Sierra and tried to repair with Disk Utility and Drive Genius.
    But the warnings remained and I couldn't repair the disk.
    Now, when I try to boot the Samsung SSD with Mojave, I got a white screen and nothing more.
    I restarted in the safe boot mode and then I could login. After this I restarted normally.
    TRIM is enabled.
    Drive Genius reports: warning: inode_val: object (oid0xd8486): invalid internal_flags (0x28000)...
    OneDrive is not installed.
    What can I do to solve this problem?
    TIA
     
  2. Mac Hammer Fan thread starter macrumors 6502a

    Mac Hammer Fan

    Joined:
    Jul 13, 2004
    Location:
    Belgium
    #2
    Update: although I get the warnings, I also get this message:The volume /dev/rdisk5s1 appears to be OK.
     
  3. Lee_Bo macrumors regular

    Lee_Bo

    Joined:
    Mar 26, 2017
    Location:
    Greenville, SC
    #3
    Any change of removing APFS? I was having quite a lot of beach balls after my MacBook Pro updated. Removed APFS and those beach balls went away.

    Just a shot in the dark.
     
  4. Mac Hammer Fan thread starter macrumors 6502a

    Mac Hammer Fan

    Joined:
    Jul 13, 2004
    Location:
    Belgium
    #4
    Mojave requires APFS for updates.
     
  5. Mac Hammer Fan, Apr 26, 2019
    Last edited: Apr 26, 2019

    Mac Hammer Fan thread starter macrumors 6502a

    Mac Hammer Fan

    Joined:
    Jul 13, 2004
    Location:
    Belgium
    #5
    update: I ran Drive Genius Consistency Check from the Mojave boot volume and the warnings disappeared. :)
     
  6. haralds macrumors 6502a

    haralds

    Joined:
    Jan 3, 2014
    Location:
    Silicon Valley, CA
    #6
    I have had an APFS corruption that could not be repaired and had to wipe the disk.
     
  7. Lee_Bo macrumors regular

    Lee_Bo

    Joined:
    Mar 26, 2017
    Location:
    Greenville, SC
    #7
    Sigh......getting old sucks.

    FileVault is what I was thinking. When my MBP updated to Mojave I enabled FileVault. Lots of beach balls after that.
     
  8. jbarley macrumors 68040

    jbarley

    Joined:
    Jul 1, 2006
    Location:
    Vancouver Island
    #8
    And you know this because....?
    Coming from an 82 yr old happily running Mojave on both supported and unsupported Classic Mac Pros.:p
     
  9. Honza1 macrumors 6502

    Joined:
    Nov 30, 2013
    Location:
    US
    #9
    Not sure what this statement is trying to state... But I'd like to point out, that I had many more HFS+ disks become corrupted and required complete wipe. Now, true, APFS has been around shorter time. But up to now the one corruption of the APFS disk I had was easily repaired by Disk tools. And it was fixed live, Disk tools started from that same disk. That was impossible with HFS+ disks.
    All disks fail, all formats will get corrupted. Data backup is the key to survival. Storage is amazingly cheap today.
     
  10. Mac Hammer Fan thread starter macrumors 6502a

    Mac Hammer Fan

    Joined:
    Jul 13, 2004
    Location:
    Belgium
    #10
    Luckily, my problem is solved with Drive Genius Consistency Check. One snapshot was deleted and the warnings went away.
     
  11. Fishrrman macrumors P6

    Fishrrman

    Joined:
    Feb 20, 2009
    #11
    Mac Hammer wrote:
    "Mojave requires APFS for updates."


    This is true... BUT...

    You can STILL run HFS+ if you want.
    Yes, you'll have to keep an APFS drive with a copy of the OS on it for updates, but the update issue can be "worked around". I've done it.

    I'm typing on my 2018 Mac Mini, which has the INTERNAL drive formatted to HFS+ and Mojave runs fine on it. In fact, I've had no problems at all (having expected to see some after reading all the posts here).

    This Mini will ALWAYS have the internal drive at HFS+ ... ;)
     
  12. Mac Hammer Fan thread starter macrumors 6502a

    Mac Hammer Fan

    Joined:
    Jul 13, 2004
    Location:
    Belgium
    #12
    Unfortunately I had a crash in Mojave again. The computer completely froze. And now I have the warnings of inode_val: object (oid0X111a3) invalid internal-flags again and if I try to repair it with Drive Genius the computer hangs. Therefore the problem isn't solved. And APFS seems to be the culprit.
     
  13. Honza1 macrumors 6502

    Joined:
    Nov 30, 2013
    Location:
    US
    #13
    Hm, or (more likely) computer has developed a problem, crashes OS, and APFS integrity becomes victim of the crash. Difficult to prove.
    May be get different system drive, install Mojave with HFS+ on it, and if that works, then you can point finger on APFS - or more likely that specific disk (hardware). If this was common APFS problem on this Mac Pro, search through the https://forums.macrumors.com/threads/mp5-1-what-you-have-to-do-to-upgrade-to-mojave.2142418/ would show at least some reports about this. If this was wide spread, there would be warning in there already. You seem to have unique problem.
     
  14. treekram macrumors 68000

    Joined:
    Nov 9, 2015
    Location:
    Honolulu HI
    #14
  15. davidlv, Apr 27, 2019
    Last edited: Apr 28, 2019

    davidlv macrumors 65816

    Joined:
    Apr 5, 2009
    Location:
    Kyoto, Japan
    #15
    1. To the OP: You might consider renaming this thread to "APFS / OWC Accelsior S PCI card issue" or something like that, to make the issue clearer.
    2. After seeing that blog mentioned by Treekram in post #14, I am afraid to update my 2009 Mac Pro running on an OWC Accelsior S PCI card with a Crucial MX500 SSD! Now it is working fine running 10.3.6 with an MSI RX560 and Bootrom 1.4.1.0.0.0. So as mentioned above, I may later try temporarily removing the OWC PCI card, install Mojave on an SSD in the SATA II bay #1, and then reinstall the High Sierra SSD in the OWC Accelsior S PCI card and use that untill there are no more security updates for HS.
     
  16. TonyK macrumors 65816

    TonyK

    Joined:
    May 24, 2009
    #16
    As others have said, I would suspect a hardware compatibility issue. If this were a general APFS issue we'd see a lot more noise.

    @Fishrrman, how does one reformat and install 10.14.4 on HFS+?
     
  17. Fishrrman macrumors P6

    Fishrrman

    Joined:
    Feb 20, 2009
    #17
    TonyK asked:
    "Fishrrman, how does one reformat and install 10.14.4 on HFS+?"

    Somewhere in the forum, I put up a "how to" on how I did it.

    Without a long writeup, here are the general steps:
    1. The very first time you boot the new Mac, set up a basic account, but migrate NOTHING to it. Just a username and password, that's all. I suggest creating THREE basic accounts with administrative privileges (temp501, temp502, temp503).
    2. Now boot to the recovery partition.
    3. DISABLE SIP
    4. Open Startup Security and DISABLE all t2 functions (as much as they can be disabled)
    5. Boot back to regular boot partition into the temp503 account.
    6. Get TWO external drives
    7. Format one drive to HFS+
    8. Format the OTHER drive to APFS.
    9. Use either CarbonCopyCloner or SuperDuper (I recommend CCC)
    10. Use CCC to clone internal drive to APFS drive. Set aside for future use.
    11. Use CCC to clone internal drive to HFS+ drive and create recovery partition.
    12. Now, boot from the HFS+ drive
    13. ERASE the internal drive to Mac OS extended with journaling enabled, GUID partition format.
    14. Now, RE-clone the contents of the HFS+ backup BACK TO the internal drive. CCC will again re-create a recovery partition on it, as well.
    15. Now, RE-BOOT to the internal drive, to the temp503 account.
    16. Go to system preference and DELETE the temp501 account.
    17. Use migration assistant to migrate your primary account from a cloned backup (I have no idea if Time Machine will work, I have NEVER used TM and DO NOT recommend it). The account will "fall into" the "501 user ID" (because you removed the prior "placeholder" account with that ID).
    18. Log out of temp503 and into your regular account.
    19. Done.
     
  18. naerct macrumors member

    naerct

    Joined:
    Mar 19, 2019
    Location:
    Southern NH
    #18
    I lost my Accelsior S when I upgraded to Mojave in my 8-core. There is a hardware compatibility problem that I discovered earlier with another PCIe card. Mojave tells you it's incompatible hardware. However, I now have it working again in my 4-core with High Sierra 13.6. Because the Accelsiors are a striped Raid, they have problems becoming APFS, and will not work as the Mojave boot drive. However, with the RAID in HFS+, it works fine. The same thing is true with RAIDs in Mojave. They only work if they are in HFS+, and are the same with either the Apple RAID0 or the SoftRaid RAID0. I don't believe that Accelsior S will ever work in Mojave or beyond. Both my 4-core and my 12-core (upgraded from 8-core to 3.33 hex core) are booting from NVMe drives with the 140 BootROM flash prior to 10.14 upgrade. You might need an APFS disk and no presence of a non-Metal video card to upgrade to Mojave, but Mojave will run from a HSF+ RAID on the original GT 120 card by itself... Really. Just don't ever try to use the NVMe Samsung 970 EVO PLUS. I had more kernel panics in the two weeks I tried to get it to work, then in the 10 years of ownership. Also, get the blog linked above. That has been my bible since the blogger revealed the EVO+ problems. I found an older EVO and everything worked well. The 970 PRO also works. This blog is also where I found that my PCI card didn't have a recommended heat sink. I had both a 960 and 970 with separate sinkless cards. Mr Greggant also recommended the Syba switch card as a reasonably priced alternative to two separate cards, and it gives the drives their full speed if in an X16 slot (#2). The card is really an enclosure for 2 NVMe blades with a heat sink and a fan. With the 970, my reads hovered just below 3GHz/s. The 960 is a about 10% slower. A bit off topic, but for those trying to keep their cMPs running, get that blog and print it out and read it before making any purchases. I keep the PDF on my desktop. I bought a 10 series Nvidia video card, but it still doesn't work in Mojave and may never. As much as I like CUDA, I had to switch over to AMD, and got the RX580 with 8GB VRAM FOR UNDER $200, unless you'd rather pay over $300 at a Mac Sales site. Neither card has the MacOS EFI. Make sure you keep your original video card as the Mac EFI may be necessary for further upgrades, especially BootROM flashes. Lastly, DO NOT TRY TO FLASH A SINGLE PROCESSOR cMP past 10.14.3, as that has been bricking those units. 14.3 works fine on my 4-core, but better on HS where it will stay.
     
  19. Mac Hammer Fan thread starter macrumors 6502a

    Mac Hammer Fan

    Joined:
    Jul 13, 2004
    Location:
    Belgium
    #19
    My Accelsior is this one: a SATA 6G with a Samsung EVO 850 SSD formatted APFS (Mojave 10.14.4)
    https://eshop.macsales.com/item/OWC/SSDACL6G.S/
    On my second MacPro, I have an Accelsior striped Raid where I boot under High Sierra HFS+
     
  20. naerct macrumors member

    naerct

    Joined:
    Mar 19, 2019
    Location:
    Southern NH
    #20
    I didn't know that yours came without a drive. I just assumed that, since the new ones were called S2, that the original ones without the eSATA ports were the S model. Originally, the Accelsior had two RAIDed SATA blades, not a mounting plate for a 2.5" SATA drive. Since you drive is not RAIDed blades, you shouldn't have any problems using it as an APFS boot drive in Mojave. The unit I use now is a full length card by Sonnet with room for two, 2.5" SATA drives on the card. It is also SATA III and has two eSATA ports for external SATA drives. I have 2 SSDs on the card. If I use them as individual drives they are fine for APFS and will boot in Mojave. If I put them in a RAID0, I have to format them as HFS+ since the new file system doesn't work with RAIDs, at least not yet. I just clone the RAID from another copy of my system boot drive. It works fine and it nearly doubles throughput (1GB/s), while doubling the chance of failure. Since I don't keep data on the boot drives and have at least 2 clones, the risk is not a factor. The card you bought just makes it connect to the PCI bus where SATA3 speeds are double over the internal SATA2 ports, otherwise your SSD could not go past the 300MB/s limit. But the only way to RAID that drive would be to have at least two of them. That's a real waste of PCI slots when you can buy the Samsung NVMe blades and get much faster speeds than any SATA drive. The 970 EVO in a classic Mac Pro gets reads around 1500MB/s, 5 times faster than a single SATA SSD. Or you can get the switch I mentioned and have room for 2 blades that are twice as fast without a RAID. (3GB/s reads) If you are interested, please consult that blog, as Mr Greggant's information is the best collection of information about the cMPs I've ever seen over 10 years of ownership. Not to mention his level of knowledge and experience. I was so impressed, I even thought about upgrading my Bluetooth and WIFI on a strictly work machine and my connection is Ethernet... too many other Mac or iOS devices for that stuff to be needed on my workhorse. Just remember not to purchase the 970 EVO PLUS, as it does not work. SATA does have a couple advantages over NVMe. It seems to be more responsive as a boot drive, and the SATA RAID does take 10 or 15 seconds off the boot time. After the boot, it's NVM2 blowing the SATA away. Those drives were verboten before Sierra, and to boot from them you need to run the flash prior to upgrading to Mojave. Boot ROM needs to be 140 or later to boot NVMe. Check it out on the second page of System reports (Boot ROM Version: ) Good Luck.
     
  21. Mac Hammer Fan thread starter macrumors 6502a

    Mac Hammer Fan

    Joined:
    Jul 13, 2004
    Location:
    Belgium
    #21
  22. Mac Hammer Fan thread starter macrumors 6502a

    Mac Hammer Fan

    Joined:
    Jul 13, 2004
    Location:
    Belgium
    #22
    I contacted OWC and they told me The Accelsior S PCI SATA 3 should be compatible with APFS. They gave the advice to reformat the drive.
     
  23. jbarley macrumors 68040

    jbarley

    Joined:
    Jul 1, 2006
    Location:
    Vancouver Island
    #23
    If this is the unit in question, if so yes it works with APFS.
    I'm running that card right now with a 500GB SanDisk SSD on my MacPro 3,1 under Mojave 10.14.4.
    I've also used it in a MacPro 4,1/5,1 with success, which now is running an OWC Accelsior E2.

    Screen Shot 2019-04-29 at 8.50.39 AM.png
     
  24. davidlv, Apr 29, 2019
    Last edited: Apr 30, 2019

    davidlv macrumors 65816

    Joined:
    Apr 5, 2009
    Location:
    Kyoto, Japan
    #24
    Could you clarify that somewhat? I have 2 internal SSDs, one on the Mac Pro 3G SATA bus, and another SSD on an OWC Accelsior S PCI card. I want to keep one of the disks at HFS+. I know that I have to remove that disk temporarily when installing Mojave to keep it from being converted to APFS, but what about when updating the Mojave system, say from version 14.4 to 14.5? Will I have to temporarily disconnect the HFS+ disk?
     
  25. haralds macrumors 6502a

    haralds

    Joined:
    Jan 3, 2014
    Location:
    Silicon Valley, CA
    #25
    Had another corruption. This time it was on an external volume with multiple Containers used for CCC clones on a regular basis. It looks like the underlying HFS+ host container was corrupted. All volumes had errors that could not be repaired.
    Had to wipe and redo.
     

Share This Page

36 April 26, 2019