kauai_lost_boi (OP)
Jr. Member
Offline
Activity: 56
Merit: 19
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 20, 2021, 06:36:51 AM |
|
Just when I thought things were going as smooth as they could be, the terminal process stopped and I got a "killed215704" reading.
WTF
|
|
|
|
kauai_lost_boi (OP)
Jr. Member
Offline
Activity: 56
Merit: 19
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 20, 2021, 04:31:00 PM |
|
I don't get how it could run out of memory. I was working with over 9 billion results and counting over a course of nearly 3 days on the first shakedown pass. This latest pass didnt even get to 2 billion in 12 hours and it was killed. I got 44 gigs of RAM on this thing, how could it run out of memory?
|
|
|
|
kauai_lost_boi (OP)
Jr. Member
Offline
Activity: 56
Merit: 19
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 20, 2021, 10:36:10 PM Last edit: June 21, 2021, 12:33:21 AM by kauai_lost_boi |
|
I ran it again starting last night, and it crashed in the exact same place and same time, just over 1 billion results 15 hours in. "killed214264"
In the shakedown runs using the "best guess" option amassing over 9 billion results with not even so much as a sniffle, In this run I noticed some stuttering, pausing and lagging but it would resume after a minute or so. The only difference in this instance from the other runs is I'm running off the token file.
At least I got the token file working, but still... This sucks
|
|
|
|
kauai_lost_boi (OP)
Jr. Member
Offline
Activity: 56
Merit: 19
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 21, 2021, 05:08:44 PM |
|
I don't get how it could run out of memory. I was working with over 9 billion results and counting over a course of nearly 3 days on the first shakedown pass. This latest pass didnt even get to 2 billion in 12 hours and it was killed. I got 44 gigs of RAM on this thing, how could it run out of memory?
I ran it again starting last night, and it crashed in the exact same place and same time, just over 1 billion results 15 hours in. "killed214264"
Unfortunately btcrecover doesn't have feature to allocate memory based on available RAM. Have you tried using these parameter to prevent OOM? --no-dupchecks --no-eta flags
Yes, I had both of those in my most current working argument listed back several posts ago python3 seedrecover.py --no-dupchecks --mnemonic-length 12 --language EN --dsw --no-eta --tokenlist ./seedtoken.txt
|
|
|
|
NotATether
Legendary
Offline
Activity: 1722
Merit: 7248
In memory of o_e_l_e_o
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 22, 2021, 08:40:11 AM |
|
"Killed [12345]" message can happen for a variety of reasons and aren't limited to out-of-memory situations. BTCrecover makes use of multiple CPU threads, so it's possible that if one of them crashed, the entire program terminates and the shell displays this message. If btcrecover made any log files, it's best to check them to see if this is the true reason for the crash or if it's something else.
|
|
|
|
kauai_lost_boi (OP)
Jr. Member
Offline
Activity: 56
Merit: 19
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 22, 2021, 07:04:37 PM Last edit: July 09, 2021, 01:34:26 AM by kauai_lost_boi |
|
When I was running BTCrecover using the "best guess" option, I was also using other specifically directed arguments, such as derivation paths, wallet types, amount of typos etc.
Maybe the current working argument using the token file is having a conflict. Without setting wallet type and derivation paths, it will give me the option to chose. I select bitcoin and it will search for all 3 BTC derivation types by default.
Whatever the difference is, I gotta determine what made the "best guess" work so fluidly and what is making it go splat with the token file at the exact same spot after some lagging and stuttering.
|
|
|
|
kauai_lost_boi (OP)
Jr. Member
Offline
Activity: 56
Merit: 19
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 24, 2021, 07:36:16 AM |
|
So I am back at it, this time with another approach. I installed the Ubuntu 20.04 SERVER ISO (Had to install a desktop interface. Loads of fun with that one.) in the hopes of eliminating the kill process issue. Gonna try the same thing as before with my argument and my tokenlist. If anyone has input, suggestions or well wishes, I could use all 3 right now. My morale is flagging and Guinness can only get me so far. ![Sad](https://bitcointalk.org/Smileys/default/sad.gif)
|
|
|
|
kauai_lost_boi (OP)
Jr. Member
Offline
Activity: 56
Merit: 19
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 24, 2021, 08:00:14 PM |
|
So after reworking the token file I am now working with this arrangement -
^1^lockedword ^2^lockedword ^3^floatingknownword ^4^floatingknownword ^7^lockedword ^8^lockedword ^9^lockedword ^10^lockedword ^11^lockedword ^12^lockedword and then 3 lines of the entire BIP39 wordlist
Getting 2.5 million results a minute. I may need to get a better computer with GPU acceleration if this project is a lost cause on the current rig I got. Looking at running this on an Asus g17 Advantage Edition when I can get it and fully upgrade the 32GB of ram
|
|
|
|
kauai_lost_boi (OP)
Jr. Member
Offline
Activity: 56
Merit: 19
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 25, 2021, 02:00:02 AM |
|
So I am at 700 million at the 6 hour mark. At current pace, If I make 1.4 billion by the 12 hour mark, I will have passed the previous hurdle. I chose to run against 1 address instead of 10 and I saw a 2x jump in speed. Instead of the 22 k/ps I'm running at 38-32 k/ps. I will know more by the time I have my milk stout and cookies.
|
|
|
|
kauai_lost_boi (OP)
Jr. Member
Offline
Activity: 56
Merit: 19
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
July 25, 2021, 05:45:15 AM Last edit: July 25, 2021, 06:19:53 AM by kauai_lost_boi |
|
1.1 billion again and it's hung up badly but started up again after an hour. Didn't get the process kill code yet but I got a feeling it's coming. Gonna let this play out and see what happens but I think this is it for me on this angle. Gonna have to get a better setup before trying again but at least I know I got the winning formula, just need the right tools to work it out.
One thing of note. While getting to 1.1 billion, it seems to have been running off the RAM because the 6 disk raid array were not blinking. Ever since the hangup, it's running much slower with less results and all 6 disks are blinking like it's Xmas.
Maybe I'll be back in a month or so. Thanx to everyone who contributed. For now I may be beaten, but I'm far from defeated.
|
|
|
|
Fili777
Newbie
Offline
Activity: 1
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
December 24, 2022, 03:21:49 PM |
|
How finish this story? I have the same issue.
|
|
|
|
despo4helpo
Newbie
Offline
Activity: 16
Merit: 10
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 21, 2023, 04:24:25 AM |
|
1.1 billion again and it's hung up badly but started up again after an hour. Didn't get the process kill code yet but I got a feeling it's coming. Gonna let this play out and see what happens but I think this is it for me on this angle. Gonna have to get a better setup before trying again but at least I know I got the winning formula, just need the right tools to work it out.
One thing of note. While getting to 1.1 billion, it seems to have been running off the RAM because the 6 disk raid array were not blinking. Ever since the hangup, it's running much slower with less results and all 6 disks are blinking like it's Xmas.
Maybe I'll be back in a month or so. Thanx to everyone who contributed. For now I may be beaten, but I'm far from defeated.
I read your saga with interest. 2 years later, have you had any success?
|
|
|
|
kauai_lost_boi (OP)
Jr. Member
Offline
Activity: 56
Merit: 19
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
March 01, 2024, 07:58:40 PM Last edit: March 01, 2024, 08:57:21 PM by kauai_lost_boi |
|
|
|
|
|
|