Debugging blocked startup

I recently had to delete my hass.db and hass.log as they had grown to 10’s of GB overnight after a bad script update I made filled them up.

When I restart Hass, it gets stuck. I get “Home Assistant is starting, please wait…” indefinitely, but can use the Config/Dev Tools/etc. There is no debug whatsoever to say where it is getting stuck. I can see what the last thing to happen is, but I don’t think that is where the fault is. Plus, the last thing changes at random when I restart.

How should I go about debugging this?

I’ve increased the overall log level to ‘debug’ and I get a load of Phillips Hue normal-looking periodic debug - it is receiving the list of lights and parsing them, and it appears to be doing this ok.

I suspect one of my integrations is breaking things. I want to do something like disable them all, then selectively re-enable them one-by-one until I find the broken one, then figure out how to fix it. Standard debug tactics. But how do I do this in Hass? There doesn’t appear to be any way to temporarily disable an integration. I don’t want to delete it completely.

Any other tips for debugging blocked startup? Thanks!