Does bitcoincore files are multi-platform?

[CryptoBuzzerd]

So, I've download bitcoincore and fully sync it on Windows. Works perfect, nice. Then I need to launch another bitcoincore node on a Linux instance, copied whole folder (blocks, chainstate, database, and all files near) to a Linux server, launched a node - and it starting to sync from scratch!  
And yes, I've checked path to datafiles, and also trying write in bitcoin.conf, and even -datadir="/user/path_to_btc_data" - anyway, it starts from scratch. Also, revert thing (fully synced datadir from Linux) - also can't "plug-n-play" on Windows. So, bitcoincore data files are not cross-platform? or #WhatI'mDoingWrong?

[1714792482]

1714792482

[1714792482]

1714792482

[1714792482]

1714792482

[Rath_]

So, bitcoincore data files are not cross-platform? or #WhatI'mDoingWrong?

They are cross-compatible. However, the node might need to reindex the blockchain data. It will take less time than as if you were downloading and verifying all the blocks again. What's the output of the following command?

bitcoin-cli getblockchaininfo

[CryptoBuzzerd]

So, bitcoincore data files are not cross-platform? or #WhatI'mDoingWrong?

They are cross-compatible. However, the node might need to reindex the blockchain data. It will take less time than as if you were downloading and verifying all the blocks again. What's the output of the following command?

bitcoin-cli getblockchaininfo

Code:

getblockchaininfo
{
  "chain": "main",
  "blocks": 606214,
  "headers": 606518,
  "bestblockhash": "0000000000000000000735977509db4c0e08990bdad5d7ed21f75ecebcbfaf8f",
  "difficulty": 12973235968799.78,
  "mediantime": 1575230540,
  "verificationprogress": 0.9984022636170466,
  "initialblockdownload": true,
  "chainwork": "00000000000000000000000000000000000000000a83fdb870fa81f26e11ed3b",
  "size_on_disk": 286042855590,
  "pruned": false,
  "softforks": [
    {
      "id": "bip34",
      "version": 2,
      "reject": {
        "status": true
      }
    },
    {
      "id": "bip66",
      "version": 3,
      "reject": {
        "status": true
      }
    },
    {
      "id": "bip65",
      "version": 4,
      "reject": {
        "status": true
      }
    }
  ],
  "bip9_softforks": {
    "csv": {
      "status": "active",
      "startTime": 1462060800,
      "timeout": 1493596800,
      "since": 419328
    },
    "segwit": {
      "status": "active",
      "startTime": 1479168000,
      "timeout": 1510704000,
      "since": 481824
    }
  },
  "warnings": ""
}

That is all I get.

[HCP]

Based on that output, it seems that your node believes that it has 606214 blocks synced... and there are 606518 headers, so it needs to download another 304 blocks. (hence the 99.84% verification progress)

Given that there has been about 2 weeks from your original post to this update... I'm assuming it just continued syncing during those 2 weeks? At this stage, it's kinda pointless attempting to troubleshoot why it didn't accept the data files that you copied over... as it is now pretty much fully synced. Unless, you're planning on trying to copy data files again to another new node?

[CryptoBuzzerd]

Yes, I'm planning finished sync and copy it to my PI device, on Ubuntu. How to prepare blockchain to it?

[Rath_]

Yes, I'm planning finished sync and copy it to my PI device, on Ubuntu. How to prepare blockchain to it?

Since you are currently syncing another node on Linux, it shouldn't need to reindex again once you move it to your Raspberry Pi. Copy the same files from your Linux node as you previously did from the Windows machine.

[Jet Cash]

I'm not sure why you are having problems. I have a node under Windows 10, and one under Ubuntu. When I started the Ubuntu one, I copied the blockchain and wallet data from the Windows machine onto an external SSD ( the Netbook doesn't have a large enough drive internally ), and I downloaded and installed the core software. When I started it for the first time, it asked me for the directory to use. I pointed it at the SSD, and it picked it up happily, and it sync'd a few recent blocks, and reported everything as fine. It really was pretty painless, but that was a while ago.

[CryptoBuzzerd]

I'm not sure why you are having problems. I have a node under Windows 10, and one under Ubuntu. When I started the Ubuntu one, I copied the blockchain and wallet data from the Windows machine onto an external SSD ( the Netbook doesn't have a large enough drive internally ), and I downloaded and installed the core software. When I started it for the first time, it asked me for the directory to use. I pointed it at the SSD, and it picked it up happily, and it sync'd a few recent blocks, and reported everything as fine. It really was pretty painless, but that was a while ago.

In theory, everything was as it should be, but I ran into problems that I can’t determine, so I tried to find out if I correctly understand the theoretical capabilities of the Bitcoin wallet. In theory, I'm right, let's see what practice shows. Really thanks to everyone who participated in the discussion, your thoughts are very valuable to me. I’ll talk about the results a bit later.

[DaveF]

How did you copy the files FTP / SMB / other?
They are cross compatible but permissions can cause a problem now and then. I don't know why but they do.

Also, from the Dave was not paying attention department, did you shutdown the windows install when you copied the files?
I have had that in a windows to windows copy when I did not shut down the node before the copy it did not see the files for some reason.

It should not matter but as we all know, should not and does not are different.

-Dave

[CryptoBuzzerd]

How did you copy the files FTP / SMB / other?
They are cross compatible but permissions can cause a problem now and then. I don't know why but they do.

No, I've copy it via linking external HDD to target PC. But you right, need to check files permissions while doing that

Also, from the Dave was not paying attention department, did you shutdown the windows install when you copied the files?
I have had that in a windows to windows copy when I did not shut down the node before the copy it did not see the files for some reason.

It should not matter but as we all know, should not and does not are different.

-Dave

Shure I always shutdown Bitcoincore before doing ANY manipulations with blockchain. It is one of the MOST rules all need to know about ANY full-crypto wallet

[CryptoBuzzerd]

This problem was little deeper - users on Windows and Linux are the same, but NTFS file system do not store permissions for linux (as I know). Will look little later - now syncing continuing.