PlotsChecker (not for XPlotter!)
-
Okey i will try, thanx !
-
@Blago Also this is okey ? :
@setlocal
@cd /d %~dp0
XPlotter_avx.exe -id 18346670433341256769 -sn 600000001 -t 6 -path F:\plots -mem 8G
@pause
-
@LeoFrk2 you skip "-n 0", but it's fine (0 by default)
-
@Blago Plot is finished but when I launch the miner, he doesn't see the plot
How can i do it ?
-
@LeoFrk2 edit miner.conf in miner's folder
example"Paths":["C:\\plots","E:\\plots","F:\\plots","G:\\plots","H:\\plots","I:\\plots","J:\\plots","K:\\plots","L:\\plots","M:\\plots","N:\\plots","O:\\plots","P:\\plots","R:\\plots","S:\\plots","U:\\plots"],
-
@Blago It work ! Thanx dude
-
@Blago
And, after plotting from -sn 900000001, what should I do ? 1000000001 is right ?
-
@LeoFrk2 yes
-
Hey, I have a massive plot file, 8tb that i get no errors from through jminer but I checked it with the plotchecker today and it says I need to delete and replot.. first plot file name is
xxxxxxxxxxxxxxxxxxxx_0_6963200_6963200<OK
xxxxxxxxxxxxxxxxxxxx_6963200_28999680_28999680<Need to delete and replot
Is there any workaround to replotting? Jminer has never said there was an issue with my plot files..I was under the impression that if you plot 6963200 nonces starting from 0, nonce#0 is where it starts from so the last nonce plotted is nonce #6963199, and the next set of nonces should start from 6963200. Do I have to replot the whole thing? Really sucks cuz it took like 4 days last time and I just got another 8tb drive I was gonna expand with :(
-
@Schoolsalesman What did you plot with? If xplotter, you can run it again to have it complete the file. If it was something else, the filename doesn't match the filesize, so there's something wrong with the file and it should be replotted.
-
I used the gpu plot generator and did a direct (optimized) plot. What do you mean the file name doesnt match the file size?
-
@Schoolsalesman The filename describes the contents of the file - the account, the starting nonce, number of nonces and stagger. The file size should = number of nonces * 262144 bytes. If the file is not that size, then something went wrong in the plotting. With a non optimized plot the file can be truncated and the name adjusted, but for optimized plots it's not possible to fix them - so they have to be replotted.
-
My apologies, I should have included exact numbers. The drive i'm using is 8tb(Actual capacity 7.27tb), 363gb remaining and the plot size is 6.91tb. So since your calculation works in that case, is my file ok?
-
@Schoolsalesman Whats the file name and file size ?
-
@haitch
xxxxxxxxxxxxxxxxxxxx_6963200_28999680_28999680
6.91 tb file size
-
@Schoolsalesman Based on that filename, the plot file should be exactly: 7,602,092,113,920 Bytes. Check the file properties - if it's not EXACTLY that number, something went wrong with the plot.
-
@haitch
6.91 TB (7,600,282,271,744 bytes).... so I have to replot? :( optimizing a plot doesn't make the size a bit smaller or anything?
-
@Schoolsalesman Nope, you have to replot. Optimizing changes the order of the nonces, but not the size of the file. Check the properties of the disk and get the number of bytes it has - the most common plotting error is setting too high a nonce count and the plotter tries to plot more than 100% of the drive. The plotter will always plot a multiple of the stagger - so <number of nonces> * 262144 must be less than disk size in bytes, and <number of nonces> div <stagger> must = 0.
To calculate the correct number of nonces:
floor((<drive size in bytes> / 262144) / <stagger>) * <stagger>
-
So is the file useless? Because when jminer runs through the plot it still finds and submits nonces from what I can tell... If replotting would only make a 100% cohesive nonce sequence instead of 95+%, could I get away with just letting this plot file be? It takes like 4-5 days to plot 8tb so I'd really rather avoid that if possible. What do you think the possible reasons could be for the bad plot file? I intend to use jminer again and wouldn't want to put in 5 days for the same result.
Also, thanks a lot for answering my questions.
-
@Schoolsalesman The file is potentially 99% complete, or 5% complete - there's no way of knowing. If it's 95% complete, there will be some targets you can't mine, but all others should be fine.
