nobodynose
Moderator
- Joined
- Sep 29, 2012
- Messages
- 3,914
- Motherboard
- ASRock Z370M Pro4
- CPU
- i7-8700
- Graphics
- RX 560
- Mac
- Classic Mac
- Mobile Phone
That doesn't mean the command didn't run, it just means it ran and found a couple of files that have the wrong ownership and need to be corrected; that's what repair_packages is supposed to do. As for the kext that couldn't be loaded, I think that's something resulting from your original attempt to change permissions on root (why again did you do that?). At this point, since it's apparent repair_packages can't repair all the damage, I believe your best option is to do a clean install of macOS.