Check out my Review of BurstCoin!
http://www.cryptotycoons.com/2014/08/burstcoin-burst-fresh-air-miners/
Follow us Twitter: https://twitter.com/cryptotycoons
Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 - page 1205. (Read 2170889 times)
August 18, 2014, 08:14:52 PM
August 18, 2014, 08:07:26 PM
Hey burstcoin, question for you. If I wanted to CPU mine Burst, I understand that I'm limited in speed by the rate I can generate plots, so it's not viable. However, would it be possible to make a mining program that only generated the relevant scoop of each nonce for the current block therefore being 4096x faster?
August 18, 2014, 07:57:07 PM
Trying now.
try -Xmx1500m
2TB and java -Xmx750m .
@BurstBurst:
What is plot file size and your available RAM and your run_mine command ?
What is plot file size and your available RAM and your run_mine command ?
try -Xmx1500m
i had the same settings as u burstburst. i've upped the allowance to 1024m and so far so good. the pc i'm running it on is a win 8.1 with 4bg of ram and running java 1.7.0_60-b19
August 18, 2014, 07:51:42 PM
Wallet can't find recent blocks is it offline ?? 
Nope, just give it a few minutes to connect. August 18, 2014, 07:47:42 PM
Wallet can't find recent blocks is it offline ??
August 18, 2014, 07:26:55 PM
BURST for sale... If you want to avoid incurring additional fees on trades and want to complete a basic BTC for BURST exchange PM me...
NO HASSLE TRADES
I have 300K + Available... I will even match the AE price of 0.003474 BTC / 1000 BURST
30K lots, 50K lots, 100K lots, and even 300K lots if needed. PM me, Thanx!
Can use escrow, or break it up into smaller tarnsactions and straight trade. Let me know.
That's cheaper than the lowest sell at Poloniex @ 0.00353028 for 52 NXT (which would be required to make that transaction)
Dgex is not working for withdrawls or deposits, so actually getting NXT back to BTC has limited options right now...
NO HASSLE TRADES
I have 300K + Available... I will even match the AE price of 0.003474 BTC / 1000 BURST
30K lots, 50K lots, 100K lots, and even 300K lots if needed. PM me, Thanx!
Can use escrow, or break it up into smaller tarnsactions and straight trade. Let me know.
That's cheaper than the lowest sell at Poloniex @ 0.00353028 for 52 NXT (which would be required to make that transaction)
Dgex is not working for withdrawls or deposits, so actually getting NXT back to BTC has limited options right now...
August 18, 2014, 07:03:15 PM
For 4TB+ plots, 2GB of RAM for the miner seems to do the trick. Been running steady for 3+ days with no issues.
It seems weird for that to be an issue. It shouldn't require more over time unless the gc isn't working right. 
August 18, 2014, 07:01:41 PM
Trying now.
try -Xmx1500m
2TB and java -Xmx750m .
@BurstBurst:
What is plot file size and your available RAM and your run_mine command ?
What is plot file size and your available RAM and your run_mine command ?
try -Xmx1500m
August 18, 2014, 06:56:29 PM
2TB and java -Xmx750m .
@BurstBurst:
What is plot file size and your available RAM and your run_mine command ?
What is plot file size and your available RAM and your run_mine command ?
try -Xmx1500m
August 18, 2014, 06:54:27 PM
2TB and java -Xmx750m .
@BurstBurst:
What is plot file size and your available RAM and your run_mine command ?
What is plot file size and your available RAM and your run_mine command ?
August 18, 2014, 06:52:29 PM
For 4TB+ plots, 2GB of RAM for the miner seems to do the trick. Been running steady for 3+ days with no issues.
August 18, 2014, 06:49:22 PM
Same problem. Anyone know How to handle large size plot with out crashing the miner ?
I think my question got overlooked, can anyone help me out with this? Thanks!
Is it just the miner that stops or is it a plot generation too?
Try adding the word pause on a line after everything else on your bat file
java -Xmxblah blah blah blah
pause
When it dies it will pause the command prompt and ask you to press a button to shut down. This way you can see what the error is that is killing the process.
Once you get that it is much easier to help diagnose the problem.
Edit:
I am assuming your on windows.
Yea, I have already added pause to it, and am awaiting the next time it crashes out.... It is only the miner, and only 1 of the 2 miners running on the system. The one on the other drive never crashes. Very strange. The plot generation is fine on both drives.
bad sectors of your HDD?
I really don't think so... well, I guess, at least I hope not... This drive, as with almost all of the drives/components in the system in question, are almost brand new WD NAS drives. Do you think that bad sectors would cause only the MINER to crash and not the PLOTTER? It would seem to me that it would be the other way around, but I've been known to be wrong before! hehe.
How is your NAS attached ?
I think you may have misunderstood, or I may have used the wrong context... The drives are NAS drives, but they are physically inside the server, connected like any other drive with SATA and power. Just regular drives, the RED drives from WD, intended for NAS use.
This makes it hard to say what is causing the crash.
We need the error or check the windows event viewer for anything suspicious.
i was/am having this happen to me. started about 3 days ago. running fine for 4.5 days and then random crashes. my single plot size was approach 2TB at the time and my "-Xmx" was limiting it to 750m. I'm wondering whethe it's a mem issue so have upped it to 1024m to see if it makes a diff.
i did ask the question here whether there is a log file i can look at the miner logs to to see if it reports why it shutsdown.
So, I am having a random issue and I am not sure why...
Every once in a while on my server machine, one of the instances that is on my G drive (miner instance) crashes out. Just closes. I don't know why it is doing this. It is only on that one drive, the other miner on the other drive is fine, and the miner on the mapped drive on the same server, mapped to my desktop is fine too. It's only the G drive miner, and randomly...
Any Ideas or suggestions on how to get it to stop? Thanks!
Every once in a while on my server machine, one of the instances that is on my G drive (miner instance) crashes out. Just closes. I don't know why it is doing this. It is only on that one drive, the other miner on the other drive is fine, and the miner on the mapped drive on the same server, mapped to my desktop is fine too. It's only the G drive miner, and randomly...
Any Ideas or suggestions on how to get it to stop? Thanks!
I think my question got overlooked, can anyone help me out with this? Thanks!
Is it just the miner that stops or is it a plot generation too?
Try adding the word pause on a line after everything else on your bat file
java -Xmxblah blah blah blah
pause
When it dies it will pause the command prompt and ask you to press a button to shut down. This way you can see what the error is that is killing the process.
Once you get that it is much easier to help diagnose the problem.
Edit:
I am assuming your on windows.
Yea, I have already added pause to it, and am awaiting the next time it crashes out.... It is only the miner, and only 1 of the 2 miners running on the system. The one on the other drive never crashes. Very strange. The plot generation is fine on both drives.
bad sectors of your HDD?
I really don't think so... well, I guess, at least I hope not... This drive, as with almost all of the drives/components in the system in question, are almost brand new WD NAS drives. Do you think that bad sectors would cause only the MINER to crash and not the PLOTTER? It would seem to me that it would be the other way around, but I've been known to be wrong before! hehe.
How is your NAS attached ?
I think you may have misunderstood, or I may have used the wrong context... The drives are NAS drives, but they are physically inside the server, connected like any other drive with SATA and power. Just regular drives, the RED drives from WD, intended for NAS use.
This makes it hard to say what is causing the crash.
We need the error or check the windows event viewer for anything suspicious.
i was/am having this happen to me. started about 3 days ago. running fine for 4.5 days and then random crashes. my single plot size was approach 2TB at the time and my "-Xmx" was limiting it to 750m. I'm wondering whethe it's a mem issue so have upped it to 1024m to see if it makes a diff.
i did ask the question here whether there is a log file i can look at the miner logs to to see if it reports why it shutsdown.
Im running a drive with 3.5TB (and growing) without the miner dying.
Let me get the command for it
Edit:
Here is my command for the miner:
java -Xmx1500m -cp pocminer.jar;lib/*;lib/akka/*;lib/jetty/* pocminer.POCMiner mine "http://127.0.0.1:8125"%*
I doubled the -Xmx. It has never crashed.
I am using 64 bit java too.
August 18, 2014, 06:48:50 PM
@BurstBurst:
What is plot file size and your available RAM and your run_mine command ?
What is plot file size and your available RAM and your run_mine command ?
August 18, 2014, 06:47:42 PM
Same problem. Anyone know How to handle large size plot with out crashing the miner ?
I think my question got overlooked, can anyone help me out with this? Thanks!
Is it just the miner that stops or is it a plot generation too?
Try adding the word pause on a line after everything else on your bat file
java -Xmxblah blah blah blah
pause
When it dies it will pause the command prompt and ask you to press a button to shut down. This way you can see what the error is that is killing the process.
Once you get that it is much easier to help diagnose the problem.
Edit:
I am assuming your on windows.
Yea, I have already added pause to it, and am awaiting the next time it crashes out.... It is only the miner, and only 1 of the 2 miners running on the system. The one on the other drive never crashes. Very strange. The plot generation is fine on both drives.
bad sectors of your HDD?
I really don't think so... well, I guess, at least I hope not... This drive, as with almost all of the drives/components in the system in question, are almost brand new WD NAS drives. Do you think that bad sectors would cause only the MINER to crash and not the PLOTTER? It would seem to me that it would be the other way around, but I've been known to be wrong before! hehe.
How is your NAS attached ?
I think you may have misunderstood, or I may have used the wrong context... The drives are NAS drives, but they are physically inside the server, connected like any other drive with SATA and power. Just regular drives, the RED drives from WD, intended for NAS use.
This makes it hard to say what is causing the crash.
We need the error or check the windows event viewer for anything suspicious.
i was/am having this happen to me. started about 3 days ago. running fine for 4.5 days and then random crashes. my single plot size was approach 2TB at the time and my "-Xmx" was limiting it to 750m. I'm wondering whethe it's a mem issue so have upped it to 1024m to see if it makes a diff.
i did ask the question here whether there is a log file i can look at the miner logs to to see if it reports why it shutsdown.
So, I am having a random issue and I am not sure why...
Every once in a while on my server machine, one of the instances that is on my G drive (miner instance) crashes out. Just closes. I don't know why it is doing this. It is only on that one drive, the other miner on the other drive is fine, and the miner on the mapped drive on the same server, mapped to my desktop is fine too. It's only the G drive miner, and randomly...
Any Ideas or suggestions on how to get it to stop? Thanks!
Every once in a while on my server machine, one of the instances that is on my G drive (miner instance) crashes out. Just closes. I don't know why it is doing this. It is only on that one drive, the other miner on the other drive is fine, and the miner on the mapped drive on the same server, mapped to my desktop is fine too. It's only the G drive miner, and randomly...
Any Ideas or suggestions on how to get it to stop? Thanks!
I think my question got overlooked, can anyone help me out with this? Thanks!
Is it just the miner that stops or is it a plot generation too?
Try adding the word pause on a line after everything else on your bat file
java -Xmxblah blah blah blah
pause
When it dies it will pause the command prompt and ask you to press a button to shut down. This way you can see what the error is that is killing the process.
Once you get that it is much easier to help diagnose the problem.
Edit:
I am assuming your on windows.
Yea, I have already added pause to it, and am awaiting the next time it crashes out.... It is only the miner, and only 1 of the 2 miners running on the system. The one on the other drive never crashes. Very strange. The plot generation is fine on both drives.
bad sectors of your HDD?
I really don't think so... well, I guess, at least I hope not... This drive, as with almost all of the drives/components in the system in question, are almost brand new WD NAS drives. Do you think that bad sectors would cause only the MINER to crash and not the PLOTTER? It would seem to me that it would be the other way around, but I've been known to be wrong before! hehe.
How is your NAS attached ?
I think you may have misunderstood, or I may have used the wrong context... The drives are NAS drives, but they are physically inside the server, connected like any other drive with SATA and power. Just regular drives, the RED drives from WD, intended for NAS use.
This makes it hard to say what is causing the crash.
We need the error or check the windows event viewer for anything suspicious.
i was/am having this happen to me. started about 3 days ago. running fine for 4.5 days and then random crashes. my single plot size was approach 2TB at the time and my "-Xmx" was limiting it to 750m. I'm wondering whethe it's a mem issue so have upped it to 1024m to see if it makes a diff.
i did ask the question here whether there is a log file i can look at the miner logs to to see if it reports why it shutsdown.
August 18, 2014, 06:42:24 PM
Miner doesn't have a log file, and really could use a bit of work.
August 18, 2014, 06:28:22 PM
So, I am having a random issue and I am not sure why...
Every once in a while on my server machine, one of the instances that is on my G drive (miner instance) crashes out. Just closes. I don't know why it is doing this. It is only on that one drive, the other miner on the other drive is fine, and the miner on the mapped drive on the same server, mapped to my desktop is fine too. It's only the G drive miner, and randomly...
Any Ideas or suggestions on how to get it to stop? Thanks!
Every once in a while on my server machine, one of the instances that is on my G drive (miner instance) crashes out. Just closes. I don't know why it is doing this. It is only on that one drive, the other miner on the other drive is fine, and the miner on the mapped drive on the same server, mapped to my desktop is fine too. It's only the G drive miner, and randomly...
Any Ideas or suggestions on how to get it to stop? Thanks!
I think my question got overlooked, can anyone help me out with this? Thanks!
Is it just the miner that stops or is it a plot generation too?
Try adding the word pause on a line after everything else on your bat file
java -Xmxblah blah blah blah
pause
When it dies it will pause the command prompt and ask you to press a button to shut down. This way you can see what the error is that is killing the process.
Once you get that it is much easier to help diagnose the problem.
Edit:
I am assuming your on windows.
Yea, I have already added pause to it, and am awaiting the next time it crashes out.... It is only the miner, and only 1 of the 2 miners running on the system. The one on the other drive never crashes. Very strange. The plot generation is fine on both drives.
bad sectors of your HDD?
I really don't think so... well, I guess, at least I hope not... This drive, as with almost all of the drives/components in the system in question, are almost brand new WD NAS drives. Do you think that bad sectors would cause only the MINER to crash and not the PLOTTER? It would seem to me that it would be the other way around, but I've been known to be wrong before! hehe.
How is your NAS attached ?
I think you may have misunderstood, or I may have used the wrong context... The drives are NAS drives, but they are physically inside the server, connected like any other drive with SATA and power. Just regular drives, the RED drives from WD, intended for NAS use.
This makes it hard to say what is causing the crash.
We need the error or check the windows event viewer for anything suspicious.
i was/am having this happen to me. started about 3 days ago. running fine for 4.5 days and then random crashes. my single plot size was approach 2TB at the time and my "-Xmx" was limiting it to 750m. I'm wondering whethe it's a mem issue so have upped it to 1024m to see if it makes a diff.
i did ask the question here whether there is a log file i can look at the miner logs to to see if it reports why it shutsdown.
thats actually an excellent point. If the plot files are two big you may need more ram to run the miner.
How big (total) is the plot on that drive?
August 18, 2014, 06:24:51 PM
So, I am having a random issue and I am not sure why...
Every once in a while on my server machine, one of the instances that is on my G drive (miner instance) crashes out. Just closes. I don't know why it is doing this. It is only on that one drive, the other miner on the other drive is fine, and the miner on the mapped drive on the same server, mapped to my desktop is fine too. It's only the G drive miner, and randomly...
Any Ideas or suggestions on how to get it to stop? Thanks!
Every once in a while on my server machine, one of the instances that is on my G drive (miner instance) crashes out. Just closes. I don't know why it is doing this. It is only on that one drive, the other miner on the other drive is fine, and the miner on the mapped drive on the same server, mapped to my desktop is fine too. It's only the G drive miner, and randomly...
Any Ideas or suggestions on how to get it to stop? Thanks!
I think my question got overlooked, can anyone help me out with this? Thanks!
Is it just the miner that stops or is it a plot generation too?
Try adding the word pause on a line after everything else on your bat file
java -Xmxblah blah blah blah
pause
When it dies it will pause the command prompt and ask you to press a button to shut down. This way you can see what the error is that is killing the process.
Once you get that it is much easier to help diagnose the problem.
Edit:
I am assuming your on windows.
Yea, I have already added pause to it, and am awaiting the next time it crashes out.... It is only the miner, and only 1 of the 2 miners running on the system. The one on the other drive never crashes. Very strange. The plot generation is fine on both drives.
bad sectors of your HDD?
I really don't think so... well, I guess, at least I hope not... This drive, as with almost all of the drives/components in the system in question, are almost brand new WD NAS drives. Do you think that bad sectors would cause only the MINER to crash and not the PLOTTER? It would seem to me that it would be the other way around, but I've been known to be wrong before! hehe.
How is your NAS attached ?
I think you may have misunderstood, or I may have used the wrong context... The drives are NAS drives, but they are physically inside the server, connected like any other drive with SATA and power. Just regular drives, the RED drives from WD, intended for NAS use.
This makes it hard to say what is causing the crash.
We need the error or check the windows event viewer for anything suspicious.
i was/am having this happen to me. started about 3 days ago. running fine for 4.5 days and then random crashes. my single plot size was approach 2TB at the time and my "-Xmx" was limiting it to 750m. I'm wondering whethe it's a mem issue so have upped it to 1024m to see if it makes a diff.
i did ask the question here whether there is a log file i can look at the miner logs to to see if it reports why it shutsdown.
August 18, 2014, 06:24:33 PM
Submitting share{"result":"deadline: 230"}
Let's hope!
Fingers crossed for you buddy!!
August 18, 2014, 06:24:18 PM
#2637 now, wonder who has got the block #2636.
This was not a mining block reward but looks like a transaction was sent on that block.
EDIT: This seems to be my own transaction of 10029 burst (was playing with the wallet).
So, what just happened ?
Your transaction was just riding along. Someone still got it
August 18, 2014, 06:23:36 PM
Submitting share{"result":"deadline: 230"}
Let's hope!
EDIT:
Jump to: