datadir – New obtain of bitcoin core v28.0, use blocks which have already been downloaded to my machine?

How can I get [the current version] to make use of the blockchain knowledge which is already on my machine from [prior versions]

I consider the suitable course of is one thing like this:

1. Shut bitcoin-qt, bitcoind and so forth. Make backups. Examine backups.
2. Find the Blockchain knowledge.
   E.g sudo discover / -name blk00000.dat
3. Configure Bitcoin Core to make use of that location. vi $HOME/.bitcoin/bitcoin.conf if listing is not in default location the place bitcoin seems. See datadir and walletdir
4. If wanted, transfer a duplicate of vital pockets.dat to acceptable location. See current steerage.

For comparability, right here is the response for getblockchaininfo on a Bitcoin node that hasn’t been run for six months on a PC that has insufficient assets (100% disk utilization)

{
  "chain": "principal",
  "blocks": 849345,
  "headers": 869149,
  "bestblockhash": "0000000000000000000090dd75955aeb49fb6a51f259f3d6ee3c9639ce241ced",
  "issue": 83675262295059.91,
  "time": 1719257861,
  "mediantime": 1719254246,
  "verificationprogress": 0.9679465468853898,
  "initialblockdownload": true,
  "chainwork": "0000000000000000000000000000000000000000803db1ef35254b7ce5b55f8a",
  "size_on_disk": 660000239919,
  "pruned": false,
  "warnings": ""
}

I feel a key factor right here is the variety of blocks this system is aware of of.

This PC has a blocks folder with about 615 GB of knowledge in it and a chainstate folder with beneath 12 GB of knowledge in it.

Your equal data does assist your conclusion that this system is not seeing all of your knowledge. Possibly it has logged a motive why it is not utilizing all the information (e.g. some error message regarding a block file?)

Within the file debug.log I see

2024-11-05T18:22:16Z Bitcoin Core model v24.0.1 (launch construct)
2024-11-05T18:22:16Z InitParameterInteraction: parameter interplay: -listen=0 -> setting -upnp=0
2024-11-05T18:22:16Z InitParameterInteraction: parameter interplay: -listen=0 -> setting -natpmp=0
2024-11-05T18:22:16Z InitParameterInteraction: parameter interplay: -listen=0 -> setting -discover=0
2024-11-05T18:22:16Z InitParameterInteraction: parameter interplay: -listen=0 -> setting -listenonion=0
2024-11-05T18:22:16Z InitParameterInteraction: parameter interplay: -listen=0 -> setting -i2pacceptincoming=0
...
2024-11-05T18:22:25Z Default knowledge listing XXXXXXX/Bitcoin
2024-11-05T18:22:25Z Utilizing knowledge listing XXXXXXX/Bitcoin
2024-11-05T18:22:25Z Config file: XXXXXXX/Bitcoinbitcoin.conf
...
2024-11-05T18:22:47Z LoadBlockIndexDB: final block file = 4309
2024-11-05T18:22:48Z LoadBlockIndexDB: final block file information: CBlockFileInfo(blocks=84, dimension=126890608, heights=845620...845702, time=2024-05-29...2024-05-29)
2024-11-05T18:22:48Z Checking all blk information are current...
...

Notice the previous few traces above. You may must seek for the most recent incidence of those to verify that this system is definitely wanting within the place you instructed.

Your debug.log ought to present you the place Bitcoin core thinks your knowledge is positioned and this could enable you to work out what is occurring.

There could also be different error messages earlier within the debug.log that designate why this system wanted to do what it’s doing.