pending_force_closing_channels stuck w/ limbo balance

[xmready]

After ignoring my bitcoin node for a couple years, I discovered that the bitcoin core database was corrupt, so I cleared out the data directory (minus the config file), updated bitcoin core to v29 and re-synced the chain. Next I updated lnd to v19, started it up, and passed the command to close all channels. After waiting a while, I noticed I had 3 pending_force_closing_channels which all had a limbo_balance. At this point I ran lnd --reset-wallet-transactions which completed successfully, but I still had 3 pending_force_closing_channels with limbo_balance. The only difference I noticed after a rescan was the blocks_til_maturity for the channels changed from 0 to different negative values. I see an on-chain wallet balance, but non of my UTXOs match an address listed as an output of the closing txs in these three channels.

I've been reading similar posts but I can't wrap my head around what is going on. Any help resolving this is greatly appreciated. Here are screenshots of the channels in question.

[guggero]

What's the state of the individual transactions on-chain? Without knowing the TXIDs it's hard to help you...

[xmready]

What's the state of the individual transactions on-chain? Without knowing the TXIDs it's hard to help you...

@guggero They were all confirmed, 2 of them confirmed about the same time I issued the close all channels command, and the 3rd one was confirmed like 10 months ago.

An update to this situation is that I stopped the lnd service, renamed the data directory and created a fresh one. I did a recovery from seed . After that finished, I did a recovery from the old channel.backup file in the renamed old data dir. Oddly the output told me that only 2 channels were recovered. Checking the pending channels only showed the 2 newer pending force close channels, and checking the wallet balance now showed an unconfirmed balance which matched their limbo balance. This was progress, except for the third 10 month old pending channel disappearing completely and me having no idea what happens with its limbo balance. Maybe it was already returned to my wallet, but the outputs from it's tx id didn't match any of my wallet addresses with unspent outputs. Maybe I'm confused to how the sweeping works and it's normal for those not to match. I honestly haven't dedicated a lot of time to deep diving all this stuff.

[guggero]

I'd try restarting with the --height-hint-cache-query-disable flag (or height-hint-cache-query-disable=true in the config file) and see if that changes anything. Then check the logs for attempted sweeps.
But other than that it sounds like you did everything correct. Hard to say what's actually going on without more info.

[xmready]

I'd try restarting with the --height-hint-cache-query-disable flag (or height-hint-cache-query-disable=true in the config file) and see if that changes anything. Then check the logs for attempted sweeps. But other than that it sounds like you did everything correct. Hard to say what's actually going on without more info.

Can you give me a high level overview on why this might help?

[guggero]

Sometimes the cache that stores the height of a transaction has incorrect values and the chain re-scan doesn't then detect spends. So disabling the height hint cache can help in such situations. The cache is just an optimization, so turning it off shouldn't have any non-performance implications.