[Bug] 1.6.1 Stopped Sync'ing At 1:09pm MST

[pawnslinger]

What happened?

At 1:09pm local time, Mountain Standard Time, my full node version 1.6.1 stopped sync'ing. I am stuck at height 3 032 763, I still have connections and they show they have newer blocks, but my node is not getting them. The rest of my system looks fine... except the farmer is not farming, of course. I have done the obvious stuff, stopped all non--essential processes, checked my firewall, rebooted the computer, re-started Chia (several times)... checked hard drive space (there is plenty of room left). I am getting new connections and they all have newer blocks than me. I have 424 plots online, but not farming. Don't know what to do next. Any ideas or help would be appreciated. My system has been stable for a long time... I have earned more than 5 XCH using Space Pool. Nothing that I can think of has changed recently.

My system is running Windows 10, AMD 3950X 16 core, 32gb of ram. The drive with the Chia db has more than 1tb of space free. No Windows updates have been done recently.

The log below shows disk error, but I don't think that is correct. Chia is running on a sata ssd with more than 1tb free space. I have no indication of a disc problem with it.

Version

1.6.1

What platform are you using?

Windows

What ui mode are you using?

GUI

Relevant log output

2022-12-29T17:17:43.682 full_node chia.full_node.full_node: ERROR    sync from fork point failed err: disk I/O error
2022-12-29T17:18:36.770 full_node chia.full_node.full_node: ERROR    sync from fork point failed err: disk I/O error
2022-12-29T17:19:48.123 full_node chia.full_node.full_node: ERROR    sync from fork point failed err: disk I/O error
2022-12-29T17:22:14.609 full_node chia.full_node.full_node: ERROR    sync from fork point failed err: disk I/O error
2022-12-29T17:23:10.092 full_node chia.full_node.full_node: ERROR    sync from fork point failed err: disk I/O error
2022-12-29T17:24:10.436 full_node chia.full_node.full_node: ERROR    sync from fork point failed err: disk I/O error
2022-12-29T17:25:44.125 full_node chia.full_node.full_node: ERROR    sync from fork point failed err: disk I/O error
2022-12-29T17:26:38.314 full_node chia.full_node.full_node: ERROR    sync from fork point failed err: disk I/O error
2022-12-29T17:27:31.293 full_node chia.full_node.full_node: ERROR    sync from fork point failed err: disk I/O error
2022-12-29T17:28:39.394 full_node chia.full_node.full_node: ERROR    sync from fork point failed err: disk I/O error
2022-12-29T17:29:47.695 full_node chia.full_node.full_node: ERROR    sync from fork point failed err: disk I/O error
2022-12-29T17:29:48.573 full_node chia.full_node.full_node: WARNING  Received unsolicited/late block from peer {'host': '195.242.72.184', 'port': 8444}
2022-12-29T17:31:07.911 full_node chia.full_node.full_node: ERROR    sync from fork point failed err: disk I/O error
2022-12-29T17:32:32.033 full_node chia.full_node.full_node: ERROR    sync from fork point failed err: disk I/O error
2022-12-29T17:34:27.843 full_node chia.full_node.full_node: ERROR    sync from fork point failed err: disk I/O error
2022-12-29T17:35:48.034 full_node chia.full_node.full_node: ERROR    sync from fork point failed err: disk I/O error
2022-12-29T17:37:54.989 full_node chia.full_node.full_node: ERROR    sync from fork point failed err: disk I/O error
2022-12-29T17:39:10.259 full_node chia.full_node.full_node: ERROR    sync from fork point failed err: disk I/O error
2022-12-29T17:40:13.693 full_node chia.full_node.full_node: ERROR    sync from fork point failed err: disk I/O error

[emlowe]

I recommend you try running chia db validate on your DB - that error is being reported by the OS so I can only assume there is some problem reading/writing to the disk

[github-actions[bot]]

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.

[github-actions[bot]]

This issue was automatically closed because it has been flagged as stale, and subsequently passed 7 days with no further activity from the submitter or watchers.