Bitcoin Wallet error - help me troubleshoot?

Masterswarm

jr. member

Activity: 54

Merit: 6

Quote from: nc50lc on September 09, 2019, 11:47:49 PM

Quote from: Masterswarm on September 09, 2019, 09:29:30 PM

The connection is over wired Ethernet, not USB. Unfortunately, despite changing some of my SMB settings, the same issue replicated itself.

Not sure what to do now, but I suspect I'll be suspending my attempts at deploying a full node. Sad

I don't think Core supports any network storage devices. That's why it failed to create block database to your NAS.

Read these issues (ranging from 2014 to 2017) for more info:

Try to run a (550MiB) pruned node in your local disk instead?

Yep. Figured as much. I'll move on to plan B.

Thanks for the assistance everyone , very much appreciated.

nc50lc

legendary

Activity: 2534

Merit: 6080

Self-proclaimed Genius

Quote from: Masterswarm on September 09, 2019, 09:29:30 PM

The connection is over wired Ethernet, not USB. Unfortunately, despite changing some of my SMB settings, the same issue replicated itself.

Not sure what to do now, but I suspect I'll be suspending my attempts at deploying a full node. Sad

I don't think Core supports any network storage devices. That's why it failed to create block database to your NAS.

Read these issues (ranging from 2014 to 2017) for more info:

Try to run a (550MiB) pruned node in your local disk instead?

Masterswarm

jr. member

Activity: 54

Merit: 6

Quote from: ?? on ??

You also might these options as well (if there's no problem with your HDD/NAS and you've tried above suggestion) :
1. Use different port for you NAS, especially if you use computer chassis's USB port or cheap card reader/port hub.
2. Run Bitcoin Core on different computer (with same NAS obviously)

The connection is over wired Ethernet, not USB. Unfortunately, despite changing some of my SMB settings, the same issue replicated itself.

Not sure what to do now, but I suspect I'll be suspending my attempts at deploying a full node. Sad

Masterswarm

jr. member

Activity: 54

Merit: 6

Quote from: jackg on September 09, 2019, 09:02:21 AM

If the drives have been recently checked for health, you can try testing the connection to the network for both your machine and the NAS drive (maybe switch the cables around).

Have you tried starting the client since, what does it do now or has the error been happening repeatedly?

You could try copying something to the NAS and back and see if it comes back in correct order (a file pretty big) just to check the NAS can allot stuff properly.

My NAS is very capable and there should not be any issues at all with it (edit: confirmed, SMART tests all pass). It runs 2 disk redundancy in any event. It's a massive 50TB rig. I'm doing some troubleshooting with settings and will report back once I have run some more tests.

aundroid

legendary

Activity: 1232

Merit: 1247

Quote from: Masterswarm on September 08, 2019, 10:52:18 PM

Thanks. My NAS should be entirely fine, it's a ZFS array and has been recently scrubbed to ensure no bad sectors.
I'll do some troubleshooting and see if I can amend this... good to know it's not simply a NAS issue.

Maybe you can post the S.M.A.R.T data of your hard disks, these values reveal many details about the current state of the HDDs.

And you can also try to change the sata cables, the sata controller or the power plug cables.
Maybe there is a contact problem (bad contact) somewhere.

jackg

copper member

Activity: 2856

Merit: 3071

https://bit.ly/387FXHi lightning theory

If the drives have been recently checked for health, you can try testing the connection to the network for both your machine and the NAS drive (maybe switch the cables around).

Have you tried starting the client since, what does it do now or has the error been happening repeatedly?

You could try copying something to the NAS and back and see if it comes back in correct order (a file pretty big) just to check the NAS can allot stuff properly.

Masterswarm

jr. member

Activity: 54

Merit: 6

Quote from: ?? on ??

I/O error usually means your storage or storage cable is broken. Try those options :
1. Check HDD's health with application such as CrystalDiskInfo
2. Use different cable or port for your NAS
3. Perform full-scan on your HDD to check bad sectors
4. Try with another HDD or internal HDD to see if the error still occurred.

Thanks. My NAS should be entirely fine, it's a ZFS array and has been recently scrubbed to ensure no bad sectors.
I'll do some troubleshooting and see if I can amend this... good to know it's not simply a NAS issue.

Masterswarm

jr. member

Activity: 54

Merit: 6

My full node is experiencing fatal errors. It is running on Windows 10. The blocks are being stored on a NAS. Here is the debug. I'd appreciate any input you have.

Quote

2019-09-07T00:29:44Z UpdateTip: new best=0000000000000333c91c07406268869513c550e85732eecddd5dacecd30b96e0 height=225962 version=0x00000002 log2_work=69.549499 tx=14450525 date='2013-03-15T08:14:46Z' progress=0.032255 cache=94.7MiB(719037txo)
2019-09-07T00:29:44Z Leaving block file 47: CBlockFileInfo(blocks=776, size=134068765, heights=225094...225972, time=2013-03-10...2013-03-15)
2019-09-07T00:29:44Z FileCommit: FlushFileBuffers failed: 5
2019-09-07T00:29:44Z *** Flushing block file to disk failed. This is likely the result of an I/O error.
2019-09-07T00:29:44Z Error: Error: A fatal internal error occurred, see debug.log for details
2019-09-07T00:37:56Z Pre-allocating up to position 0x1000000 in blk00048.dat
2019-09-07T00:37:56Z tor: Thread interrupt
2019-09-07T00:37:56Z Shutdown: In progress...
2019-09-07T00:37:56Z opencon thread exit
2019-09-07T00:37:56Z torcontrol thread exit
2019-09-07T00:37:56Z addcon thread exit
2019-09-07T00:37:56Z net thread exit
2019-09-07T00:37:56Z msghand thread exit
2019-09-07T00:37:56Z scheduler thread interrupt
2019-09-07T00:37:56Z Dumped mempool: 0s to copy, 0.026025s to dump

Topic: Bitcoin Wallet error - help me troubleshoot? (Read 206 times)