How to plot entire drive?
-
@Blago Thanks for your reply.
So in my case. 1TB 32GB ram
I would put 38146972 / 65536 = 582.0765
Then 582 * 65536 = 38141952So my command would end up being ID_0_38141952_65536_7 ?
Next one plot would be ID_38141953_38141952_65536_7 ?
-
@Havoc yes, but for the second one you can start at 38,141,952 - plotting 38,141,952 nonces starting at nonce 0 means the last nonce will be 38,141,951
-
@Havoc said in How to plot entire drive?:
Next one plot would be ID_38141953_38141952_65536_7
ID_38141952_38141952_65536_7
-
@limpopo said in How to plot entire drive?:
I think leaving some space can also grantee long life for your HDD
As far as i know only if you use SSD-Drives...
-
@piezo No need to leave space available. Both regular HDD and SSD have space reserved for remapping bad blocks. And since the mining process is only reading the disk, not modifying it, there is less likelihood of a block going bad than there is with a drive that is constantly being read & written.
-
@haitch I saw an article where it says
"Do not use 100% of your HDD. If you do this, you HDD will be extremely slow. Please use only 90% of your HDD space and let 10% free. For example, if you have a 1TB HDD, let 100GB free."https://docs.google.com/document/d/1mTwPqBbkjfL3abIPkqNRcHpQp-3r2de7sDdmANJpR3Y/edit
Do this still apply?
-
@Wolf The article is incorrect on that point. My primary miner has only a few GB free on all it's drives, and it is not slow.
-
Will you still be able to plot and mine if you have a nonces size that is not a multiple of stagger? If yes, will it be less effective?
-
@Propagandalf The number of nonces in the file must always be a multiple of the stagger. If you try and plot a number that is not a multiple, the plotter will adjust the number it plots, that can lead to it trying to plot more than 100% of the available capacity.
-
@haitch said in How to plot entire drive?:
@Propagandalf The number of nonces in the file must always be a multiple of the stagger. If you try and plot a number that is not a multiple, the plotter will adjust the number it plots, that can lead to it trying to plot more than 100% of the available capacity.
Thanks! That explains a lot, because when I have been using wplotgenerator I have calculated amount of plots based on free space in bytes, but forgotten to round off to nearest multiple of stagger. Hence, the plotter would usually stall at the end with the message "waiting for last write" or something like that. Now I know why. Nonetheless, I fixed the file by closing the window and running plotschecker, which truncated it and made a valid plot file. Next time I will round it off on forehand so that running plotschecker will be unnecessary.
-
@Propagandalf said in How to plot entire drive?:
plotschecker
Do you know where I can find plotschecker for linux?
-
@Tate-A said in How to plot entire drive?:
@Propagandalf said in How to plot entire drive?:
plotschecker
Do you know where I can find plotschecker for linux?
I have no idea, sorry. @Blago do you know if/where there's a version for Linux?
-
@Propagandalf said in How to plot entire drive?:
@Tate-A said in How to plot entire drive?:
@Propagandalf said in How to plot entire drive?:
plotschecker
Do you know where I can find plotschecker for linux?
I have no idea, sorry. @Blago do you know if/where there's a version for Linux?
it's a simple program, I think somebody (linux-users) can make (recompile) it for Linux (i have only Win)
-
Sorry, for the kinda dumb question here but I'm trying to figure out if I've overlapped these nonces on my android device. I just want to be clear...
If I started my first plot at 0 and plotted 4096 nonces (1 Gb), do I start my next plot at 4096 (and the next at 8192)?
I think the starting at 0 thing is throwing me off and I just want to make sure I'm not overlapping the first and last nonce of each plot. Thanks in advance.
-K
-
@k.coins You are correct in your assumptions! :)
-
@Propagandalf wheew... don't have to replot - thanks!


