Closed jakub-polak closed 1 year ago
The most obvious explanation is that your disk is going bad. Can you try syncing to a different SSD?
The most obvious explanation is that your disk is going bad. Can you try syncing to a different SSD?
This is not entirely true. I had several times "database disk image is malformed" then exchanged SSD to new one then got again "database disk image is malformed" then I exchanged (again) to NEW SSD NVME M2 and the second time in the middle ( on the second SSD) I have database disk image is malformed during synchronization.
It would be good if CHIA TEAM could focus on such CONSTANT & REPEATING issues not only bullshit like the last NFT updates !!!!
Please check the setting of db_sync
in config.yaml for both wallet and node. Please make sure it is set to either "auto"
or "full"
.
The most obvious explanation is that your disk is going bad. Can you try syncing to a different SSD?
This is not entirely true. I had several times "database disk image is malformed" then exchanged SSD to new one then got again "database disk image is malformed" then I exchanged (again) to NEW SSD NVME M2 and the second time in the middle ( on the second SSD) I have database disk image is malformed during synchronization.
It would be good if CHIA TEAM could focus on such CONSTANT & REPEATING issues not only bullshit like the last NFT updates !!!!
I can confirm this. I have tried different disks and the issue persists.
Please check the setting of
db_sync
in config.yaml for both wallet and node. Please make sure it is set to either"auto"
or"full"
.
OK - I had "auto" switched to "full" nad continue sync as for now ...
And again problem with sync - log says:
2023-03-04T22:42:44.022 full_node asyncio : ERROR Task was destroyed but it is pending! 2023-03-04T22:42:44.332 full_node asyncio : ERROR Task was destroyed but it is pending! 2023-03-04T22:43:05.069 full_node chia.full_node.full_node: ERROR sync from fork point failed err: b'\x8b\xce\xac\xeb\xa4\xc5\x0e\xf6\x1f\x16\xa0vA\x84-\xd8\x8d\xbe,+R\x8e\x01_Is#\x9ba\x84\xeb\xd1' 2023-03-04T22:43:45.569 full_node chia.full_node.full_node: ERROR sync from fork point failed err: b'\x8b\xce\xac\xeb\xa4\xc5\x0e\xf6\x1f\x16\xa0vA\x84-\xd8\x8d\xbe,+R\x8e\x01_Is#\x9ba\x84\xeb\xd1' 2023-03-04T22:44:29.613 full_node chia.full_node.full_node: ERROR sync from fork point failed err: b'\x8b\xce\xac\xeb\xa4\xc5\x0e\xf6\x1f\x16\xa0vA\x84-\xd8\x8d\xbe,+R\x8e\x01_Is#\x9ba\x84\xeb\xd1' 2023-03-04T22:44:49.270 full_node asyncio : ERROR Task was destroyed but it is pending! 2023-03-04T22:44:49.861 full_node asyncio : ERROR Task was destroyed but it is pending! 2023-03-04T22:44:59.161 full_node chia.full_node.full_node: WARNING Syncing failed, CancelledError 2023-03-04T22:46:16.534 full_node chia.full_node.full_node: ERROR sync from fork point failed err: b'\x8b\xce\xac\xeb\xa4\xc5\x0e\xf6\x1f\x16\xa0vA\x84-\xd8\x8d\xbe,+R\x8e\x01_Is#\x9ba\x84\xeb\xd1' 2023-03-04T22:47:21.999 full_node chia.full_node.full_node: ERROR sync from fork point failed err: b'\x8b\xce\xac\xeb\xa4\xc5\x0e\xf6\x1f\x16\xa0vA\x84-\xd8\x8d\xbe,+R\x8e\x01_Is#\x9ba\x84\xeb\xd1' 2023-03-04T22:48:58.617 full_node chia.full_node.full_node: ERROR sync from fork point failed err: b'\x8b\xce\xac\xeb\xa4\xc5\x0e\xf6\x1f\x16\xa0vA\x84-\xd8\x8d\xbe,+R\x8e\x01_Is#\x9ba\x84\xeb\xd1' 2023-03-04T22:49:48.622 full_node chia.full_node.full_node: ERROR sync from fork point failed err: b'\x8b\xce\xac\xeb\xa4\xc5\x0e\xf6\x1f\x16\xa0vA\x84-\xd8\x8d\xbe,+R\x8e\x01_Is#\x9ba\x84\xeb\xd1'
What the hell does it mean ???!!!
@rones-dev Could you please make further responses within your issue #14558?
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.
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.
What happened?
I was trying to sync my database multiple times and it always get malformed around blocks 728k -
Added blocks 728007 to 728039
. Multiple times it was exactly this block, some times it goes up to 731k.There were no crashes while syncing. Removal of
db
andwallet
directories didn't help.Please let me know what details could be helpful for solving that.
Version
1.6.2
What platform are you using?
Linux
What ui mode are you using?
CLI
Relevant log output