-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
panic: freepages: failed to get all reachable pages (page 18562: multiple references) #4102
Comments
Are you able to start with |
@Roasbeef I abandoned trying to recover on 0.9.0-beta but got a different error when trying to recover on 0.7.1-beta: |
It sounds like the freepages space of your database got corrupted. You could try to create a copy in safe mode that ignores the freepages. I added the Anyway, it probably is better to try running |
I think your assumption was probably correct. I was able to recover using a channel.backup file that the zap iOS wallet had and the 24-word cipher seed. I'm still missing some funds in the wallet but it looks like their is some ways to try and recover this. We can probably close this issue. |
Ok, closing the issue. |
Background
Not exactly sure if I got myself into a bad state but I tried to recover LND version 0.7.1-beta on 0.9.0-beta after my RaspiBlitz hdd died. Trying to start he LND service produces the stack trace below.
Your environment
Steps to reproduce
Trying to start the service produces the following error
Mar 19 04:25:56 DarkTerritory lnd[21850]: panic: freepages: failed to get all reachable pages (page 18562: multiple references)
Mar 19 04:25:56 DarkTerritory lnd[21850]: goroutine 15 [running]:
Mar 19 04:25:56 DarkTerritory lnd[21850]: github.com/coreos/bbolt.(*DB).freepages.func2(0x245e880)
Mar 19 04:25:56 DarkTerritory lnd[21850]: github.com/coreos/bbolt@v1.3.3/db.go:1003 +0xcc
Mar 19 04:25:56 DarkTerritory lnd[21850]: created by github.com/coreos/bbolt.(*DB).freepages
Mar 19 04:25:56 DarkTerritory lnd[21850]: github.com/coreos/bbolt@v1.3.3/db.go:1001 +0x108
The text was updated successfully, but these errors were encountered: