Order limit problem

Iam getting lot of this logs is it ok or i need to do something?

2026-09-10T14:40:25+03:00 ERROR piecestore could not get hash and order limit {“piece_id”: “4BDGAM4KU7WIXKVXU4ESCGBS7SHKMIM2QQDGE7P73L6ZZWNIJWJA”, “satellite_id”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “action”: “GET_REPAIR”, “offset”: 0, “size”: 11264, “remote_address”: “88.208.196.67:40070”, “error”: “footer length field too large: 40401 > 512”, “errorVerbose”: “footer length field too large: 40401 > 512\n\tstorj.io/storj/storagenode/piecestore.(*hashStoreReader).GetPieceHeader:693\n\tstorj.io/storj/storagenode/piecestore.pieceHashAndOrderLimitFromReader:16\n\tstorj.io/storj/storagenode/piecestore.(*Endpoint).Download:778\n\tstorj.io/common/pb.DRPCPiecestoreDescription.Method.func2:302\n\tstorj.io/drpc/drpcmux.(*Mux).HandleRPC:33\n\tstorj.io/common/rpc/rpctracing.(*Handler).HandleRPC:62\n\tstorj.io/common/experiment.(*Handler).HandleRPC:43\n\tstorj.io/drpc/drpcserver.(*Server).handleRPC:166\n\tstorj.io/drpc/drpcserver.(*Server).ServeOne:108\n\tstorj.io/drpc/drpcserver.(*Server).Serve.func2:156\n\tstorj.io/drpc/drpcctx.(*Tracker).track:35”}

This may be a data corruption, is audit score okay? Maybe you can check your drives health?

Can you paste the first 512 bytes of that file? Note, it will contain your node’s ID, so if you don’t want to, no worries.

In any case, this piece’s header is likely toast. Header is only used for GET_REPAIRs, so you may keep the file in hope that audits or regular GETs hit parts of the file that are still healthy. However, it will affect your scores, because failed repairs are counted in.

If you have many of these problems in different files, check your hardware. This is not supposed to happen.

I forgot on what node i have seen this, from my 100+ nodes, now I checking it all, I see about 3-4 nodes with this records, it just cant be that all is broken, checked the disks no error, RAM is with ECC. Scores are near 100%

I stiil searching this particular node.