Closed ilias-t closed 1 year ago
Hi @ilias-t o/
What model of mac do you have? Have you ran the installer more than once and seen this? Do you get the same result running upstream's install script https://github.com/AsahiLinux/asahi-installer ?
Hey @eslerm I'm on an M1 and have run the script several times with the same result. I also just tried running the bootstrap script in the upstream repo and was able to reproduce the same result. Let me know if you'd prefer that I move the issue there instead.
Thanks!
I haven't come across overhead space
before, but that sounds like the issue. Could you run diskutil list
in MacOS and share the results?
The system should look like the before in https://github.com/UbuntuAsahi/ubuntu-asahi/issues/28#issuecomment-1539568477 More info in upstream's Partitioning Cheatsheet.
Sure thing, here are the results from diskutil list
:
Compared to the initial config in this video, the partition names and order differ.
The man page for diskutil
hints at how "overhead" occurs in the resizeVolume
section:
You can grow a volume (back) to its maximum size possible, provided no new partitions have been created that are in the way, by specifying R for the new volume size. You should use R instead of attempting an absolute value such as 100% because the latter cannot count partition map overhead.
Hmm, I'm not seeing the difference. Here's another shot without my external USB plugged in that looks mostly identical. Not sure what else to try given there are no time machine backups. I also tried running First Aid on the disk and it came back fine. I wonder if it's related to being on the beta OS. Is there anyway to instruct the script to use an already existing partition?
In the other example Machintosh HD - Data
is disk3s1
and there's some reordering.
The rest of the error code suggests resizing the volume. Possibly diskutil resizeVolume disk0s2 R
?
The most certain test is to erase and reinstall macos using recovery. If you do, could you please try running the installer partially before and after updating to 14.0 to find the suggested min_size
for each?
Reinstalled the OS and no luck. Going to close this as it doesn't seem to be an issue with this project. Thanks for help!
Thanks for checking reinstall. Upstream will definitely be interested if this is MacOS 14.0 specific. If you file an issue, please link it.
There was a MacOS 14.0 (Sonoma) report upstream (https://github.com/AsahiLinux/asahi-installer/issues/199) but, in the logs there is zero overhead. So, it feems unlikely that MacOS 14.0 itself is causing overhead partitioning.
The new size is the new size for your macOS partition. You have ~1TB total, 431GB free space, and 382GB available space after purgeable file overhead. That makes your minimum macOS partition size around 600GB. Everything is working as intended here.
The extra 11GB overhead is probably because you have a stale installer for Sonoma or something like that left over. Unless you're worried about squeezing down your macOS install to the minimum size (which I doubt you intend, since you're using more than half of your disk on it already), there is nothing to worry about.
@marcan oh, thank you for clarifying! I was under the impression that it was needing the 600GB for the new partition size. It makes perfect sense now that it's asking how much space to allocate to the macOS partition. Much appreciated
The installer is enforcing a surprisingly large amount of space as the minimum for the partition size. Why would it ever need +600GBs of size?
Notes: