Unexpected shutdown of a runner: not a directory

Is this the same node you had issues with when you used SMB? And you ended up moving to an M1 Mac?

You already had file system issues as a result of using SMB, which will probably explain the missing files and other weird things you see.

I also notice you posted this.

If your node takes more than 10 seconds to stop, the process will be force killed this way. This could cause all sorts of problems as well. Please always stop your node with.

docker stop -t 300 storagenode

Before quiting docker or shutting down/restarting the machine.

2 Likes