Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

BootCamp not working. Deleting com.apple.os.update snapshots using tmutil?

ErikGrim

ErikGrim

macrumors 604
Original poster
Jun 20, 2003
6,522
5,145
Brisbane, Australia
I’m unable to partition my 512GB SSD even with 225GB free space available. I’ve deleted all local TimeMachine backups, disabled external backups on TimeMachine, thinned with urgent tmutil thinlocalsnapshots / 1000000000 1

Yet, when I try to find out how much I can resize my partition to I still get
Code: 
diskutil apfs resizecontainer disk0s2 limits
Resize limits for APFS Physical Store partition disk0s2:
  Current Physical Store partition size on map:   500.1 GB (500068036608 Bytes)
  Minimum (constrained by file/snapshot usage):   500.1 GB (500068036608 Bytes)
  Recommended minimum (if used with macOS):       500.1 GB (500068036608 Bytes)
  Maximum (constrained by partition map space):   500.1 GB (500068036608 Bytes)

The culprit seems to be
Code: 
tmutil listlocalsnapshots /               
Snapshots for volume group containing disk /:
com.apple.os.update-190312682FDBFD811EAF7E1DE7AA32CC00611E1594F50D161F143E85BF633A4C
com.apple.os.update-MSUPrepareUpdate

Which I can’t delete with the regular tmutil deletelocalsnapshots / as they have no date. Just running that command errors with Failed to delete all Time Machine local snapshots for volume group containing disk '/'

Any ideas? I can’t find any references to these particular snapshots other than on iOS jailbreak pages.
 
Last edited:
J

JimmyjamesEU

Suspended
Jun 28, 2018
397
426
ErikGrim said:
I’m unable to partition my 512GB SSD even with 225GB free space available. I’ve deleted all local TimeMachine backups, disabled external backups on TimeMachine, thinned with urgent tmutil thinlocalsnapshots / 1000000000 1

Yet, when I try to find out how much I can resize my partition to I still get
Code: 
diskutil apfs resizecontainer disk0s2 limits
Resize limits for APFS Physical Store partition disk0s2:
  Current Physical Store partition size on map:   500.1 GB (500068036608 Bytes)
  Minimum (constrained by file/snapshot usage):   500.1 GB (500068036608 Bytes)
  Recommended minimum (if used with macOS):       500.1 GB (500068036608 Bytes)
  Maximum (constrained by partition map space):   500.1 GB (500068036608 Bytes)

The culprit seems to be
Code: 
tmutil listlocalsnapshots /               
Snapshots for volume group containing disk /:
com.apple.os.update-190312682FDBFD811EAF7E1DE7AA32CC00611E1594F50D161F143E85BF633A4C
com.apple.os.update-MSUPrepareUpdate

Which I can’t delete with the regular tmutil deletelocalsnapshots / as they have no date. Just running that command errors with Failed to delete all Time Machine local snapshots for volume group containing disk '/'

Any ideas? I can’t find any references to these particular snapshots other than on iOS jailbreak pages.
Click to expand...

You can't delete root snapshots because the os is booted from one of them. It's part of the system to allow faster updates. There are only a couple on root, they take up really minimal space. Any space used by snapshots will have been used by the user data from '/System/Volumes/Data'. Try your commands on that instead of '/'.
 
  • Like
Reactions: Quackers
ErikGrim

ErikGrim

macrumors 604
Original poster
Jun 20, 2003
6,522
5,145
Brisbane, Australia
JimmyjamesEU said:
You can't delete root snapshots because the os is booted from one of them. It's part of the system to allow faster updates. There are only a couple on root, they take up really minimal space. Any space used by snapshots will have been used by the user data from '/System/Volumes/Data'. Try your commands on that instead of '/'.
Click to expand...
Code: 
tmutil listlocalsnapshots /System/Volumes/Data                                                
Snapshots for volume group containing disk /System/Volumes/Data:
com.apple.os.update-190312682FDBFD811EAF7E1DE7AA32CC00611E1594F50D161F143E85BF633A4C
com.apple.os.update-MSUPrepareUpdate

Same result? I never saw any of these snapshots prior to installing Big Sur (I had to remove all my TimeMachnine local snapshot to even get it installed, so I did this right before). My theory is that these are the snapshots that the installer creates in case of failure mid way through the install so it can roll back, and they just never got cleared out.

If they are indeed as you say a minimal root snapshot, how come they are blocking the entirety of the volume from being partitioned? This did not happen on Catalina.

Thoughts?
 
J

JimmyjamesEU

Suspended
Jun 28, 2018
397
426
ErikGrim said:
Code: 
tmutil listlocalsnapshots /System/Volumes/Data                                              
Snapshots for volume group containing disk /System/Volumes/Data:
com.apple.os.update-190312682FDBFD811EAF7E1DE7AA32CC00611E1594F50D161F143E85BF633A4C
com.apple.os.update-MSUPrepareUpdate

Same result? I never saw any of these snapshots prior to installing Big Sur (I had to remove all my TimeMachnine local snapshot to even get it installed, so I did this right before). My theory is that these are the snapshots that the installer creates in case of failure mid way through the install so it can roll back, and they just never got cleared out.

If they are indeed as you say a minimal root snapshot, how come they are blocking the entirety of the volume from being partitioned? This did not happen on Catalina.

Thoughts?
Click to expand...

Weird. Listing snapshots on "/System/Volume/Data" usually returns snapshots called something like "com.apple.TimeMachine.<date snapshots was taken>.local". The ones you list are present on every Big Sur root volume.

Try "diskutil apfs listSnapshots /System/Volume/Data"

It's an early beta so who knows what's going on, but I dont see how the root volume could be blocking a partition. Perhaps something went wrong with the resize container command. I used disk utility to resize the container, and it was fine. Might be possible only by wiping and resintalling. Hopefully you didn't install over your Catalina install.
 
ErikGrim

ErikGrim

macrumors 604
Original poster
Jun 20, 2003
6,522
5,145
Brisbane, Australia
JimmyjamesEU said:
Weird. Listing snapshots on "/System/Volume/Data" usually returns snapshots called something like "com.apple.TimeMachine.<date snapshots was taken>.local"

Try "diskutil apfs listSnapshots /System/Volume/Data"

It's an early beta so who knows what's going on, but I dont see how the root volume could be blocking a partition. Perhaps something went wrong with the resize container command. I used disk utility to resize the container, and it was fine. Might be possible only by wiping and resintalling. Hopefully you didn't install over your Catalina install.
Click to expand...
That’s because I have already deleted the TimeMachine dated snapshots, as that is usually why your free space is not what it seems.

Neither the resize command nor DiskUtility work for partitioning because the minimum container size is the entire SSD.


Screen Shot 2020-07-02 at 13.23.26.png
 
J

JimmyjamesEU

Suspended
Jun 28, 2018
397
426
ErikGrim said:
That’s because I have already deleted the TimeMachine dated snapshots, as that is usually why your free space is not what it seems.

Neither the resize command nor DiskUtility work for partitioning because the minimum container size is the entire SSD.


View attachment 929866
Click to expand...

Sorry, I should have been more specific. I resized my Catalina partition using disk utility. I think there is a bug in the Big Sur version, so that would probably apply to the diskutil resize command as well. You're probably gonna have to nuke Big Sur, reboot into Catalina, then set the partitions the way you like from there.
 
ErikGrim

ErikGrim

macrumors 604
Original poster
Jun 20, 2003
6,522
5,145
Brisbane, Australia
JimmyjamesEU said:
Sorry, I should have been more specific. I resized my Catalina partition using disk utility. I think there is a bug in the Big Sur version, so that would probably apply to the diskutil resize command as well. You're probably gonna have to nuke Big Sur, reboot into Catalina, then set the partitions the way you like from there.
Click to expand...
Considering I only considered going BootCamp because Steam is broken on Big Sur, I think that’d be redundant ;)
 
ErikGrim

ErikGrim

macrumors 604
Original poster
Jun 20, 2003
6,522
5,145
Brisbane, Australia
ErikGrim

ErikGrim

macrumors 604
Original poster
Jun 20, 2003
6,522
5,145
Brisbane, Australia
JimmyjamesEU said:
That example is using Big Sur disk utility.
Click to expand...
Negative.
1593996386549.png

[automerge]1593996527[/automerge]
tyc0746 said:
Why are so many people upgrading to a beta OS, then complaining that it's not reliable or fully-functional :rolleyes:
Click to expand...
Mate. I’ve been running every beta OS since the original Copland. I am fully aware of what I am getting into. Let the adults talk.
 
J

JimmyjamesEU

Suspended
Jun 28, 2018
397
426
ErikGrim said:
Your instructions made no difference. I was just saying that example you linked to didn’t use Big Sur.
Click to expand...

The instructions do use Big Sur. They are instructions for creating boot camp partition once Big Sur has been installed. The fact that Big Sur is being used is specifically mentioned in the instructions.

bigsurbootcamp.png
 
ErikGrim

ErikGrim

macrumors 604
Original poster
Jun 20, 2003
6,522
5,145
Brisbane, Australia
To my surprise (one build number newer?), this was fixed in beta 2, both for partitioning through Disk Utility and terminal AND BootCamp. :eek:
 
tomadimitrie

tomadimitrie

macrumors newbie
Jul 8, 2020
11
3
Finally found a fix! Deleting snapshots using `tmutil` didn't work but I deleted them with `diskutil` from Recovery: `diskutil apfs listSnapshots <Macintosh HD's disk id>` and then `diskutil apfs deleteSnapshot <disk id> -uuid <snapshot uuid from the previous command>` for every snapshot. I had 3, two of them were deleted and one returned "insufficient privileges" but it doesn't matter, now everything works. Do it at your own risk, I don't know whether it will work on your Mac.
 
  • Love
  • Like
Reactions: tinygoblin and ErikGrim
Buju-San

Buju-San

macrumors newbie
Jul 9, 2020
4
0
tomadimitrie said:
Finally found a fix! Deleting snapshots using `tmutil` didn't work but I deleted them with `diskutil` from Recovery: `diskutil apfs listSnapshots <Macintosh HD's disk id>` and then `diskutil apfs deleteSnapshot <disk id> -uuid <snapshot uuid from the previous command>` for every snapshot. I had 3, two of them were deleted and one returned "insufficient privileges" but it doesn't matter, now everything works. Do it at your own risk, I don't know whether it will work on your Mac.
Click to expand...

How didi you delete them? I was able to list them 3, but unable to delete from recovery as the HD in not mounted and unable to mount. I tried also from Single user and no way. Trying login as normal user give me reply that no enough privileges.

Any help?

Thanks,
Jose
 
tomadimitrie

tomadimitrie

macrumors newbie
Jul 8, 2020
11
3
Buju-San said:
How didi you delete them? I was able to list them 3, but unable to delete from recovery as the HD in not mounted and unable to mount. I tried also from Single user and no way. Trying login as normal user give me reply that no enough privileges.

Any help?

Thanks,
Jose
Click to expand...
The HD was already mounted for me. Do you use FileVault, have a firmware password or have an encrypted HD?
 
Buju-San

Buju-San

macrumors newbie
Jul 9, 2020
4
0
None of those.

In Disk Utility my HDD appears as two, Macintosh HD APFS disk1s5 (the one with the errors) and Macintosh HD-Data disk1s1.

If I go into Recovery mode, disk1s5 is unmounted.
 
tomadimitrie

tomadimitrie

macrumors newbie
Jul 8, 2020
11
3
Buju-San said:
None of those.

In Disk Utility my HDD appears as two, Macintosh HD APFS disk1s5 (the one with the errors) and Macintosh HD-Data disk1s1.

If I go into Recovery mode, disk1s5 is unmounted.
Click to expand...
What error do you get when trying to mount?
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom