Fun & learning with Electrum EPS, Electrum wallet & Bitcoin Core QT on Linux

[arabspaceship123]

Thanks I received support in other topics like Fun & learning with Electrum EPS, Electrum wallet & Bitcoin Core QT in Win 11

Now I'll test Electrum EPS, Electrum wallet & Bitcoin Core on Linux. I'll use a comp with Linux I won't use Virtualbox. I'd like to get advice for migrating Bitcoin blocks to Linux first. I don't want to download the blocks because I've got them on Win 11 SSD I'll copy the Bitcoin folder to Linux.

Successful migration is Electrum EPS working with Linux. If EPS isn't compatible with Linux I'll use Bitcoin Core QT to test with Electrum wallet.

[DireWolfM14]

I don't want to download the blocks because I've got them on Win 11 SSD I'll copy the Bitcoin folder to Linux.

As long as you're logged into the Linux machine with the same user account you'll be using to run Bitcoin you shouldn't have any issues.  The only concern is if the file permissions aren't copied over to the new machine appropriately with the correct ownership.  As long as you pay attention to that and make sure the file paths are set correctly, you shouldn't have any problems.

Successful migration is Electrum EPS working with Linux. If EPS isn't compatible with Linux I'll use Bitcoin Core QT to test with Electrum wallet.

I've never used EPS, but it looks like the binaries are only available for Windows.  If you're comfortable compiling the source code, you may be able to get to work on Linux.  Otherwise, I recommend using Romanz Electrs if your disk space is limited, or Fulcrum if you have extra storage.

[Yamane_Keto]

1. copy the blocks, chainstate, and indexes folders (It's best to be careful with wallet.dat and copy it) from %APPDATA%\Bitcoin  to the new Linux data directory
2. restart the Linux node
3. Download Electrum Personal Server from the official GitHub.
4. Copy the sample configuration file: cp config.ini_sample config.ini
5. somtimes you may need to update your path using echo 'PATH=$HOME/.local/bin:$PATH' >> ~/.profile
6. electrum-personal-server config.ini

[nc50lc]

Now I'll test Electrum EPS, Electrum wallet & Bitcoin Core on Linux.

Since it's been a few years now, you might reconsider "Electrum EPS" since it's now abandoned by its developer.
By the way, EPS stands for "Electrum Personal Server", so by saying Electrum EPS, you're saying "Electrum Electrum Personal Server".

You have a few other options like Electrs and Fulcrum.
The former is quite lightweight and doesn't require txindex but not as light as EPS since it builds its own database while the latter has better performance but has tighter requirements.

For the Bitcoin Core's datadir, copying the directory's contents should work as mentioned by others.
But I'm concerned on the issue in your old Windows setup where it returns with errors when using --txindex and the corrupted block indicated in your logs.
But it works anyways since txindex isn't required by EPS.
Let's see if it's just a fluke.

[arabspaceship123]

I've never used EPS, but it looks like the binaries are only available for Windows.  If you're comfortable compiling the source code, you may be able to get to work on Linux.  Otherwise, I recommend using Romanz Electrs if your disk space is limited, or Fulcrum if you have extra storage.

I like Romanz Electrs git page. I will use Electrs if I use a small SSD.

3. Download Electrum Personal Server from the official GitHub.

Windows binaries are a problem in Linux.

For the Bitcoin Core's datadir, copying the directory's contents should work as mentioned by others.
But I'm concerned on the issue in your old Windows setup where it returns with errors when using --txindex and the corrupted block indicated in your logs.
But it works anyways since txindex isn't required by EPS.
Let's see if it's just a fluke.

It was a concern on Win 11. There was the error in Bitcoin Core 30 after I terminated the update in task manager. It was fine to function after using Bitcoin Core 26 like it was before upgrade.

[nc50lc]

But I'm concerned on the issue in your old Windows setup where it returns with errors when using --txindex and the corrupted block indicated in your logs.

It was a concern on Win 11. There was the error in Bitcoin Core 30 after I terminated the update in task manager. It was fine to function after using Bitcoin Core 26 like it was before upgrade.

Interesting, a corrupted block detected in v30 yet it works in v26.
That may had been an unknown issue in Bitcoin Core or it's a silent/undetected error in v26 that's fixed in the later versions.

Nevertheless, please update if that datadir works in your new Linux setup.

[arabspaceship123]

Interesting, a corrupted block detected in v30 yet it works in v26.
That may had been an unknown issue in Bitcoin Core or it's a silent/undetected error in v26 that's fixed in the later versions.

Nevertheless, please update if that datadir works in your new Linux setup.

Bitcoin Core should fail indexing if a block is corrupted. On Win 11 it gave the corrupt error after closing Bitcoin Core 30 with end task in the task manager because Bitcoin Core 30 upgrade was slow 40 minute later. Win 11 loads Bitcoin Core 26 index without error.

I will test Linux on 256GB SSD. My Bitcoin folder blockchain will be on SSD on USB. Where in the Linux SSD can I copy the Win 11 %APPDATA% Bitcoin folder?

[nc50lc]

I will test Linux on 256GB SSD. My Bitcoin folder blockchain will be on SSD on USB. Where in the Linux SSD can I copy the Win 11 %APPDATA% Bitcoin folder?

Anywhere since it's not the internal SSD,

During Bitcoin Core's first install launch (GUI's Welcome Screen), make sure to point the datadir to that directory.
Or you can keep the default datadir settings but set a datadir=<path> config in your bitcoin.conf file (in the default datadir) and point it to the copied bitcoin datadir.

The latter is easier to manage and works in bitcoind.

[arabspaceship123]

Anywhere since it's not the internal SSD,

During Bitcoin Core's first install launch (GUI's Welcome Screen), make sure to point the datadir to that directory.
Or you can keep the default datadir settings but set a datadir=<path> config in your bitcoin.conf file (in the default datadir) and point it to the copied bitcoin datadir.

The latter is easier to manage and works in bitcoind.

Thanks I will locate it in the internal SSD during the first install. The external SSD will store the blockchain in the Bitcoin folder. It will double the way I tested Bitcoin Core 26 and 30 in Win 11.

[arabspaceship123]

I've decided to wait until I buy another SSD to copy the Bitcoin folder. If they become corrupted I'll have to download the blocks again for my Win11. I'll keep Bitcoin on Linux and Win11 on different SSD.

[nc50lc]

I'll keep Bitcoin on Linux and Win11 on different SSD.

Oh, so when you mentioned that "it'll be on an SSD on USB" you meant the same SSD that your Win11 setup uses?
Yes?

It's a good decision then.
Although will work, using an external SSD isn't too reliable in the long run.

[arabspaceship123]

I'll keep Bitcoin on Linux and Win11 on different SSD.

Oh, so when you mentioned that "it'll be on an SSD on USB" you meant the same SSD that your Win11 setup uses?
Yes?

It's a good decision then.
Although will work, using an external SSD isn't too reliable in the long run.

No I am using Win11 on internal 256GB SSD. I'm downloading Bitcoin on portable 1TB Silicon Power 2.5 SSD to connect with USB socket. My Win11 EPS set works with Bitcoin Core 26. The external SSD for downloading Bitcoin has been perfect. Why is external SSD unreliable in the long run? I'm using something different for Linux with internal 128GB SSD. I will buy a new SSD for the Bitcoin testing on Linux. I don't want to test with my 1TB Silicon Power 2.5 SSD. I'll have to download all of it again if it gets corrupted.

[nc50lc]

Why is external SSD unreliable in the long run?

All those plug/unplug, connector push/pull, cable twist, etc.
Unless it's not being moved, one of those will eventually fail specially the cable in my own experience.
If that happens while file is being written, it will corrupt something and its consequences on Bitcoin Core isn't simple to solve.
Of course, it depends on your usage.

[satscraper]

Why is external SSD unreliable in the long run?

It probably depends on the quality of the external SSD itself and the quality of the USB‑related hardware ^{(ports, cables)} as well. My node has been using  high quality Samsung 870 EVO 2TB for more than two years with no issues. In my view, internal NVMe SSDs are less reliable because they tend to overheat  more than often ^{at least based on my own observations}.

[nc50lc]

My node has been using  high quality Samsung 870 EVO 2TB for more than two years with no issues.

Question:
Have you been moving that external drive (once a week/month or more) or is it's been staying in place during those times?

Because in the latter, its connector and ports aren't stressed too much which could have greatly contributed to its reliability.
That's aside it being Samsung, which is no doubt high-quality hardware.

[satscraper]

My node has been using  high quality Samsung 870 EVO 2TB for more than two years with no issues.

Question:
Have you been moving that external drive (once a week/month or more) or is it's been staying in place during those times?

Because in the latter, its connector and ports aren't stressed too much which could have greatly contributed to its reliability.
That's aside it being Samsung, which is no doubt high-quality hardware.

In fact, I have two SSDs by Samsung serving as backups of each other, so I swap them periodically on a monthly basis. This allows me to avoid rebuilding from scratch if something unexpected happens.  instead, I  just copy the content of the backup disk to the corrupted one if needed. Saves a lot of time indeed.

Regarding USB ports, I have a few different machines ^{let's count them: one, two... three... five in total}. Some of them are as old as 20 years, and only one of them has the broken USB port, but it was my fault because I accidentally snagged the cable connector inserted into that port with my hand.

Back to SSDs, I connect them using StarTech SATA to USB adapter.

[arabspaceship123]

All those plug/unplug, connector push/pull, cable twist, etc.
Unless it's not being moved, one of those will eventually fail specially the cable in my own experience.
If that happens while file is being written, it will corrupt something and its consequences on Bitcoin Core isn't simple to solve.
Of course, it depends on your usage.

The 128GB SSD with Linux is internal. The SSD I'll buy for Bitcoin is connected with USB. I'll remove the cable after use. I'll buy a new SSD for Bitcoin to stop sharing it on different Linux and Win11 computers. I'll be forced to download again if it gets corrupted.

It probably depends on the quality of the external SSD itself and the quality of the USB‑related hardware ^{(ports, cables)} as well. My node has been using  high quality Samsung 870 EVO 2TB for more than two years with no issues. In my view, internal NVMe SSDs are less reliable because they tend to overheat  more than often ^{at least based on my own observations}.

Samsung quality matters. Samsung EVO 2TB is better than 1TB Silicon Power. I'm using a cheap USB cable, I remove it after use. It's 3 years since I used my 1TB Silicon Power 2.5 SSD to test. It's a reliable SSD.

[satscraper]

All those plug/unplug, connector push/pull, cable twist, etc.
Unless it's not being moved, one of those will eventually fail specially the cable in my own experience.
If that happens while file is being written, it will corrupt something and its consequences on Bitcoin Core isn't simple to solve.
Of course, it depends on your usage.

The 128GB SSD with Linux is internal. The SSD I'll buy for Bitcoin is connected with USB. I'll remove the cable after use. I'll buy a new SSD for Bitcoin to stop sharing it on different Linux and Win11 computers. I'll be forced to download again if it gets corrupted.

It probably depends on the quality of the external SSD itself and the quality of the USB‑related hardware ^{(ports, cables)} as well. My node has been using  high quality Samsung 870 EVO 2TB for more than two years with no issues. In my view, internal NVMe SSDs are less reliable because they tend to overheat  more than often ^{at least based on my own observations}.

Samsung quality matters. Samsung EVO 2TB is better than 1TB Silicon Power. I'm using a cheap USB cable, I remove it after use. It's 3 years since I used my 1TB Silicon Power 2.5 SSD to test. It's a reliable SSD.

To avoid problems with any USB cable connecting your node's SSD to  USB port, and also to check the condition of the port itself, I would recommend using the USB tester capable of measuring the supplied voltage. Personally, I use the FNB58, which reads parameters such as V, A, and W. In addition, its oscilloscope mode is capable of displaying voltage ripple, fluctuations, and spikes. It also has the option to measure the cable resistance.

[Forsyth Jones]

My node has been using  high quality Samsung 870 EVO 2TB for more than two years with no issues.

Question:
Have you been moving that external drive (once a week/month or more) or is it's been staying in place during those times?

Because in the latter, its connector and ports aren't stressed too much which could have greatly contributed to its reliability.
That's aside it being Samsung, which is no doubt high-quality hardware.

In fact, I have two SSDs by Samsung serving as backups of each other, so I swap them periodically on a monthly basis. This allows me to avoid rebuilding from scratch if something unexpected happens.  instead, I  just copy the content of the backup disk to the corrupted one if needed. Saves a lot of time indeed.

I always buy Samsung SSDs whenever I can, I have 1 Samsung sata SSD (I think it's the EVO 870 2TB) to run Bitcoin Core Full Node at the time, after I bought a new notebook in 2021 or 22, but it doesn't have a SATA port, only NVME, I bought 2 new Samsung NVME 990 PRO 2TB SSDs (there's one that I don't I unpacked it until today, it was to be used on the PS5), all of this to run Bitcoin Core + electrum server (electrs) to have my own electrum server to connect to apps like bluewallet, btc-rpc-explorer...

It worked for a while, but I couldn't update it anymore and electrs stopped working... Since then I've been racking my head trying to make it work, but I gave up, when I have the patience for it, I could try again... 

For now I'm only running Bitcoin Core as it's the only desktop wallet I use besides the Trezor Suite.

txindex is enabled, so Bitcoin Core can be used as a server...

I remember running EPS a few times, in fact, I used it a lot until 2022, but it was never updated again, so I migrated to electrs, where I used it until 2024 (where the problems started).