Dashboard problems

     Hello guys, just started a storage node a few days ago(special thx to https://forum.storj.io/u/BrightSilence and https://forum.storj.io/u/Alexey) 

but after 37 hours the dashboard stopped working .
1. When I try to open the dashboard in the terminal I get this
docker exec -it storagenode /app/dashboard.sh
Error: open /app/config/config.yaml: no such file or directory
Usage:
/app/storagenode dashboard [flags]
2. In the logs I get this:
2020-01-16T09:13:15.694Z ERROR console:endpoint api handler server error {“status code”: 500, “error”: “storagenode console web error: storage node dashboard service error: disk I/O error”, “errorVerbose”: “storagenode console web error: storage node dashboard service error: disk I/O error\n\tstorj.io/storj/storagenode/console.(*Service).GetAllSatellitesData:295\n\tstorj.io/storj/storagenode/console/consoleserver.(*Server).satellitesHandler:146\n\tnet/http.HandlerFunc.ServeHTTP:2007\n\tgithub.com/gorilla/mux.(*Router).ServeHTTP:212\n\tnet/http.serverHandler.ServeHTTP:2802\n\tnet/http.(*conn).serve:1890”}
3. In the browser dashboard I get no data :slight_smile:

Are there any suggestions?

I guess you are using a Raspberry Pi with an USB Hard-Drive.
Question 1: Is the Drive shown in your drive manager?
Question 2: Did you mount your drive via fstab? https://documentation.storj.io/resources/faq/linux-static-mount

I guess that the hard drive isn’t mounted anymore.

Thank you for the reply ,

Yes I am using a raspberry , I have mounted it via fstab ,and you are correct , I dont know why the drive name has changed from sda1 to sdb 1 , do you reccomend any particular way of solving it?

Being a bit impatient , I have rebooted the raspberry to see what happens and now it works? do you by any chance now the cause of this problem? It’s a bit weird the hdd changing name while the raspberry is running and nobody changed the usb port or anything

Unfortunatly thats where my knowledge of linux ends.
I can only guess, that something went wrong with the static mount.

Besides, did you stopped the node with “docker stop -t 300 storagenode” before restarting?
I got a malformed database because of not doing that on my first node.

Hard to say what the cause is, but I would at the least check that you’re not using a bad cable. Perhaps something got briefly disconnected when moving something around.

Edit: for fstab, make sure you use UUID to mount the storage, so that changes in kernel naming don’t impact your mounts.

3 Likes