{"id":42741,"date":"2024-04-03T15:04:56","date_gmt":"2024-04-03T19:04:56","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=42741"},"modified":"2024-04-03T15:05:29","modified_gmt":"2024-04-03T19:05:29","slug":"a-disk-so-full-it-couldnt-be-restored","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2024\/04\/03\/a-disk-so-full-it-couldnt-be-restored\/","title":{"rendered":"A Disk So Full, It Couldn’t Be Restored"},"content":{"rendered":"

Glenn Fleishman<\/a> (Mastodon<\/a>):<\/p>\n

\n

Turned out, my kid had managed a neat trick, though they were not alone: they had filled macOS’s startup volume storage so full that the operating system was incapable of deleting files in any fashion. Instead of halting the massive Steam download when the drive became disastrously full, macOS continued to write files until there was just 41K free on the drive.<\/p>\n

[…]<\/p>\n

Due to our gigabit Internet connection and the size of the Steam file, macOS outstripped its ability to throttle filling storage because it was also making a local Time Machine snapshot<\/a>.<\/p>\n

[…]<\/p>\n

It was time to restart to see if it would clear caches. Unfortunately, restarting left the Mac unable to start up at all. No matter what I tried, it would reach about halfway through the progress bar before failing.<\/p>\n

[…]<\/p>\n

I shifted to recoveryOS, Apple’s somewhat new name for the special disk partition in macOS that lets you run operations on the main startup volume while it’s not mounted, including Disk Utility repairs and reinstallation. From there, I hit the wall as well, as Terminal commands continued to fail with the same error.<\/p>\n<\/blockquote>\n

He had to erase the Mac and ran into a Sonoma bug trying to restore from a network Time Machine backup.<\/p>\n\n

Previously:<\/p>\n