Hello @mac_editor
I make a mistake to create à snapshot volume, and my mac boot into him. I want to delete it. I try multiple command like
sudo tmutil deletelocalsnapshots
But it's not working. Please Help
To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.
.@salim_nxt, You need to use diskutil apfs commands which should do the trick. Search google or check the help output for diskutil for more information.
purge-wrangler ✧ tbt-flash ✧ purge-nvda ✧ set-eGPU
Insights Into macOS Video Editing Performance
Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]
Thanks you for the speed of the answer
I try a lot off diskutil apfs command nothing work. The snapshot volume w'ont be deleted :/
How do I disassociate my boot volume from this volume? I try to re enable scrutil root in recovery, mac won't boot, then I disable it again.Thanks again for helping me
![]()
To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.
.@salim_nxt, Make sure it isn't the actively booted snapshot. Also see snapshots for your boot disk, not the snapshot itself. Then use diskutil apfs deletesnapshot command. Big Sur boots off of a snapshot, so switch back to an old one to delete inactive ones.
purge-wrangler ✧ tbt-flash ✧ purge-nvda ✧ set-eGPU
Insights Into macOS Video Editing Performance
Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]
I had a kernel panic issue when I turn on the mac after I executed purge-wrangler script 6.3.0, and I can't recover from the time machine. In the end, I have to reinstall the Big Sur to resolve the issue.
HW: MacBook Pro (Retina, 13-inch, Late 2013) + Razer Core X + AMD Radeon RX 580
SW: macOS Big Sur Version 11.0.1 (20B29) + PurgeWrangler 6.3.2
This hardware set worked fine under Mojave.
I followed all the procedures in the Beginner's Guide. My FileVault is off, csrutil disabled, csrutil authenticated-root disabled, and latest purge-wrangle script installed. I plugged my eGPU in and ran the script. Everything looks fine, but the kernel panic happened when I was restarting my MBP and it kept restarting. I tried to recover from the time machine, but it didn't work, the kernel panic still existed. So my final solution is to reinstall the macOS Big Sur.
BTW, I did unplugged everything while restarting.
Any thoughts?
[Update] I tried the whole procedures again, and now it works. I have no idea why it successes this time.
[Geekbench 5 Improvement]
- Metal API
- macOS 10.14.6 (Mojave) : 31583
- macOS 11.0.1 (Big Sur) : 34420
- Open CL API
- macOS 10.14.6 (Mojave) :28920
- macOS 11.0.1 (Big Sur) : 32107
To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.
.I upgraded my Trashcan Mac Pro 2013 to Big Sur, and now purge-wrangler wants me to disable SIP, which is already disabled. Apparently, Apple has been working hard to make our lives more difficult :-)
Reading through this post was a bit intimidating, and I still did not get what to do to make my Vega 64 in Sonnet Breakaway Box work.
Are there any developments as to making eGPU possible on Thunderbolt 2 again?
To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.
.and now purge-wrangler wants me to disable SIP, which is already disabled.
If it's already disabled then the script wouldn't ask you to disable it - simple stuff. macOS Big Sur update(s) can re-enable SIP (partially) so you might want to check things and also read up on the updates to the script as it already supports Big Sur. Happy reading.
purge-wrangler ✧ tbt-flash ✧ purge-nvda ✧ set-eGPU
Insights Into macOS Video Editing Performance
Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]
@mac_editor, The first thing that I did is went back to the recovery mode and disabled SIP again. Here is the proof :-)
___________________________________________________________________________________________
[email protected] ~ % csrutil status
System Integrity Protection status: unknown (Custom Configuration).
Configuration:
Apple Internal: disabled
Kext Signing: disabled
Filesystem Protections: disabled
Debugging Restrictions: disabled
DTrace Restrictions: disabled
NVRAM Protections: disabled
BaseSystem Verification: enabled
This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.
_________________________________________________________________________________________
Purge-wrangler tried to launch again and the same thing happened:
[email protected] ~ % purge-wrangler
Password:
Please disable System Integrity Protection.
To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.
.BaseSystem Verification: enabled
Here's the proof Also it says right there - unknown (Unsupported configuration).
This is what SIP disabled looks like:
System Integrity Protection status: disabled.
purge-wrangler ✧ tbt-flash ✧ purge-nvda ✧ set-eGPU
Insights Into macOS Video Editing Performance
Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]
Sorry, I forgot... An attempt to do "csrutil authenticated-root disable" results in an error message "authentic-root command not found".
FileVault is not enabled.
To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.
.