Latest posts of: Upwind5420

Show Posts
Pages: [1]

on: April 02, 2024, 06:29:27 PM

Let me add one additional thing. I installed via snap. It is working in the gui. I am currently a couple weeks behind but that will catch up shortly. When I launch in the command line from /snap/bitcoin-core/current/bin directory ./bitcoind -prune=550. So is my whole problem that I am just launching from the wrong location and trying to download the blockchain twice. And sorry for the noob questions.

on: April 02, 2024, 06:10:56 PM

Still producing an error message with the new sata cable. Not seeing any hardware errors. With pruning off, I was able to get pretty far through the process before running out of space but with pruning on, it fails and then I have to start over.

on: April 01, 2024, 01:38:15 PM

Quote from: LoyceV on March 31, 2024, 07:53:55 AM Quote from: Upwind5420 on March 31, 2024, 12:24:06 AM Cpu and memory are both clean at this point. Did you check the temperature during IBD? It doesnt show up in the list of sensors. I was only able to monitor during stress testing which was okay.

on: March 31, 2024, 02:40:57 AM

Quote from: ABCbits on March 30, 2024, 10:01:24 AM It'd be great if you include additional information as suggested on this thread, [READ BEFORE POSTING] Tech Support Help Request Format. If you use computer and that SSD use SATA port, i also recommend you to try different SATA cable. Sorry about that. Here is the info. Bitcoin Client Software and Version Number: Bitcoin Core 26.0 Operating System: Ubuntu 24.04 System Hardware Specs: AMD Athalon 5350 / 16G DDR 3/1600 (2 8G chips) / 500 G SSD Description of Problem: Issue syncing initial blockchain and never able to complete. Any Related Addresses: NA Any Related Transaction IDs: NA Screenshot of the problem: NA Log Files from the Bitcoin Client: NA Trying another SATA cable now.

on: March 31, 2024, 12:24:06 AM

Quote from: Upwind5420 on March 30, 2024, 07:13:17 PM Quote from: LoyceV on March 29, 2024, 07:30:14 PM Read this thread on Github. The suggestions are to check hardware: memtest, CPU and disk temperature. Any chance your fans are dusty? If it's not hardware, that leaves software. Try if a different OS helps. Okay I have started running tests. Cpu and memory are both clean at this point.

on: March 30, 2024, 07:13:17 PM

Quote from: LoyceV on March 29, 2024, 07:30:14 PM Read this thread on Github. The suggestions are to check hardware: memtest, CPU and disk temperature. Any chance your fans are dusty? If it's not hardware, that leaves software. Try if a different OS helps. Okay I have started running tests.

on: March 29, 2024, 07:11:14 PM

SMART shows 0 errors. Memory is fairly new as well (about a year old with little use) and I have 16G

on: March 29, 2024, 06:46:23 PM

I seem to be having a problem with my initial sync. Part way through I get an error of Falal LevelDB error: Corruption: block checksum mismatch. I have a brand new 500G ssd which is showing no errors so its not likely hardware. The problem is that I have to run a pruned node since the 500g drive is not large enough to run without it but when that fails, I have to reindex which starts it over. This has happened multiple times now (at different locations). Any thoughts on what I am doing wrong?

Pages: [1]