Something is seriously wrong with my Macbook!!

Looking for a guru save here.


Looks like I have duplicate system files, system log is a dumpster fire. I thought they were caused by a bad postgresql install, which I was able to resolve. Then I thought it was due to X-Code update failing. So I downloaded the file direct and applied it. But, App Store still wants to update it.


I come from a Windows world but have been working with macOS for the past 4 years so I should be able to figure this out.


Let me know what else I can provide besides the EtreCheck file. (btw, I'm aware of the failing battery and have one here ready to put in, but I'm waiting until it's more dire as should I mess that up and need to buy a new MB, I'd like to wait until the new Apple Silicon laptops are out).


Posted on Oct 29, 2020 8:07 AM

Reply

Similar questions

25 replies

Oct 31, 2020 10:09 PM in response to Barney-15E

Okay, here's where we're at now:


Read up on Kernel Extensions, or kexts.

Watched a video or two on kexts.

Marrying info I gathered from all resources, in Terminal, ran



echo "Team ID,Bundle Identifier,KEXT Allowed,Developer Name,Flags"> ~/Desktop/kext.csv
sudo sqlite3 /var/db/SystemPolicyConfiguration/KextPolicy "SELECT * FROM kext_policy;" | sed 's/|/,/g' >> ~/Desktop/kext.csv
open ~/Desktop/kext.csv


Team ID	Bundle Identifier	KEXT Allowed	Developer Name	Flags
RR43DU5BN9	com.protech.NoSleep	1	Pavel Prokofiev	8
QX5T8D6EDU	com.bluestacks.kext.Hypervisor	1	BlueStack Systems	 Inc.	8
3T5GSNBU6W	com.boxcryptor.BCFS.filesystems.bcfs	1	Benjamin Fleischer	8
6HB5Y2QTA3	com.hp.kext.io.enabler.compound	1	HP Inc.	0
6Q6RVXVYC2	com.webroot.driver.WebrootSecureAnywhere	0	Webroot Software	 Inc.	4


4/5 of these can go. Boxcryptor is the only one I'd want to keep around but I can even rebuild everything if need be. Webroot I installed for 1 hour before removing it, bluestacks shouldn't be on here at all, hp printers were removed quite some time ago. IT could be the NoSleep that is the problem as I believe it had stopped by MB from sleeping and it ran completely out of power. Got a 'kernal panic' went I finally got it going, this was 4-8 weeks ago. Next I ran the following to find the non-apple kexts and got back.


kextstat | grep -v com.apple

Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
  143    0 0xffffff7f83971000 0x4000     0x4000     com.protech.NoSleep (1.4.0) 79207772-D7BF-34EE-B7B6-6E90A96D8062 <6 5 3>
  159    0 0xffffff7f83c9c000 0x17000    0x17000    com.boxcryptor.BCFS.filesystems.bcfs (3.10.4) 70019C97-2135-3E55-A67B-EED2E21A4933 <8 6 5

and running


kextfind -loaded -not -b -s com.apple
/Library/Extensions/NoSleep.kext



At this point I restarted and went into recovery mode, Terminal, did a 'rm -rf NoSleep.kext' and then sniffed through as many folders as I could think of clearing out SecureAnywhere.kext, hp_io_enabler_compound.kext (MacHD/Library/StagedExt/Lib/Extensions) as well as in LaunchAgents and LaunchDaemons (I found a protech.plist which is the No Sleep app).




Restarted. I've attached the system.log from that point. Spotlight did not work at all at first but came back within 5-10 minutes.


Interestingly, these commands didn't change the output of the 6x6 table above, but I'm guessing they are looking elsewhere.


echo "Team ID,Bundle Identifier,KEXT Allowed,Developer Name,Flags"> ~/Desktop/kext2.csv

sudo sqlite3 /var/db/SystemPolicyConfiguration/KextPolicy "SELECT * FROM kext_policy;" | sed 's/|/,/g' >> ~/Desktop/kext2.csv

open ~/Desktop/kext2.csv


But this looks better...


Greg~ $kextstat | grep -v com.apple
Index Refs Address      Size    Wired   Name (Version) UUID <Linked Against>
 158  0 0xffffff7f83aac000 0x17000  0x17000  com.boxcryptor.BCFS.filesystems.bcfs (3.10.4) 70019C97-2135-3E55-A67B-EED2E21A4933 <8 6 5


I'll let you tell me how the logs look as I can't make any sense of that yet.


What's next coach?? :)


Thanks,


Greg

Nov 2, 2020 6:39 AM in response to Entreprenerdz

Can you explain what your reasoning as to why we are on this path?

Because you think there is a problem with your Mac and those mdworker messages repeating ad nauseam are the only indication of any problem at all. I'm not sure they are indicative of a problem, but I don't get streams of those messages on my Macs. The messages do occur, but not like you are getting them.

And, can I just do a reinstall of the OS?

If you completely erase the drive, reinstall macOS, then Migrate your user from the backup, that may resolve any problems you are having. Don't install anything and don't migrate your apps until you confirm the problem you are seeing has been eradicated. If you then need to install any of the software that hacks the kernel, install them one-at-a-time to confirm they are not the cause.

The attached file should hopefully be enlightening.

Not at all. The only people who will find it enlightening are the developers of the software that is posting the messages. That is why the software is posting those messages, to enlighten the developer about issues with their software.


I checked mine, but again, haven't really checked it before but 80Gb Other, and greyed out so I can not see what it is troubles me.

There are probably hundreds of posts about what "Other" means, most with directions on how to handle it.


I just advise using a tool that works, GrandPerspective or OmniDiskSweeper. The built-in storage management is broken and hardly useful.

I only use those tools find what it is that is taking up space, not to actually delete the items. I do that in the Finder, or move them to offline storage. There are other tools that will do the job, too, but both of these are free and don't come with other baggage. I find the graphic display of GrandPerspective easier to use, but ODS's hierarchical view by size works, too.

Oct 29, 2020 8:57 AM in response to Entreprenerdz

Entreprenerdz wrote:

diskutil list internal
/dev/disk0 (internal, physical):
  #:            TYPE NAME          SIZE    IDENTIFIER
  0:   GUID_partition_scheme            *251.0 GB  disk0
  1:            EFI EFI           314.6 MB  disk0s1
  2:         Apple_APFS Container disk1     250.7 GB  disk0s2

/dev/disk1 (synthesized):
  #:            TYPE NAME          SIZE    IDENTIFIER
  0:   APFS Container Scheme -           +250.7 GB  disk1
                 Physical Store disk0s2
  1:        APFS Volume Macintosh HD - Data   208.2 GB  disk1s1
  2:        APFS Volume Preboot         80.8 MB  disk1s2
  3:        APFS Volume Recovery        529.0 MB  disk1s3
  4:        APFS Volume VM           3.2 GB   disk1s4
  5:        APFS Volume Macintosh HD      11.3 GB  disk1s5



I see no duplicate of macOS system or data Volumes.




for general comparison only...


/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *1.0 TB disk0

1: EFI EFI 314.6 MB disk0s1

2: Apple_APFS Container disk1 1.0 TB disk0s2


/dev/disk1 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +1.0 TB disk1

Physical Store disk0s2

1: APFS Volume Macintosh HD 11.3 GB disk1s1

2: APFS Volume Macintosh HD - Data 280.4 GB disk1s2

3: APFS Volume Preboot 80.8 MB disk1s3

4: APFS Volume Recovery 529.0 MB disk1s4

5: APFS Volume VM 4.3 GB disk1s5

Oct 29, 2020 9:04 AM in response to Entreprenerdz

I think I have duplicate installs of system files as I have a metric $h!t ton of these:
rtcreportingd[5530]: objc[5530]: Class RTCReporting is implemented in both /System/Library/PrivateFrameworks/RTCReporting.framework/Versions/A/RTCReporting and /usr/libexec/rtcreportingd. One of the two will be used. Which one is undefined

That is not what that implies. That is why it is never a good idea to make judgments based on what you find in Console. The messages aren't meant for you at all.

Oct 29, 2020 8:26 AM in response to leroydouglas

diskutil list internal

/dev/disk0 (internal, physical):

  #:            TYPE NAME          SIZE    IDENTIFIER

  0:   GUID_partition_scheme            *251.0 GB  disk0

  1:            EFI EFI           314.6 MB  disk0s1

  2:         Apple_APFS Container disk1     250.7 GB  disk0s2


/dev/disk1 (synthesized):

  #:            TYPE NAME          SIZE    IDENTIFIER

  0:   APFS Container Scheme -           +250.7 GB  disk1

                 Physical Store disk0s2

  1:        APFS Volume Macintosh HD - Data   208.2 GB  disk1s1

  2:        APFS Volume Preboot         80.8 MB  disk1s2

  3:        APFS Volume Recovery        529.0 MB  disk1s3

  4:        APFS Volume VM           3.2 GB   disk1s4

  5:        APFS Volume Macintosh HD      11.3 GB  disk1s5

Oct 29, 2020 8:59 AM in response to leroydouglas

So the following is just normal logging and nothing to be concerned with?


Oct 29 08:47:05 Gregorys-MacBook com.apple.geod[6416]: objc[6416]: Class GEOETAProvider is implemented in both /System/Library/PrivateFrameworks/GeoServices.framework/Versions/A/GeoServices and /System/Library/PrivateFrameworks/GeoServices.framework/Versions/A/XPCServices/com.apple.geod.xpc/Contents/MacOS/com.apple.geod. One of the two will be used. Which one is undefined.
Oct 29 08:47:06 Gregorys-MacBook com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.backupd-helper.6411): Failed to bootstrap path: path = /System/Library/CoreServices/backupd.bundle/Contents/Resources/backupd-helper, error = 2: No such file or directory
Oct 29 08:47:09 Gregorys-MacBook com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.photolibraryd.6418): Failed to bootstrap path: path = /System/Library/PrivateFrameworks/PhotoLibraryServices.framework/Versions/A/Support/photolibraryd, error = 2: No such file or directory
Oct 29 08:47:11 Gregorys-MacBook com.apple.geod[6420]: objc[6420]: Class GEOETAProvider is implemented in both /System/Library/PrivateFrameworks/GeoServices.framework/Versions/A/GeoServices and /System/Library/PrivateFrameworks/GeoServices.framework/Versions/A/XPCServices/com.apple.geod.xpc/Contents/MacOS/com.apple.geod. One of the two will be used. Which one is undefined.
Oct 29 08:47:15 Gregorys-MacBook syslogd[131]: ASL Sender Statistics
Oct 29 08:47:22 Gregorys-MacBook com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.signpost_reporter.6426): Failed to bootstrap path: path = /usr/libexec/signpost_reporter, error = 108: Invalid path
Oct 29 08:49:54 Gregorys-MacBook com.apple.xpc.launchd[1] (com.apple.mdworker.shared.01000000-0300-0000-0000-000000000000[6441]): Service exited due to SIGKILL | sent by mds[156]
Oct 29 08:50:37 Gregorys-MacBook com.apple.xpc.launchd[1] (com.apple.mdworker.shared.01000000-0400-0000-0000-000000000000[6465]): Service exited due to SIGKILL | sent by mds[156]
Oct 29 08:51:21 Gregorys-MacBook com.apple.xpc.launchd[1] (com.apple.mdworker.shared.01000000-0500-0000-0000-000000000000[6468]): Service exited due to SIGKILL | sent by mds[156]
Oct 29 08:51:51 Gregorys-MacBook com.apple.xpc.launchd[1] (com.apple.mdworker.shared.04000000-0700-0000-0000-000000000000[6464]): Service exited due to SIGKILL | sent by mds[156]
Oct 29 08:51:51 Gregorys-MacBook com.apple.xpc.launchd[1] (com.apple.mdworker.shared.05000000-0300-0000-0000-000000000000[6392]): Service exited due to SIGKILL | sent by mds[156]
Oct 29 08:53:23 Gregorys-MacBook com.apple.xpc.launchd[1] (com.apple.mdworker.shared.04000000-0000-0000-0000-000000000000[6484]): Service exited due to SIGKILL | sent by mds[156]
Oct 29 08:54:33 Gregorys-MacBook com.apple.xpc.launchd[1] (com.apple.mdworker.shared.08000000-0700-0000-0000-000000000000[6505]): Service exited due to SIGKILL | sent by mds[156]
Oct 29 08:55:39 Gregorys-MacBook com.apple.xpc.launchd[1] (com.apple.mdworker.shared.04000000-0100-0000-0000-000000000000[6523]): Service exited due to SIGKILL | sent by mds[156]
Oct 29 08:56:17 Gregorys-MacBook com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0B000000-0400-0000-0000-000000000000[6534]): Service exited due to SIGKILL | sent by mds[156]
Oct 29 08:56:17 Gregorys-MacBook com.apple.xpc.launchd[1] (com.apple.mdworker.shared.04000000-0200-0000-0000-000000000000[6535]): Service exited due to SIGKILL | sent by mds[156]
Oct 29 08:56:31 Gregorys-MacBook com.apple.xpc.launchd[1] (com.apple.mdworker.shared.04000000-0300-0000-0000-000000000000[6546]): Service exited due to SIGKILL | sent by mds[156]
Oct 29 08:57:13 Gregorys-MacBook com.apple.xpc.launchd[1] (com.apple.mdworker.shared.05000000-0400-0000-0000-000000000000[6493]): Service exited due to SIGKILL | sent by mds[156]
Oct 29 08:57:23 Gregorys-MacBook com.apple.xpc.launchd[1] (com.apple.mdworker.shared.01000000-0600-0000-0000-000000000000[6528]): Service exited due to SIGKILL | sent by mds[156]
Oct 29 08:57:23 Gregorys-MacBook syslogd[131]: ASL Sender Statistics
Oct 29 08:57:48 Gregorys-MacBook com.apple.xpc.launchd[1] (com.apple.mdworker.shared.0B000000-0500-0000-0000-000000000000[6553]): Service exited due to SIGKILL | sent by mds[156]


Oct 29, 2020 9:14 AM in response to Barney-15E

No specific behavior, just taking my time and trying to resolve things I think are issues as I plug away coding here.


I recall having a system failure and reboot, and it said to check out the system log. Which made me aware of Console.


Attempting to get a little more umph outta this under powered Macbook until the new Apple Silicon one is (hopefully) released later this year.


I was just assuming that 100000 characters of log in under 2 hours was a little extreme. Plus, not knowing what com.apple.mdworker.shared.##### is is bothering me for some reason.


A behavior I can remember is spotlight wasn't bringing anything up, but I was able to get it to reindex itself.

Nov 2, 2020 5:42 AM in response to Barney-15E

I had done that before doing my previous post, but I've deleted some more personal files, restarted, and reindexed the terminal way, restarted, reindexed the GUI way, restarted.


I hadn't heard of .Spotlight-V100/ before I did some research and found Where is Spotlight index stored and how t… - Apple Community and ran

sudo du -hcd 1 / .Spotlight-V100/

in Terminal (before restart) and got

Greg~ $sudo du -hcd 1 /.Spotlight-V100/
Password:
du: /.Spotlight-V100/: No such file or directory
 0B	total


After the reboot collecting a different kind of console.log (more on that later), I ran it again and got somewhat of a file, lots of errors, and it's taking up 369GB (on a 750gb drive!).


FYI, I am not really seeing a downturn in performance on Spotlight at all. It seems very fast imo. I DO find the plethora of errors immediately after restarting and the constant stream of


Nov  2 05:11:35 Gregorys-MacBook com.apple.xpc.launchd[1] (com.apple.mdworker.shared.02000000-0200-0000-0000-000000000000[2872]): Service exited due to SIGKILL | sent by mds[156]


to be very troublesome.


My request:

Can you explain what your reasoning as to why we are on this path? And, can I just do a reinstall of the OS? I believe it will put Catalina on, and what are the drawbacks of doing so? This is my web dev machine and I know it's been configured a LOT, most likely a good portion that would take me quite some time to figure out how to do again.


btw, I can't open previous system.log files in this post thread... with my mac or PC.... weirdness.


Please help! (Console coming next)


Greg

Nov 2, 2020 5:49 AM in response to Entreprenerdz






This time I thought I'd just grab the Faults and Errors from the main Greg's Macbook in Console since reboot. It doesn't look very healthy. 778 lines of errors in under 5 minutes. Image is just to show you the selection on the left panel, and the Faults and Errors filter applied right after reboot. The attached file should hopefully be enlightening.










Nov 2, 2020 11:36 AM in response to Barney-15E

That's fair. And you're right... those errors are valid, there was no input files provided. (C++ compiling or something).


But again, everything works, it's just ugly in the console and I'm noticing more and more areas of concern, lag, etc.


I deleted a bunch of media and non-critical stuff and now my drive is missing 100Gb of space. So I'll be taking care of that first.


But I've found a lot of these homebrew/XCode issues, more that they can't get the command tools installed, but I think the fix will be about the same.


My current game plan is:

  • get drive space sorted out, using your tool and Disk Utility as needed.
  • take a list of all my homebrews and then uninstall them all
  • Uninstall XCode
  • reboot, see what the console looks like
  • if all is good, install JUST the CLT as I only need them for homebrew.
  • Then install brews as needed to get my project to compile again.


fingers crossed... I see a faint hint of light up ahead in this tunnel...


Thanks for your time and effort.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Something is seriously wrong with my Macbook!!

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.