macOS Mojave 10.14.4 Disk Utility Problem

Discussion in 'macOS Mojave (10.14)' started by dialogos, Mar 26, 2019.

  1. dialogos macrumors regular

    Joined:
    Sep 22, 2017
    #1
    I will describe the steps.

    1. Open disk utility, click on upper left side , select view -> Show all devices
    2. Run First Aid on Container Disk
    3. Run First Aid in the subdisk under container disk. If the first aid runs without a problem try to run it again. Eventually you will get a corruption error.

    At least this is my experience in different machines after the update.
     
  2. jbarley macrumors 68040

    jbarley

    Joined:
    Jul 1, 2006
    Location:
    Vancouver Island
    #2
    Works just fine for me.
    But then I normally just run it once to completion.
    In my experience if you screw with anything long enough, you can get it to break.:D
     
  3. dialogos thread starter macrumors regular

    Joined:
    Sep 22, 2017
    #3
    I mentioned it runs fine if I run it once. Could you try to run it second time? I assume you're clicking the first aid for the disk that is under the container right?
     
  4. jbarley macrumors 68040

    jbarley

    Joined:
    Jul 1, 2006
    Location:
    Vancouver Island
    #4
    Just for you, I ran it a 2nd and a 3rd and a 4th and 5th time, and all is still OK. But as I mentioned earlier maybe if I played long enough I could get it to fail.
    And yes I am running first aid on the disk that shows under the container, which BTW is the boot partition.
     
  5. dialogos, Mar 26, 2019
    Last edited: Mar 26, 2019

    dialogos thread starter macrumors regular

    Joined:
    Sep 22, 2017
    #5
    I don't know what to say. I tried it on a third machine and I get the same error. Anyway my computer works fine so I won't pay attention to it.

    By the way let me explain how I discovered it. I didn't play long enough with it. People here recommended in the past to run disk utility after an update. While running disk utility I wasn't sure if I had to run it on the container disk or the boot partition so I run it on both :) One after the other one :)
     
  6. benwiggy macrumors 68020

    Joined:
    Jun 15, 2012
    #6
    People recommended running "Repair Permissions" from Disk Utility after installing things more than 10 years ago, even though it wasn't really necessary.
    There's absolutely no need to run DU after installing an OS update. You can do it if you like, and at best, it will keep the elephants away from your Mac. (See? Still no elephants!)
     
  7. dialogos thread starter macrumors regular

    Joined:
    Sep 22, 2017
    #7
    Guys you're confusing me :):) it was something like a year ago that I was advised to run Disk Utility after updates. Before that I wouldn't even bother :)

    The thing is that now I have already run it, my computer runs fine but it bothers me that I get this weird message that my drive is corrupted. I get the same message on two imacs and one macbook. Do you believe I should ignore it?

    I tried to run my own experiment. I restarted my computer. Run Disk Utility on Boot Volume. Everything was fine. I run it on the container disk - everything was fine. I run it on Boot Volume again and I got the same error message.

    My understanding from what you're saying is I shouldn't bother so I leave it here. If you're advising not to run disk utility again I will simply follow the advise, no problem at all :)

    But if you wish try try run the process above in case there is a bug. People more experienced than me may I understand it better.
     
  8. benwiggy macrumors 68020

    Joined:
    Jun 15, 2012
    #8
    I'm saying you don't need to. Someone else may come up with a reason why it's a good idea, but I'd want details.

    It's possible the error messages themselves are the bug. There have been a number of bugs with DU in Mojave.
     
  9. dialogos thread starter macrumors regular

    Joined:
    Sep 22, 2017
    #9
    Thanks a lot!
     
  10. crjackson2134 macrumors 601

    crjackson2134

    Joined:
    Mar 6, 2013
    Location:
    Charlotte, NC
    #10
    I've got 4 SSD's, and 4 HHD's. I tried to recreate the problem you described on each drive (both APFS and HFS+). I could not duplicate your issue.

    Grab a scratch drive, wipe it clean (reformat it), then do a clean install (no app/data migrations). Then try again and report back.
     
  11. dialogos thread starter macrumors regular

    Joined:
    Sep 22, 2017
    #11
    Hello crjackson2134, first of all thanks for trying to replicate the problem. I wouldn't mind doing a clean install but it's time so time consuming and my machines work fine.

    As far as I know all my internal drives are APFS (this is the new format for ssd's right? ) Out of curiosity did you run the First Aid in Container disk first and then to the boot volume?

    I tried to run it on an external ssd disk which I have but I couldn't get the same error message. I get it only for my internal disk.

    To be honest I don't want to spend time especially with clean format. As long as you can't replicate I assume it's something from my side. Maybe the software I use in all of my computers? I don't have something special other than what I need for my work.

    Once again thanks a lot !
     
  12. Mac56 macrumors newbie

    Joined:
    Feb 22, 2015
    #12
    --- Post Merged, Mar 30, 2019 ---
    I have exactly the same problem, tried a fresh install of 14.4 with no additional software installed, only OS, the second run of First Aid on the boot disk gets the error, it only happens with the boot disk, reinstalled 14.2 via time machine and all is now ok. I called Apple support, on their request run and sent data to Apple, I am now waiting for a response from 2nd level support.
     
  13. Lenones macrumors newbie

    Joined:
    Apr 26, 2019
    #13
    Good afternoon. Please tell me how you solved the problem with the disk utility? I faced a similar problem on my MBP 2018. The motherboard and SSD were replaced, but it did not solve the problem. Can be you share your experience?
     
  14. Mac56 macrumors newbie

    Joined:
    Feb 22, 2015
    #14
    Hi, it's not solved, Apple support called to inform that they are aware of the issue and working on it and that there is no problem with iMac Pro. I have seen that the same error seems to be present in the Pro computers (tested on a couple of MacBook Pro) and not, for example, in the standard iMac.
     
  15. Lenones macrumors newbie

    Joined:
    Apr 26, 2019
    #15
    Thanks for the info. I have PRO. I will hope that the error is not critical.
     
  16. KoolAid-Drink macrumors 65816

    Joined:
    Sep 18, 2013
    Location:
    California
    #16
    Odd. My rMBP does not have this issue, in 10.14.4. I did a First Aid check of the container disk for my startup volume twice, no issues both times.
     
  17. Lenones macrumors newbie

    Joined:
    Apr 26, 2019
    #17

    Did you made a test on a MBP 2018?
     
  18. KoolAid-Drink macrumors 65816

    Joined:
    Sep 18, 2013
    Location:
    California
    #18
    Nah, rMBP 2015.
     

Share This Page

17 March 26, 2019