MBP 10.1 Big Sur bootlog reports many 'command not found'

Question

Lance.scs Author

Level 1

19 points

MBP 10.1 Big Sur bootlog reports many 'command not found'

My MBP is a bit slow starter. Like, something is wrong.

The bootlog reports many times 'command not found"

andre@andre-server ~ % /Volumes/EFI/BOOTLOG ; exit;

/Volumes/EFI/BOOTLOG: line 1: SlingShot:: command not found

/Volumes/EFI/BOOTLOG: line 2: Memory: command not found

/Volumes/EFI/BOOTLOG: line 3: Memory: command not found

/Volumes/EFI/BOOTLOG: line 4: Drive: command not found

/Volumes/EFI/BOOTLOG: line 5: Drive: command not found

/Volumes/EFI/BOOTLOG: line 6: NetworkFinishOSRSHostInfoLookup:: command not found

/Volumes/EFI/BOOTLOG: line 7: NetworkInitNetwork:: command not found

/Volumes/EFI/BOOTLOG: line 8: SlingShot:: command not found

/Volumes/EFI/BOOTLOG: line 9: ShowError:: command not found

: command not foundG: line 10:

/Volumes/EFI/BOOTLOG: line 11: SlingShot:: command not found

/Volumes/EFI/BOOTLOG: line 12: Memory: command not found

/Volumes/EFI/BOOTLOG: line 13: Memory: command not found

/Volumes/EFI/BOOTLOG: line 14: Drive: command not found

/Volumes/EFI/BOOTLOG: line 15: Drive: command not found

/Volumes/EFI/BOOTLOG: line 16: NetworkFinishOSRSHostInfoLookup:: command not found

/Volumes/EFI/BOOTLOG: line 17: NetworkInitNetwork:: command not found

/Volumes/EFI/BOOTLOG: line 18: SlingShot:: command not found

/Volumes/EFI/BOOTLOG: line 19: ShowError:: command not found

: command not foundG: line 20:

Saving session...

...copying shared history...

...saving history...truncating history files...

...completed.

Deleting expired sessions... 16 completed.

[Process completed]

Could anyone advise me please?

MacBook Pro 15″, macOS 11.7

Posted on Nov 12, 2024 3:00 AM

Reply

Answer 1

John Galt

Level 10

146,330 points

Nov 12, 2024 6:53 AM in response to Lance.scs

Something appears to be invoking a Terminal script upon logging in, and whatever that may be is probably being launched as either a system or user launch agent or daemon.

Start investigating by inspecting the contents of the following three folders:

~/Library/LaunchAgents

/Library/LaunchDaemons

/Library/LaunchAgents

All three.

If you need help doing that, read About those " will damage your computer" messages - Apple Community. It describes a different problem, but the means to investigate it remains the same, and it has illustrated step-by-step instructions. Post screenshots if you so choose — that document describes how to do that also.

Reply