Windows 10 GUI Node service Storj V3 stop randomly, unexpectaly

Mimi · November 19, 2023, 5:39pm

Hello, i don’t know why, my node become offline after some hours, minutes, randomly, unexpectaly…
The windows service “Storj V3 Storage Node” stop.
This is the log :

2023-11-18T11:10:24+01:00	INFO	piecestore	download started	{Piece ID: NLIPOV7PI6VJD7QJ3OFNJUE7PKI45UWCYPNSB5ND2GR3MSZHKL7A, Satellite ID: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs, Action: GET, Offset: 0, Size: 256, Remote Address: 138.2.135.177:40288}
2023-11-18T11:10:24+01:00	INFO	piecestore	upload started	{Piece ID: 67RXIJMB3XXWNLJEYAH5J2J26DRFBZASIL7IUHHT2BNKGROJ5XVA, Satellite ID: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs, Action: PUT, Available Space: 1226904129408, Remote Address: 50.7.230.34:42986}
2023-11-18T11:10:24+01:00	INFO	piecestore	upload started	{Piece ID: DT4YPDFS5UHFUXO57RNUBTDMJTSS4LUQA2W5YOIQVK6R32JY6IMQ, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Available Space: 1226904129408, Remote Address: 23.237.233.138:40714}
2023-11-18T11:10:26+01:00	INFO	piecestore	upload started	{Piece ID: C6ZP2IPCMPACEYAMREVZOFA2P5SMYQZL7WN2QZCBBIWFFSRRGLVA, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Available Space: 1226904129408, Remote Address: 50.7.230.34:55734}
2023-11-18T11:10:30+01:00	INFO	piecestore	download started	{Piece ID: VI3FFO6XKQ4EXA2NXCDODFHEIZLOSII65YR2LQT6VMAOQGVRU6LQ, Satellite ID: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs, Action: GET, Offset: 1011968, Size: 2304, Remote Address: 130.162.246.56:34682}
2023-11-18T11:10:32+01:00	INFO	piecestore	upload started	{Piece ID: EQKGBZJLBL3Z3E53GRK4JFD2JAHSBBXUB77LFIABJ7VVTD56FM4A, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Available Space: 1226904129408, Remote Address: 5.161.117.79:17616}
2023-11-18T11:10:37+01:00	INFO	piecestore	upload started	{Piece ID: DWBT6A6PHATGWAALOVTC5B6T33KJUNLWZSLTPI6C5OOD6NLGI6JQ, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Available Space: 1226904129408, Remote Address: 50.7.22.194:36876}
2023-11-18T11:10:37+01:00	INFO	piecestore	upload started	{Piece ID: BPI3SKUVPWPNG2RFBGR2FP5BJW5OUSZFH2MD4RAAU5YYH56P23AQ, Satellite ID: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs, Action: PUT, Available Space: 1226904129408, Remote Address: 50.7.22.194:42454}
2023-11-18T11:10:42+01:00	INFO	piecestore	upload started	{Piece ID: ESWHWX6SKOTUCJUIVFPWG2OQ6OFZ2KDUYN2PSOBDEFXH2N7NX6DQ, Satellite ID: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs, Action: PUT_REPAIR, Available Space: 1226904129408, Remote Address: 157.90.236.201:36794}
2023-11-18T11:10:44+01:00	INFO	piecestore	download started	{Piece ID: 5I2WJB4ND3QO72HUMHEYUP6TRVLZZMV45PXMEO4AI6NZWBENXXQQ, Satellite ID: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs, Action: GET, Offset: 0, Size: 256, Remote Address: 130.162.246.56:38100}
2023-11-18T11:10:47+01:00	ERROR	orders	cleaning DB archive	{error: ordersdb: database is locked, errorVerbose: ordersdb: database is locked\n\tstorj.io/storj/storagenode/storagenodedb.(ordersDB).CleanArchive:325\n\tstorj.io/storj/storagenode/orders.(Service).CleanArchive:157\n\tstorj.io/storj/storagenode/orders.(Service).Run.func2:141\n\tstorj.io/common/sync2.(Cycle).Run:160\n\tstorj.io/common/sync2.(Cycle).Start.func1:77\n\tgolang.org/x/sync/errgroup.(Group).Go.func1:75}
2023-11-18T11:10:47+01:00	INFO	piecestore	download canceled	{Piece ID: NLIPOV7PI6VJD7QJ3OFNJUE7PKI45UWCYPNSB5ND2GR3MSZHKL7A, Satellite ID: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs, Action: GET, Offset: 0, Size: 0, Remote Address: 138.2.135.177:40288}
2023-11-18T11:10:47+01:00	INFO	piecestore	download canceled	{Piece ID: QZSZCMGE6RGYOMLZ46VSTFZX3RZASGK2W4S3FZ7UAOUWE2LMAWPA, Satellite ID: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs, Action: GET, Offset: 0, Size: 0, Remote Address: 130.162.246.56:47940}
2023-11-18T11:10:47+01:00	INFO	piecestore	upload canceled	{Piece ID: 5HRB5WNKBMV467N42MCDL3K7DWC6TPIFN2JYLVUXB32RZ7XDM5JQ, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Size: 458752, Remote Address: 79.127.220.98:52490}
2023-11-18T11:10:47+01:00	INFO	piecestore	download canceled	{Piece ID: VI3FFO6XKQ4EXA2NXCDODFHEIZLOSII65YR2LQT6VMAOQGVRU6LQ, Satellite ID: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs, Action: GET, Offset: 1011968, Size: 0, Remote Address: 130.162.246.56:34682}
2023-11-18T11:10:47+01:00	INFO	piecestore	download canceled	{Piece ID: 5I2WJB4ND3QO72HUMHEYUP6TRVLZZMV45PXMEO4AI6NZWBENXXQQ, Satellite ID: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs, Action: GET, Offset: 0, Size: 0, Remote Address: 130.162.246.56:38100}
2023-11-18T11:10:47+01:00	INFO	piecestore	download started	{Piece ID: 5I2WJB4ND3QO72HUMHEYUP6TRVLZZMV45PXMEO4AI6NZWBENXXQQ, Satellite ID: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs, Action: GET, Offset: 0, Size: 256, Remote Address: 130.162.246.56:38100}
2023-11-18T11:10:47+01:00	INFO	piecestore	download canceled	{Piece ID: 5I2WJB4ND3QO72HUMHEYUP6TRVLZZMV45PXMEO4AI6NZWBENXXQQ, Satellite ID: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs, Action: GET, Offset: 0, Size: 0, Remote Address: 130.162.246.56:38100}
2023-11-18T11:10:47+01:00	INFO	piecestore	upload canceled (race lost or node shutdown)	{Piece ID: JU4P6S2EVVCEMA4W7GEQMV6AUNSFCQTI6B5PWUHJR47TSIZGAKAQ}
2023-11-18T11:10:47+01:00	INFO	piecestore	download canceled	{Piece ID: RW2MUQUY3LFW3LX3LVEDYGGJCIGMKFOVF7J7RNMITX4GDNQ3HXMQ, Satellite ID: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs, Action: GET, Offset: 0, Size: 0, Remote Address: 130.162.246.56:47964}
2023-11-18T11:10:47+01:00	INFO	piecestore	upload canceled (race lost or node shutdown)	{Piece ID: EFP6Y3DPS6246U2ANWVAUVU2JEF54N22HGLYEIDCFLPRSDDROP3A}
2023-11-18T11:10:47+01:00	INFO	piecestore	download started	{Piece ID: RW2MUQUY3LFW3LX3LVEDYGGJCIGMKFOVF7J7RNMITX4GDNQ3HXMQ, Satellite ID: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs, Action: GET, Offset: 0, Size: 256, Remote Address: 130.162.246.56:47964}
2023-11-18T11:10:47+01:00	INFO	piecestore	upload started	{Piece ID: TNQPAKEG3ENOJM663LNVKTG5YQWXYFW35UB7Y5RFB374MRJ7FTYQ, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Available Space: 1226903266432, Remote Address: 5.161.143.41:15794}
2023-11-18T11:10:47+01:00	INFO	piecestore	upload started	{Piece ID: LCRS3TUILD2T4B2W5QTWMOADCZGHO5NVT22W3DRMUV5KBZH4Y74A, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Available Space: 1226903168128, Remote Address: 79.127.220.97:52176}
2023-11-18T11:10:47+01:00	INFO	piecestore	download canceled	{Piece ID: RW2MUQUY3LFW3LX3LVEDYGGJCIGMKFOVF7J7RNMITX4GDNQ3HXMQ, Satellite ID: 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs, Action: GET, Offset: 0, Size: 0, Remote Address: 130.162.246.56:47964}
2023-11-18T11:10:47+01:00	INFO	piecestore	upload canceled (race lost or node shutdown)	{Piece ID: BXCXWARCL5JMKNIE2FDCJT62XZADOSEW27IJOF4EN64K6USYUBQQ}
2023-11-18T11:10:47+01:00	INFO	piecestore	upload started	{Piece ID: V43MDR6XKGJSBYEDVCXQQWTYGOPUXB7R7LVBHJ2DJI73LE4S3GCQ, Satellite ID: 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S, Action: PUT, Available Space: 1226900905856, Remote Address: 5.161.77.10:8724}

Can you helpme ? Thanks a lot.

daki82 · November 19, 2023, 9:31pm

looks like there is some slow disk/to much iops problem.
consider moving the databases to an ssd (or flashdrive ( if available))

to save the sleeptime you can configure the service to restart after some min, when it fails.

any Fatal errors in the log?
what hardware?
What drive ?
and what clustersize ?
filesystem is it using?
how full is it?

how much fragmentation?

Alexey · November 20, 2023, 3:42am

Even this error related to a database will not stop the service, so you likely have a fatal error right before the service is stopped.
PowerShell:

sls fatal "C:\Program Files\Storj\Storage Node\storagenode.log" | select -last 10

Mimi · November 20, 2023, 12:18pm

Hello, thanks for your reply.
My node is on an (old) server Dell, in a Proxmox VM Windows 10 pro.
I attribute 2 cores, 4 GB RAM.
The disk is a usb 2.0 HD, NTFS, recent.
It’s a dedicated disk, with 500GB used for the node.
No fragmentation at this time.

Mimi · November 20, 2023, 12:19pm

Thanks for your help. I don’t see any “fatal error”. I am not at home, so, i post the résult of the powershell command as soon as possible.

daki82 · November 20, 2023, 3:04pm

do you have a type number?
what does recent mean?

you did just finish a defragmentation?

Mimi · November 20, 2023, 5:57pm

The result of “sls fatal “C:\Program Files\Storj\Storage Node\storagenode.log” | select -last 10” :

C:\Program Files\Storj\Storage Node\storagenode.log:2516025:2023-11-14T14:35:52+01:00 INFO piecestore uploaded{“Piece
ID”: “V76RMCW2YP5GFATAL46EPRBICNHSAZXZUHG5HRBOJW2PETQMBRHQ”, “Satellite ID”:
“12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “Action”: “PUT”, “Size”: 17408, “Remote Address”:
“5.161.176.200:22946”}
C:\Program Files\Storj\Storage Node\storagenode.log:2971080:2023-11-16T05:59:22+01:00 FATAL Unrecoverable error
{“error”: “filewalker: CreateFile E:\DATA STORJ\blobs\ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa\3l\3tdp
r2xehzlge5gb3nhsoj7f6jcsy6fwpa5dlaaosiyv5xsefq.sj1: Le fichier ou le répertoire est endommagé et illisible.;
filewalker: CreateFile E:\DATA STORJ\blobs\v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa\fe\wmb4klel4uavs7t
cx5c5epve6anebdr7abowvppjr3i4psqvjq.sj1: Le fichier ou le répertoire est endommagé et illisible.”, “errorVerbose”:
“group:\n— filewalker: CreateFile E:\DATA STORJ\blobs\ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa\3l\3t
dpr2xehzlge5gb3nhsoj7f6jcsy6fwpa5dlaaosiyv5xsefq.sj1: Le fichier ou le répertoire est endommagé et illisible.\n\tstorj.
io/storj/storagenode/pieces.(*FileWalker).WalkSatellitePieces:69\n\tstorj.io/storj/storagenode/pieces.(*FileWalker).Wal
kAndComputeSpaceUsedBySatellite:74\n\tstorj.io/storj/storagenode/pieces.(*Store).SpaceUsedTotalAndBySatellite:726\n\tst
orj.io - This website is for sale! - orj Resources and Information.\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2.1:87\n\tr
untime/pprof.Do:51\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2:86\n\tgolang.org/x/sync/errgroup.(*Group).Go.
func1:75\n— filewalker: CreateFile E:\DATA STORJ\blobs\v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy44mqqaaaaaaa\fe\w
mb4klel4uavs7tcx5c5epve6anebdr7abowvppjr3i4psqvjq.sj1: Le fichier ou le répertoire est endommagé et illisible.\n\tstorj
.io/storj/storagenode/pieces.(*FileWalker).WalkSatellitePieces:69\n\tstorj.io/storj/storagenode/pieces.(*FileWalker).Wa
lkAndComputeSpaceUsedBySatellite:74\n\tstorj.io/storj/storagenode/pieces.(*Store).SpaceUsedTotalAndBySatellite:726\n\ts
torj.io/storj/storagenode/pieces.(*CacheService).Run:57\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2.1:87\n\t
runtime/pprof.Do:51\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2:86\n\tgolang.org/x/sync/errgroup.(*Group).Go
.func1:75”}
C:\Program Files\Storj\Storage Node\storagenode.log:2995819:2023-11-16T20:53:49+01:00 FATAL Unrecoverable error
{“error”: “filewalker: open E:\DATA STORJ\blobs\qstuylguhrn2ozjv4h2c6xpxykd622gtgurhql2k7k75wqaaaaaa\ag: Le
fichier ou le répertoire est endommagé et illisible.; filewalker: CreateFile E:\DATA STORJ\blobs\ukfu6bhbboxilvt7jrw
lqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa\3l\3tdpr2xehzlge5gb3nhsoj7f6jcsy6fwpa5dlaaosiyv5xsefq.sj1: Le fichier ou le
répertoire est endommagé et illisible.; filewalker: CreateFile E:\DATA STORJ\blobs\v4weeab67sbgvnbwd5z7tweqsqqun7qox
2agpbxy44mqqaaaaaaa\fe\wmb4klel4uavs7tcx5c5epve6anebdr7abowvppjr3i4psqvjq.sj1: Le fichier ou le répertoire est
endommagé et illisible.”, “errorVerbose”: “group:\n— filewalker: open E:\DATA
STORJ\blobs\qstuylguhrn2ozjv4h2c6xpxykd622gtgurhql2k7k75wqaaaaaa\ag: Le fichier ou le répertoire est endommagé et il
lisible.\n\tstorj.io/storj/storagenode/pieces.(*FileWalker).WalkSatellitePieces:69\n\tstorj.io/storj/storagenode/pieces
.(*FileWalker).WalkAndComputeSpaceUsedBySatellite:74\n\tstorj.io/storj/storagenode/pieces.(*Store).SpaceUsedTotalAndByS
atellite:726\n\tstorj.io/storj/storagenode/pieces.(*CacheService).Run:57\n\tstorj.io/storj/private/lifecycle.(*Group).R
un.func2.1:87\n\truntime/pprof.Do:51\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2:86\n\tgolang.org/x/sync/err
group.(*Group).Go.func1:75\n— filewalker: CreateFile E:\DATA STORJ\blobs\ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sj
xvw5qaaaaaa\3l\3tdpr2xehzlge5gb3nhsoj7f6jcsy6fwpa5dlaaosiyv5xsefq.sj1: Le fichier ou le répertoire est endommagé et i
llisible.\n\tstorj.io/storj/storagenode/pieces.(*FileWalker).WalkSatellitePieces:69\n\tstorj.io/storj/storagenode/piece
s.(*FileWalker).WalkAndComputeSpaceUsedBySatellite:74\n\tstorj.io/storj/storagenode/pieces.(*Store).SpaceUsedTotalAndBy
Satellite:726\n\tstorj.io/storj/storagenode/pieces.(*CacheService).Run:57\n\tstorj.io/storj/private/lifecycle.(*Group).
Run.func2.1:87\n\truntime/pprof.Do:51\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2:86\n\tgolang.org/x/sync/er
rgroup.(*Group).Go.func1:75\n— filewalker: CreateFile E:\DATA STORJ\blobs\v4weeab67sbgvnbwd5z7tweqsqqun7qox2agpbxy
44mqqaaaaaaa\fe\wmb4klel4uavs7tcx5c5epve6anebdr7abowvppjr3i4psqvjq.sj1: Le fichier ou le répertoire est endommagé et
illisible.\n\tstorj.io/storj/storagenode/pieces.(*FileWalker).WalkSatellitePieces:69\n\tstorj.io/storj/storagenode/piec
es.(*FileWalker).WalkAndComputeSpaceUsedBySatellite:74\n\tstorj.io/storj/storagenode/pieces.(*Store).SpaceUsedTotalAndB
ySatellite:726\n\tstorj.io/storj/storagenode/pieces.(*CacheService).Run:57\n\tstorj.io/storj/private/lifecycle.(*Group)
.Run.func2.1:87\n\truntime/pprof.Do:51\n\tstorj.io/storj/private/lifecycle.(*Group).Run.func2:86\n\tgolang.org/x/sync/e
rrgroup.(*Group).Go.func1:75”}
C:\Program Files\Storj\Storage Node\storagenode.log:3127101:2023-11-17T15:52:31+01:00 FATAL Unrecoverable error
{“error”: “piecestore monitor: timed out after 1m0s while verifying writability of storage directory”, “errorVerbose”:
“piecestore monitor: timed out after 1m0s while verifying writability of storage directory\n\tstorj.io/storj/storagenod
e/monitor.(*Service).Run.func2.1:176\n\tstorj.io/common/sync2.(Cycle).Run:160\n\tstorj.io/storj/storagenode/monitor.(
Service).Run.func2:165\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75”}
C:\Program Files\Storj\Storage Node\storagenode.log:3184783:2023-11-17T23:31:57+01:00 FATAL Unrecoverable error
{“error”: “piecestore monitor: timed out after 1m0s while verifying writability of storage directory”, “errorVerbose”:
“piecestore monitor: timed out after 1m0s while verifying writability of storage directory\n\tstorj.io/storj/storagenod
e/monitor.(*Service).Run.func2.1:176\n\tstorj.io/common/sync2.(Cycle).Run:160\n\tstorj.io/storj/storagenode/monitor.(
Service).Run.func2:165\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75”}
C:\Program Files\Storj\Storage Node\storagenode.log:3277544:2023-11-18T13:39:38+01:00 INFO piecestore upload started
{“Piece ID”: “ELJQBXOGRQYPMVYQOS3QQMFATAL7JRGBIH4BP7XXD2OUF2HE2LFQ”, “Satellite ID”:
“12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “Action”: “PUT”, “Available Space”: 1224727868800, “Remote
Address”: “79.127.220.97:50984”}
C:\Program Files\Storj\Storage Node\storagenode.log:3277581:2023-11-18T13:39:47+01:00 INFO piecestore upload canceled
(race lost or node shutdown) {“Piece ID”: “ELJQBXOGRQYPMVYQOS3QQMFATAL7JRGBIH4BP7XXD2OUF2HE2LFQ”}
C:\Program Files\Storj\Storage Node\storagenode.log:3280770:2023-11-18T13:55:40+01:00 FATAL Unrecoverable error
{“error”: “piecestore monitor: timed out after 1m0s while verifying readability of storage directory”, “errorVerbose”:
“piecestore monitor: timed out after 1m0s while verifying readability of storage directory\n\tstorj.io/storj/storagenod
e/monitor.(*Service).Run.func1.1:152\n\tstorj.io/common/sync2.(Cycle).Run:160\n\tstorj.io/storj/storagenode/monitor.(
Service).Run.func1:141\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75”}
C:\Program Files\Storj\Storage Node\storagenode.log:3285880:2023-11-18T18:49:12+01:00 FATAL Unrecoverable error
{“error”: “open E:\DATA STORJ\trash: Le chemin d’accès spécifié est introuvable.”}
C:\Program Files\Storj\Storage Node\storagenode.log:3296455:2023-11-18T21:01:01+01:00 FATAL Unrecoverable error
{“error”: “piecestore monitor: timed out after 1m0s while verifying writability of storage directory”, “errorVerbose”:
“piecestore monitor: timed out after 1m0s while verifying writability of storage directory\n\tstorj.io/storj/storagenod
e/monitor.(*Service).Run.func2.1:176\n\tstorj.io/common/sync2.(Cycle).Run:160\n\tstorj.io/storj/storagenode/monitor.(
Service).Run.func2:165\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75”}

And i have fatal error ; i made a chkdsk /r, the result is :

Étape 4 : Recherche de clusters incorrects dans les données des fichiers utilisateur…
Erreur lecture disquec000000e e fin reste : 31:29:17
Espace disque insuffisant pour remplacer les clusters endommagés
détectés dans le fichier 717A8 nommé .
An unspecified error occurred (6e74667363686b2e b75). e fin reste : 31:29:18 .
An unspecified error occurred (6e74667363686b2e 17b4).

What can i do ? Thanks

daki82 · November 20, 2023, 9:11pm

looks bad. write and read timeouts aside.

what does the dashboard say? audits failing?
can you get S.M.A.R.T data?

is this a 500 gb full disk? without 10%reserve free?
if audits failing:
likely uninstall storj, generate a new identity, replace the disk with a used/new drive 8TB (cmr) or bigger.

if no audits are failing, you can try to stop the node, move/clone the data and adapt the path in the yaml. then restart the node.

Alexey · November 21, 2023, 3:17am

You filesystem is corrupted. Please stop the node either from the Services applet or from the elevated PowerShell:

Stop-Service storagenode

and check and fix errors on your disk with the command (as an Administrator):

chkdsk e: /f /r /x

Perhaps you need to run it several times until all errors will be fixed. Then you can start the node back

Start-Service storagenode

and check errors in the logs.

Mimi · November 22, 2023, 12:14pm

Thanks for your reply. I check the disk with this command lines.

Mimi · November 22, 2023, 12:15pm

Thanks for your reply. Audits failing. I try the solution of Alexey.

daki82 · November 22, 2023, 4:42pm

Wish you luck.
If you have questions, feel free to ask.

JWvdV · November 22, 2023, 7:10pm

For how long this node has run well?
I mean, USB 2.0 disk sounds like ‘worse than even a micro-SDXC’ nowadays. Probably you also have to limit concurrent requests, to for example 2 (to prevent too many concurrent random writes, which inherently are slow and choke your HD).

Alexey · November 23, 2023, 2:16am

Not needed. Firstly they need to fix a broken filesystem. The next - add an external power supply to their HDD, then monitor how is it perform.