I do not have any pictures at the moment but it has happened a few times within the last few weeks.
Randomly in the dedicated server random chunks usually 16x16 or 32x16 will be replaced with fresh ones, sometimes resulting in a massive hole to the void as well along-side a new chunk.
For example; In my nether within a fortress the entire fortress for a 16x16x256 hole appeared deleting a perfect square, same happened in the overworld near a bridge I made and within a building I made too requiring us to fix it manually.
It seems to be a chunk error/failure to load/regeneration bug?
Any info on how to fix this?
I have moved the BDS to an SSD for testing
EDIT: I have also seen a few chunk/void errors appear when typing "Stop" into the cmd. I have started kicking all players before reboots to minimise the chances but it still happens sometimes.
Related issues
Attachments
Comments
migrated
migrated
migrated
Hi Daniel,
Just to confirm, are you running 1.14.32.1? It came out on its own without an accompanying client update so many have missed it. It included a bunch of improvements around chunk loading and storage and crashes.
One way to tell if you're on 1.14.32.1 is the presence of "Running AutoCompaction.." on a regular basis.
Ionic
migrated
Hi Daniel,
Just to confirm, are you running 1.14.32.1? It came out on its own without an accompanying client update so many have missed it. It included a bunch of improvements around chunk loading and storage and crashes.
One way to tell if you're on 1.14.32.1 is the presence of "Running AutoCompaction.." on a regular basis.
Ionic
migrated
I believe I may be running from a slightly older version of 1.14, I have not updated since the first of march (Maybe earlier due to only finding zip files already existing elsewhere)
I will try the solution and let you know if there are any further chunk errors, so far I've had 3 within the past 2 weeks or so.
Thank you, I will update you within 7 days if any issue occurs.
migrated
I believe I may be running from a slightly older version of 1.14, I have not updated since the first of march (Maybe earlier due to only finding zip files already existing elsewhere)
I will try the solution and let you know if there are any further chunk errors, so far I've had 3 within the past 2 weeks or so.
Thank you, I will update you within 7 days if any issue occurs.
migrated
Awesome thank Daniel.
Best of luck crosses fingers
Ionic
migrated
Awesome thank Daniel.
Best of luck crosses fingers
Ionic
migrated
Update: Issue happened again but even worse.
[media]
migrated
Update: Issue happened again but even worse.
[media]
migrated
migrated
migrated
Any ideas on fixing this? It is happening often to the point we have to put creative on and fix it/rebuild our stuff
migrated
Any ideas on fixing this? It is happening often to the point we have to put creative on and fix it/rebuild our stuff
migrated
Another Update: It seems to fix itself SLIGHTLY between server reboots, may it be a corrupted DB?
When I reboot the server it either - spawns as picture 1, rebuilds my changes, re-adds new chunks, covers itself etc.
Any ideas?
migrated
Another Update: It seems to fix itself SLIGHTLY between server reboots, may it be a corrupted DB?
When I reboot the server it either - spawns as picture 1, rebuilds my changes, re-adds new chunks, covers itself etc.
Any ideas?
migrated
Are you using the stop command when shutting it down?
migrated
Are you using the stop command when shutting it down?
migrated
Yes.
Every server shutdown the "stop" command is run. I sometimes notice errors appear when I run the stop command (Mostly when there are other players in the server at the time).
I usually kick every player/leave the server before running the stop cmd so no dbs are being written to during the time of reboot.
migrated
Yes.
Every server shutdown the "stop" command is run. I sometimes notice errors appear when I run the stop command (Mostly when there are other players in the server at the time).
I usually kick every player/leave the server before running the stop cmd so no dbs are being written to during the time of reboot.
migrated
If you want to fix this I suggest you use an app called blocktopograph and use the begin section then cover the area affected by the corruption then delete the chunks and go back to minecraft, and it should be fixed
But it will reset it, like if it was new
migrated
If you want to fix this I suggest you use an app called blocktopograph and use the begin section then cover the area affected by the corruption then delete the chunks and go back to minecraft, and it should be fixed
But it will reset it, like if it was new
migrated
Was this world not compressed into a zip before? If yes, then this is a problem in the compression algorithm of your archiver, which will lead to the loss of some part of your world.
migrated
Was this world not compressed into a zip before? If yes, then this is a problem in the compression algorithm of your archiver, which will lead to the loss of some part of your world.
migrated
The world can no longer be restored.
migrated
The world can no longer be restored.
migrated
Likely the same issue covered by MCPE-58514 which has been resolved in the 1.16.2 BETA's.
While it won't restore lost chunks, this should stop occurring with the 1.16.2 release.
migrated
Likely the same issue covered by MCPE-58514 which has been resolved in the 1.16.2 BETA's.
While it won't restore lost chunks, this should stop occurring with the 1.16.2 release.