One of docker node has gone offline with strange reason

[Alexey]

@Aka985

Is it normal?

Using HDD - yes. If you could use docker with a temporary RAM disk, then it would be faster, but you need to have 2x amount of RAM for the size of the restoring database.
See

Used_serial.db malformed

It’s much simpler than you thought: docker run -it --rm --mount type=tmpfs,destination=/ramdisk,tmpfs-size=1.5G --mount type=bind,src=Y:\storagenode2\storage\,dst=/data sstc/sqlite3 sh /data # cp used_serial.db /ramdisk/ /data # sqlite3 /ramdisk/used_serial.db sqlite> .mode insert sqlite> .output /ramdisk/dump_all.sql sqlite> .dump sqlite> .exit /data # rm /ramdisk/used_serial.db /data # cat /ramdisk/dump_all.sql | grep -v TRANSACTION | grep -v ROLLBACK | grep -v COMMIT >/ramdisk/dump_all_notra…

@Aka985

Location of file is:

but you use

@Aka985

Get-ChildItem F:\StorjD4.3\storage\

instead of

Get-ChildItem F:\Storj4.3\storage\

The same problem here:

@Aka985

further commands this file shall be recreated if I understood right.

the path F:\StorjD4.3\bandwidth.db doesn’t exist, because the actual path is F:\Storj4.3\storage\bandwidth.db

You may use TAB key to finish typing path, i.e. start with f:\Sto then press TAB on your keyboard, it should ether finish the path or give you a suggestion. Or you may just copy path from the Explorer and paste it to the terminal.