Error starting 2nd node on windows

A quick preface, I have used the community toolbox, increased the ports+1, signed a new identity, created the folders in the new data folder for the node to run. However, it still crashes out, here is the relevant log:

2020-12-15T22:54:14.965-0500	INFO	Configuration loaded	{"Location": "C:\\Program Files\\Storj1\\Storage Node\\config.yaml"}
2020-12-15T22:54:14.979-0500	INFO	Operator email	{"Address": "denysashikhin@gmail.com"}
2020-12-15T22:54:14.979-0500	INFO	Operator wallet	{"Address": "0x16779f73177060b49951718ed39a6eb939ae0c32"}
2020-12-15T22:54:15.077-0500	INFO	db	database does not exists	{"database": "secret"}
2020-12-15T22:54:15.363-0500	INFO	Telemetry enabled	{"instance ID": "1v25exHEAWkzh4fFTXdDFSr5qxhzbcURfK2kBoGRUERLTcAmpc"}
2020-12-15T22:54:17.837-0500	INFO	db.migration	Database Created	{"version": 46}
2020-12-15T22:54:18.304-0500	INFO	preflight:localtime	start checking local system clock with trusted satellites' system clock.
2020-12-15T22:54:19.039-0500	INFO	preflight:localtime	local system clock is in sync with trusted satellites' system clock.
2020-12-15T22:54:19.040-0500	INFO	Node 1v25exHEAWkzh4fFTXdDFSr5qxhzbcURfK2kBoGRUERLTcAmpc started
2020-12-15T22:54:19.040-0500	INFO	Public server started on [::]:28968
2020-12-15T22:54:19.040-0500	INFO	Private server started on 127.0.0.1:7779
2020-12-15T22:54:19.040-0500	INFO	trust	Scheduling next refresh	{"after": "5h33m39.13786766s"}
2020-12-15T22:54:19.041-0500	INFO	bandwidth	Performing bandwidth usage rollups
2020-12-15T22:54:19.043-0500	ERROR	services	unexpected shutdown of a runner	{"name": "piecestore:monitor", "error": "piecestore monitor: error verifying location and/or readability of storage directory: open D:\\storj2\\data\\storage-dir-verification: The system cannot find the file specified.", "errorVerbose": "piecestore monitor: error verifying location and/or readability of storage directory: open D:\\storj2\\data\\storage-dir-verification: The system cannot find the file specified.\n\tstorj.io/storj/storagenode/monitor.(*Service).Run.func1.1:121\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/storj/storagenode/monitor.(*Service).Run.func1:118\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2020-12-15T22:54:19.044-0500	ERROR	nodestats:cache	Get pricing-model/join date failed	{"error": "context canceled"}
2020-12-15T22:54:19.044-0500	ERROR	contact:service	ping satellite failed 	{"Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", "attempts": 1, "error": "ping satellite error: rpc: dial tcp: operation was canceled", "errorVerbose": "ping satellite error: rpc: dial tcp: operation was canceled\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:108\n\tstorj.io/common/rpc.TCPConnector.DialContext:72\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:175\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:96\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:87\n\tstorj.io/common/rpc.Dialer.dialPool:141\n\tstorj.io/common/rpc.Dialer.DialNodeURL:95\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:124\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2020-12-15T22:54:19.044-0500	ERROR	contact:service	ping satellite failed 	{"Satellite ID": "12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB", "attempts": 1, "error": "ping satellite error: rpc: dial tcp: operation was canceled", "errorVerbose": "ping satellite error: rpc: dial tcp: operation was canceled\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:108\n\tstorj.io/common/rpc.TCPConnector.DialContext:72\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:175\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:96\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:87\n\tstorj.io/common/rpc.Dialer.dialPool:141\n\tstorj.io/common/rpc.Dialer.DialNodeURL:95\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:124\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2020-12-15T22:54:19.044-0500	INFO	contact:service	context cancelled	{"Satellite ID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE"}
2020-12-15T22:54:19.044-0500	INFO	contact:service	context cancelled	{"Satellite ID": "12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB"}
2020-12-15T22:54:19.044-0500	ERROR	contact:service	ping satellite failed 	{"Satellite ID": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", "attempts": 1, "error": "ping satellite error: rpc: dial tcp: operation was canceled", "errorVerbose": "ping satellite error: rpc: dial tcp: operation was canceled\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:108\n\tstorj.io/common/rpc.TCPConnector.DialContext:72\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:175\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:96\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:87\n\tstorj.io/common/rpc.Dialer.dialPool:141\n\tstorj.io/common/rpc.Dialer.DialNodeURL:95\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:124\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2020-12-15T22:54:19.044-0500	INFO	contact:service	context cancelled	{"Satellite ID": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6"}
2020-12-15T22:54:19.044-0500	ERROR	contact:service	ping satellite failed 	{"Satellite ID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", "attempts": 1, "error": "ping satellite error: rpc: dial tcp: operation was canceled", "errorVerbose": "ping satellite error: rpc: dial tcp: operation was canceled\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:108\n\tstorj.io/common/rpc.TCPConnector.DialContext:72\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:175\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:96\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:87\n\tstorj.io/common/rpc.Dialer.dialPool:141\n\tstorj.io/common/rpc.Dialer.DialNodeURL:95\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:124\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2020-12-15T22:54:19.044-0500	INFO	contact:service	context cancelled	{"Satellite ID": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs"}
2020-12-15T22:54:19.044-0500	ERROR	contact:service	ping satellite failed 	{"Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "attempts": 1, "error": "ping satellite error: rpc: dial tcp: operation was canceled", "errorVerbose": "ping satellite error: rpc: dial tcp: operation was canceled\n\tstorj.io/common/rpc.TCPConnector.DialContextUnencrypted:108\n\tstorj.io/common/rpc.TCPConnector.DialContext:72\n\tstorj.io/common/rpc.Dialer.dialEncryptedConn:175\n\tstorj.io/common/rpc.Dialer.DialNodeURL.func1:96\n\tstorj.io/common/rpc/rpcpool.(*Pool).Get:87\n\tstorj.io/common/rpc.Dialer.dialPool:141\n\tstorj.io/common/rpc.Dialer.DialNodeURL:95\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatelliteOnce:124\n\tstorj.io/storj/storagenode/contact.(*Service).pingSatellite:95\n\tstorj.io/storj/storagenode/contact.(*Chore).updateCycles.func1:87\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/common/sync2.(*Cycle).Start.func1:71\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2020-12-15T22:54:19.044-0500	INFO	contact:service	context cancelled	{"Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S"}
2020-12-15T22:54:19.544-0500	ERROR	servers	unexpected shutdown of a runner	{"name": "debug", "error": "debug: http: Server closed", "errorVerbose": "debug: http: Server closed\n\tstorj.io/private/debug.(*Server).Run.func2:108\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}
2020-12-15T22:54:20.572-0500	FATAL	Unrecoverable error	{"error": "piecestore monitor: error verifying location and/or readability of storage directory: open D:\\storj2\\data\\storage-dir-verification: The system cannot find the file specified.", "errorVerbose": "piecestore monitor: error verifying location and/or readability of storage directory: open D:\\storj2\\data\\storage-dir-verification: The system cannot find the file specified.\n\tstorj.io/storj/storagenode/monitor.(*Service).Run.func1.1:121\n\tstorj.io/common/sync2.(*Cycle).Run:92\n\tstorj.io/storj/storagenode/monitor.(*Service).Run.func1:118\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:57"}

I’m not sure what that ending error is telling me, or how I would go about fixing it. So any advice is appreciated!

the new version cand create folder and hdd check file, you created folders by hand, but you cant create hdd check file, i work on new version that can make it all, but i have problem with passing spases to paths.
delete all handmade folders.
try in cmd this with corelated paths to yours
C:\Program Files\Storj1\Storage Node\storagenode.exe setup --storage.path D:\ --config-dir D:\ --identity-dir D:\

this will create needed folders in directory, will make config but you can delet it, and make you needed check files with your indentity

Since there is a space in the path you probably need to encapsulate it in double quotes.

"C:\Program Files\Storj1\Storage Node\storagenode.exe" setup --storage.path D:\ --config-dir D:\ --identity-dir D:\

@Vadim could that be a solution to your problem too?

I made extencive tests today, problem that i cant pass quots cmd by software, it makes doble quotes and node dont like it. I hope today i found solution, now i wait spare HDD to test it on real instalation.
quotes are needed to pass paths with spases to arguments

Any eta one the fix/update?

I have the same problem exactly after a simple reboot…

The solution is to run a storagenode.exe setup once.
@Girard The reason - either Windows deleted it during disks auto-check after abruptly shutdown or you skipped some versions during update.
In @thelastspark 's case that file has not be created during manual emulation of the setup process.