Since your failed system was on Catalina, which uses the Read-Only System Volume scheme with separate System and Data volumes, it sounds like you backed up only the System volume. The /Users directory, however, is stored in Data.
One possibility for why you did this is that the Data volume might be corrupted and unmountable and therefore didn’t show up in ...
I don't have a lot of experience administering/doing mass deployment of scripts over Jamf but I am positive the following links would be very helpful for you. I believe what you are looking for is how to work around Apple's Preferences Policy Control Payloads (PPPC).
Please take a look at the following resources:
GitHub - homebysix
Apple Official Doc about ...
Try format it in another computer - anything will do. If it still won't, or if it shows the same data even after formatting, assume the write-protect firmware has kicked in & it's now dead.
There's a full work-through of this issue on our sister site, Super User - What can I do if my USB flash drive is write-protected or read-only?
You are supposed to install third party software to /usr/local/bin. This is the default used by most Unix installers and build systems.
(Alternative directories in the root for example under /opt can be used if you have fu;ll control of how the software is built)
The folder /usr/bin is protected by SIP as it contains software supplied by Apple as part of ...
You can do this in Finder with a simple keystroke and one click.
Before opening your file do this:
Select the file in Finder
Press Command-I (this is the same as Get Info in the File menu)
Tick the box next to Lock in the General section.
This sets the immutable bit - meaning you can't change the file in any way.
Leave the Get Info window open and, when ...
User Richard Wick posted an answer which explains that the command has to call the setuid function in order to elevate the privileges of the command.
So changing command ownership to root and adding the s bit to the command's file mode is not enough. The command itself must also be written to ask the operating system for root privileges.
As of Big Sur this is no longer really feasible.
The root filesystem on macOS has been protected strongly forever, with each of the last few OS revisions increasing protections (with SIP, etc)
macOS mounts the System area read-only and as of Big Sur makes sure to only trust it if it has not been changed.
If you violate that trust, certain parts of ...
I had a similar issue with files in a portable drive I swapped between Windows and MacOS. For some unexplained reason some files had the user immutable flag set, thus, would not be deleted even using sudo rm.
For me, what worked was to run the following command in the terminal:
sudo chflags -R nouchg '/Volumes/DriveName/DirectoryPath'
I am no expert, but put ...