iMac 2017 random restarts, Catalina, recovery couldn't find hard drive

[madask]

I can't tell if there's a problem with the hard drive or with the Catalina update, but I'm having random restarts and then yesterday recovery couldn't find the hard drive. Things seem fine today. I've disconnected my Time Machine USB hard drive so that it doesn't corrupt a backup.

I'm having trouble determining whether the issue is the hard drive or software. I've already run Disk Utility checks and it says everything's fine. I have the 1TB drive that came with the Mac and it was about 70% full but I got it down to 50% yesterday before it went unresponsive for a while. I don't know if those things are related. I'm just unable to determine the problem.

Is there somewhere in software on the macOS that I can see what happened, or determine what to do, or some way to clear cache or something since I think possibly the Catalina updates may have caused the issue and I'd prefer to try to clear up software issues before attempting to replace the hard drive.

 

[Cory Cooper]

Hello and welcome.

-Which model 2017 iMac - 21.5 or 27-inch, Retina or not?
-What type of drive is in the iMac - 1 TB (5400-rpm SATA), 1 TB Fusion Drive, or 1 TB flash?
-Are you getting any errors/kernel panics?
-Which applications are open when the issue occurs?
-Do you have any third-party utilities like MacKeeper or antivirus installed?

You can check the logs using the Console application, which is in the Utilities folder.

C

 

[madask]

Crashed again 10 minutes ago... looks like on different executables or services, but similar errors.

I don't know what to look for or do here. I can't tell if the issue is software, RAM, hard drive... I was doing something completely different here than yesterday. I'd like to just reinstall Catalina from its current version but it seems that would wipe files outside of the OS; maybe I'm reading something wrong. I can't tell.

I hope nobody's getting overwhelmed by the data I'm leaving, but I think it's necessary so far to investigate this.

 

[Cory Cooper]

Hello,

-Yes, that is an iMac (Retina 5K, 27-inch, 2017)
-Sounds like a 1 TB Fusion Drive
-Most of the crash stuff sounds like macOS-related processes

I would probably find a drive to create a full Time Machine backup or clone of your data first. Always better to be safe than sorry.

It may be good to download and run EtreCheck (you don't need to pay for the Power User feature upgrade. You can then post its report here. It will do a full analysis of your system, and identify any issues that may be causing the crashing.

C

 

[madask]

Hi, thanks, I tried EtreCheck, it looks pretty good; I was going through the data earlier this week, removing some things, and I will upload the data when I've had a chance to understand it, but in the meantime I captured the Mac error pop-ups that usually happen, which may be a better quick indicator of what's happening (I'm still not convinced it's a hardware issue).

 

[madask]

There's a lot of information to go through in EtreCheck, and I don't want to turn people off or introduce a bunch of red herring rabbit holes, but here's the "Major Issues" section:

Top Processes Snapshot by CPU:
    Process (count) CPU (Source - Location)
    diagnosticd 53.88 % (Apple)
    system_profiler (2) 49.22 % (Apple)
    Console 41.28 % (Apple)
    Google Chrome Helper (Renderer) (47) 30.24 % (Google, Inc.)
    EtreCheckPro 20.58 % (Etresoft, Inc.)

Top Processes Snapshot by Memory:
    Process (count) RAM usage (Source - Location)
    Google Chrome Helper (Renderer) (47) 4.43 GB (Google, Inc.)
    phpstorm 695 MB (JetBrains s.r.o.)
    EtreCheckPro 610 MB (Etresoft, Inc.)
    system_profiler (2) 591 MB (Apple)
    MySQLWorkbench 497 MB (Oracle America, Inc.)

Top Processes Snapshot by Network Use:
    Process Input / Output (Source - Location)
    mDNSResponder 6 MB / 553 KB (Apple)
    MySQLWorkbench 164 KB / 12 KB (Oracle America, Inc.)
    netbiosd 61 KB / 17 KB (Apple)
    apsd 4 KB / 3 KB (Apple)
    phpstorm 120 B / 368 B (JetBrains s.r.o.)

Top Processes Snapshot by Energy Use:
    Process (count) Energy (0-100) (Source - Location)
    Google Chrome Helper (Renderer) (47) 22 (Google, Inc.)
    WindowServer 5 (Apple)
    Google Chrome Helper (GPU) 2 (Google, Inc.)
    Google Chrome 2 (Google, Inc.)
    phpstorm 1 (JetBrains s.r.o.)

Virtual Memory Information:
    Physical RAM: 16 GB

    Free RAM: 2.30 GB
    Used RAM: 9.86 GB
    Cached files: 3.84 GB

    Available RAM: 6.14 GB
    Swap Used: 0 B

Software Installs (past 30 days):
    Install Date Name (Version)
    2020-07-07 Adobe Acrobat Reader DC (20.009.20074) (20.009.20074)
    2020-07-17 macOS 10.15.6 Update
    2020-07-24 MRTConfigData (1.64)
    2020-07-24 XProtectPlistConfigData (2127)
    2020-07-29 macOS Mojave (10.14.6)

Clean up:
    /Library/LaunchDaemons/com.oracle.oss.mysql.mysqld.plist
        /usr/local/mysql/bin/mysqld
        Executable not found
    ~/Library/LaunchAgents/tv.plex.player-helper.plist
        /Applications/Plex Media Player.app/Contents/MacOS/../Resources/PMP Helper
        Executable not found

Diagnostics Information (past 7-30 days):

End of report

Cory Cooper, I'm not quite sure what you're looking for. This may have been completely normal before the crashes or Catalina.

I need to find relevant reasons why the crashes are happening, such as what path to go down with error reporting (like with the Console app), and I think it would be better to investigate actual errors related to the crashes than every possible thing that could look odd in the system.

 

[madask]

Attention for @Cory-cooper.3

 

[Cory Cooper]

Hello,

Sorry for the delay in response...

The Unknown Caller error is kind of a mystery, as it can be caused by several things. The easiest fix to try is:

-Power off your Mac
-Press the power button and immediately hold the Shift key down until you see the Apple logo/progress bar
-Let the Mac startup into Safe Mode
-Once that is complete and you see the Desktop and the words Safe Boot in red in the menu bar, click  > Restart from the menu bar

Note: It can take several minutes to startup into Safe Boot mode.

Let us know if that fixes those errors, and we can go from there.

C