Lets assume I did build a huge mining rig with 500+ TB. Does what you are saying imply that it might be wiser to split the mining rig into two times 250+ TB or even four times 125+ TB?
Posts made by TheTiny
-
RE: Does round time really matters?posted in Mining & Plotting
-
Read Speedposted in Mining & Plotting
I did like to know if thats about normal, or whether I should try to optimize my read performance:
1% done (0TB 79GB), avg.'89 MB/s'
2017-06-07 20:45:59.943 INFO 5720 --- [readerPool-2550] burstcoin.jminer.JMinerCommandLine : 12% done (3TB 597GB), avg.'476 MB/s', eff.'528 MB/s'
2017-06-07 20:46:01.522 INFO 5720 --- [readerPool-2551] burstcoin.jminer.JMinerCommandLine : 23% done (7TB 114GB), avg.'507 MB/s', eff.'543 MB/s'
2017-06-07 20:46:03.256 INFO 5720 --- [readerPool-2551] burstcoin.jminer.JMinerCommandLine : 34% done (10TB 712GB), avg.'507 MB/s', eff.'506 MB/s'
2017-06-07 20:46:04.677 INFO 5720 --- [readerPool-2548] burstcoin.jminer.JMinerCommandLine : 45% done (14TB 229GB), avg.'528 MB/s', eff.'604 MB/s'
2017-06-07 20:46:06.427 INFO 5720 --- [readerPool-2549] burstcoin.jminer.JMinerCommandLine : 56% done (17TB 827GB), avg.'522 MB/s', eff.'501 MB/s'
2017-06-07 20:46:08.083 INFO 5720 --- [readerPool-2549] burstcoin.jminer.JMinerCommandLine : 67% done (21TB 344GB), avg.'522 MB/s', eff.'518 MB/s'
2017-06-07 20:46:09.845 INFO 5720 --- [readerPool-2548] burstcoin.jminer.JMinerCommandLine : 78% done (24TB 942GB), avg.'518 MB/s', eff.'498 MB/s'
2017-06-07 20:46:11.556 INFO 5720 --- [readerPool-2549] burstcoin.jminer.JMinerCommandLine : 89% done (28TB 459GB), avg.'516 MB/s', eff.'501 MB/s'
2017-06-07 20:46:13.988 INFO 5720 --- [readerPool-2550] burstcoin.jminer.JMinerCommandLine : 100% done (31TB 977GB), avg.'491 MB/s', eff.'353 MB/s'
2017-06-07 20:46:14.238 INFO 5720 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : FINISH block '368561', best deadline '723241', round time '15s 888ms'1% done (0TB 79GB), avg.'121 MB/s'
2017-06-07 20:53:22.613 INFO 5720 --- [readerPool-2552] burstcoin.jminer.JMinerCommandLine : 12% done (3TB 597GB), avg.'469 MB/s', eff.'501 MB/s'
2017-06-07 20:53:24.183 INFO 5720 --- [readerPool-2557] burstcoin.jminer.JMinerCommandLine : 23% done (7TB 114GB), avg.'504 MB/s', eff.'546 MB/s'
2017-06-07 20:53:25.946 INFO 5720 --- [readerPool-2557] burstcoin.jminer.JMinerCommandLine : 34% done (10TB 712GB), avg.'502 MB/s', eff.'498 MB/s'
2017-06-07 20:53:27.666 INFO 5720 --- [readerPool-2555] burstcoin.jminer.JMinerCommandLine : 45% done (14TB 229GB), avg.'501 MB/s', eff.'499 MB/s'
2017-06-07 20:53:29.494 INFO 5720 --- [readerPool-2555] burstcoin.jminer.JMinerCommandLine : 56% done (17TB 827GB), avg.'497 MB/s', eff.'480 MB/s'
2017-06-07 20:53:31.183 INFO 5720 --- [readerPool-2555] burstcoin.jminer.JMinerCommandLine : 67% done (21TB 344GB), avg.'499 MB/s', eff.'508 MB/s'
2017-06-07 20:53:32.901 INFO 5720 --- [readerPool-2557] burstcoin.jminer.JMinerCommandLine : 78% done (24TB 942GB), avg.'500 MB/s', eff.'511 MB/s'
2017-06-07 20:53:34.443 INFO 5720 --- [readerPool-2555] burstcoin.jminer.JMinerCommandLine : 89% done (28TB 459GB), avg.'507 MB/s', eff.'556 MB/s'
2017-06-07 20:53:36.561 INFO 5720 --- [readerPool-2557] burstcoin.jminer.JMinerCommandLine : 100% done (31TB 977GB), avg.'493 MB/s', eff.'405 MB/s'
2017-06-07 20:53:36.812 INFO 5720 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : FINISH block '368563', best deadline '1116458', round time '15s 819ms' -
RE: How does Pool Mining work with Burst, and why do it at all?posted in Mining & Plotting
@Energy thank you. I know that calculator. What I do not know is if it's numbers are proofen by experience. After all I am considering to invest 370-1480€ per month into burst coin mining. ;)
-
RE: How does Pool Mining work with Burst, and why do it at all?posted in Mining & Plotting
@HiDevin @tross Thank you!
Makes sense.Is 600 BURST per month and TB a reasonable expectation?
I am considering to increase my stack by 10-40 TB per Month if that assumption holds. -
RE: How does Pool Mining work with Burst, and why do it at all?posted in Mining & Plotting
Re: [How does Pool Mining work with Burst](and why do it at all?)
Ah... I think I just solved the mistory by myself.
I thought the 35.82 BURST payment was from the lexicon pool, which would had implied that my pool earnings would had been quite empty before I hit the block, but that wasn't that case. The 38 BURST are from the previous pool I was mining on and therefor I do not know how much of I had on my lexicon pool collection before I hit the block.
Is there anyway to know that?
I am used to have quite precise mining statistics when mining ETH on ethermine.org
How come none of the BURST mining pools seem to offer individual mining statistics?If you solo mine you get all the block+fees, but you could be waiting days for a block.
What is an recomanded TB size to consider solo mining?
And how to choose the right pool depending on your current TB stack? -
How does Pool Mining work with Burst, and why do it at all?posted in Mining & Plotting
Can someone explain to me how Pool mining in Burst works?
Both technically as well as on the allocation side of things?Just to be clear: I am well aware what Pool Mining in general is. I come from ETH Mining and I am used to mine using mining pools. However I was a bit suprised when looking at my first 24h Mining results at http://burst.lexitoshi.uk
Although I am mining with 32TB the pool only payed out: 35.82 BURST after 24 hours...
I found this suprisingly low and I thought the entire pool must had been very unlucky.Few minutes later I was lucky enough to mine my first block and to my suprise I got 1914.50 BURST for my efforts, although the block according to the blockchain explorer was only worth 1853 BURST.
Here my mining balance and the Block in Question:
http://burstcoin.biz/address/2330812927884415672
http://burstcoin.biz/block/12879097186606044125Here are the rules of the Pool:
http://burst.lexitoshi.uk/howitwork.htmlI had expected something like a 50/50 share between rewards I get from mining a block myself and what I share with the Mining Pool, but thats obviously not what is happening...
Can someone explain that to me?
And how is this any different to what I would see if I did solo mine? -
RE: jminer 0.4.9-SNAPSHOT crash on startupposted in Help & Support
@luxe Thank you for your advice! I will do so :)
-
RE: jminer 0.4.9-SNAPSHOT crash on startupposted in Help & Support
ok! Thats good to know... But it kind of messes up the console:
: FINISH block '366051', best deadline '601611', round time '41s 265ms'
2017-05-31 21:14:34.870 WARN 6332 --- [askExecutor-206] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
2017-05-31 21:14:35.316 WARN 6332 --- [askExecutor-207] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
2017-05-31 21:14:49.309 WARN 6332 --- [askExecutor-217] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
2017-05-31 21:14:59.305 WARN 6332 --- [askExecutor-222] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
2017-05-31 21:15:03.303 WARN 6332 --- [askExecutor-224] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
2017-05-31 21:15:05.305 WARN 6332 --- [askExecutor-225] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
2017-05-31 21:15:07.308 WARN 6332 --- [askExecutor-226] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
2017-05-31 21:15:09.309 WARN 6332 --- [askExecutor-227] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
2017-05-31 21:15:11.303 WARN 6332 --- [askExecutor-228] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
2017-05-31 21:15:17.309 WARN 6332 --- [askExecutor-231] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
2017-05-31 21:15:19.312 WARN 6332 --- [askExecutor-232] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
2017-05-31 21:15:31.312 WARN 6332 --- [askExecutor-238] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
2017-05-31 21:15:55.315 WARN 6332 --- [askExecutor-250] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
2017-05-31 21:16:11.324 WARN 6332 --- [askExecutor-258] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
2017-05-31 21:16:21.333 INFO 6332 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : -------------------------------------------------------
2017-05-31 21:16:21.359 INFO 6332 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : START block '366052', scoopNumber '2312', capacity '31977 GB'
2017-05-31 21:16:21.360 INFO 6332 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : targetDeadline '1512000', baseTarget '827485'
2017-05-31 21:16:21.364 INFO 6332 --- [askExecutor-294] burstcoin.jminer.JMinerCommandLine : winner block '366051', 'BURST-6VYA-JEY2-R37W-EQFD9'
2017-05-31 21:16:21.514 INFO 6332 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '29379444' > '1512000' skipped
2017-05-31 21:16:21.515 INFO 6332 --- [ readerPool-15] burstcoin.jminer.JMinerCommandLine : 1% done (0TB 79GB), avg.'107 MB/s'
2017-05-31 21:16:21.526 INFO 6332 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '25429018' > '1512000' skipped
2017-05-31 21:16:21.541 INFO 6332 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '24886582' > '1512000' skipped
2017-05-31 21:16:21.690 INFO 6332 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '7221606' > '1512000' skipped
2017-05-31 21:16:22.092 INFO 6332 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '1404051' send (pool)
2017-05-31 21:16:23.239 INFO 6332 --- [ readerPool-14] burstcoin.jminer.JMinerCommandLine : 12% done (3TB 597GB), avg.'460 MB/s', eff.'497 MB/s'
2017-05-31 21:16:23.983 INFO 6332 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '28667' send (pool)
2017-05-31 21:16:24.616 WARN 6332 --- [askExecutor-295] b.j.c.n.task.NetworkSubmitPoolNonceTask : Error: Failed to submit nonce to pool due Exception.
2017-05-31 21:16:24.616 INFO 6332 --- [askExecutor-295] burstcoin.jminer.JMinerCommandLine : dl '1404051' NOT confirmed! [ 16d 6h 0m 51s ]
2017-05-31 21:16:24.647 INFO 6332 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '37091141' > '1512000' skipped
2017-05-31 21:16:24.737 INFO 6332 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '174708' send (pool)
2017-05-31 21:16:25.049 INFO 6332 --- [ readerPool-16] burstcoin.jminer.JMinerCommandLine : 23% done (7TB 114GB), avg.'467 MB/s', eff.'474 MB/s'
2017-05-31 21:16:26.118 INFO 6332 --- [ readerPool-15] burstcoin.jminer.core.round.Round : dl '325688' queued
2017-05-31 21:16:26.678 INFO 6332 --- [ readerPool-15] burstcoin.jminer.JMinerCommandLine : 34% done (10TB 712GB), avg.'489 MB/s', eff.'539 MB/s'
2017-05-31 21:16:26.976 INFO 6332 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '100510' send (pool)
2017-05-31 21:16:28.190 INFO 6332 --- [ readerPool-11] burstcoin.jminer.JMinerCommandLine : 45% done (14TB 229GB), avg.'506 MB/s', eff.'567 MB/s'
2017-05-31 21:16:29.897 INFO 6332 --- [ readerPool-15] burstcoin.jminer.JMinerCommandLine : 56% done (17TB 827GB), avg.'508 MB/s', eff.'514 MB/s'
2017-05-31 21:16:30.695 INFO 6332 --- [ roundPool-1] burstcoin.jminer.JMinerCommandLine : dl '28667' send (pool)
2017-05-31 21:16:31.607 INFO 6332 --- [ readerPool-11] burstcoin.jminer.JMinerCommandLine : 67% done (21TB 344GB), avg.'507 MB/s', eff.'502 MB/s'
2017-05-31 21:16:33.326 INFO 6332 --- [askExecutor-300] burstcoin.jminer.JMinerCommandLine : dl '100510' confirmed! [ 1d 3h 55m 10s ]
2017-05-31 21:16:33.374 INFO 6332 --- [ readerPool-11] burstcoin.jminer.JMinerCommandLine : 78% done (24TB 942GB), avg.'505 MB/s', eff.'497 MB/s'
2017-05-31 21:16:35.160 INFO 6332 --- [ readerPool-16] burstcoin.jminer.JMinerCommandLine : 89% done (28TB 459GB), avg.'502 MB/s', eff.'480 MB/s'
2017-05-31 21:16:37.630 INFO 6332 --- [ readerPool-15] burstcoin.jminer.JMinerCommandLine : 100% done (31TB 977GB), avg.'479 MB/s', eff.'347 MB/s'
2017-05-31 21:16:49.332 INFO 6332 --- [askExecutor-298] burstcoin.jminer.JMinerCommandLine : dl '174708' confirmed! [ 2d 0h 31m 48s ]
2017-05-31 21:16:49.379 INFO 6332 --- [askExecutor-303] burstcoin.jminer.JMinerCommandLine : dl '28667' confirmed! [ 0d 7h 57m 47s ]
2017-05-31 21:17:07.323 WARN 6332 --- [askExecutor-286] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
2017-05-31 21:17:09.323 WARN 6332 --- [askExecutor-287] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
2017-05-31 21:17:11.436 WARN 6332 --- [askExecutor-288] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
2017-05-31 21:17:13.334 WARN 6332 --- [askExecutor-289] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.
2017-05-31 21:17:17.323 WARN 6332 --- [askExecutor-291] b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.That can't be right, or?
Particular this line here:
2017-05-31 21:17:24.110 WARN 6332 --- [askExecutor-297] b.j.c.n.task.NetworkSubmitPoolNonceTask : Error: Failed to submit nonce to pool due Exception. -
RE: jminer 0.4.9-SNAPSHOT crash on startupposted in Help & Support
ok... Now I only get:
Unable to get mining info from wallet, caused by connectionTimeout, currently '30 sec.' try increasing it!
and after increasing the connectionTimeout value to 100000:
b.j.c.n.t.NetworkRequestMiningInfoTask : Unable to get mining info from wallet.What am I missing?
-
RE: jminer 0.4.9-SNAPSHOT crash on startupposted in Help & Support
Never mind! ... I found it... It was the wrong devise selected :/
-
jminer 0.4.9-SNAPSHOT crash on startupposted in Help & Support
I tryed to get the jminer running on my machine, but it crashes right from the start.
I assume its some silly mistake on the configuration part, but to be honest I have no clue where to look.java -jar -d64 -XX:+UseG1GC burstcoin-jminer-0.4.9-SNAPSHOT.jar
20:50:06.677 [main] INFO burstcoin.jminer.JMinerApplication - Starting the engines ... please wait!
2017-05-31 20:50:07.534 INFO 8792 --- [ main] b.jminer.core.checker.util.OCLChecker : -------------------------------------------------------
2017-05-31 20:50:07.536 INFO 8792 --- [ main] b.jminer.core.checker.util.OCLChecker : List of system openCL platforms and devices (* = used for mining)
2017-05-31 20:50:07.536 INFO 8792 --- [ main] b.jminer.core.checker.util.OCLChecker :
2017-05-31 20:50:07.540 INFO 8792 --- [ main] b.jminer.core.checker.util.OCLChecker : * PLATFORM-[0] NVIDIA CUDA - (OpenCL 1.2 CUDA 8.0.0)
2017-05-31 20:50:07.541 INFO 8792 --- [ main] b.jminer.core.checker.util.OCLChecker : DEVICE-[0] GeForce GTX 970 (4GB) - NVIDIA Corporation (OpenCL 1.2 CUDA | '376.53')
2017-05-31 20:50:07.542 INFO 8792 --- [ main] b.jminer.core.checker.util.OCLChecker : [0] work group size: '1024', computing units: '13', available 'true'
2017-05-31 20:50:07.543 WARN 8792 --- [ main] s.c.a.AnnotationConfigApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'OCLChecker': Invocation of init method failed; nested exception is java.lang.ArrayIndexOutOfBoundsException: Invalid device id
2017-05-31 20:50:07.555 ERROR 8792 --- [ main] o.s.boot.SpringApplication : Application startup failedorg.springframework.beans.factory.BeanCreationException: Error creating bean with name 'OCLChecker': Invocation of init method failed; nested exception is java.lang.ArrayIndexOutOfBoundsException: Invalid device id
at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:137) ~[spring-beans-4.3.7.RELEASE.jar!/:4.3.7.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:409) ~[spring-beans-4.3.7.RELEASE.jar!/:4.3.7.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1620) ~[spring-beans-4.3.7.RELEASE.jar!/:4.3.7.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:555) ~[spring-beans-4.3.7.RELEASE.jar!/:4.3.7.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483) ~[spring-beans-4.3.7.RELEASE.jar!/:4.3.7.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306) ~[spring-beans-4.3.7.RELEASE.jar!/:4.3.7.RELEASE]
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230) ~[spring-beans-4.3.7.RELEASE.jar!/:4.3.7.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302) ~[spring-beans-4.3.7.RELEASE.jar!/:4.3.7.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197) ~[spring-beans-4.3.7.RELEASE.jar!/:4.3.7.RELEASE]
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:761) ~[spring-beans-4.3.7.RELEASE.jar!/:4.3.7.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:866) ~[spring-context-4.3.7.RELEASE.jar!/:4.3.7.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:542) ~[spring-context-4.3.7.RELEASE.jar!/:4.3.7.RELEASE]
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:737) ~[spring-boot-1.5.2.RELEASE.jar!/:1.5.2.RELEASE]
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:370) ~[spring-boot-1.5.2.RELEASE.jar!/:1.5.2.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:314) ~[spring-boot-1.5.2.RELEASE.jar!/:1.5.2.RELEASE]
at burstcoin.jminer.JMinerApplication.main(JMinerApplication.java:60) [classes!/:0.4.9-SNAPSHOT]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_131]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[na:1.8.0_131]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[na:1.8.0_131]
at java.lang.reflect.Method.invoke(Unknown Source) ~[na:1.8.0_131]
at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48) [burstcoin-jminer-0.4.9-SNAPSHOT.jar:0.4.9-SNAPSHOT]
at org.springframework.boot.loader.Launcher.launch(Launcher.java:87) [burstcoin-jminer-0.4.9-SNAPSHOT.jar:0.4.9-SNAPSHOT]
at org.springframework.boot.loader.Launcher.launch(Launcher.java:50) [burstcoin-jminer-0.4.9-SNAPSHOT.jar:0.4.9-SNAPSHOT]
at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:51) [burstcoin-jminer-0.4.9-SNAPSHOT.jar:0.4.9-SNAPSHOT]
Caused by: java.lang.ArrayIndexOutOfBoundsException: Invalid device id
at burstcoin.jminer.core.checker.util.OCLChecker.initChecker(OCLChecker.java:103) ~[classes!/:0.4.9-SNAPSHOT]
at burstcoin.jminer.core.checker.util.OCLChecker.postConstruct(OCLChecker.java:78) ~[classes!/:0.4.9-SNAPSHOT]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_131]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[na:1.8.0_131]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[na:1.8.0_131]
at java.lang.reflect.Method.invoke(Unknown Source) ~[na:1.8.0_131]
at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleElement.invoke(InitDestroyAnnotationBeanPostProcessor.java:366) ~[spring-beans-4.3.7.RELEASE.jar!/:4.3.7.RELEASE]
at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor$LifecycleMetadata.invokeInitMethods(InitDestroyAnnotationBeanPostProcessor.java:311) ~[spring-beans-4.3.7.RELEASE.jar!/:4.3.7.RELEASE]
at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:134) ~[spring-beans-4.3.7.RELEASE.jar!/:4.3.7.RELEASE]
... 23 common frames omittedMy property files currently looks like this:
plotPaths=I:/Burst/plots,H:/Burst/plots,G:/Burst/plots,F:/Burst/plots,
poolMining=true
numericAccountId=2330812927884415672
poolServer=http://pool.burstcoin.eu:8124
walletServer=http://localhost:8125
winnerRetriesOnAsync=
winnerRetryIntervalInMs=
devPool=false
devPoolCommitsPerRound=
soloServer=http://localhost:8125
passPhrase=xxxxxxxxxxxxxx
targetDeadline=
platformId=0
deviceId=1
chunkPartNonces=320000
refreshInterval=2000
connectionTimeout=30000 -
RE: [ERROR] Error while writting to plots fileposted in Help & Support
@Evo said in [ERROR] Error while writting to plots file:
The solution, for me at least, was to use multiple smaller plot files to file the drives. I use around 2TB each, adjusted as needed to fit the available free space. When mining, this is not a bit slower either. You might try this and see if you have better luck. Let us know...
Thats good to know! I did read/hear somewhere that you should have your plotfiles as big as possible.
Should my current try fail again, I will follow your advise. -
RE: [ERROR] Error while writting to plots fileposted in Help & Support
1 GB worked just fine... I now restarted 8 TB using the Lex-Wallet calculator.
Fingers crossed that this time it works, -
RE: [ERROR] Error while writting to plots fileposted in Help & Support
@PingOfd3ath said in [ERROR] Error while writting to plots file:
can i ask what calculator? the one in lexicon's wallet?
No.. I did mean my brain + "calc" ... where can I find the lexicons wallet you are talking about.
need to have it fit into the AVAILABLE system resources, you can have 16gb of RAM but you only have say 5 GB of RAM available, if that makes sense
Sure! But that obviously varries depending on the work of the machine. Currently its 11.1 GB
But worst case the machine should start swapping. Obviously not good for the performance, but at least in theorie it shouldn't break the process. Particular not at the very end... -
RE: [ERROR] Error while writting to plots fileposted in Help & Support
contact with a man that knows more about the gpu plotter
Thank you!
that error is normally when there is no /burst/ folder before starting the plot generator
What am I supposed to do? I just created the folder "Burst" by hand.
that stagger works out but is a very strange stagger, may i ask how you got it?
With the calculator :P
Tried to get the stagger as high as possible while still being a subdivision of 30496000
4x16000 also just so seemed to fit into the 16 GB of RAM. Or did I mess it up? -
[ERROR] Error while writting to plots fileposted in Help & Support
I am starting to give up on trying to plot my hard drive. :/
I have 4x8TB HDD and tryed it with:
gpuPlotGenerator generate direct F://Burst/2330812927884415672_0_30496000_16000 G://Burst/2330812927884415672_30496000_30496000_16000 H://Burst/2330812927884415672_60992000_30496000_16000 I://Burst/2330812927884415672_91488000_30496000_16000It did run multiple days, but didn't finish although all of the disks had still some TB of free space. The only error message I got was "[ERROR] Error while writting to plots file"
I now tryed it again with plotting only one file:
gpuPlotGenerator generate direct F://Burst/2330812927884415672_0_30496000_32000It took 3 days and again ended with the same error message. This time the disk only had 1.27 GB left.
Here the full return of the console:
GPU plot generator v4.0.3
Author: Cryo
Bitcoin: 138gMBhCrNkbaiTCmUhP9HLU9xwn5QKZgD
Burst: BURST-YA29-QCEW-QXC3-BKXDLLoading platforms...
Loading devices...
Loading devices configurations...
Initializing generation devices...
[0] Device: GeForce GTX 970 (OpenCL 1.2 CUDA)
[0] Device memory: 256MB
[0] CPU memory: 256MB
Initializing generation contexts...
[0] Path: F://Burst/2330812927884415672_0_30496000_30496000
[0] Nonces: 0 to 30495999 (7TB 277GB 320MB)
[0] CPU memory: 7GB 832MBDevices number: 1
Plots files number: 1
Total nonces number: 30496000
CPU memory: 8GB 64MBGenerating nonces...
0.10% (31744/30496000 remaining nonces), 17800.37 nonces/minutes, ETA: 1d 4h 31m 26s...
[ERROR] Error while writting to plots fileWhat am I doing wrong?!
-
RE: {"errorDescription":"Unknown account","errorCode":5}posted in Mining & Plotting
@haitch Ah! Ok! Thats probably the reason. Although that still doesn't explain why I failed so many time with Fauncets before. Anyway... Now it works! :) Thank you and happy mining
-
RE: {"errorDescription":"Unknown account","errorCode":5}posted in Mining & Plotting
@haitch thank you for the offer! Fauncets work for the first wallet, but didn't for my second wallet. Might this be due to the second wallet only beeing 92% in sync yet?