Bitcoin Forum
November 04, 2025, 02:43:51 AM *
News: Latest Bitcoin Core release: 30.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 [2]  All
  Print  
Author Topic: [error] Fatal LevelDB error: Corruption: block checksum mismatch  (Read 379 times)
28e7166c23e70c2014feb5d64 (OP)
Newbie
*
Offline Offline

Activity: 19
Merit: 2


View Profile
September 28, 2025, 10:24:03 AM
 #21

Ok. In the past days I went through the IBD again using my super powerful computer, and kept a `.tar` archive of it from yesterday. Right now the node is running in the not so powerful older computer without any apparent issue since yesterday. During the past days I had 0 issues in the super powerful computer with the IBD and also running the node, starting and stopping `bitcoind` tens of times. In the not so powerful computer I know the risk of corruption is high if I stop `bitcoind`.

If the external SSD were the problem, how could it work flawlessly in the super powerful machine and fail in the not so powerful machine? This points me to think about something else.
LoyceV
Legendary
*
Offline Offline

Activity: 3850
Merit: 20287


Thick-Skinned Gang Leader and Golden Feather 2021


View Profile WWW
September 28, 2025, 10:50:26 AM
Last edit: September 28, 2025, 03:10:05 PM by LoyceV
 #22

If the external SSD were the problem, how could it work flawlessly in the super powerful machine and fail in the not so powerful machine? This points me to think about something else.
During IBD on a system low on RAM, it writes terabytes of data to disk. Your powerful computer won't have that problem.

¡uʍop ǝpᴉsdn pɐǝɥ ɹnoʎ ɥʇᴉʍ ʎuunɟ ʞool no⅄
28e7166c23e70c2014feb5d64 (OP)
Newbie
*
Offline Offline

Activity: 19
Merit: 2


View Profile
September 28, 2025, 03:03:13 PM
 #23

If the external SSD were the problem, how could it work flawlessly in the super powerful machine and fail in the not so powerful machine? This points me to think about something else.
During IBD on a system low on ram, it writes terabytes of data to disk. Your powerful computer won't have that problem.

Does this apply also to normal node operation? I.e. after the IBD. The not so powerful machine has 8 GB RAM, the other 64.
LoyceV
Legendary
*
Offline Offline

Activity: 3850
Merit: 20287


Thick-Skinned Gang Leader and Golden Feather 2021


View Profile WWW
September 28, 2025, 03:11:14 PM
 #24

Does this apply also to normal node operation? I.e. after the IBD. The not so powerful machine has 8 GB RAM, the other 64.
I expect it to write about 10 GB per week.

¡uʍop ǝpᴉsdn pɐǝɥ ɹnoʎ ɥʇᴉʍ ʎuunɟ ʞool no⅄
Cricktor
Legendary
*
Offline Offline

Activity: 1302
Merit: 3123



View Profile
October 07, 2025, 04:13:21 PM
Last edit: October 07, 2025, 04:36:07 PM by Cricktor
 #25

If the external SSD were the problem, how could it work flawlessly in the super powerful machine and fail in the not so powerful machine? This points me to think about something else.
You could have a problem with reliable enough power delivery via USB on your less powerful device. Allthough, when Samsung says that a T7 can operate with as little as 0.5A/5V, it doesn't really hint to a power issue.

Have you tried different USB ports on your "potato" computer?

You used the same USB-cable to connect the T7 to both machines?

If your Samsung T7 2TB works without issues on your "super" powerful machine, I would conclude there's no immediate internal issue with the T7. When on the other hand you get corruption of data on your T7 on your "less" powerful machine, I would conclude it has something to do with this particular computer (assuming both run the same OS to exclude variables), whatever it is.

As you don't seem to disconnect the T7 prematurely, it must be something else that separates both machines.

Not sure how to detect this. I would assume that a Linux system would log issues that USB devices exhibit or report, but I don't know what specifically to search for and in which log file. There might also be a way to arm the USB subsystem to be more verbose for debugging such an issue. But I don't know how myself.

Maybe you ask in a more Linux specific forum how to tackle such potential USB issues.

Are you 100% sure, you use a USB3 port on your less powerful machine to connect the T7? According to Samsung even USB2 would be fine, but that's at the very limit of USB2, despite it's dog-slow compared to a decent USB3 connection (USB3.2 recommended for a T7).

Pages: « 1 [2]  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!