-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fulcrum process error starting [VirtualBox vboxsf fsync] #100
Comments
Let me ask you -- did you copy the database from someplace like from another install, or? I have never seen that error. What filesystem is it on (ext4, etc)? |
It is a new installation from zero, never used Fulcrum before, so no pre existing database. Just an empty data dir. I am using binary release from https://github.com/cculianu/Fulcrum/releases/download/v1.6.0/Fulcrum-1.6.0-x86_64-linux.tar.gz filesystem is NTFS, it is a WD Blue SSD NVMe. Ubuntu is running in a VirtualBox, however I see that the mounted directory says type
Let me explain in more detail:
In the Ubuntu VM I am running a bitcoind with datadir in /media/*username*/minodobitcoin/bitcoin They are running from about a year ago, without any disk problem at all. |
|
Thanks for the response. Unfortunately I cannot give the whole volume to the VM because the VM itself (.vmi) is installed in another directory of this volume. |
Then you need to create another filesystem.. or you can run it with |
Hey @zx9r -- would you mind renaming the issue to something that includes "VirtualBox" and/or May be good for others to be able to quickly find this issue... |
I finally installed an Ubuntu 20.04 into a USB drive and mounted the SSD from there to get rid of VMs and run Linux natively. Fulcrum fully synced in about 14h which is pretty awesome |
Awesome!! Just curious: Did you use the |
Yes, --fast-sync=6000 (6GB) |
Nice nice nice! :D |
I'm going to go ahead and close this issue but I will pin it first so others may see it in case they also are using VirtualBox's vboxsf. |
The workaround I used was to create a second harddrive for the VirtualBox VM rather than trying to use a directory on VirtualBox shared drive which only supports basic file copy operations. So far 35.7% sync'ed in about 45 minutes. The Bitcoin Core blockchain directory is located on the shared drive and it works just fine. |
First run. Ubuntu 20.04.3 LTS.
Here it is the output:
The
meta
directory is created fine with the following files:and this is the content of the LOG file:
The text was updated successfully, but these errors were encountered: