SCB + chantools did not redeem the funds.

[antonvier]

Well, I'm not a developer, just a reasonably enlightened user.

LND version 0.16.4-beta in a machine with Debian 5.10.191-1 (2023-08-16) x86_64 GNU/Linux (DietPi last release). Backend neutrino

the events:

1 - Node Crash
2 - a channel was not in the SCB, I contacted the channel operator and he gave the force-close
3 - I restored the node via seed a few hours later, there were no conditions to recover the drive, totally lost, no channel.db, I gave the command to restore via SCB in Thunderhub
4 - the process seemed to be going well, however a power outage problem occurred in my region, when the power came back the node was working OK, however the process seems to have been interrupted / changed.
5 - at this point (and in the same way for several hours) I have on the LNDg home screen (thunderhub too) a xx,000,000 value in "balance", exactly the same value in "on-chain" and "unconfirmed" and "0" in "confirmed" and "limbo". In the "balance" tab several addresses and transactions, all showing zero confirmations.
6 - On the Amboss.space page of the node have the addresses of the closing transactions, and all have multiple confirmations in the mempool.space, but strangely 3 channels that were opened together in the "batch mode" remain open.

After that I followed guidelines and ran the "Chantools SweepremoteClosed". This command recovered only the funds of the channel that was closed remotely at my request by the operator. It was not in the SCB, it had been created a short time before. I ran the SCB again via thunderhub, nothing changed, just like when I ran the "sweepremoteclosed" again. This is the screen with the "balance" tab of my node in LNDg, it's been the same way since I ran the commands.

https://imgur.com/luasapQ

[guggero]

Since the first recovery attempt you did was interrupted, the wallet is probably now in an incomplete state.
Please try a full recovery from the seed again and make sure that everything is fully synced, then apply the SCB again.
Also, using the SCB can take quite a while sometimes (give it at least a day or so). Also, you are reliant on your peer being online, as SCB does nothing other than ask the peer to force close (but over the encrypted p2p connection). So if the peer isn't online anymore, there's nothing you can do. If the peer exists but has a different IP address than was in your SCB file, you might need to manually connect to them and then the force close should be initiated.

[antonvier]

All of these pending transactions have already shown up as confirmed, and I haven't even run SCB again. Now I'm going to analyze the inputs and see if there's a channel missing and if there's a channel missing, I'm going to run the SCB. Thank you so much for the great advice!