Starting to test each plot with 30 challenges each
Testing plot \\192.168.1.223\public\chia-plots-1\plot-k32-2021-03-29-14-48-cc85c222721bef984ca7db765790df34690406701900a0c55c5ff26d6cddade1.plot k=32
Pool public key: b59e5c3f507029ac4bbff11e00aac05588effc49d210273080ee17f0fcbdf09c70501ce9aa2686411d00ed3bc8d77814
Farmer public key: 8d577c6df158f02314668bdb591de52a0ddc1b04c45f99d81ffaba5ccb0b27dc4fd5918725d9df94cef414971a753db5
ERROR <class 'RuntimeError'>: Src size is incorrect error in getting challenge qualities for plot \\192.168.1.223\public\chia-plots-1\plot-k32-2021-03-29-14-48-cc85c222721bef984ca7db765790df34690406701900a0c55c5ff26d6cddade1.plot
ERROR Proofs 0 / 30, 0.0
Summary
Found 0 valid plots, total size 0.00000 TiB
WARNING 1 invalid plots found:
WARNING \\192.168.1.223\public\chia-plots-1\plot-k32-2021-03-29-14-48-cc85c222721bef984ca7db765790df34690406701900a0c55c5ff26d6cddade1.plot
Dang, I didn’t realize plots could come out bad… I guess I’ll be checking the debug log more closely and deleting these plots??
I’m also scared because all my plots are checking out bad? I picked a random one and it also produces this error?
Well damn. I can go to bed at least, I was worried all my plots were bad
Looks like the ones in the debug log are indeed bad plots though, all the ones I check turn out to be bad, so I should auto-delete those… sheesh… what’s up with these bad plots, where are they coming from?!
I’d move one that says it’s bad to a local disk and check it again just to take all of the networking and the second machine / NAS out of the loop.
Hmm yeah none of my plotters are overclocked to my knowledge, but that would make sense. I’ll keep an eye on any patterns that emerge…
Here’s a regex that matches the correct lines in the C:\Users\user\.chia\mainnet\log\debug.log
ERROR\s+File:\s(\\\\.*?\.plot)
And the command you use to test is
.\chia plots check -n 5 -g {filename}
Overnight 3 files emerged as bad from my debug.log and I checked them all, they are confirmed bad via the above command, and I deleted them. It looks like you can use a wide variety of forms for {filename} including:
the full path to the file \\192.168.1.16\chia-final-y\plot-k32-2021-04-20-04-34-938dc97711b9f71981d50983dffc6c00d13e6d801c0c1fe7cbfdc121f14b3b64.plot
just the filename plot-k32-2021-04-20-04-34-938dc97711b9f71981d50983dffc6c00d13e6d801c0c1fe7cbfdc121f14b3b64.plot
just the guid (the end plus .plot) 938dc97711b9f71981d50983dffc6c00d13e6d801c0c1fe7cbfdc121f14b3b64.plot
Checked my logs and found a bad plot… killed it. Doing some chia checks now on various dates. (while this is running, a few seconds are added to my farm response times.)
Yeah the logs will WARN or ERROR if they find bad plots, so it’s a good idea to grep your logs for that periodically… as I covered in Protip: check your debug.log regularly
I had a spate of bad plots lately, I think the way I was copying them off the NAS was corrupting them … but this command is absolute gold for finding bad plots. You don’t need to set the iterations very high to find them, either.
In addition to the previous sequences, I like doing it per-drive, per date, like so:
.\chia plots check -n 5 -g K:\plot-k32-2021-04-02
This’ll quickly check all plots on that drive (K) created on 04-02-2021 which is handy. (Five is the minimum number of checks, but it suffices for my purposes.)
@codinghorror I have one server which creates plots with <class 'RuntimeError'>: Src size is incorrect error in getting challenge qualities for plot error 100% of the time so I’m trying to determine what exactly on this server is causing this behavior. Note that plots check with -n 5 passes for me on all these plots, but as soon as I do -n 10 all of them fail. Good thing that I checked these plots when dropping them in to my harvester as harvester log did not show any issues with these plots during farming.
The built in pre-boot men test passes and Prime95 does not report any errors/warning although I could not run it overnight. I think something may be causing this at the RAID used for tmp location or possibly ReFS used on the tmp as well. I’ll try creating a plot on an external drive to test.
Does not look like it is CPU or RAM related as I tested plot creation agains an external HDD via USB3 and resulting file checks out fine. It is either something with ReFS file system that is on the tmp drive or the RAID controller for tmp drive. I will try to do some testing on ReFS with an external or iSCSI drive to confirm if it is that as I would be really surprised if it was this ent. grade RAID card.
I am seeing a few of these errors “Error using prover object Src size is incorrect” or “Error using prover object Error (generic)” or “Error using prover object Invalid size for deltas” but every time I run it against plots check with n = 30 or even 100 against the specific plot it passes so I am not sure what these errors mean?