Unable to run dashboard

keep getting this error

“Error response from daemon: Container de4fa37e2d5e3892f72f6445d67cd313d77093c6ae9933616ee78e52cfc7e794 is restarting, wait until the container is running”

when loading the dashboard, now i dont know if my node is running or not. Have rebooted and restarted the node, but still unable to launch the dashboard.

Hi Adamthwaite, would you mind printing the logs with
docker logs --tail 20 storagenode
and pasting them here

it would seem the image is malformed, how do i fix this ?

2019-08-02T18:29:05.048Z INFO vouchers Voucher request denied. Vetting process not yet complete
ERROR: 2019/08/02 18:29:17 pickfirstBalancer: failed to NewSubConn: rpc error: code = Canceled desc = grpc: the client connection is closing
2019-08-02T18:29:18.696Z FATAL infodb: database disk image is malformed
2019-08-02T18:29:20.826Z INFO Configuration loaded from: /app/config/config.yaml
2019-08-02T18:29:20.845Z INFO Operator email: *****
2019-08-02T18:29:20.846Z INFO operator wallet: *****
2019-08-02T18:29:21.514Z INFO running on version v0.16.1
2019-08-02T18:29:21.632Z INFO db.migration Latest Version {“version”: 14}
2019-08-02T18:29:21.634Z INFO vouchers Checking vouchers
2019-08-02T18:29:21.634Z INFO vouchers Requesting voucher {“satellite”: “121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6”}
2019-08-02T18:29:21.635Z INFO bandwidth Performing bandwidth usage rollups
2019-08-02T18:29:21.641Z INFO Node 1T6r86nNw7nMpnFgC8zN66nZgHMzbdwBtrcYYZUueFaBnhbPhj started
2019-08-02T18:29:21.641Z INFO Public server started on [::]:28967
2019-08-02T18:29:21.641Z INFO Private server started on 127.0.0.1:7778
2019-08-02T18:29:21.662Z ERROR bandwidth Could not rollup bandwidth usage
2019-08-02T18:29:21.672Z ERROR piecestore:orderssender listing orders
2019-08-02T18:29:21.743Z INFO running on version v0.16.1
2019-08-02T18:29:22.802Z INFO vouchers Voucher request denied. Vetting process not yet complete
2019-08-02T18:29:36.151Z FATAL infodb: database disk image is malformed
2019-08-02T18:29:38.107Z INFO Configuration loaded from: /app/config/config.yaml

Update: The Knowledge Base article to fix malformed disk image problems @Alexey was referring to is now at https://support.storj.io/hc/en-us/articles/360029309111-How-to-fix-a-database-disk-image-is-malformed-