I mistakely deleted all .db files / No used Space in Dashboard

[Paku]

Hi everyone,

I hope someone can help me.
i mistakely deleted all .db files. After that i restartet the Node and all .db files where new created.
The node is now running again and and seems to be ok.

• SATUS: Online
• QUIC: OK
  
  

But i have approx. 6.4TB of Data, allocated are approx. 10 TB
The node is now running for about 14 H and shows only about. 15 GB in the Dashboard.

Is there a way to make the dashboard show the correct used value again?
or do I have to start from scratch?

The log file says a lot of Info Message except for:

on start up:

WARN piecestore:monitor Disk space is less than requested. Allocated space is {“bytes”: 7384090361856}

ERROR blobscache trashTotal < 0 {“trashTotal”: -4719104}

ERROR blobscache satPiecesTotal < 0 {“satPiecesTotal”: -1536}
ERROR blobscache satPiecesContentSize < 0 {“satPiecesContentSize”: -1024}

during operation, now and then an error message like this:

ERROR piecestore download failed

ERROR piecestore upload failed

[jammerdan]

@Paku

Is there a way to make the dashboard show the correct used value again?

Wrong used & remaining disk space

I think you’re just seeing new incoming data be accounted for. The file walker will update the total once it’s done all at once. Not gradually.

So if all your databases are back you probably simply have to wait until recalculations are complete.

[Paku]

Hello and thank you for the quick response and answer.

How long can the recalculation take?
Days or months?

Or do I have to change this line so that the recalculation is executed at startup ?

Thanks in Advance

[jammerdan]

@Paku

Or do I have to change this line so that the recalculation is executed at startup ?

Well spotted however execution of filewalker is enabled by default. So unless you have disabled it, there is no further action required.
Duration depends, hard to tell without details on your setup. From a couple of hours to a several days I’d say.

[nyancodex]

if you can get the solution for this then please tell me. I made the same mistake.

[Alexey]

@Paku

ERROR blobscache trashTotal < 0 {“trashTotal”: -4719104}

ERROR blobscache satPiecesTotal < 0 {“satPiecesTotal”: -1536}
ERROR blobscache satPiecesContentSize < 0 {“satPiecesContentSize”: -1024}

Looks like the same problem:

Wrong used & remaining disk space

I just did it. Same situation I don’t know why the filewalker not running. ingress stopped, only “downloaded”, no more “uploaded” filewalker still not running, no CPU usage and disk stats is still 0B for used space. these error messages keep showing in logs [image]

For some reason some piece sizes are calculated wrongly.

@Paku did you check your disk for errors? If not, please do it. If the checker would find errors and fix them, then you probably would need to recreate these two databases (please backup them first):

@Alexey

try to recreate the database piece_spaced_used.db.

@Alexey

Try also to recreate the pieceinfo.db database, but make a backup of it first.

[Paku]

First of all: thank you for your support

Will do this and let you know.

Thanks again!

[Paku]

Have now run the scan with “chkdsk T: /f”

Everything seems to be okey.

And checked my Databases:

every time I stop and restart the node, it starts from zero.

Dashboard is empty, only new traffic is shown until I stop the node = empty dashboard again.

piece_spaced_used.db. = 24KB not growing

additionally, here is the "storagenode-updater.log
there is something wrong??

[Alexey]

@Paku

every time I stop and restart the node, it starts from zero.

Dashboard is empty, only new traffic is shown until I stop the node = empty dashboard again.

You need to allow the filewalker to finish its job (let it run few days).

@Paku

additionally, here is the "storagenode-updater.log
there is something wrong??

nothing

Invalid configuration file key -error

These are messages from updater. And they are not errors. Log messages have different severity levels. Roughly: info, warning, error, fatal. These are merely an info ones. Updater uses same config file as node and just complains that it sees some settings that it doesn’t know. Nothing to worry about here. But… is your node not working? How can you tell? Can you access dashboard? What it shows?

[Paku]

Thank you for the effort and i will report.

[Paku]

ATTENTION:
We are back!!

Dashboard is now correct
and also survives a quit and restart

Thanks to @Alexey
Big thanks to everyone who helped here!!!

What was the solution? That’s a good question here!
And I can’t really answer that either.

For anyone who comes across this thread and has the same problem.

Node:
Win 10 version 1.77.2

My solution regarding the dashboard (does not recognize the existing data) was:

• Backup Identity folder ( Key and Cert )( just to be sure )
  APPDATA/Storj/Identity/storagenode

• Backup .DB files ( just to be sure )
  -do not touch the STORAGEDATAS

• uninstalled and deleted everything (.yaml / .json / .DBs etc) (but not the STORAGEDATAS and not the Identity Folder)

• also the hidden folders in Windows

• Reinstalling the node with the same information
  (paths / wallet address / email etc.)

• A really fresh new installation with existing Identity and Storage Files

• Start the Node

• Wait…

• After 45 hours everything was back.

[Alexey]

With this you just re-created all databases, so all steps (except backup) was not necessary, you might just use this instruction to recreate all databases: https://support.storj.io/hc/en-us/articles/4403032417044-How-to-fix-database-file-is-not-a-database-error

But the real question is - what databases should be only re-created to keep most of the history?
I thought that these ones should be enough:

Wrong used & remaining disk space

If you have checked your databases and found no issues, you could try to recreate the database piece_spaced_used.db. What’s filesystem by the way?

Wrong used & remaining disk space

Seems the filewalker is running. Try also to recreate the pieceinfo.db database, but make a backup of it first.

But seems I was wrong, we need also to re-create some other database, and I’m now wondering, which one?

@nyancodex have you succeed?

From the list of all databases

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----         4/27/2023   7:09 AM       48988160 bandwidth.db
-a----         4/26/2023   7:43 PM         131072 heldamount.db
-a----         4/11/2023   7:40 PM          16384 info.db
-a----         4/11/2023   7:40 PM          24576 notifications.db
-a----         4/11/2023   7:40 PM          32768 orders.db
-a----         4/11/2023   7:40 PM          24576 pieceinfo.db
-a----         4/27/2023   6:32 AM        9383936 piece_expiration.db
-a----         4/27/2023   6:22 AM          24576 piece_spaced_used.db
-a----         4/11/2023   7:40 PM          24576 pricing.db
-a----         4/27/2023   3:41 AM          36864 reputation.db
-a----         4/11/2023   7:40 PM          32768 satellites.db
-a----         4/23/2023   7:15 AM          24576 secret.db
-a----         4/26/2023   7:43 PM         786432 storage_usage.db
-a----         4/11/2023   7:40 PM          20480 used_serial.dB

perhaps only storage_usage.db may be enough to re-create, instead of these ones

-a----         4/11/2023   7:40 PM          24576 pieceinfo.db
-a----         4/27/2023   6:32 AM        9383936 piece_expiration.db
-a----         4/27/2023   6:22 AM          24576 piece_spaced_used.db

[nyancodex]

I’ll give a shot to recreate all databases.