Error with blockchain after abnormal shutdown about monero HOT 7 CLOSED

A useful flag here might be might be:

--block-sync-size=x

where x is the number of blocks to write to disk at once. Default is only 100, but even with full blocks setting it to 500 would only be 150 MB sync'd at a time.

I think you can do something similar but measured in bytes with something like:

--db-sync-mode=safe:sync:250000000bytes

250000000 bytes (~250 MB) is the default here so I'm not 100% how it relates to the block-sync-size, if it just uses whichever number is smaller, or if these are in fact slightly different settings.

Anyway, playing around with these settings may help with HDD syncing speed

edit: this is more of a support thing but I'm not sure the DB is actually corrupted, though with an abnormal shutdown it is likely. But the logs given are wallet logs, not daemon logs, and when you run monerod.exe the issue very likely is that you did not tell it about your custom blockchain location, so it starts over from scratch at the default location. You will need to start it from the command line using something like:

monerod.exe --data-dir D:\path\to\folder\containing\lmdb\and\p2pstate.bin\

then report back with whatever output that gives you

from monero.

Did your system crash / have power loss / force shutdown during sync? If yes it likely means your blockchain is corrupted. You have to delete it any resync from scratch.

from monero.

Did your system crash / have power loss / force shutdown during sync? If yes it likely means your blockchain is corrupted. You have to delete it any resync from scratch.

Why make such an unreliable system? Why can't I just cut the file to the point where the data is intact and continue downloading? Why didn’t the developers even want to organize blockchain downloads using the torrent file method? I downloaded some 110 GB for 12 days...

from monero.

Why make such an unreliable system?

You can set the database to --db-sync-mode safe, then it won't corrupt on a crash but it will also sync slower.

We currently use the fast sync method for the initial blockchain sync and switch over to the safe sync method once the blockchain is fully downloaded and verified.

Why can't I just cut the file to the point where the data is intact and continue downloading?

Because it's a database with a complex internal structure, not a sequential file that can be simply cut at a specific point.

Why didn’t the developers even want to organize blockchain downloads using the torrent file method? I downloaded some 110 GB for 12 days...

We already use a P2P system to download the blockchain, using torrent for this doesn't make sense.

If you have a fast SSD you can sync up in less than 24h, I assume you use an HDD, that's why you are syncing up so slowly.

from monero.

Why didn’t the developers even want to organize blockchain downloads using the torrent file method? I downloaded some 110 GB for 12 days...

We already use a P2P system to download the blockchain, using torrent for this doesn't make sense.

If you have a fast SSD you can sync up in less than 24h, I assume you use an HDD, that's why you are syncing up so slowly.

My HDD can to write 160MB/s, my 5G-Wi-Fi can to download 20MB/s, but the blockchain was downloaded average on ~100KB/s.

Why can't I just cut the file to the point where the data is intact and continue downloading?

Because it's a database with a complex internal structure, not a sequential file that can be simply cut at a specific point.

I thought that blockchain has structure as BLOCK_1-NONSE_1-BLOCK_2-NONSE_2..., where SHA256 after each nonse lower some value. This file could be trimmed to the last NONSE...

from monero.

My HDD can to write 160MB/s, my 5G-Wi-Fi can to download 20MB/s, but the blockchain was downloaded average on ~100KB/s.

Your download speed is mostly irrelevant because it's not the bottleneck, you don't just download but also simultanouly verify the blockchain. This is the resource intensive part that requires a disk with fast random IO speeds. SSDs are ideal for this, a HDD will be slow.

from monero.

I thought that blockchain has structure as BLOCK_1-NONSE_1-BLOCK_2-NONSE_2..., where SHA256 after each nonse lower some value. This file could be trimmed to the last NONSE...

What you are describing is a simplified conceptual data structure for a blockchain, in real-world applications this is more complex.

We use LMDB (B-tree internally) to store the blockchain data. It's simply not possible to cut the database file like you are suggesting.

from monero.