bitcoind – bitcoin daemon crashing on preliminary block obtain

I am attempting to do the preliminary block obtain so I can run a full node. Did not expertise any points till the obtain bought to about 87% then bitcoind crashed with out logging any errors. I’ve tried restarting it a number of occasions, nevertheless every time after I come again to my laptop a couple of hours later to test on it I discover that it has crashed and any obtain progress has been misplaced.

I’m doing this on my private laptop computer, utilizing a 1 terabyte exterior arduous drive (not SSD) and a wired Ethernet connection. I’ve disabled sleep on my laptop and have been leaving it plugged into energy.

Particulars:

• OS: Ubuntu 22.04.5 LTS
• CPU structure: x86_64
• CPU: Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
• RAM: 16gb
• Web velocity: 90 Mbit/s obtain
• Bitcoin Core model: v27.0.0

That is the command I am utilizing to run the daemon:

bitcoind -daemon -debug -datadir=/media/me/TOSHIBA EXT/bitcoin/ -dbcache=10000

That is the final 25 strains from the debug.log file earlier than it crashed:

2024-09-14T03:44:04Z [validation] Enqueuing MempoolTransactionsRemovedForBlock: block top=830276 txs eliminated=0
2024-09-14T03:44:04Z UpdateTip: new greatest=00000000000000000001914a6db5b53b3f8d673fbd9ebc1a569f37ccbbf97861 top=830276 model=0x20c98000 log2_work=94.729419 tx=965218034 date="2024-02-13T10:37:40Z" progress=0.888359 cache=2550.2MiB(20688484txo)
2024-09-14T03:44:04Z [bench]   - Join postprocess: 0.40ms [3.08s (0.70ms/blk)]
2024-09-14T03:44:04Z [bench] - Join block: 2522.60ms [6781.75s (1545.87ms/blk)]
2024-09-14T03:44:04Z [validation] Enqueuing BlockConnected: block hash=00000000000000000001914a6db5b53b3f8d673fbd9ebc1a569f37ccbbf97861 block top=830276
2024-09-14T03:44:04Z [validation] Enqueuing UpdatedBlockTip: new block hash=00000000000000000001914a6db5b53b3f8d673fbd9ebc1a569f37ccbbf97861 fork block hash=000000000000000000018e3f91a815472d0d994b832624751bbfbac25aa739cf (in IBD=true)
2024-09-14T03:44:04Z [validation] MempoolTransactionsRemovedForBlock: block top=830273 txs eliminated=0
2024-09-14T03:44:04Z [estimatefee] Blockpolicy estimates up to date by 0 of 0 block txs, since final block 0 of 0 tracked, mempool map dimension 0, max goal 0 from present
2024-09-14T03:44:04Z [validation] BlockConnected: block hash=000000000000000000031be2ac7b85a7db0493498a39f4580be01431134e4c13 block top=830273
2024-09-14T03:44:04Z [validation] UpdatedBlockTip: new block hash=000000000000000000031be2ac7b85a7db0493498a39f4580be01431134e4c13 fork block hash=00000000000000000003238c6e2e4551b0b5375ae52499bf03bf5de12a29e2bf (in IBD=true)
2024-09-14T03:44:04Z [validation] MempoolTransactionsRemovedForBlock: block top=830274 txs eliminated=0
2024-09-14T03:44:04Z [estimatefee] Blockpolicy estimates up to date by 0 of 0 block txs, since final block 0 of 0 tracked, mempool map dimension 0, max goal 0 from present
2024-09-14T03:44:04Z [validation] BlockConnected: block hash=00000000000000000000f3e8fcccf8ee483ebed02694c5773780a61a17a95037 block top=830274
2024-09-14T03:44:04Z [validation] UpdatedBlockTip: new block hash=00000000000000000000f3e8fcccf8ee483ebed02694c5773780a61a17a95037 fork block hash=000000000000000000031be2ac7b85a7db0493498a39f4580be01431134e4c13 (in IBD=true)
2024-09-14T03:44:04Z [validation] MempoolTransactionsRemovedForBlock: block top=830275 txs eliminated=0
2024-09-14T03:44:04Z [estimatefee] Blockpolicy estimates up to date by 0 of 0 block txs, since final block 0 of 0 tracked, mempool map dimension 0, max goal 0 from present
2024-09-14T03:44:04Z [validation] BlockConnected: block hash=000000000000000000018e3f91a815472d0d994b832624751bbfbac25aa739cf block top=830275
2024-09-14T03:44:04Z [validation] UpdatedBlockTip: new block hash=000000000000000000018e3f91a815472d0d994b832624751bbfbac25aa739cf fork block hash=00000000000000000000f3e8fcccf8ee483ebed02694c5773780a61a17a95037 (in IBD=true)
2024-09-14T03:44:04Z [validation] MempoolTransactionsRemovedForBlock: block top=830276 txs eliminated=0
2024-09-14T03:44:04Z [estimatefee] Blockpolicy estimates up to date by 0 of 0 block txs, since final block 0 of 0 tracked, mempool map dimension 0, max goal 0 from present
2024-09-14T03:44:04Z [validation] BlockConnected: block hash=00000000000000000001914a6db5b53b3f8d673fbd9ebc1a569f37ccbbf97861 block top=830276
2024-09-14T03:44:04Z [validation] UpdatedBlockTip: new block hash=00000000000000000001914a6db5b53b3f8d673fbd9ebc1a569f37ccbbf97861 fork block hash=000000000000000000018e3f91a815472d0d994b832624751bbfbac25aa739cf (in IBD=true)
2024-09-14T03:44:04Z [bench]   - Load block from disk: 194.05ms
2024-09-14T03:44:04Z [bench]     - Sanity checks: 4.44ms [12.23s (2.79ms/blk)]
2024-09-14T03:44:04Z [bench]     - Fork checks: 0.04ms [0.14s (0.03ms/blk)]

Issues I’ve already tried:

• run the daemon with debugging enabled and test the debug.log file for apparent issues
• test if the exterior arduous drive is corrupted: I’ve run some exams utilizing smartctl and badblocks they usually have not reported any points
• experiment with completely different values for dbcache
• search for the final block hash listed within the debug.log file in a public block explorer to confirm it exists
• have a look at the bitcoin supply code the place the final log comes from (validation.cpp line 2592). If I needed to guess I might say possibly one thing between that and the subsequent go online line 2683 is inflicting bitcoind to crash with out logging something.

I’d actually admire any assist with this. I am discovering it actually arduous to debug as a result of I’ve to go away my laptop working in a single day to see if it crashes each time I strive one thing new.