A few of us have migrated from the Pi to a NUC / Laptop as follows
You have a pi . Your node gets very big. Performance degrades. You have your original seed with the mnemonic
You install umbrel on a new Linux machine
You stop the old pi and copy the umbrel folder which has got your channel.db and seed.
You reconfigure the new enviroment
Start the new machine.
You then see a different seed / mnemonic.
Migration was successful and the node works well but the old mnemonic from the pi and the mnemonic from the umbrel installed on the new ubuntu/debian (the current machine) do not match.
Any thoughts on this?. It is a cause for concern. Is the new seed safe if there is a need for disaster recovery closing all channels to recover funds on chain?. Would you suggest closing all channels and starting fresh?. This would of course be an absolute pain.
It could be a bug in the web middleware of Umbrel dashboard, that display the old cache words.
Maybe @mayank can confirm this aspect.
When you start a new node instance in the NUC you should select the option of “restore from seed”, not creating a new wallet/instance, then put your old seed.
Then copy the data, that already contain the wallet and channels.
The most important thing is:
the node ID is the same
the BTC addresses are the same generated
the channels are back online
If all these are the same as before, is nothing to worry.
From my experiences with recovering Umbrel, you may install a new Umbrel instance with same seed words, syncronize BTC 100%, shutdown, copy from the old disk machine channel.db file (write over the new machine channels.db), then restart the new install. Nothing else should be copied. All lightning channels are back.
Not really, only that is not only the channel.db, is also wallet.db
read the guide for restoring Umbrel point 7, only that you are doing the way around. Is the same procedure. You can copy the whole blockchain data too to save some time (if that date is not corrupted). But don’t copy the electrs data too, leave it to re-index with a clean index files.
So basically a copy paste of the Umbrel from the old node overwriting the Umbrel files on the PI SD card with exception of electrs data.
Since the old node had the synced data on the same “drive” and the PI uses a SSD apart from the umbrel files that are located on the SD card. Would that cause any issues with finding the sync data on the PI after the copy paste?
…wallet locked, unlock it to enable full RPC access…
I have tried both methods described in “Umbrel Troubleshooting Guide - Wallet is locked. How to unlock it in command line” I also checked the bitcoin and tor passwords in lnd.conf against .env and they match.
Everything else seems to work like the mnemonic and 2FA from the old node.
Understandable. Anyway, something was wrong in the migration process.
I did that process and other users too and wasn’t happen that. Maybe you didn’t copied all OK and LND is trying to create a new channel.db or index or who knows…
Have some patience… waiting a bit longer always get good results without fucking everything.