Closed jayhohoho2019 closed 8 months ago
To clarify, farmer did not seem to be aware of the problem the harvester was having, as farmer was reporting the plots from that harvester also. On the harvester side, chia_harvester and daemon were both running. the plots were not accessible to harvester (ls /mnt/farm returned I/O error).
Did you resolve where the I/O error came from? is it from a disk going bad?
Could be cable, could be power supply, could be a disk or the 5-bay disk enclosure the HDDs are in. But after a reboot of the Pi4 harvester the error has not come back.
Regardless of the I/O error source, chia harvester did log the errors, but the farmer node wasn't picking it up.
This issue has not been updated in 14 days and is now flagged as stale. If this issue is still affecting you and in need of further review, please comment on it with an update to keep it from auto closing in 7 days.
The I/O error on the Pi4 harveser has not returned so far. However I suspect if/when it returns, farmer would still be unaware that the plots from that harvester had become unavailable.
This issue has not been updated in 14 days and is now flagged as stale. If this issue is still affecting you and in need of further review, please comment on it with an update to keep it from auto closing in 7 days.
closing old issue
What happened?
A remote harvester was reporting ERROR for weeks that had prevented its harvester to read most of the plots, but the farmer node did not seem to have any clue. My monitoring was only on the farmer node which, among other things, checks the output of
chia farmer summary
periodically. If the reported plot count for all harvesters falls under a threshold it would alert. It never did during the last few weeks when this 1 harvester was almost entirely out of action.chia plotnft show
was also showing the incorrect plot count.Version
1.2.11
What platform are you using?
Linux
What ui mode are you using?
CLI
Relevant log output