-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v3.1.0-beta1 --disk-16 Windows Testing Results #397
Comments
I have the same problem |
same here, but by the next try they look totally fine, are ro replotting currently (as i am) i seem to occur randomly over all my c5 plots, plottet and harvestetd on windows 11 greetz |
I have the same issue. Tested plots with Win10 and Win11 -z5 -t15 --disk16 --temp1 --temp2(different drive) Spec: i7 10700K, 3080ti, 32gb, WD Blue NVMe x 2, Windows 10 and Windows 11 |
I create plots on a Linux system using the following command: This command utilizes bladebit_cuda256, which is the standard version of bladebit but compiled with a modification as per this GitHub pull request: #401. To verify the integrity of the plots, I use the command: When I set the number of check iterations to 10, the plot is considered OK as shown in this console output: $ chia plots check -n 10 -g /mnt/disk1/plots/plot-k32-c01-2023-12-25-11-09-1e96bc83b836f80dcf995b2de3adbfdd936f4a9ea0a7130de120fae633edce35.plot
2023-12-25T14:37:27.856 chia.plotting.check_plots : WARNING Use 30 challenges (our default) for balance of speed and accurate results
2023-12-25T14:37:27.856 chia.plotting.check_plots : INFO Loading plots in config.yaml using plot_manager loading code (parallel read: True)
[.....]
2023-12-25T14:37:41.870 chia.plotting.check_plots : INFO Proofs 8 / 10, 0.8. Filepath: /mnt/disk1/plots/plot-k32-c01-2023-12-25-11-09-1e96bc83b836f80dcf995b2de3adbfdd936f4a9ea0a7130de120fae633edce35.plot
2023-12-25T14:37:41.875 chia.plotting.check_plots : INFO
2023-12-25T14:37:41.875 chia.plotting.check_plots : INFO Summary
2023-12-25T14:37:41.875 chia.plotting.check_plots : INFO Found 1 valid plots, total size 0.08544 TiB
2023-12-25T14:37:41.875 chia.plotting.check_plots : INFO 1 plots of size 32 However, if the number of iterations is increased to 100, the plot is flagged as NOT OK, and an error is generated, as shown in this output: $ chia plots check -n 100 -g /mnt/disk1/plots/plot-k32-c01-2023-12-25-11-09-1e96bc83b836f80dcf995b2de3adbfdd936f4a9ea0a7130de120fae633edce35.plot
2023-12-25T14:37:52.921 chia.plotting.check_plots : INFO Loading plots in config.yaml using plot_manager loading code (parallel read: True)
[...]
2023-12-25T14:39:14.196 chia.plotting.check_plots : ERROR <class 'ValueError'>: Invalid size for deltas: 45966 error in getting challenge qualities for plot /mnt/disk1/plots/plot-k32-c01-2023-12-25-11-09-1e96bc83b836f80dcf995b2de3adbfdd936f4a9ea0a7130de120fae633edce35.plot
2023-12-25T14:39:14.196 chia.plotting.check_plots : ERROR Proofs 62 / 100, 0.62 Filepath: /mnt/disk1/plots/plot-k32-c01-2023-12-25-11-09-1e96bc83b836f80dcf995b2de3adbfdd936f4a9ea0a7130de120fae633edce35.plot
2023-12-25T14:39:14.197 chia.plotting.check_plots : INFO
2023-12-25T14:39:14.197 chia.plotting.check_plots : INFO Summary
2023-12-25T14:39:14.197 chia.plotting.check_plots : WARNING 1 invalid plots found:
2023-12-25T14:39:14.197 chia.plotting.check_plots : WARNING 1 bad plots:
2023-12-25T14:39:14.197 chia.plotting.check_plots : WARNING /mnt/disk1/plots/plot-k32-c01-2023-12-25-11-09-1e96bc83b836f80dcf995b2de3adbfdd936f4a9ea0a7130de120fae633edce35.plot This discrepancy in the plot validation process is concerning and needs further investigation. |
Windows 10 testing, I created 14 plots with
--disk-16
and all of the plots are bad;harvester chia.harvester.harvester: ERROR Exception fetching qualities for \\...\...\plot-k32-c07-....plot. Destination buffer is too small
chia plots check
reports every plot as<class 'ValueError'>: Invalid size for deltas: 57359 error in getting challenge qualities for plot...
Let me know whether there's anything I can do to help understand the issue better.
The text was updated successfully, but these errors were encountered: