Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 - page 628. (Read 2171078 times)
October 19, 2014, 11:21:39 PM
350 burst a day last week, but it seems that burst price is too low, lots of miners leave away, now should be more, last week , has 6000TB, now seems only 5000TB
October 19, 2014, 11:12:17 PM
October 19, 2014, 10:57:18 PM
If i have 1tb drive and 8gb ram, then how many bursts will i be mining daily?
October 19, 2014, 10:02:39 PM
I use Blago's miner across all of my 5 rigs (8 TB each) total 40 TB.
Since when Uray has changed his servers, I get lots of block which ends up even before my miner can complete reading the entire plots (~25 sec)
And I get really lot many blocks with this kind of message ! almost like once every 4-5 blocks (i.e. ~20-25%)
So who is the culprit here,
Uray's Pool which can't response in time after hardware change ?
Blago's miner which takes more time to sending the data ?
Something else which makes very short blocks & get those 20-25% blocks by solo ?
If it's something else, may be it's the reason why people reported above don't find enough blocks by solo !
Since when Uray has changed his servers, I get lots of block which ends up even before my miner can complete reading the entire plots (~25 sec)
Quote
-------------- New block 24862, basetarget 3581481 --------------
[2988616918834149562] confirmed deadline: 2954071 34d 4h 34m 31s
Thread "D:\plots\" done! [~25 sec] (18 files)
Thread "E:\plots\" done! [~25 sec] (18 files)
recieving data...
-------------- New block 24864, basetarget 3583972 --------------
shares lost due to new block
[2988616918834149562] confirmed deadline: 2954071 34d 4h 34m 31s
Thread "D:\plots\" done! [~25 sec] (18 files)
Thread "E:\plots\" done! [~25 sec] (18 files)
recieving data...
-------------- New block 24864, basetarget 3583972 --------------
shares lost due to new block
And I get really lot many blocks with this kind of message ! almost like once every 4-5 blocks (i.e. ~20-25%)
So who is the culprit here,
Uray's Pool which can't response in time after hardware change ?
Blago's miner which takes more time to sending the data ?
Something else which makes very short blocks & get those 20-25% blocks by solo ?
If it's something else, may be it's the reason why people reported above don't find enough blocks by solo !
miner sends data and waits for an acknowledgment from the server. In the first 2 minutes it takes a lot of time on overloaded servers.
Now I do asynchronous work with the server - first send all the data, and then we'll wait for them to confirm.
October 19, 2014, 09:58:20 PM
I get quiet a few red lines about some plots being "locked?". But nothing uses the files beside the miner so I'm not sure what's going on.
This error occurs when the unexpected end of file.
Recalculate size/file name, reduce the "CacheSize".
Miner reads the file in chunks of CacheSize nonces, but suddenly the end of file (possibly in the middle).
October 19, 2014, 09:12:28 PM
I get quiet a few red lines about some plots being "locked?". But nothing uses the files beside the miner so I'm not sure what's going on.
This error occurs when the unexpected end of file.
Recalculate size/file name, reduce the "CacheSize".
I think that locked files are being skipped in that block, I guess that's why it says 99%.
October 19, 2014, 08:05:28 PM
I use Blago's miner across all of my 5 rigs (8 TB each) total 40 TB.
Since when Uray has changed his servers, I get lots of block which ends up even before my miner can complete reading the entire plots (~25 sec)
And I get really lot many blocks with this kind of message ! almost like once every 4-5 blocks (i.e. ~20-25%)
So who is the culprit here,
Uray's Pool which can't response in time after hardware change ?
Blago's miner which takes more time to sending the data ?
Something else which makes very short blocks & get those 20-25% blocks by solo ?
If it's something else, may be it's the reason why people reported above don't find enough blocks by solo !
Since when Uray has changed his servers, I get lots of block which ends up even before my miner can complete reading the entire plots (~25 sec)
Quote
-------------- New block 24862, basetarget 3581481 --------------
[2988616918834149562] confirmed deadline: 2954071 34d 4h 34m 31s
Thread "D:\plots\" done! [~25 sec] (18 files)
Thread "E:\plots\" done! [~25 sec] (18 files)
recieving data...
-------------- New block 24864, basetarget 3583972 --------------
shares lost due to new block
[2988616918834149562] confirmed deadline: 2954071 34d 4h 34m 31s
Thread "D:\plots\" done! [~25 sec] (18 files)
Thread "E:\plots\" done! [~25 sec] (18 files)
recieving data...
-------------- New block 24864, basetarget 3583972 --------------
shares lost due to new block
And I get really lot many blocks with this kind of message ! almost like once every 4-5 blocks (i.e. ~20-25%)
So who is the culprit here,
Uray's Pool which can't response in time after hardware change ?
Blago's miner which takes more time to sending the data ?
Something else which makes very short blocks & get those 20-25% blocks by solo ?
If it's something else, may be it's the reason why people reported above don't find enough blocks by solo !
October 19, 2014, 07:59:38 PM
I get quiet a few red lines about some plots being "locked?". But nothing uses the files beside the miner so I'm not sure what's going on.
This error occurs when the unexpected end of file.
Recalculate size/file name, reduce the "CacheSize".
October 19, 2014, 06:09:00 PM
- Client (using dcct's, but happens with java client too) reports a deadline of 6/7 digits.
- Pools (tried several) report a deadline of hours.
- Pools (tried several) report a deadline of hours.
I'm not seeing this with Uray's miner and crowetic's, fanepatent's et al.'s pool.
October 19, 2014, 05:51:08 PM
11 Days without a block with 9TB - what is going on with this thing? Was finding a block every day or two at most for the last 50 days until the 8th of October. Everything running as it should.
There's a spot of bad luck and then there's this.
There's a spot of bad luck and then there's this.
9TB is not enough to solo mine IMO. Why don't you come join us at mine.burstcoin.info? I'm still doing my giveaway of 1600 burst for new miners.
9TB is and has been plenty for a block every couple of days/3 days max. Why is it suddenly not happening now? Has anything changed since the 9th of October that could stop the java miner from working as it should?
Same here with 60TB. Doesn't find block since 2 days. Before that it worked great. No idea what happens then.
Something is definitely wrong then. Who is getting more than their fair share of the blocks? Is it possible to rig the process or tip the scales to make your plots 'luckier' than others?
same here, not only am I not getting any blocks (12TB), but all my nonce submitted are all at least 8 digits, the smallest nonce submitted was 6 digits (in 5 days).
after 5 days of this, I switched to pool2.burstcoin.io, 4 digit nonce are more frequent now. Not sure what's going on.
Exactly what I am getting as well. Literally nothign has changed since the 8th of October and yet I still haven't got a block and most "best" deadlines are 5 or 6 figures.
What is going on here? it ain't monumental bad luck - not for all of us.
12hrs after switching from solo to pool2, got a block.
October 19, 2014, 05:36:11 PM
Exactly what I am getting as well. Literally nothign has changed since the 8th of October and yet I still haven't got a block and most "best" deadlines are 5 or 6 figures.
What is going on here? it ain't monumental bad luck - not for all of us.
Question: are you just looking at your miner's output, or are you watching what the pool is reporting, too?
Because, since 1 week ago (sort of), I have been looking at both at the same time, and this is what I found:
- Client (using dcct's, but happens with java client too) reports a deadline of 6/7 digits.
- Pools (tried several) report a deadline of hours.
I don't know if it's the client's fault, or the pool's fault.
But we are paid by the pools, not the clients, so what I see the pool report is what is used to calculate payment.
Anyway, there's some serious fail coding somewhere.
I've seen so many people talk about the future of this altcoin and focusing on advertising and investors, blah blah, but the blunt truth is that any investor will not want to invest on something that is so broken.
well done m3ta, grammar and spell checker says "you passed"
October 19, 2014, 05:24:08 PM
Anyway, there's some serious fail coding somewhere.
I've seen so many people talk about the future of this altcoin and focusing on advertising and investors, blah blah, but the blunt truth is that any investor will not want to invest on something that is so broken.
I've seen so many people talk about the future of this altcoin and focusing on advertising and investors, blah blah, but the blunt truth is that any investor will not want to invest on something that is so broken.
Some of third party tools are incompatible or have known issues, but dev can't be held responsible for other developers code. Did you try dev2 pool? I've checked the shares list and it did register all the shares which were sent to it.
October 19, 2014, 04:55:41 PM
Exactly what I am getting as well. Literally nothign has changed since the 8th of October and yet I still haven't got a block and most "best" deadlines are 5 or 6 figures.
What is going on here? it ain't monumental bad luck - not for all of us.
Question: are you just looking at your miner's output, or are you watching what the pool is reporting, too?
Because, since 1 week ago (sort of), I have been looking at both at the same time, and this is what I found:
- Client (using dcct's, but happens with java client too) reports a deadline of 6/7 digits.
- Pools (tried several) report a deadline of hours.
I don't know if it's the client's fault, or the pool's fault.
But we are paid by the pools, not the clients, so what I see the pool report is what is used to calculate payment.
Anyway, there's some serious fail coding somewhere.
I've seen so many people talk about the future of this altcoin and focusing on advertising and investors, blah blah, but the blunt truth is that any investor will not want to invest on something that is so broken.
October 19, 2014, 04:31:32 PM
is this legit?
You can check the commit, which is a very simple change, and run it from source, if you're paranoid.
October 19, 2014, 04:31:02 PM
11 Days without a block with 9TB - what is going on with this thing? Was finding a block every day or two at most for the last 50 days until the 8th of October. Everything running as it should.
There's a spot of bad luck and then there's this.
There's a spot of bad luck and then there's this.
9TB is not enough to solo mine IMO. Why don't you come join us at mine.burstcoin.info? I'm still doing my giveaway of 1600 burst for new miners.
9TB is and has been plenty for a block every couple of days/3 days max. Why is it suddenly not happening now? Has anything changed since the 9th of October that could stop the java miner from working as it should?
Same here with 60TB. Doesn't find block since 2 days. Before that it worked great. No idea what happens then.
Something is definitely wrong then. Who is getting more than their fair share of the blocks? Is it possible to rig the process or tip the scales to make your plots 'luckier' than others?
same here, not only am I not getting any blocks (12TB), but all my nonce submitted are all at least 8 digits, the smallest nonce submitted was 6 digits (in 5 days).
after 5 days of this, I switched to pool2.burstcoin.io, 4 digit nonce are more frequent now. Not sure what's going on.
Exactly what I am getting as well. Literally nothign has changed since the 8th of October and yet I still haven't got a block and most "best" deadlines are 5 or 6 figures.
What is going on here? it ain't monumental bad luck - not for all of us.
October 19, 2014, 03:30:22 PM
Burst 1.1.4
Download: https://mega.co.nz/#!3hRECaCa!bnxGQJhsAU4EreDtvmFxkEWfccgsEp4rqxeen5eGWT0
https://github.com/BurstProject/burstcoin
This is a small update to apply a bug fix from nxt 1.2.9. Nxt considers this a critical bugfix
Download: https://mega.co.nz/#!3hRECaCa!bnxGQJhsAU4EreDtvmFxkEWfccgsEp4rqxeen5eGWT0
https://github.com/BurstProject/burstcoin
This is a small update to apply a bug fix from nxt 1.2.9. Nxt considers this a critical bugfix
is this legit?
October 19, 2014, 03:27:38 PM
11 Days without a block with 9TB - what is going on with this thing? Was finding a block every day or two at most for the last 50 days until the 8th of October. Everything running as it should.
There's a spot of bad luck and then there's this.
There's a spot of bad luck and then there's this.
9TB is not enough to solo mine IMO. Why don't you come join us at mine.burstcoin.info? I'm still doing my giveaway of 1600 burst for new miners.
9TB is and has been plenty for a block every couple of days/3 days max. Why is it suddenly not happening now? Has anything changed since the 9th of October that could stop the java miner from working as it should?
Same here with 60TB. Doesn't find block since 2 days. Before that it worked great. No idea what happens then.
Something is definitely wrong then. Who is getting more than their fair share of the blocks? Is it possible to rig the process or tip the scales to make your plots 'luckier' than others?
same here, not only am I not getting any blocks (12TB), but all my nonce submitted are all at least 8 digits, the smallest nonce submitted was 6 digits (in 5 days).
after 5 days of this, I switched to pool2.burstcoin.io, 4 digit nonce are more frequent now. Not sure what's going on.
October 19, 2014, 02:49:32 PM
With dcct's miner on ubuntu, I occasionally get failures like this:
No mining happens after that, these errors just keep repeating. Anyone know why, or how to prevent/mitigate this?
Code:
Sun Oct 19 03:05:14 EDT 2014 New block 24597, basetarget 3524215
Sun Oct 19 03:05:14 EDT 2014 0 MB read/0 GB total/no deadline
Sun Oct 19 03:05:24 EDT 2014 1298 MB read/5192 GB total/deadline 107733s (107723s left)
Sun Oct 19 03:05:34 EDT 2014 2631 MB read/10526 GB total/deadline 107733s (107713s left)
Sun Oct 19 03:05:44 EDT 2014 3894 MB read/15576 GB total/deadline 107733s (107703s left)
Sun Oct 19 03:05:54 EDT 2014
Sun Oct 19 03:05:54 EDT 2014 New block 24598, basetarget 3572447
Sun Oct 19 03:05:54 EDT 2014
Sun Oct 19 03:05:54 EDT 2014 Error opening file /media/mnt3/pocminer_v1/plots//7515816275136675106_5489982836908570030_14251415_7500
Sun Oct 19 03:05:54 EDT 2014
Sun Oct 19 03:05:54 EDT 2014 Error opening file /media/mnt1/pocminer_v1/plots//7515816275136675106_4649136569149861420_6328811_7500
Sun Oct 19 03:05:54 EDT 2014
Sun Oct 19 03:05:54 EDT 2014 Node: Connection refused
Sun Oct 19 03:05:54 EDT 2014
Sun Oct 19 03:05:54 EDT 2014 Could not get mining info from Node. Will retry..
Sun Oct 19 03:05:54 EDT 2014
Sun Oct 19 03:05:54 EDT 2014 Error opening file /media/mnt2/pocminer_v1/plots//7515816275136675106_1451734932719538615_14488138_7500
Sun Oct 19 03:05:55 EDT 2014
Sun Oct 19 03:05:55 EDT 2014 Error sending result to node
Sun Oct 19 03:05:14 EDT 2014 0 MB read/0 GB total/no deadline
Sun Oct 19 03:05:24 EDT 2014 1298 MB read/5192 GB total/deadline 107733s (107723s left)
Sun Oct 19 03:05:34 EDT 2014 2631 MB read/10526 GB total/deadline 107733s (107713s left)
Sun Oct 19 03:05:44 EDT 2014 3894 MB read/15576 GB total/deadline 107733s (107703s left)
Sun Oct 19 03:05:54 EDT 2014
Sun Oct 19 03:05:54 EDT 2014 New block 24598, basetarget 3572447
Sun Oct 19 03:05:54 EDT 2014
Sun Oct 19 03:05:54 EDT 2014 Error opening file /media/mnt3/pocminer_v1/plots//7515816275136675106_5489982836908570030_14251415_7500
Sun Oct 19 03:05:54 EDT 2014
Sun Oct 19 03:05:54 EDT 2014 Error opening file /media/mnt1/pocminer_v1/plots//7515816275136675106_4649136569149861420_6328811_7500
Sun Oct 19 03:05:54 EDT 2014
Sun Oct 19 03:05:54 EDT 2014 Node: Connection refused
Sun Oct 19 03:05:54 EDT 2014
Sun Oct 19 03:05:54 EDT 2014 Could not get mining info from Node. Will retry..
Sun Oct 19 03:05:54 EDT 2014
Sun Oct 19 03:05:54 EDT 2014 Error opening file /media/mnt2/pocminer_v1/plots//7515816275136675106_1451734932719538615_14488138_7500
Sun Oct 19 03:05:55 EDT 2014
Sun Oct 19 03:05:55 EDT 2014 Error sending result to node
No mining happens after that, these errors just keep repeating. Anyone know why, or how to prevent/mitigate this?
October 19, 2014, 08:30:13 AM
I think it's just the fact that you're competing with large pools. It even takes out small-med sized pool a while to find a block... I know that Uray's pools find a lot and so does the dev's v2.
October 19, 2014, 05:06:19 AM
11 Days without a block with 9TB - what is going on with this thing? Was finding a block every day or two at most for the last 50 days until the 8th of October. Everything running as it should.
There's a spot of bad luck and then there's this.
There's a spot of bad luck and then there's this.
9TB is not enough to solo mine IMO. Why don't you come join us at mine.burstcoin.info? I'm still doing my giveaway of 1600 burst for new miners.
9TB is and has been plenty for a block every couple of days/3 days max. Why is it suddenly not happening now? Has anything changed since the 9th of October that could stop the java miner from working as it should?
Same here with 60TB. Doesn't find block since 2 days. Before that it worked great. No idea what happens then.
Something is definitely wrong then. Who is getting more than their fair share of the blocks? Is it possible to rig the process or tip the scales to make your plots 'luckier' than others?
Jump to: