Node service stops on Windows GUI

This morning one of the nodes stooped working. Node services starts without errors but it stops right after.

This is what i see in logs:

2020-03-16T13:02:30.081+0100 INFO Configuration loaded from: C:\Program Files\Storj\Storage Node\config.yaml
2020-03-16T13:02:30.100+0100 INFO Operator email: ***************************
2020-03-16T13:02:30.101+0100 INFO operator wallet: ***************************
2020-03-16T13:02:30.757+0100 INFO version running on version v0.34.6
2020-03-16T13:02:30.867+0100 INFO db.migration Database Version {“version”: 31}
2020-03-16T13:02:31.444+0100 INFO preflight:localtime start checking local system clock with trusted satellites’ system clock.
2020-03-16T13:02:32.304+0100 INFO preflight:localtime local system clock is in sync with trusted satellites’ system clock.
2020-03-16T13:02:32.316+0100 INFO bandwidth Performing bandwidth usage rollups
2020-03-16T13:02:32.318+0100 INFO Node 123P9Snpdy1CP2FtT5kJJfVzBasgFgZeuWfHpw67UioyK4ESkGF started
2020-03-16T13:02:32.318+0100 INFO Public server started on [::]:28967
2020-03-16T13:02:32.318+0100 INFO Private server started on 127.0.0.1:7778
2020-03-16T13:02:32.318+0100 INFO trust Scheduling next refresh {“after”: “5h46m33.214706835s”}
2020-03-16T13:02:32.395+0100 INFO piecestore:monitor Remaining Bandwidth {“bytes”: 29841050808832}
2020-03-16T13:02:32.459+0100 INFO version running on version v0.34.6
2020-03-16T13:02:32.613+0100 INFO piecestore upload started {“Piece ID”: “LFGHGHM4DKC2T4KBKBWEMECZRJTOEDZ2XRI7P65GSEWMXDCNWM4Q”, “Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “Action”: “PUT”, “Available Bandwidth”: 29841050808832, “Available Space”: 3233179876608}
2020-03-16T13:02:32.843+0100 INFO piecestore uploaded {“Piece ID”: “LFGHGHM4DKC2T4KBKBWEMECZRJTOEDZ2XRI7P65GSEWMXDCNWM4Q”, “Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “Action”: “PUT”}
2020-03-16T13:02:34.164+0100 INFO piecestore upload started {“Piece ID”: “2KWBOYXQNBZX2WPTQ4BWI3QXESI7B62PUIFCNZAHBYIGSWVFX52A”, “Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “Action”: “PUT”, “Available Bandwidth”: 29841050786048, “Available Space”: 3233179853312}
2020-03-16T13:02:34.180+0100 INFO piecestore uploaded {“Piece ID”: “2KWBOYXQNBZX2WPTQ4BWI3QXESI7B62PUIFCNZAHBYIGSWVFX52A”, “Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “Action”: “PUT”}
2020-03-16T13:02:34.553+0100 INFO piecestore upload started {“Piece ID”: “YOGP6OS3JFX5HGEQK2Y7RIZHBAKS6GDE2DV347KLUN2SGCKAQGKQ”, “Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “Action”: “PUT”, “Available Bandwidth”: 29841050783744, “Available Space”: 3233179850496}
2020-03-16T13:02:34.885+0100 ERROR piecestore:cache error getting current space used calculation: {“error”: “FindNextFile C:\StorjStorageNode\blobs\v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa\cb: El archivo o directorio está dañado o es ilegible.”}
2020-03-16T13:02:34.906+0100 INFO piecestore upload canceled {“Piece ID”: “YOGP6OS3JFX5HGEQK2Y7RIZHBAKS6GDE2DV347KLUN2SGCKAQGKQ”, “Satellite ID”: “12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs”, “Action”: “PUT”, “error”: “context canceled”, “errorVerbose”: “context canceled\n\tstorj.io/common/rpc/rpcstatus.Wrap:79\n\tstorj.io/storj/storagenode/piecestore.(*Endpoint).doUpload:367\n\tstorj.io/storj/storagenode/piecestore.(*drpcEndpoint).Upload:214\n\tstorj.io/common/pb.DRPCPiecestoreDescription.Method.func1:986\n\tstorj.io/drpc/drpcserver.(*Server).doHandle:199\n\tstorj.io/drpc/drpcserver.(*Server).HandleRPC:173\n\tstorj.io/drpc/drpcserver.(*Server).ServeOne:124\n\tstorj.io/drpc/drpcserver.(*Server).Serve.func2:161\n\tstorj.io/drpc/drpcctx.(*Tracker).track:51”}

Edit:
Seems a file is corrupted, checked and several files in the specified directory are corrupted.
Tried a restore, but files are corrupted more than a week ago. Storj has been working fine till restart this morning.

Have you looked in to this ?

Yes, couldn’t recover the corrupted files from backups, since it seems, files are corrupt more than a week ago.

Done a disk repair and Storj services now starts fine.

Did you try chkdsk command ?

yes, that solved it, just maybe, node should solve this automatically, or at least not completely stop

The fixing of filesystem errors is a prerogative of OS. The storagenode should not have any OS-specific tools integrated.

1 Like