Closed tomnelhams closed 3 months ago
grahampugh
commented
9 months ago You have set min-drive-space to 25GB but that's almost certainly too small. My guess is that is why it's getting through the drive space but then doesn't have enough space to mount the installer.
tomnelhams
commented
9 months ago Thanks very much for your response! I will give changing that variable a try, although I don't fully understand what difference that should make in the grand scheme of the script?
My understanding is that this is a check, this is confirmed in the script output.
2023-12-04 10:36:59 | v31.0 | [check_free_space] OK - 78 GB free/purgeable disk space detected
The macOS installer is 12GB, I would assume it would need to write more data over that over the update, but 65GB of extra write seems to be a bit of a stretch? The erase-install pkg again is only 9MB and the extra installs that the script pushes will certainly not add up to an extra 65GB...
This error code seems to relate to a temp image:
'/private/tmp/com.ninxsoft.mist/052-09398/052-09398.dmg'
The hdiutil is used to manipulate disk images, this is what is erroring in the script, not the total storage space on the Mac.
My question is, what is this temp file size supposed to be? Where is the limit on this temp image dictated and why is this exceeding said limit in such a way that the script fails, despite the Mac having plenty of available space?
grahampugh
commented
9 months ago The error message is from mist-cli. For whatever reason, it has run out of space. You can ask for details in the mist-cli GitHub page, but I believe that the installer is downloaded in parts, and mist creates a temporary writable DMG to assemble them together, which is then discarded once the assembled app is moved to the application folders. But each step needs space (startosinstall also needs space to prepare the snapshot), so there's no point trying to get away with setting a lower space limit than the recommendation.
grahampugh
commented
9 months ago The error message is from mist-cli. For whatever reason, it has run out of space. You can ask for details in the mist-cli GitHub page, but I believe that the installer is downloaded in parts, and mist creates a temporary writable DMG to assemble them together, which is then discarded once the assembled app is moved to the application folders. But each step needs space (startosinstall also needs space to prepare the snapshot), so there's no point trying to get away with setting a lower space limit than the recommendation.
grahampugh
commented
3 months ago Closing through lack of response.
Describe the bug An M1 MBA upgrading to macOS Sonoma, has 78GB free storage, goes through the entire install phase of the program and then at the very end, produces an error -
Invalid Exit Status Code: '1', Message: hdiutil: create failed - No space left on deviceTo Reproduce
If applicable, please provide the full command used when running the script. /Library/Management/erase-install/erase-install.sh --os 14 --update --no-fs --reinstall --check-power --power-wait-limit=180 --confirm --no-timeout --min-drive-space=25 --rebootdelay=180
Please describe how the script was run. Jamf policy via the Uploaded pkg.
Expected behavior The machine runs the install process and then restarts and updates to macOS Sonoma 14.1.2
Code/log output Please supply the full command used, and if applicable, add full output from Terminal or from
/var/log/erase-install.log. Don't post a partial log - I need the whole thing. Either upload the log as a file, or paste the output in a code block like this:Screenshots N/A
Environment (please complete the following information):
Additional context We are currently testing the upgrade to Sonoma, we have had 2/3 machines successfully update using this exact policy, but this machine gets the whole way through the process and then produces this error/exit code? I have flushed and run this policy twice, each time producing this error. After restarting the machine, it re-asks for permissions as if something has changed, but it hasn't updated to 14.