Ok, but from where is G:\Storj\blobs and database files in the G:\Storj\?
To fix the orders.db:
Stop the storagenode
Remove the G:\Storj\storage\orders.db
Execute
sqlite3 G:\Storj\storage\orders.db
CREATE TABLE unsent_order (
satellite_id BLOB NOT NULL,
serial_number BLOB NOT NULL,
order_limit_serialized BLOB NOT NULL, -- serialized pb.OrderLimit
order_serialized BLOB NOT NULL, -- serialized pb.Order
order_limit_expiration TIMESTAMP NOT NULL, -- when is the deadline for sending it
uplink_cert_id INTEGER NOT NULL,
FOREIGN KEY(uplink_cert_id) REFERENCES certificate(cert_id)
);
CREATE TABLE order_archive_ (
satellite_id BLOB NOT NULL,
serial_number BLOB NOT NULL,
order_limit_serialized BLOB NOT NULL,
order_serialized BLOB NOT NULL,
uplink_cert_id INTEGER NOT NULL,
status INTEGER NOT NULL,
archived_at TIMESTAMP NOT NULL,
FOREIGN KEY(uplink_cert_id) REFERENCES certificate(cert_id)
);
CREATE UNIQUE INDEX idx_orders ON unsent_order(satellite_id, serial_number);
CREATE TABLE versions (version int, commited_at text);
.exit
I checked Storj/blobs and it looks like that folder is empty currently while storj/storage/blobs has 6 folders.
I ran what you typed in and it encountered errors at order_serialized BLOB NOT NULL, – serialized pb.Order during unsent_order:
At line:4 char:91
+ ... order_limit_serialized BLOB NOT NULL, -- seri ...
+ ~
Missing expression after ',' in pipeline element.
At line:4 char:119
+ ... rder_limit_serialized BLOB NOT NULL, -- serialized pb.OrderLimit
+ ~
Missing closing ')' in expression.
At line:5 char:91
+ ... order_serialized BLOB NOT NULL, -- seri ...
+ ~
Missing expression after ',' in pipeline element.
+ CategoryInfo : ParserError: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : MissingExpression
Seems to be running fine now after doing that, here’s the output from the log.
2020-08-01T13:22:57.379-0500 INFO Telemetry enabled
2020-08-01T13:22:57.386-0500 INFO db.migration.27 Add index archived_at to ordersDB
2020-08-01T13:22:57.424-0500 INFO db.migration Database Version {"version": 43}
2020-08-01T13:22:58.386-0500 INFO preflight:localtime start checking local system clock with trusted satellites' system clock.
2020-08-01T13:22:59.255-0500 INFO preflight:localtime local system clock is in sync with trusted satellites' system clock.
2020-08-01T13:22:59.256-0500 INFO bandwidth Performing bandwidth usage rollups
2020-08-01T13:22:59.257-0500 INFO Node 12CMjYzRsLfx6GAjMTPg9JQ8sJWwpTuDNmVUEMR1Kavd77pgMpv started
2020-08-01T13:22:59.257-0500 INFO Public server started on [::]:28967
2020-08-01T13:22:59.257-0500 INFO Private server started on 127.0.0.1:7778
2020-08-01T13:22:59.259-0500 INFO trust Scheduling next refresh {"after": "3h40m56.956315756s"}
Based on the total disk space module on the dashboard, it seems to be successfully grabbing everything correctly.
I guess you were previously running an older version. This file was added in a database migration step. What you did was the correct way to fix this.
This is because we had to recreate the piece_spaced_used.db. There is no loss of data for that since the node walks the pieces to see how much space is used. That just takes some time after boot, hence why it showed as empty until that was done.
