Well this isn’t good. I can’t seem to login to my computer this morning. It reboots fine. I get to the login screen, but when I put in my password the progress bar moves ahead a few pixels and then just stops. The computer freezes solid. So solid there’s no mouse, caps lock doesn’t toggle, and the time stops updating.

Tried safe mode which didn’t work either.

Well, I don’t really know what to do. If I knew more about the internals I could probably fix whatever is wrong in recovery mode Terminal, but I kinda don’t.

I can get in Recovery Mode just fine. I ran Disk Utilities repair stuff on all the volumes. There were warnings about things not being the expected size. I ran it again, they were all gone.

Reboot - same effect.

I have a second user account on this machine that was setup for testing so its the most basic user account (not startup things) and it does the exact same thing - gets maybe 1/10th of the way on the progress bar and the whole entire computer locks up.

In Recovery Mode Terminal I got a list of APFS snapshots on my Data volume and there were a lot. So I painstakingly deleted every one of them using terminal commands (couldn’t get the tmutil to work - it complained about frameworks and dylibs).

Sadly that didn’t fix it either.

Well I have no idea what to do.

If I try to reinstall Tahoe, it has me unlock my drive and then it says, “The volume cannot be downgraded.”

So it won’t even let me do that.

My Time Machine backup was a networked one. It does talk to the server and find snapshots, but takes like 10 minutes just to do that. I tried plugging the drive in directly but it won’t see the snapshots that way. So to even *try* a recovery that way is apparently going to be an over-network recovery which given it’s like 1TB and this damn slow will take… ooh… the rest of the week maybe. And I don’t even know if it’ll work.
And the moment I commit to that option, it’s going to wipe my drive. So if it doesn’t work I’m fucked.
I found a 4TB drive, wiped it, and am going to attempt to install Tahoe fresh to that external drive using recovery. Then assuming that works, I’ll see if I can read or capture the Data volume directly to at least get another copy of it. After that I’m not sure. Can migration assistant work? Could I maybe use that to migrate from my internal drive to my external one and see if that works? I don’t know. Used to be you could do all kinds of stuff but everything so fucking locked down anymore.
The thing is, I can read the Data volume from Terminal in Recovery Mode. I mean, I can’t check every single thing, but it’s there. So if it’s corrupted or broken it’s not *entirely* broken. I don’t know what would cause a hard freeze like this when trying to login or how to find out what it is. Like, it’s a complete and total OS freeze. Caps lock doesn’t even work anymore when it stops. Just nothing at all.

This plan to install Tahoe on the external drive is also not going to be quick because for some reason it’s saying it will take 4 hours and 27 minutes. And worse, it’s been saying that for at least 10 minutes now. I can’t tell if it’s doing anything at all. No indication of if it’s downloading… at what speed… how things are going.. Nothing.

I guess we aren’t supposed to know about anything at all anymore.

To make matters worse, I’m still a bit sick.

So yeah. This is awesome.

Down to 4 hours and 2 minutes.

This is ridiculous. My internet is not this slow. I don’t know why it’s this slow.

I thought maybe I’d go on my wife’s computer and figure out how to get the Tahoe installer downloaded and build the external bootable drive over there because maybe it’d download faster, etc.

Except I can’t find a Tahoe standalone installer.

I found some softwareupdate command line tool that is supposed to download it. So I tried that. It gives an error.

I search for the error and I find threads going back years about how it doesn’t work for people with the same error. No one knows why.

Awesome.

Good job, guys.

Time estimate suddenly dropped to 52 minutes. The progress bar is at 100%.

Fuck this. Time for lunch.

15 minutes later and it’s still at 52 minutes.

Neat.

About a minute remaining.

Sure Jan.

@bigzaphod I long ago gave up trying to make sense of, or trusting, the estimated times given by, well, pretty much any Apple process: downloads, installs, whatever.

But it has definitely gotten worse.

It sucks that you're having to deal with this at all, let alone while still sick. Hope you're able to make some real progress soon.

@bigzaphod If it’s any consolation, there is one positive result:

Reminding me that a) I had several local code branches that had not been published and could be lost, so I took care of that; b) it's been *months* since I last ran a full clone of my mac — so I dug out that drive and am running one now.