Bitcoin Forum
May 27, 2024, 02:54:41 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Corrupted Litecoin Wallet.dat  (Read 3342 times)
Cameltoemcgee (OP)
Newbie
*
Offline Offline

Activity: 54
Merit: 0



View Profile
December 20, 2013, 02:44:17 AM
 #1

wallet.dat was fine, have multiple copies of it. then i reinstalled windows, afterwards i copied the entire litecoin folder that i backed up before the windows reinstall back into %appdata% roaming, and installed the latest version  of litecoin-qt... now it thinks its corrupted Sad

Additionally, found a thread that mentions how to fix corrupt wallets...

tried using https://github.com/gavinandresen/bitcointools fixwallet.py and it doesn't run properly Sad

the error i get is: "Skipping tem of type minversion"

Running dbdump.py --wallet Comes up with "Skipping tem of type minversion" after showing all the keys and stuff, last few lines of output below.

Change Pool key 101: 1CfgWf8ML3qZo9hdNg2bJSaY8vp68GQn11 (Time: Tue Sep 10 21:03:
21 2013)
addrIncoming:
Version: 80600
Block Locator top: 00000000000000046cf4629a0a4bd42fecb0b94ea17b67c9fd4c624c15ceb
0aa
Default Key: 0x03fb...df7d 1Fnw1LL9ChZtoaW5sxHTYU843SNihfP6mX
Skipping item of type minversion



Can anyone help me get my litecoins back?
bitpop
Legendary
*
Offline Offline

Activity: 2912
Merit: 1060



View Profile WWW
December 26, 2013, 09:47:34 AM
 #2

Try this https://github.com/jackjack-jj/pywallet

Cameltoemcgee (OP)
Newbie
*
Offline Offline

Activity: 54
Merit: 0



View Profile
December 31, 2013, 04:35:44 AM
 #3

Thanks bitpop,

Managed to dump the private keys and whatnot, so i know i haven't lost all my coins, but i'll be buggered if i can work out how to import all the dumped keys into a new wallet.dat that works...

pywallet spits out errors when i try Sad

Cheers!
bitpop
Legendary
*
Offline Offline

Activity: 2912
Merit: 1060



View Profile WWW
December 31, 2013, 04:47:09 AM
 #4

Thanks bitpop,

Managed to dump the private keys and whatnot, so i know i haven't lost all my coins, but i'll be buggered if i can work out how to import all the dumped keys into a new wallet.dat that works...

pywallet spits out errors when i try Sad

Cheers!

Try the debug window and manual rpc command

Cameltoemcgee (OP)
Newbie
*
Offline Offline

Activity: 54
Merit: 0



View Profile
January 13, 2014, 10:38:25 PM
Last edit: January 14, 2014, 12:04:20 AM by Cameltoemcgee
 #5

Hi Guys,

Gonna resurrect this one. I thought i had dumped the litecoin backup... apparently not though. tried importing a private key, and it spat out an error. running the dump command again i realised i was dumping an unencrypted bitcoin wallet! FAIL!

I tried using the below command to dump my "corrupted" litecoin wallet.dat

pywallet.py --dumpwallet --otherversion=48 --datadir=C:\litecoin > dump.txt

no go, i still have the version of the blockchain that i copied off before the reformat and install of windows along with multiple copies of the same wallet.dat but it spits out the following whether i try it in the current litecoin directory with a new blockchain and old copy of the wallet.dat, or the backup copy of the blockchain and wallet located in C:\litecoin.

ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this
again.


I definitely don't have LTC or BTC running and permissions look fine on the folder... has anyone seen this before?

Its getting to the point now i'm willing to pay a decent reward if someone can help me get it back... .2 BTC or 10 LTC if i can get into my wallet!

After reading through the debug.log i found the following reference to  db.log

2014-01-13 12:27:12 init message: Verifying wallet...
2014-01-13 12:27:12 dbenv.open LogDir=C:\Users\\AppData\Roaming\Litecoin\database ErrorFile=C:\Users\\AppData\Roaming\Litecoin\db.log
2014-01-13 12:27:12 Renamed wallet.dat to wallet.1389616032.bak
2014-01-13 12:27:12 Error: Salvage found errors, all data may not be recoverable.
2014-01-13 12:27:12 Salvage(aggressive) found no records in wallet.1389616032.bak.
2014-01-13 12:27:15 Shutdown : In progress...
2014-01-13 12:27:15 StopNode()
2014-01-13 12:27:15 Flushed 0 addresses to peers.dat  6ms
2014-01-13 12:27:15 Shutdown : done

the db.log file referenced shows the following...

file unknown has LSN 1/674149, past end of log at 1/28
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
Page 0: metadata page corrupted
Page 0: could not check metadata page
wallet.dat: DB_VERIFY_BAD: Database verification failed
file unknown has LSN 1/674149, past end of log at 1/1076
Commonly caused by moving a database from one database environment
to another without clearing the database LSNs, or by removing all of
the log files from a database environment
wallet.1389617886.bak: DB_VERIFY_BAD: Database verification failed


Hopefully someone much smarter than i am has some idea of whats going on here.
Cameltoemcgee (OP)
Newbie
*
Offline Offline

Activity: 54
Merit: 0



View Profile
January 16, 2014, 07:41:26 AM
 #6

For anyone that has been following this thread, I got my wallet back... luckily, google keeps file revisions on its google drive, i had a previous revision of the encrypted archive i back it up to up there.... replaced the wallet.dat with that and its all good.

If i didn't have it, my wallet would have been gone. done and dusted.

Don't make the same mistake as i did which was simply copying the wallet.dat whilst litecoin-qt was running!!!!

Phew!

thanks to those of you who tried to help me out! Smiley
Pages: [1]
  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!