BURST BASH!!!!! 48 HOURS Starting Monday 18:00 CET
-
@RichBC leave the # off sorry!
-
@tross OK all set and nearly there, just need another confirmation, but we need some more miners.
Rich
-
Go to http://burst.lexitoshi.uk/# for another 24hr of fun! People are still going to my pool ! Go to lexicon pool and get free burst!
-
@IceBurst said in BURST BASH!!!!! 48 HOURS Starting Monday 18:00 CET:
Very interesting, I always wondered about sloppy graphics now I have my own to submit. Here is a clean run, with values as requested on the new JMiner 4.5. See how Block #1 on the start works fine and then I don't get confirms from any future blocks?
@IceBurst In jminer 4.5 the 'strange dl' stuff is only logged if you enable 'debug=true' in jminer.properties. If not it will just not confirm. The 'strange dl' is not necessary related to a pool, i also get it on solo from time to time, may indicate a partly corrupted plotfile, i'm not sure why in some cases the calculated dl by miner does not match with calculated from wallet. (But thats why this shows up) It may be just a read issue ... i fixed some of this by replotting the affected plotfiles ... but i'm getting lazy these days, so i just live with it if it appears from time to time. If you enable debug, you may notice, that it is the same plotfile causing this in most cases.
Edit: Your drive may also be the issue, check SMART status or/and try chkdsk on it.
-
@luxe Thanks @luxe as you can see in my properties file I do have debug=true. It's very odd that it happens consistently after the first block and only on this one pool, I switched back to Burst-Team today and the issue never showed up again. If my drives are failing I'm in big trouble as this machine isn't even a year old yet or my office raid array is failing which would be even worse! If I find time to look at it some more I will but I think for the time being I'm marking this as, "Closed" - "Over Come By Events"
-IceBurst
-
sending another 3k shortly just waiting for my wallet to start up

