I just made 25 bucks in burst!

I fired up a backup server that I normally leave powered down. It contains a 60 x 2TB RAID 60 volume and a 12 x 4TB RAID 6 volume. Figured those would be pretty good for giving burst a go.

Raid controller is an Areca 1882 and the mobo a SuperMicro X10SRL-F with a Xeon E52630L V3 CPU and 2 x 16GB sticks of Samsung DDR4 ECC.

I'm plotting the 12x4TB volume now at a rate of about 12k nonces/min. Looks like this is going to take a while. I bet the 60 x 2TB volume is going to be real drag...

plottingspeed.PNG


I do have a pair of 980Ti's in my gaming rig, but unless I can plot across my LAN (I do have a 10G network), I don't see that working.

My guess is I'm looking at about a month to plot these drives using the Xeon?

Also, it would be awesome if someone could slip me a few coins. The facets seems to have all run dry.
 
I fired up a backup server that I normally leave powered down. It contains a 60 x 2TB RAID 60 volume and a 12 x 4TB RAID 6 volume. Figured those would be pretty good for giving burst a go.

Raid controller is an Areca 1882 and the mobo a SuperMicro X10SRL-F with a Xeon E52630L V3 CPU and 2 x 16GB sticks of Samsung DDR4 ECC.

I'm plotting the 12x4TB volume now at a rate of about 12k nonces/min. Looks like this is going to take a while. I bet the 60 x 2TB volume is going to be real drag...

plottingspeed.PNG


I do have a pair of 980Ti's in my gaming rig, but unless I can plot across my LAN (I do have a 10G network), I don't see that working.

My guess is I'm looking at about a month to plot these drives using the Xeon?

Also, it would be awesome if someone could slip me a few coins. The facets seems to have all run dry.
With that much space you should solo mine 168tb will make about 1500$ a month so before you get too far plotting you may wish to drop them out of raid the 2tb drives will take about 4 hours each the 4tb at 14k will take 17 hours each if the drives are mapped over smb you should be able to plot on your gaming rig...not sure how well that will work though...

And for any of us to send you some we need your burst address
 
Last edited:
With that much space you should solo mine 168tb will make about 1500$ a month so before you get too far plotting you may wish to drop them out of raid the 2tb drives will take about 4 hours each the 4tb at 14k will take 17 hours each if the drives are mapped over smb you should be able to plot on your gaming rig...not sure how well that will work though...

And for any of us to send you some we need your burst address

Sorry, my address is BURST-9EYZ-VLFW-GTES-4NB5A. Yeah, I'm at 2% now on the smaller volume. I'll kill it and switch the controller to JBOD mode. And then maybe also try playing with mounting over the network for plotting.
 
Sorry, my address is BURST-9EYZ-VLFW-GTES-4NB5A. Yeah, I'm at 2% now on the smaller volume. I'll kill it and switch the controller to JBOD mode. And then maybe also try playing with mounting over the network for plotting.

Just sent you 5. I owed it forward from Lunas :p
 
Just wondering, how many nonces/min until the spinning drive becomes the bottleneck?
The 980ti should be able to do up to 40k nonces/min from what I was reading.
 
Just sent you 5. I owed it forward from Lunas :p

Awesome thanks!

So what plotter should I use with my pair of 980Tis? Is there one that will take advantage of them both at once? If not, can I specify which one to use? i.e. use 980Ti #1 to plot drive 1 and 980Ti #2 to plot drive 2, and so on?
 
Sorry, my address is BURST-9EYZ-VLFW-GTES-4NB5A. Yeah, I'm at 2% now on the smaller volume. I'll kill it and switch the controller to JBOD mode. And then maybe also try playing with mounting over the network for plotting.
2 other pieces of advice i dont know why but the burst forums recommend formatting at a 64k cluster size i surmise it has to do with read speeds and they must be ntfs

The plotter is gpuplotgenerator on the burst forum and yes but i dont have experience with setting multiple cards. And i checked your max size it is down from when i checked you should make about 44717 coins a month current prices is in the $650 area.
 
Last edited:
Awesome thanks!

So what plotter should I use with my pair of 980Tis? Is there one that will take advantage of them both at once? If not, can I specify which one to use? i.e. use 980Ti #1 to plot drive 1 and 980Ti #2 to plot drive 2, and so on?

You use gpuPlotGenerator, https://github.com/bhamon/gpuPlotGe.../v4.1.1/gpuPlotGenerator-bin-win-x64-4.1.1.7z

You will be making bat files for each GPU and drive you want to plot it seems.
Here you can see my GPU's listed in the setup,
gpu-plot-settings.jpg


I don't have any spare drives or drive space to play with to try it out though.

I watched this video to see what to do, but he only has 1 video card.


just watched this one, it's informative as well,
 
Last edited:
Thanks guys. So I broke down the raid arrays and now have 72 individual drives within Disk Manager that I have started formatting using 64K blocks and ntfs. The thing is that Windows only support 26 drive letters, so I'm creating mount points instead that look like this:

C:\burstdrives\disk01

The network path is: \\ARGON\disk01

When I go into the burst client and click the Write Plots tab, the Plotter pop-up only allows me to select a drive with a letter assigned to it, or a shared network drive (also with a letter assigned to it). While I won't be using the build in plotter to prep the drives, I wonder if I'm going to run into the same issue once the drives a plotted and I attempt to begin mining? I'd hate to waste weeks plotting mapped drives only to discover the burst client can't deal with them.
 
Last edited:
Don't use the AIO/GUI at all. Use Xplotter and/or gpuplotgenerator for your plotting (or both in your case maybe), and use the miner-burst program for reading. I'd think that v3 Xeon has AVX2, you'll want to use that exe.

Modifying the miner.conf file is easy enough.
 
I tried Xplotter, but I get a message that it won't run on my PC. The sse version runs, but only at about 7500 nonces/min.

I was not able to get gpuplotgenerator to work with this path to the drive: \\ARGON\disk01

I'm going to try just assigning a drive letter to disk01 temporarily and then map it locally on the rig with the 980Ti's to see if that works. Worst case, I guess I can pop the drives out of the server one at a time and plot them in the gaming rig. That is going to suck with 72 drives tho...

Another option would be to swap the 14 Core E5-2683 V3 from my production server to the backup server, but maybe that CPU doesn't support AVX2 either?
 
I tried Xplotter, but I get a message that it won't run on my PC. The sse version runs, but only at about 7500 nonces/min.

I was not able to get gpuplotgenerator to work with this path to the drive: \\ARGON\disk01

I'm going to try just assigning a drive letter to disk01 temporarily and then map it locally on the rig with the 980Ti's to see if that works. Worst case, I guess I can pop the drives out of the server one at a time and plot them in the gaming rig. That is going to suck with 72 drives tho...

Another option would be to swap the 14 Core E5-2683 V3 from my production server to the backup server, but maybe that CPU doesn't support AVX2 either?

Dual Xeon E5-2680 V3 does 55K nonces/min, so your single 2683 may do 25K nonces/min. Your 980Ti should be quite a bit faster.

I was thinking that with so many drives, why not break it up into 10TB Raid 5 or 6, so you don't have to do so many single drive plots, and you wouldn't have issues with configuring the miner to see all the paths to the 72 individual drives.
 
Yes, prod has E5-2683 and the backup has E5630L V3. But keep in mind that both of those CPUs were ES versions from Japan, so they may not have all features that the production units do.

I'm going to try running xplotter on the 2683 to see if it works.

Yeah, I think setting up some RAID5 sets with 6 members in each (or maybe 12 if I want to risk it) is the way to go.

So if I loose a raid set during mining, what happens?

EDIT: well here's what CPUZ is showing, so not sure why AVX2 does not appear to be working...

CPUZ.PNG


And the prod server:

cpuz2.JPG


Come to think about it, using xplotter, I can have them both plot drives/arrays at the same time. They have a 10Gig connection between them.
 
humm you may need to pool some of the drives i have been trying to find something about this you should be able to just assign them to files you can then manually configure the miner with the additional locations... not sure maybe the bios on your board does not enable all the features of the es you have...

i would probably run a test if the miner will take locations without a drive letter if it does great. otherwise raid 0 as redundancy means nothing to this raid 0 to group some of the 2tb drives to reduce the drive letter use.
 
Yeah, what is really weird is that xplotter ran once from a non-admin command prompt, but gave a warning about reduced performance and to run it from a admin command prompt. When I did that is when I got the error. Anyway, I'll try again once the arrays are initialized. I just did 12 arrays, each either 10 or 20TB raw. 12 drive letters should be compatible with everything. Hopefully the first few will be ready to go by morning.

burstraidsets.PNG


The Areca can only do 4 at a time.
 
I noticed some people seem to say that more RAM may be better for plotting.. Does anyone know more about this? Does it make a difference for GPU plotting only or also CPU? Also any idea if the RAM speed makes any difference?
 
I noticed some people seem to say that more RAM may be better for plotting.. Does anyone know more about this? Does it make a difference for GPU plotting only or also CPU? Also any idea if the RAM speed makes any difference?
i would think vram would help for gpu but in both cases the plotter plots the math to the ram then writes to the drive so in theory if you had a 4tb disk to plot and you had 4tb of ram it would go faster and be plotted optimized. but generally i have not seen a difference going from 8 to 24 except my system now seems faster...
 
What happens when you have say 20 drives and you're mining away and one of them fails? Do the other 19 keep chugging away, and all you have to do is replace the one that failed with another one the same size, re-plot it using the same sn start value, and then add it back to the mining pool?

I was thinking that I could do a bunch of raid0 arrays with 4 members each instead of all these raid5 arrays with 6 members each, but only of the loss of a single raid0 array would not be catastrophic to the current mining operation.
 
What happens when you have say 20 drives and you're mining away and one of them fails? Do the other 19 keep chugging away, and all you have to do is replace the one that failed with another one the same size, re-plot it using the same sn start value, and then add it back to the mining pool?

I was thinking that I could do a bunch of raid0 arrays with 4 members each instead of all these raid5 arrays with 6 members each, but only of the loss of a single raid0 array would not be catastrophic to the current mining operation.
yep if a drive fails after rebuilding the array you would just replot that one... same if you have say 20 drives if one fails the rest will continue mining and you can just replot with the same starting nounce and as long as it doesn't extend into another range example drive 1 has 1-10000 drive two has 10001-20000 if drive 1 goes down and you replot it and for some reason it goes to 10002 there will be an issue. but realistically you could use 42000000000000000000000000000000000000 as your starting number and do this for each array 42100000000000000000000000000000000000 42200000000000000000000000000000000000, 42300000000000000000000000000000000000 and keep going until you hit 429 then do 42110000000000000000000000000000000000

As far as i know there is no maximum number you can put as the nouces and if i use the same nouce you are using that is fine too they are linked to mining address so my 4200000000000000000000000000000000 is mine and mine alone

going raid 0 with them will maximise the space and that is what you want because the data on the drives is not important at all you dont need to worry about redundancy or error checking just size.

What i did when i started this is emptied all my oldest drives and drives i pulled as scrap and a bunch of flash drives and memory cards and tossed them all in the plotter. i only bought 3 drives at this time 2x 4tb an d 1x 3tb the rest i had was something i had sitting around doing nothing. 4 laptop drives 2x 500gb 1x 250 1x 160 all got tossed on the pile 2 are actually in a dock i can swap them out if i get my hands on bigger drives... i have several usb 3.0 ports also open.
 
Last edited:
Good deal. Redid them all as raid0 arrays with 4 members in each. Still was not able to kick of xplotter from the command line from either server, but invoking xplotter from within the Burst GUI worked. Go figure...

plottingspeed2.PNG


I just realized that I have 2 6TB WD Reds sitting on the shelf as spares for my production server, so I'll toss those in the server as well. So that takes me to 180TB. Maybe I'll plot those on my 6700k rig and then toss them into the server. I'll also mount some of the raid0 arrays to my prod server and xplot them from there once I figure out why I can't get the damn thing to run from the command line.
 
So on the plotting, these should be safe values, right?

XPlotter_avx.exe -id 2597790682173387743 -sn 400000001 -n 30481152 -t 16 -path d:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 500000001 -n 30481152 -t 16 -path e:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 600000001 -n 30481152 -t 16 -path f:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 700000001 -n 30481152 -t 16 -path g:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 800000001 -n 30481152 -t 16 -path h:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 900000001 -n 30481152 -t 16 -path i:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 1000000001 -n 30481152 -t 16 -path j:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 1100000001 -n 30481152 -t 16 -path k:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 1200000001 -n 30481152 -t 16 -path l:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 1300000001 -n 30481152 -t 16 -path m:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 1400000001 -n 30481152 -t 16 -path n:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 1500000001 -n 30481152 -t 16 -path o:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 1600000001 -n 30481152 -t 16 -path p:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 1700000001 -n 30481152 -t 16 -path q:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 1800000001 -n 30481152 -t 16 -path r:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 1900000001 -n 60962302 -t 16 -path s:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 2100000001 -n 60962302 -t 16 -path t:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 2300000001 -n 60962302 -t 16 -path u:\Burst\plots

The first 15 arrays are 8 TB (7,999,844,188,160 bytes to be exact) and I'm leaving 8.5 GB of free space.

The last 3 arrays are 16 TB (15,999,858,311,168) and I plan to leave 17GB of free space.

That Burst Wallet GUI did not allow me to specify memory, so hopefully I'll be able to kick the next one off from the command like and specify something like 24 GB since the server has 32 available. The 8 cores are running in the low to mid 40's, so not very much stress is being put on them at the moment.
 
It turns out that the xplotter_avx.exe I had manually downloaded was corrupt. The one that came with Burst Wallet was ok. So I'm now able to execute xplotter on the 14 core server against the shared drive from the server with all the raid0 arrays on it.

Problem is that even though I gave Everyone full permissions when I shared the E: drive, when I run xplotter against the mapped drive from the other server, I get the following:

xplotter-permissions.JPG


I had no problem manually creating the burst and plots sub-folders on the mapped drive from the 14 core server, but even after doing that, xplotter did not have permission to write to it apparently. How can I grant xplotter permission to write to the mapped drive from the server hosting the plotter drives, or should I launch xplotter by some means other than via the batch file as admin?

That first 8TB raid0 array is at 13%, so it is painstakingly slow. Other than this permissions issue, I think I'm really close to being able to have the 14 core Xeon assist with getting these arrays plotted!
 
Last edited:
So on the plotting, these should be safe values, right?

XPlotter_avx.exe -id 2597790682173387743 -sn 400000001 -n 30481152 -t 16 -path d:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 500000001 -n 30481152 -t 16 -path e:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 600000001 -n 30481152 -t 16 -path f:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 700000001 -n 30481152 -t 16 -path g:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 800000001 -n 30481152 -t 16 -path h:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 900000001 -n 30481152 -t 16 -path i:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 1000000001 -n 30481152 -t 16 -path j:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 1100000001 -n 30481152 -t 16 -path k:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 1200000001 -n 30481152 -t 16 -path l:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 1300000001 -n 30481152 -t 16 -path m:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 1400000001 -n 30481152 -t 16 -path n:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 1500000001 -n 30481152 -t 16 -path o:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 1600000001 -n 30481152 -t 16 -path p:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 1700000001 -n 30481152 -t 16 -path q:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 1800000001 -n 30481152 -t 16 -path r:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 1900000001 -n 60962302 -t 16 -path s:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 2100000001 -n 60962302 -t 16 -path t:\Burst\plots
XPlotter_avx.exe -id 2597790682173387743 -sn 2300000001 -n 60962302 -t 16 -path u:\Burst\plots

The first 15 arrays are 8 TB (7,999,844,188,160 bytes to be exact) and I'm leaving 8.5 GB of free space.

The last 3 arrays are 16 TB (15,999,858,311,168) and I plan to leave 17GB of free space.

That Burst Wallet GUI did not allow me to specify memory, so hopefully I'll be able to kick the next one off from the command like and specify something like 24 GB since the server has 32 available. The 8 cores are running in the low to mid 40's, so not very much stress is being put on them at the moment.
Yep looks good also the setting for ram is -mem 32g with that set it should use all free ram
 
Yep, that's what I'll do once this first volume is plotted. I was using the AIO for this initial volume plot, and it did not give me any options.

I tried doing a unc share (i.e. \\ARGON\E in my case) for xplotter from my 8 core server (BRAMA), but same error as above. So neither a mapped drive letter to a volume on another server, nor a unc reference seems to work with xplotter. Bummer.... Guess I'll look into another LGA-2011 Xeon that will do more nonces/min than what I'm running at the moment. What's the best bang for the buck these days for that? Is there a particular benchmark/attribute I should look at?

I'm up to 26% on my first volume averaging 12.5k nonces/min now.. Geez

So once this first volume is plotted, should I start mining solo, or way until I get past 100TB ish?
 
Yep, that's what I'll do once this first volume is plotted. I was using the AIO for this initial volume plot, and it did not give me any options.

I tried doing a unc share (i.e. \\ARGON\E in my case) for xplotter from my 8 core server (BRAMA), but same error as above. So neither a mapped drive letter to a volume on another server, nor a unc reference seems to work with xplotter. Bummer.... Guess I'll look into another LGA-2011 Xeon that will do more nonces/min than what I'm running at the moment. What's the best bang for the buck these days for that? Is there a particular benchmark/attribute I should look at?

I'm up to 26% on my first volume averaging 12.5k nonces/min now.. Geez

So once this first volume is plotted, should I start mining solo, or way until I get past 100TB ish?
you can or you can do a pool if you do a pool you will get coins while it grows vs only getting coins when you hit blocks
 
Thanks. It probably makes sense to join a pool then until I have enough plotted storage to go solo. The odds of hitting a block with only 8 or 16TB are probably pretty slim. Any progress on a [H]pool? That would be pretty cool.

I messed around with trying to run xplotter on the 2nd server to a mapped drive and got closer, but still get an error when trying to actually write the plot.

commandprompt3.JPG


So xplotter does create the file, but for some reason it still can't plot it:

commandprompt4.JPG


I tried just creating the burst directory and when I run it then, it creates the plots sub dir and the big ass file, but then fails with the same error.
 
Last edited:
You didn't compress the drive after/during formatting did you? I found that I couldn't plot on compressed drives and had to de-compress the ones I had.
 
I run into the same problem. Just create the directories yourself:

"x:\Burst\plots"

I'm not sure why it has problems doing that, but it happens even when running it as an administrator.

EDIT: Oops, I was a few posts behind. I thought you were still having trouble getting the directories created with xplotter.
 
Nope, no compression at all. I looked up the error message and got this:

--- cut ---
The following code fails when trying to logically extend my Windows 8.1 file with SetFileVaildData().
The returned Windows error code and message is:
ERROR_PRIVILEGE_NOT_HELD 1314 (0x522) A required privilege is not held by the client.
I'm running the code as Administrator and I have asserted that the process indeed has the SE_MANAGE_VOLUME_NAME privilege using OpenProcessToken() and GetTokenInformation().
--- cut ---

So it appears to be some sort of permissions thing... I guess I could try running it from a non admin command prompt. Not sure what kind of performance penalty that would result in.
 
I shared the next volume and get the exact same error:

commandprompt5.JPG


Just for grins, I tried kicking it off from a non admin command prompt and then it started off fine:

commandprompt6.JPG


But as soon as xplotter started writing out the scoops, it does so extremely slowly:

commandprompt7.JPG


I have a 10G link between the servers so it should be flying writing the scoops to the 4x2TB RAID0 array. Here's me copying a 65GB file to the other mapped network drive:

commandprompt8.JPG


I guess xplotter just does not like dealing with mapped network drives between windows boxes?
 

Attachments

  • upload_2017-7-6_10-6-35.png
    upload_2017-7-6_10-6-35.png
    65.5 KB · Views: 18
I got 2 blocks just today!! That makes 3 for me so far in a few weeks. I had to get another machine up and going for mining because I was plotting/mining at the same time off one rig and the miner would see the plots even though they weren't ready.

Just for clarification, my current mining rig is an E8500 with 8GB ram running Windows 10. Gpu mining with a Nvidia 950.

It really is luck on your deadlines since I was always first deadline reported for a while on my i7.

GL all!!!
 
I shared the next volume and get the exact same error:

commandprompt5.JPG


Just for grins, I tried kicking it off from a non admin command prompt and then it started off fine:

commandprompt6.JPG


But as soon as xplotter started writing out the scoops, it does so extremely slowly:

commandprompt7.JPG


I have a 10G link between the servers so it should be flying writing the scoops to the 4x2TB RAID0 array. Here's me copying a 65GB file to the other mapped network drive:

commandprompt8.JPG


I guess xplotter just does not like dealing with mapped network drives between windows boxes?
You can always plot then move the file to the network drive...
 
Yeah, that's my plan. I went ahead and inserted one of my 6TB RED drives in Brama (prod server) and xplotter fired right up and did its thing:

commandprompt10.JPG


It plots at twice the speed of Argon (backup server). However, since it is writing to a single 5400 RPM drive instead of 4 7200 RPM drives in RAID0, the writing of the scoops can't quite keep up with the nonces creation. It gets to about 52%, then the nonces creation pauses until the write is complete. See below.

commandprompt11.JPG


I went ahead and busted out another E5-2683 so that both servers can be plotting @ 24k nonces/min, and once I'm done with this 5400 RPM RED, everything else will be 4 drives in RAID0 arrays, so there will be no waiting for writes to complete. :)

It will be pretty easy to swap 4 drives at a time between Brama and Argon as everything is sitting in the same rack. In the shot below you can see xplotter is writing scoops to one of the 4 x 2TB raid sets.

burstminers.JPG
 
That pic above makes me sick with envy, lol. A shit ton of drives and some sweet Adcom power amps.
 
It might be just me, but I can't plot in a path Drive Letter:/burst/plots from 2nd drive on with AIO Xploter.
I had to use D:/plots, E:/plots, F:/plots etc.
I asked to Blago about creating batch file on each drive.



You may manually create folder "plots" on each drives (sometimes windows disallow plotter for creating folders)

your batch someting like:


@setlocal

@cd /d %~dp0

C:\BurstAIOWallet-0.1.50-64Bit\XPlotter\XPlotter_avx.exe -id 12948905964149xxxxxx -sn XXX -n 0 -t 2 -path E:\plots -mem 8g

C:\BurstAIOWallet-0.1.50-64Bit\XPlotter\XPlotter_avx.exe -id 12948905964149xxxxxx --sn XXX -n 0 -t 2 -path F:\plots -mem 10g

C:\BurstAIOWallet-0.1.50-64Bit\XPlotter\XPlotter_avx.exe -id 12948905964149xxxxxx --sn XXX -n 0 -t 2 -path G:\plots -mem 12g

@pause


if you set "-n 0" plotter will create plot at max size

And please, run batch as Admin

You can specify how many threads you want to use with -t x.

First drive works as -sn 0 -n 0 from start to the end
From second drive on : starting nonce + total nonce of last drive.

By the way, AVX2 is used on CPU minner, not Xplotter?
 
It might be just me, but I can't plot in a path Drive Letter:/burst/plots from 2nd drive on with AIO Xploter.
I had to use D:/plots, E:/plots, F:/plots etc.
I asked to Blago about creating batch file on each drive.



You may manually create folder "plots" on each drives (sometimes windows disallow plotter for creating folders)

your batch someting like:


@setlocal

@cd /d %~dp0

C:\BurstAIOWallet-0.1.50-64Bit\XPlotter\XPlotter_avx.exe -id 12948905964149xxxxxx -sn XXX -n 0 -t 2 -path E:\plots -mem 8g

C:\BurstAIOWallet-0.1.50-64Bit\XPlotter\XPlotter_avx.exe -id 12948905964149xxxxxx --sn XXX -n 0 -t 2 -path F:\plots -mem 10g

C:\BurstAIOWallet-0.1.50-64Bit\XPlotter\XPlotter_avx.exe -id 12948905964149xxxxxx --sn XXX -n 0 -t 2 -path G:\plots -mem 12g

@pause


if you set "-n 0" plotter will create plot at max size

And please, run batch as Admin

You can specify how many threads you want to use with -t x.

First drive works as -sn 0 -n 0 from start to the end
From second drive on : starting nonce + total nonce of last drive.

By the way, AVX2 is used on CPU minner, not Xplotter?
yes that is correct...

here is a example gpuplotgen bat

Code:
@echo off

:: BatchGotAdmin
:-------------------------------------
REM  --> Check for permissions
    IF "%PROCESSOR_ARCHITECTURE%" EQU "amd64" (
>nul 2>&1 "%SYSTEMROOT%\SysWOW64\cacls.exe" "%SYSTEMROOT%\SysWOW64\config\system"
) ELSE (
>nul 2>&1 "%SYSTEMROOT%\system32\cacls.exe" "%SYSTEMROOT%\system32\config\system"
)

REM --> If error flag set, we do not have admin.
if '%errorlevel%' NEQ '0' (
    echo Requesting administrative privileges...
    goto UACPrompt
) else ( goto gotAdmin )

:UACPrompt
    echo Set UAC = CreateObject^("Shell.Application"^) > "%temp%\getadmin.vbs"
    set params = %*:"=""
    echo UAC.ShellExecute "cmd.exe", "/c ""%~s0"" %params%", "", "runas", 1 >> "%temp%\getadmin.vbs"

    "%temp%\getadmin.vbs"
    del "%temp%\getadmin.vbs"
    exit /B

:gotAdmin
@echo on
    pushd "%CD%"
    CD /D "%~dp0"
gpuPlotGenerator generate direct E:\burst\plots\00000000000000000_42400000000000_3801088_8192
pause

here is xplotter bat

Code:
@echo off

:: BatchGotAdmin
:-------------------------------------
REM  --> Check for permissions
    IF "%PROCESSOR_ARCHITECTURE%" EQU "amd64" (
>nul 2>&1 "%SYSTEMROOT%\SysWOW64\cacls.exe" "%SYSTEMROOT%\SysWOW64\config\system"
) ELSE (
>nul 2>&1 "%SYSTEMROOT%\system32\cacls.exe" "%SYSTEMROOT%\system32\config\system"
)

REM --> If error flag set, we do not have admin.
if '%errorlevel%' NEQ '0' (
    echo Requesting administrative privileges...
    goto UACPrompt
) else ( goto gotAdmin )

:UACPrompt
    echo Set UAC = CreateObject^("Shell.Application"^) > "%temp%\getadmin.vbs"
    set params = %*:"=""
    echo UAC.ShellExecute "cmd.exe", "/c ""%~s0"" %params%", "", "runas", 1 >> "%temp%\getadmin.vbs"

    "%temp%\getadmin.vbs"
    del "%temp%\getadmin.vbs"
    exit /B

:gotAdmin
@echo on
@setlocal
@cd /d %~dp0
XPlotter_avx.exe -id 0000000000000000000000000 -sn 4231000058000 -n 0 -t 4 -path E:\burst\plots -mem 12G
@pause

both of the above will give errors if the files are not there to fix that add

mkdir e:\Burst\Plots\

or add the directory structure yourself
 
Last edited:
Great info Lunas, thanks!

So my first array completed plotting. Based on how long it took, I can now estimate that it will take a little over 9 days before I'm done plotting 174TB. I made this handy chart that I'll be updating as I go along:

plotterstats.JPG


I'm making the assumption that once I drop a E5-2683 into Argon and increase RAM to 64G, it will plot at 24,500 nonces/min, a little faster than Brama with its E5-2683ES and 32GB, which is also doing a bunch of other stuff. I'm also making the assumption that both servers will be plotting in parallel, so when I divide the total 470 hours in half, I get 235 hours or 9.8 days.
 
Back
Top