2015-Jun-10 15:09:39.287259 Transaction does not exist: tx with hash 530dcf67fad
acf8dcc05b6d7314b1c181362c2af43842eecb22fb9d9587706de not found in db
2015-Jun-10 15:09:39.361263 Transaction does not exist: tx with hash 530dcf67fad
acf8dcc05b6d7314b1c181362c2af43842eecb22fb9d9587706de not found in db
2015-Jun-10 15:09:39.386265 Transaction does not exist: tx with hash 530dcf67fad
acf8dcc05b6d7314b1c181362c2af43842eecb22fb9d9587706de not found in db
2015-Jun-10 15:09:39.389265 Failed to add block to blockchain, verification fail
ed, height = 240001
2015-Jun-10 15:09:39.393265 skipping rest of import file
2015-Jun-10 15:09:39.395265 Finished at height: 240001 block: 240000
More info would be helpful.
OS?
Free space on HD?
Source of code? (did u compile head, or some other commit?)
System RAM?
as far as I understand the "not found in db", thats normal behavior indicating that the transaction is not in the database, so it should be added to the database. From the way this thing behaves, I think the blockchain import (and converter for that matter) functions as a virtual node, and that the old blockchain is also a virtual node. So essentially, your new blockchain is syncing from an old blockchain - its just that the two of them are files sitting on the same hard drive. Its not like a file conversion, per se - you're actually building the blockchain from scratch, so the "not found in database" is simply the new blockchain going "hey, this isn't in the database, we should add it" as it "syncs" from the old blockchain. I could be wrong though.
Windows 7
~300GB
The code is yours, downloaded from https://mega.co.nz/#!5YNACDTJ!N0pIow27_Tfsx4dMfMq4HA11ZSlEt7L135HvYEOuBU8
6GB RAM
I'm trying the converter again now with batch size 10000, just for the hell of it.
Maybe somebody could just upload the lmdb file...?