Skip to main content
11 events
when toggle format what by license comment
Jan 6, 2017 at 21:50 answer added Richard Horrocks timeline score: 3
Jan 3, 2017 at 0:40 comment added galahad @Avatar Yes. That solved the problem.
Dec 29, 2016 at 9:18 comment added alper @variable I am facing with the same problem. My node has 2GB RAM, so due to the low memory while mining, DAG generation always fails and force me to remove /.ethash file, start mining and re-create DAG files from scratch. Does disable autodag solved your problem?
Jul 9, 2016 at 23:40 vote accept galahad
Jul 8, 2016 at 15:07 history edited galahad CC BY-SA 3.0
added 32 characters in body; edited title
Jul 8, 2016 at 15:06 answer added galahad timeline score: 4
Jul 8, 2016 at 13:53 comment added galahad Yes. Starting over from the beginning is a temporary solution but that would delete all the data, which is not desired. I saw this --autodag option in geth --help but couldn't figure out how to use it.
Jul 8, 2016 at 3:32 comment added niksmac Okay, so DAG is supposed to contain the previous work you have done to prove your work; PoW, so it has to recreate to match the new blocks in it. the way i do is to delete the chain data and start from block #1
Jul 8, 2016 at 3:21 comment added galahad @niksmac While mining my private blockchain, , automatic generation of DAG for epoch 1 started at block #16092. I had a lot of processes running at that time and the DAG generation failed due to low memory which ultimately stopped the mining process. So, I pre-generated DAG for epoch 1 and then started mining again. I want to disable this because I don't want the miner to crash while generating DAG for epoch 2 again.
Jul 8, 2016 at 3:13 comment added niksmac Why do you want to disable DAG Generation? out of curiosity.
Jul 7, 2016 at 15:45 history asked galahad CC BY-SA 3.0