How do you fix the issue with: WARNING Looking up qualities on ...

[long-pham]

I tried many ways but couldn't figure out the root cause. Could you share your experience fixing this issue? All 5000 plots are connected to USB hubs to a Mac Mini M1, running chia fullnode v1.1.7

$ cat ~/.chia/mainnet/log/debug.log | grep qualities
2021-06-18T08:09:21.501 harvester chia.harvester.harvester: WARNING  Looking up qualities on /Volumes/SeaB/plots/plot-k32-2021-04-22-21-15-2040bb47bc7b6ed326a048710beeec4b89b44dd3a27f1c2c06863913e176dfe6.plot took: 5.075508117675781. This should be below 5 seconds to minimize risk of losing rewards.
2021-06-18T12:30:36.828 harvester chia.harvester.harvester: WARNING  Looking up qualities on /Volumes/SeaB/plots/plot-k32-2021-04-24-20-55-fdb936be333341c60bb7abe81bdd3d818be9a8864129439509670cc0672042f6.plot took: 5.0666351318359375. This should be below 5 seconds to minimize risk of losing rewards.
2021-06-18T14:55:49.271 harvester chia.harvester.harvester: WARNING  Looking up qualities on /Volumes/SeaR/plots/plot-k32-2021-04-29-00-23-483957cecde7313c13b7e579bcefe570a14b5fbfbb7927b663888ee467d27f9e.plot took: 5.103079080581665. This should be below 5 seconds to minimize risk of losing rewards.
2021-06-18T15:19:41.179 harvester chia.harvester.harvester: WARNING  Looking up qualities on /Volumes/SeaSb/plots/plot-k32-2021-06-06-23-03-4e964daddf524a35e9db736e214f4aded8b58647ade50c5d729d9e6f40aba697.plot took: 5.128448009490967. This should be below 5 seconds to minimize risk of losing rewards.
2021-06-18T15:41:51.064 harvester chia.harvester.harvester: WARNING  Looking up qualities on /Volumes/SeaQ1/plots/plot-k32-2021-05-27-22-28-c33f1d2e75c88845579a6d1c0d8ec67877b5f17575fc6ad529c694434964cbe7.plot took: 5.355412006378174. This should be below 5 seconds to minimize risk of losing rewards.
2021-06-18T15:41:51.362 harvester chia.harvester.harvester: WARNING  Looking up qualities on /Volumes/SeaB/plots/plot-k32-2021-04-23-20-40-5ce19aa56bf3fecfc65321181e0e0936921e73cfc870688137080f50f1e9e769.plot took: 5.6532721519470215. This should be below 5 seconds to minimize risk of losing rewards.

[rmica]

There could be many root causes. Try to figure out what were you doing at 09:21 12:30 15:55 and so on. Were you transferring new plots?
It's only a my personal experience, if you have lookup time warnings without peaks or big standard deviations (yours are all in the 5 sec range), then you have a structural, not software, issue. Did you hit a limit with 5k plots on USB?

[long-pham]

None of the issue. No issue with 5k plots on M1

[BaneusCatrix]

I have a similar problem. I have plots on a linux fileserver on USB connected drives and on mdraid devices (13x HGST 3TB HUS72303CLAR3000 in RAID6 and 4x HGST 4TB HDN726040ALE614 in RAID5). Chia only reports this problem with plots on the mdraid devices, not on the USB disks. I monitor disk utilization and there is no spike or peak at the timestamps chia is complaining. The same is happening on a second machine. It is running TrueNAS with ZFS (raidz2). I measured thoughput and latency with bonnie++ an both machines and all values are looking good. Does chia have problems with (software)-raid devices?

Edit: Chia version 1.2.3 on Alma Linux 8.4 and Chia version 1.2.4.dev0 on TrueNAS 12.2-RELEASE-p9

[keliew]

I think you hit the bug which was fixed in 1.2.3, but need to be configured (parallel_read).

See https://github.com/Chia-Network/chia-blockchain/releases/tag/1.2.3 and https://github.com/Chia-Network/chia-blockchain/blob/1.2.3/chia/util/initial-config.yaml#L134

[TaijiMonster]

I am already on 1.2.4 and yet still keep getting such error, does this mean the plots are bad or low qualities or something?

[keliew]

I am already on 1.2.4 and yet still keep getting such error, does this mean the plots are bad or low qualities or something?

Most likely the issue(s) is/are due to hardware and/or system configuration.

If the plot is bad, it'd throw an error directly.

[BrandtH22]

@long-pham , since this ticket was opened a number of years ago without further comments it seems this issue has been resolved.
We will be closing this ticket but if we have closed this ticket in error do not hesitate to reach out to us again with any followup questions or comments.

The best place to reach our support team is on Discord (https://discord.gg/chia) or by reopening this ticket.