Umbrel on Linux migration looks successful but Bitcoind fails to start

Support and Troubleshooting
1

Migrated from 0.5.2 to 1.1.2 in a VM. Umbrel and migration data are on the same 4TB drive. Waited 3 days and the bitcoin app still doesn’t show anything. Looks like Electrs storage was migrated properly (47GB) but the Bitcoin blockchain data still shows under System (736GB) and the app doesn’t show any activity. Should I move the blockchain data manually?

Latest log from bitcoind:

2024-06-13T09:40:38Z [Chainstate [ibd] @ height 847167 (0000000000000000000268badcef2cfa54fe6e50cb512d5fb90af3ab56604be0)] resized coinsdb cache to 8.0 MiB
2024-06-13T09:40:38Z [Chainstate [ibd] @ height 847167 (0000000000000000000268badcef2cfa54fe6e50cb512d5fb90af3ab56604be0)] resized coinstip cache to 318.9 MiB
2024-06-13T09:40:38Z init message: Verifying blocks…
2024-06-13T09:40:38Z Verifying last 6 blocks at level 3
2024-06-13T09:40:38Z Verification progress: 0%
2024-06-13T09:40:38Z LevelDB read failure: Corruption: not an sstable (bad magic number)
2024-06-13T09:40:38Z Fatal LevelDB error: Corruption: not an sstable (bad magic number)
2024-06-13T09:40:38Z You can use -debug=leveldb to get more complete diagnostic messages
2024-06-13T09:40:38Z Fatal LevelDB error: Corruption: not an sstable (bad magic number)
2024-06-13T09:40:38Z : Error opening block database.
Please restart with -reindex or -reindex-chainstate to recover.
2024-06-13T09:40:38Z Aborted block database rebuild. Exiting.
2024-06-13T09:40:38Z Shutdown: In progress...
2024-06-13T09:40:38Z scheduler thread exit
2024-06-13T09:40:38Z Flushed fee estimates to fee_estimates.dat.
2024-06-13T09:40:39Z Shutdown: done```
2

same here, upgraded from 0.5.4 to 1.1.2 and it worked fine. Then I decided to upgrade from my old Pi4 to Pi5. Booted ok but Bitcoind log shows “Please restart with -reindex or -reindex-chainstate to recover.”

I may try this -reindex-chainstate to recover - #2 by smolgrrr

3

I had a long list of issues actually. My Mac hard drive was formatted in ExFAT (just a normal hard drive with a different packaging). I should have checked and reformatted I was just lazy.
Then I also got the issue where SCP doesn’t actually make sure the file is properly copied over, I had to use rsync to have a perfect copy. From there it all went flawlessly.