3 day power outage to node now i am failing audits

had several days of no power to the storage node, i am passing online status however i am in suspension currently as i am getting hammered with this error. anyway to run a job to clean up the storage or something ? or will this process out at some point ?
2024-12-02T15:29:19-05:00 ERROR piecestore download failed {“Piece ID”: “6FZTA2OPDQ6EUNZDA7KDBMM57ZGNPVKA5OP6THY3VM5EZ7IYQOGA”, “Satellite ID”: “12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S”, “Action”: “GET”, “Offset”: 0, “Size”: 2319104, “Remote Address”: “79.127.226.105:56052”, “error”: “pieces error: filestore error: unable to open "J:\\blobs\\ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa\\6f\\zta2opdq6eunzda7kdbmm57zgnpvka5op6thy3vm5ez7iyqoga.sj1": The file or directory is corrupted and unreadable.”, “errorVerbose”: “pieces error: filestore error: unable to open "J:\\blobs\\ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa\\6f\\zta2opdq6eunzda7kdbmm57zgnpvka5op6thy3vm5ez7iyqoga.sj1": The file or directory is corrupted and unreadable.\n\tstorj.io/storj/storagenode/blobstore/filestore.(*Dir).Open:360\n\tstorj.io/storj/storagenode/blobstore/filestore.(*blobStore).Open:118\n\tstorj.io/storj/storagenode/pieces.(*Store).Reader:323\n\tstorj.io/storj/storagenode/piecestore.(*Endpoint).Download:762\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”}

Stop the node, run chkdsk /f j:. Then buy an UPS.

1 Like

check disk is having a party thats not good

house has power walls, …

1 Like

With all the NTFS fragility it’s still hard to imagine the power outage could screw it up so much. I’m wondering if there is some underlying hardware issue — such as faulty disk controller or bad ram.

No I know what the issue is. It’s a virtual box guest running on a hypervisor backed by btfrs… And that didn’t handle things very nicely. Ima let chkdsk run but I don’t have high hopes.

1 Like

:scream:

Why would not you run storagenode directly on the storage appliance, accessing btrfs sub volume natively? But I guess it’s a rhetorical question at this point…

1 Like

Unfortunately I’m agree with @arrogantrabbit

It started as a standalone windows device and I didn’t know how to convert it to Linux,

This way:

Specifically: