Error Codes: What they mean and Severity Level [READ FIRST]

Hi All

having trouble getting a second node open with this error after creating a node with the windows GUI. and using GUI Toolbox to open the second node. I am studying how multiple nodes function so I can master the software. This is the error I am getting

2021-07-02T19:52:28.856+1000 FATAL Unrecoverable error {“error”: “Error starting master database on storagenode: group:\n— CreateFile D:\blobs: The system cannot find the file specified.\n— CreateFile D:\temp: The system cannot find the file specified.\n— CreateFile D:\garbage: The system cannot find the file specified.\n— CreateFile D:\trash: The system cannot find the file specified.”, “errorVerbose”: “Error starting master database on storagenode: group:\n— CreateFile D:\blobs: The system cannot find the file specified.\n— CreateFile D:\temp: The system cannot find the file specified.\n— CreateFile D:\garbage: The system cannot find the file specified.\n— CreateFile D:\trash: The system cannot find the file specified.\n\tmain.cmdRun:162\n\tstorj.io/private/process.cleanup.func1.4:363\n\tstorj.io/private/process.cleanup.func1:381\n\tgithub.com/spf13/cobra.(*Command).execute:852\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:960\n\tgithub.com/spf13/cobra.(*Command).Execute:897\n\tstorj.io/private/process.ExecWithCustomConfig:88\n\tstorj.io/private/process.Exec:65\n\tmain.(*service).Execute.func1:64\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}

and the node is not writing anything to the data disk. I think the error involves storage path and Database2 path as I had no idea what to put in Database2. Can someone help me with putting the correct files back in please?

This is often a permissions problem writing directly into the root of a drive. Reinstall the node or adjust the config.yaml with the StorJ directory set to D:\Node or D:\Storj instead of the root of the D:\ drive.

2021-07-02T20:06:44.999+1000 FATAL Unrecoverable error {“error”: “Error starting master database on storagenode: group:\n— CreateFile D:\Storagenode1\blobs: The system cannot find the file specified.\n— CreateFile D:\Storagenode1\temp: The system cannot find the file specified.\n— CreateFile D:\Storagenode1\garbage: The system cannot find the file specified.\n— CreateFile D:\Storagenode1\trash: The system cannot find the file specified.”, “errorVerbose”: “Error starting master database on storagenode: group:\n— CreateFile D:\Storagenode1\blobs: The system cannot find the file specified.\n— CreateFile D:\Storagenode1\temp: The system cannot find the file specified.\n— CreateFile D:\Storagenode1\garbage: The system cannot find the file specified.\n— CreateFile D:\Storagenode1\trash: The system cannot find the file specified.\n\tmain.cmdRun:162\n\tstorj.io/private/process.cleanup.func1.4:363\n\tstorj.io/private/process.cleanup.func1:381\n\tgithub.com/spf13/cobra.(*Command).execute:852\n\tgithub.com/spf13/cobra.(*Command).ExecuteC:960\n\tgithub.com/spf13/cobra.(*Command).Execute:897\n\tstorj.io/private/process.ExecWithCustomConfig:88\n\tstorj.io/private/process.Exec:65\n\tmain.(*service).Execute.func1:64\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57”}

still doing it after the rename

not sure what is going on here

What user is running the ‘storagenode’ service? Normally it would be ‘system’ , ‘local system’ or ‘network service’. The account which is running the service needs permissions to the D:\ drive. Also just checking you’re not using an SMB share? That’s not supported. It must be a local or iSCSI device.

Full control was not switched on for D: which i changed I started the node and for a second it went green and then went offline again. the error log is showing nothing now when I start the node and the node is not showing on localhost, thanks for your patience with inexperience

At this point I would probably clear the D:\ drive, uninstall and put the correct permissions in place before re-installing.

ye its turned into a mess

Sweet reinstalled and working thank ye for your directions

1 Like

This is because of missing setup step. In Windows GUI it’s done via reinstall, in docker - Storage Node - Node Operator

3 posts were split to a new topic: My nods are offline for 6 hours

2 posts were merged into an existing topic: Node throwing Warning: QUIC: rpc: quic: timeout

3 posts were split to a new topic: Download identity. Error “Parameter cannot be processed because the parameter name ‘o’ is ambiguous”

Noting on contact:service ping satellite failed??

ERROR piecestore
download failed
“error”: “context
deadline exceeded”

What is this one all about?

Variation of “Context canceled” - your node was too slow to give a piece.

4 posts were split to a new topic: ERROR piecedeleter could not send delete piece to trash: file does not exist

I have an error:

ERROR collector error during collecting pieces: {"Process": "storagenode", "error": "database disk image is malformed"}

how can I figure out which database is malformed? I will delete it and restart node.

You can also search the forum :slight_smile: If you still get stuck make a separate thread about it. This is not the right thread for your issue.

1 Like

I meant how to find which file is corrupted, or just remove all of them?

You may use a script from the above guide (depends on used approach and OS), it will check all databases one by one.

1 Like