raspberry pi errors 0.17.0.1

[mattbellme]

Getting this error:

LevelDB read failure: Corruption: not an sstable (bad magic number)
2018-10-31T20:27:25Z Fatal LevelDB error: Corruption: not an sstable (bad magic number)
2018-10-31T20:27:25Z You can use -debug=leveldb to get more complete diagnostic messages
2018-10-31T20:27:25Z

************************
EXCEPTION: 15dbwrapper_error       
Fatal LevelDB error: Corruption: not an sstable (bad magic number)       
bitcoin in AppInit()       

2018-10-31T20:27:25Z Shutdown: In progress...
2018-10-31T20:27:25Z scheduler thread interrupt
2018-10-31T20:27:26Z Shutdown: done


Anyone know how to fix it?  I followed this guide to set it up https://github.com/Stadicus/guides/blob/master/raspibolt/raspibolt_20_pi.md

[achow101]

Your databases are corrupt. Start bitcoind with -reindex.

[bob123]

This means your data is somehow corrupted.

Did you connect a hard drive via USB ?
Data might get corrupted if there isn't a continuous connection to the hard drive. And USB connections tend to be interrupted quite often.

Usually it should be enough to run core with the -reindex parameter to fix that.

[mattbellme]

blocks are on a usb drive

did -reindex got the same error

now i get this error

Binding RPC on address ::1 port 8332 failed.
2018-11-01T08:14:51Z Binding RPC on address 127.0.0.1 port 8332 failed.
2018-11-01T08:14:51Z Unable to bind any endpoint for RPC server
2018-11-01T08:14:51Z Error: Unable to start HTTP server. See debug log for details.
2018-11-01T08:14:51Z Shutdown: In progress...
2018-11-01T08:14:51Z scheduler thread interrupt
2018-11-01T08:14:51Z Shutdown: done

[bob123]

now i get this error

Binding RPC on address ::1 port 8332 failed.
[...]

This means that bitcoind couldn't bind the port 8332.

Can you check whether anything else is using this port currently ?

If there isn't anything else running (which is probably the case on a PI), you might want to try to either:
(1) shutdown the daemon by executing bitcoin-cli stop or
(2) rebooting your PI.

[mattbellme]

Thanks for the help

I ended up having to wipe my hdd and start again, now it works.