Error opening block database

[LoyceV]

Code:

2018-03-01 22:53:18 IO error: d:\Bitcoin\blocks\index/000419.dbtmp: Could not rename file.
2018-03-01 22:53:18 Database I/O error

Could this be a file system limitation? Which file system do you use?

I think I will abandon this on Windows and look into running a node on Linux instead as this is just way too unreliable

May I suggest installing a "Linux file system" on your external drive? Ext4 is a good default choice.

[1715241028]

1715241028

[1715241028]

1715241028

[1715241028]

1715241028

[1715241028]

1715241028

[Sellingaccs]

Code:

2018-03-01 22:53:18 IO error: d:\Bitcoin\blocks\index/000419.dbtmp: Could not rename file.
2018-03-01 22:53:18 Database I/O error

Could this be a file system limitation? Which file system do you use?

I think I will abandon this on Windows and look into running a node on Linux instead as this is just way too unreliable

May I suggest installing a "Linux file system" on your external drive? Ext4 is a good default choice.

That is a great suggestion! I'd personally recommend Minitool Partition Wizard to use for creating partition, IF you wish to create partitions via Windows OS. That tool is easy to use and very reliable. It is very similar to Gparted IMO.


However creating partitions is usually safer on GNU/Linux OS and i think that he should create the partition from installation of Xubuntu or liveCD. Xubuntu is lightweight, as it features XFCE instead of Gnome3 as DE.

[themossinator]

hey thanks for replies - I am now running on Ubuntu 16.04 LTS - so far so good, blockchain syncing now but its taking quite a while, not sure why, it seemed to sync a hell of a lot faster on Windows

Anyway, my final problem (i hope) is that I cannot open port 8333, have seen suggestions that ISPs may block this port but I think its probably more something on my end

If i use one of those port checking websites it says 8333 is Open but https://bitnodes.earn.com/ says Not Reachable

does anyone know what Im missing here? I am only getting 8 active connections on my Bitcoin Core

thanks

[LoyceV]

If i use one of those port checking websites it says 8333 is Open but https://bitnodes.earn.com/ says Not Reachable

does anyone know what Im missing here?

Let's start with the obvious: did you portforward port 8333 in your modem settings to the IP address of your Ubuntu?

[themossinator]

If i use one of those port checking websites it says 8333 is Open but https://bitnodes.earn.com/ says Not Reachable

does anyone know what Im missing here?

Let's start with the obvious: did you portforward port 8333 in your modem settings to the IP address of your Ubuntu?

yes

[jackg]

If i use one of those port checking websites it says 8333 is Open but https://bitnodes.earn.com/ says Not Reachable

does anyone know what Im missing here?

Let's start with the obvious: did you portforward port 8333 in your modem settings to the IP address of your Ubuntu?

yes

Do you use a VPN or have a service that monitors your network traffic (a "physical firewall" for outbound/inbound data).

Since you're still getting connections, what does it say at the bottom? Is it still syncing or is there another error. 8 perrs seems about right.

If you're still stuck after this, I'd suggest you try and change the port to something else (22 would be my suggestion - it's usually for SSH so should be available unless your router already uses that port).

[themossinator]

If i use one of those port checking websites it says 8333 is Open but https://bitnodes.earn.com/ says Not Reachable

does anyone know what Im missing here?

Let's start with the obvious: did you portforward port 8333 in your modem settings to the IP address of your Ubuntu?

yes

Do you use a VPN or have a service that monitors your network traffic (a "physical firewall" for outbound/inbound data).

Since you're still getting connections, what does it say at the bottom? Is it still syncing or is there another error. 8 perrs seems about right.

If you're still stuck after this, I'd suggest you try and change the port to something else (22 would be my suggestion - it's usually for SSH so should be available unless your router already uses that port).

says its syncing with network, only 2 active connections

how to change the default port?

thanks

[jackg]

For ALL OSes, locate the bitcoin-qt script (for microsoft windows it's bitcoin-qt.exe for linux, you can probably jsut type bitcoin-qt into the console).

FOR WINDOWS:
Open command prompt and type Path_You_Just_Found+"\bitcoin-qt.exe -port=22"

For Linux:
Open command prompt and type "bitcoin-qt -port=22".

Hopefully that should work correctly. If not, try installing TOR and forcing your packets through it.

[themossinator]

Its actually ok, when my wallet finished syncing it's working!! thanks to everyone for helping me! 

[PabloRod2]

I got a similar error, i use the core at another location, now I use a MacBook to check some things and even tho the hard disk is updated till yesterday without issues the Mac client shows the following errors

https://i.ibb.co/rxrm3CV/BC1.png
https://i.ibb.co/84hgKkY/BC2.png

Any ideas? I know i could format the drive and re-download the hole database, I would like no avoid doing that

[AdolfinWolf]

Any ideas? I know i could format the drive and re-download the hole database, I would like no avoid doing that

Hmm. Those errors could mean a variety of things. Best thing you could probably do is make a backup first, then maybe open a new thread (as you're currently bumping a year-old thread) with a debug.log attached ( => https://en.bitcoin.it/wiki/Data_directory).

If you're not interested in opening another thread, you can try some of the following:

https://bitcoin.stackexchange.com/questions/60709/when-should-i-use-reindex-chainstate-and-when-reindex/60711#60711

Reindex it and see if that fixes your DB issues. (Again that might be unnecessary if you can check the debug.log to see what the error might be.)
(Maybe there is an error with the -datadir (since you use it a "different" location?) but if you've used the wallet succesfully before, i kind of doubt it.)