[ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000

[CryptoSurfer]

Is anyone also getting the error "Error reading file: ......" when using mklink to another drive ?

[1714060876]

1714060876

[1714060876]

1714060876

[1714060876]

1714060876

[neite99]

Is anyone also getting the error "Error reading file: ......" when using mklink to another drive ?

the only time I get that is when I am using plot files that are still being generated or plot files that didnt finish the entire generation process.

[CryptoSurfer]

Is anyone also getting the error "Error reading file: ......" when using mklink to another drive ?

the only time I get that is when I am using plot files that are still being generated or plot files that didnt finish the entire generation process.

In this case both plots are still being generated but the only error is from the file on the other disk.
Weird.

[neite99]

Is anyone also getting the error "Error reading file: ......" when using mklink to another drive ?

the only time I get that is when I am using plot files that are still being generated or plot files that didnt finish the entire generation process.

In this case both plots are still being generated but the only error is from the file on the other disk.
Weird.

On the one I am generating now it doesnt always say error when its being generated. But when it does its always on a plot that is incomplete (being generated or never finished)

[luxe]

Is anyone also getting the error "Error reading file: ......" when using mklink to another drive ?

my experience is that only mklink /h (hardlink) would work, but u can not use that on differnt drives ... (i know i have posted that before, cause i thought it would work) so on windows i found no other solution than running one miner instance on every drive! that will work! every drive will commit its own found deadlines for the same address!

@burstcoin: you are AWESOME!
@Wulfcastle: Thx for all that work, its so GOOD looking :-)

bouth of you should publish a burst address, so that we can donate!

[BChydro]

Hey everyone

Some of you may know me as the person behind the new Burst UI. I've also gone ahead and decided to redesign the Burst OP. I've decided to put emphasis on the stand-out features of Burst. Let me know what you think

[OP REMOVED]

Just bumping this to the new page.

That's some awesome work. What's your burst account ID? You deserve some compensation.

[crowetic]

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!

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.

[Cobra]

my experience is that only mklink /h (hardlink) would work, but u can not use that on differnt drives ... (i know i have posted that before, cause i thought it would work) so on windows i found no other solution than running one miner instance on every drive! that will work! every drive will commit its own found deadlines for the same address!

I am using Windows 8 storage spaces which seems to work well. You can thin provision it as well.  Multiple drives can appear as a single logical drive. When you create the storage space it asks for the max, I put in 63TB (looks like that is the most it would take) so you can just keep adding drives to the pool to expand without worrying about the headaches of sym links.  It is working fine, finding blocks and appears fast enough. (I am using multiple USB3 hard drives)

[neite99]

If that is the case then we really need the error that shows up before the command prompt shuts down. So waiting for the "pause" to catch it is probably the next step.

[CryptoSurfer]

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!

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.

[crowetic]

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!

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.

Yea, I know it's difficult, usually I could tell what the issue was right away, but in this case, I'm simply not sure. This server has virtual machines running on it, DNS server, VPN, FTP, HTTP, etc etc, so it's got a ton going on... If you know of something in particular that may help you help me narrow it down, anything would be appreciated. Thanks!

So far it hasn't crashed since I added pause to the batch... so hopefully it just won't anymore, but it happened at least 8 times, so I don't think it will magically disappear.

[neite99]

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!

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.

Yea, I know it's difficult, usually I could tell what the issue was right away, but in this case, I'm simply not sure. This server has virtual machines running on it, DNS server, VPN, FTP, HTTP, etc etc, so it's got a ton going on... If you know of something in particular that may help you help me narrow it down, anything would be appreciated. Thanks!

So far it hasn't crashed since I added pause to the batch... so hopefully it just won't anymore, but it happened at least 8 times, so I don't think it will magically disappear.

Have you glanced through the event viewer log?

[luxe]

my experience is that only mklink /h (hardlink) would work, but u can not use that on differnt drives ... (i know i have posted that before, cause i thought it would work) so on windows i found no other solution than running one miner instance on every drive! that will work! every drive will commit its own found deadlines for the same address!

I am using Windows 8 storage spaces which seems to work well. You can thin provision it as well.  Multiple drives can appear as a single logical drive. When you create the storage space it asks for the max, I put in 63TB (looks like that is the most it would take) so you can just keep adding drives to the pool to expand without worrying about the headaches of sym links.  It is working fine, finding blocks and appears fast enough. (I am using multiple USB3 hard drives)

yes, thats true (good point!), if you combine multiple drives to one big drive you have no problem ... but can windows handle it, if one of this drives fails ... will i lose all my plots?! anyway ... too late for me right now :-) but all others with same problem now have 2 options :-)

[crowetic]

my experience is that only mklink /h (hardlink) would work, but u can not use that on differnt drives ... (i know i have posted that before, cause i thought it would work) so on windows i found no other solution than running one miner instance on every drive! that will work! every drive will commit its own found deadlines for the same address!

I am using Windows 8 storage spaces which seems to work well. You can thin provision it as well.  Multiple drives can appear as a single logical drive. When you create the storage space it asks for the max, I put in 63TB (looks like that is the most it would take) so you can just keep adding drives to the pool to expand without worrying about the headaches of sym links.  It is working fine, finding blocks and appears fast enough. (I am using multiple USB3 hard drives)

This is a really decent idea. I may have to try this later.

[crowetic]

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!

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.

Yea, I know it's difficult, usually I could tell what the issue was right away, but in this case, I'm simply not sure. This server has virtual machines running on it, DNS server, VPN, FTP, HTTP, etc etc, so it's got a ton going on... If you know of something in particular that may help you help me narrow it down, anything would be appreciated. Thanks!

So far it hasn't crashed since I added pause to the batch... so hopefully it just won't anymore, but it happened at least 8 times, so I don't think it will magically disappear.

Have you glanced through the event viewer log?

Not at this point. But what exactly would I be looking for. There is so much there that it would take a very long time to look through without knowing a general idea of what I am looking for.

[neite99]

my experience is that only mklink /h (hardlink) would work, but u can not use that on differnt drives ... (i know i have posted that before, cause i thought it would work) so on windows i found no other solution than running one miner instance on every drive! that will work! every drive will commit its own found deadlines for the same address!

I am using Windows 8 storage spaces which seems to work well. You can thin provision it as well.  Multiple drives can appear as a single logical drive. When you create the storage space it asks for the max, I put in 63TB (looks like that is the most it would take) so you can just keep adding drives to the pool to expand without worrying about the headaches of sym links.  It is working fine, finding blocks and appears fast enough. (I am using multiple USB3 hard drives)

yes, thats true (good point!), if you combine multiple drives to one big drive you have no problem ... but can windows handle it, if one of this drives fails ... will i lose all my plots?! anyway ... too late for me right now :-) but all others with same problem now have 2 options :-)

This strategy reminds me of dynamic disks in windows server. there was always some random issue with those that made it a bad idea to use that way. But maybe the found a way to stabilize it in windows 8. Haven't tried it yet. Looking forward to hearing how it turns out.

[neite99]

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!

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.

Yea, I know it's difficult, usually I could tell what the issue was right away, but in this case, I'm simply not sure. This server has virtual machines running on it, DNS server, VPN, FTP, HTTP, etc etc, so it's got a ton going on... If you know of something in particular that may help you help me narrow it down, anything would be appreciated. Thanks!

So far it hasn't crashed since I added pause to the batch... so hopefully it just won't anymore, but it happened at least 8 times, so I don't think it will magically disappear.

Have you glanced through the event viewer log?

Not at this point. But what exactly would I be looking for. There is so much there that it would take a very long time to look through without knowing a general idea of what I am looking for.

Start with the application logs. It will probably be Java related.

Event logs are your best friend when you need to diagnose a windows issue. Its a good idea to just dive on and see if you can start to understand what problems are occurring. Then you can google the error codes and event ID's and get answers for the problem.

[Vorksholk]

Alright, I have hammered down pricing and the backend infrastructure for a hosted Burstcoin mining solution.

Here's the pricing:
0.06BTC gets you one month mining with one terabyte (after formatting you get a full terabyte). Each subsequent month is 0.03BTC. The initial high cost is to account for generation, which requires significant computational resources. I have no idea about profitability, and it is far too early in this coin's life to predict anything. For now, of course, generating and mining with a plot will require your private key to be held on the remote server, so the smartest method would be that I give you the public address that is being mined to, and twice daily I empty the mining address to an address of your choice (in this way you can see the mining occurring publicly, and twice daily all mined balances are secured in an address only you have access to).

This service would also work well with pooled mining upon release. Discounts are available for larger orders, with 10TB+ being priced at 0.055BTC/TB, and 20TB+ being priced at 0.05BTC/TB. I have 3TB ready to go live (as a bundle, as the plots are made for one address), and can put extra Terabytes up in a timely manner.

Each server is based on 4TB hard drives, which when formatted result in 3.6TB of space I can sell.

[callmejack]

my experience is that only mklink /h (hardlink) would work, but u can not use that on differnt drives ... (i know i have posted that before, cause i thought it would work) so on windows i found no other solution than running one miner instance on every drive! that will work! every drive will commit its own found deadlines for the same address!

I am using Windows 8 storage spaces which seems to work well. You can thin provision it as well.  Multiple drives can appear as a single logical drive. When you create the storage space it asks for the max, I put in 63TB (looks like that is the most it would take) so you can just keep adding drives to the pool to expand without worrying about the headaches of sym links.  It is working fine, finding blocks and appears fast enough. (I am using multiple USB3 hard drives)

yes, thats true (good point!), if you combine multiple drives to one big drive you have no problem ... but can windows handle it, if one of this drives fails ... will i lose all my plots?! anyway ... too late for me right now :-) but all others with same problem now have 2 options :-)

This strategy reminds me of dynamic disks in windows server. there was always some random issue with those that made it a bad idea to use that way. But maybe the found a way to stabilize it in windows 8. Haven't tried it yet. Looking forward to hearing how it turns out.

never heard of windows storage space but may it be a simple timeout due to systemload?
never tried running the mining on windows due to the 2tb volume size limit but it sounds like microsoft has broken this with their new storage space technology.
if the drives are attached by usb3 may it be a cable issue? i had struggled some time ago with a 28 port usb3 hub. some attached devices have frozen the whole bus and forced a port reset by the driver resulting in loosing all devices.
it was one of the cables which broke everything...
if you have the plots on the failing drive already generated try to plug it into a usb2 port. the performance should be enough to parse 8tb plotdata within 4 minutes.

[burstcoin]

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!

I think my question got overlooked, can anyone help me out with this? Thanks!

How much ram do you have? If you're running too many jvms with not enough ram on windows, sometimes windows pops a box asking you to close something, then if you don't it auto-kills something. I have a comp with 4G ram running 2 miners that tends to kill 1 miner on occasion, and on another comp my wallet seems to have gotten auto-killed about when I left for work today, causing me to lose about 9-10 hours of mining time.

Best suggestion if lack of ram is the case is lower the -Xmx values, or add ram.

This can also be triggered by scheduled services starting up, which increase ram usage, so check the scheduler if anything is set to run.