It has been verified that there is a problem with this block, so there is no need to re-examine the whole SSD. Can it not be replot only for this block?
When you lost the reward, it’s clear that there’s something wrong with the plot.
It is fine.
I don’t understand what you mean by “block” here. You clearly had an issue with majority of plotted sectors if not all, so you basically need to replot everything.
I mean, if it’s just minority plots, it’s a lot less expensive to accurately capture a replot than it is to do a full replot.
If I plot as a stand-alone and then move to a cluster, will it affect the files I plot?Will this lead to large-scale FL?
First of all, it doesn’t seem to be the minority:
Second, as I said earlier, checking is as expensive as replotting, so you might as well replot it.
You can switch between regular CLI, cluster and Space Acres any time, all official applications have the same format. No idea what “FL” is though.
reward skiped.
In the current version of Farm,If there are multiple SSDs on a stand-alone drawing machine and one of them has cache obsolescence, will it cause problems with all the disk plot data?
If cache is simply out of date, it’ll be synced and plotting will happen concurrently. There will be no issues with plots themselves, that would be a bug and serious usability issue in the software.
Either expired, I described a problem, or the cache of the test environment exists in a SSD, what happens
Look, you can do whatever you want. I suggested the most likely reason and how to definitively solve it. If you don’t like the solution you can do whatever, but I don’t have a better answer for you.
I don’t dislike your solution, but we have more machines and SSDs. This may happen. I need to pay attention to the places I need to be careful when operating.
Just to solve this problem completely and quickly