ive been running a pure vanilla server for over a year now. ive been through a few different hosts but i am currently with xfactorservers. ive had my share of problems over the past year with all the game updates but im still hanging on to my original world created during beta 1.5
every couple of days i backup my world. i zip the world via xafactor's TCadmin console then manually download the zip file. after downloading i unzip the world and test its integrity. unless teh world was corrupted somehow prior to the zipping ive never had an issue.. until now.
i attempted to unzip the world as i normally do but during the unpacking i get the following error in winrar:
-----------------------------------------------------------------------------------------------------------------------
! D:\minecraft stuff\Landsverge 1.1 1-30-12 original.zip: CRC failed in world\region\r.1.-1.mcr. The file is corrupt
-----------------------------------------------------------------------------------------------------------------------
the world folder i ended up with simply had this region file omitted. this has happened twice within a month. the first time it happened i took a copy of this region file from a previous backup of two days prior and plugged it into the world that failed to unzip properly. i then tested the world thoroughly in single player and found no apparent adverse effects in the world. I was further reassured when i noticed the game was updating the file as i played. also, the world folder was then able to be zipped and unzipped without issues.
things were fine for a couple weeks and well over a dozen more backups that passed my integrity testing. then today i got the CRC error again, and for the exact same region file. this time i tried a couple more things; again i took a previous, problem-free version of the file and plugged it into the world folder that failed to unzip properly. and again that worked as it did before. additionally i tried playing the world on single player without a copy of this file and i was confused by the results.
the world seemed fine, just as i left it prior to zipping it for download. so still no in-game changes through all of this. however, when i checked the region folder i found that the game had generated a new r.1.-1.mcr and it was about 400k in size. the previous, and supposedly corrupted, file by the very same name was about 5 megs.. quite a difference, but there was still no sign of any change in-game.
i decided the safest thing was to do what i did the first time and replace the file with a 2-day younger copy of itself, but more importantly, also about 5 meg in size.
ive read that CRC errors in winrar/winzip can be a result of problems with the zip utility itself. so i tried reinstalling winrar with the latest stable version for my OS. i still get this issue no matter how many times i try to rezip the world folders with the faulty region file.
im hoping someone else has experienced this and has more enlightening info for me. maybe its a quirky inconvenience im just going to have to deal with, or ignore. it would help if i understood the structure of the region files and what they mean exactly.. possibly how i can identify them with actualy regions in-game.
i still get this issue no matter how many times i try to rezip the world folders with the faulty region file.
You mean you are zipping it always with the same software on the same machine (i.e. Using TCAdmin)?
So although you have updated YOUR version of zip, the backup is still being made with the same old version?
If you have shell access to your server machines, I would attempt to verify that it is consistent in situ.
Second things. Even if the server was updating the region the zip should still be consistent, even if MC considered the resulting region file corrupt. A corrupt zip could be caused by a bug in the zipper or unzipper, or from running out of disk space or from corruption during the ftp.
Last thing. A region file contains multiple chunks, and its size varies depending upon how many of the chunks have been generated... I believe the MCRegion format is documented on the Wiki.
You mean you are zipping it always with the same software on the same machine (i.e. Using TCAdmin)?
So although you have updated YOUR version of zip, the backup is still being made with the same old version?
If you have shell access to your server machines, I would attempt to verify that it is consistent in situ.
Second things. Even if the server was updating the region the zip should still be consistent, even if MC considered the resulting region file corrupt. A corrupt zip could be caused by a bug in the zipper or unzipper, or from running out of disk space or from corruption during the ftp.
Last thing. A region file contains multiple chunks, and its size varies depending upon how many of the chunks have been generated... I believe the MCRegion format is documented on the Wiki.
i dont really have options for zipping. i have to use their TCadmin console interface to do that. so yeah, thre could be some kind of sporatic issue with that. and ive got no other way to access the server machine. if the problem is with the zip utility it would have to be on their end.
minecraft isnt showing me any signs of considering any part of the world as corrupt. ive had to deal with corruption in the past in the form of bad chunks mostly. fortunately server traffic has been extremely low in the past month so i am easily able to check every part of the world that has seen any play time. the game updating and increasing the file in question seems to confirm that im checking the right place.
what i dont get is when i replace the file with an older one or leave it out entirely to allow the game to generate a new, much smaller, file the resulting game world doesnt seem to change at all. i would think a sizable group of chunks would be recreated or at least rolled back when i do that.. whether the file is really corrupt or not.
on another note, we plan on starting the world over again when 1.2 hits. but some choice creations will be getting MCedited out of the current world and pasted into the new world. ill be starting fresh with a server reinstall as well. it would be nice to have a way to verify if any of these cut/paste areas include some kind of corruption before placing them in a fresh world. the only way i know how to test bad chunks is to generate a cartograph G map for the world and try to spot plain white blocks in the map instead of the terrain that should be there. and ive run that test on the current world and found nothing bad.
what i dont get is when i replace the file with an older one or leave it out entirely to allow the game to generate a new, much smaller, file the resulting game world doesnt seem to change at all. i would think a sizable group of chunks would be recreated or at least rolled back when i do that.. whether the file is really corrupt or not.
Given the same version of minecraft, a chunk will always come back the same way. So when you revert to an older file, the only things that will be lost are things like: entities (passive mobs), modifications (ore extracted, torches placed, buildings built), growth (wheat / mushrooms / saplings)
If those chunks are saved only because someone flew over them, then you won't notice any changes. Or if they were created because of someone spelunking, you would only notice changes underground.
Given the same version of minecraft, a chunk will always come back the same way. So when you revert to an older file, the only things that will be lost are things like: entities (passive mobs), modifications (ore extracted, torches placed, buildings built), growth (wheat / mushrooms / saplings)
If those chunks are saved only because someone flew over them, then you won't notice any changes. Or if they were created because of someone spelunking, you would only notice changes underground.
so i had it wrong about where the region was. i had cartograph G generate a map with the world that unzipped without the r.1.-1 file and it showed me a huge block of chunks missing from an area. i loaded the map in single player and explored it to find that the game just generated new terrain in its place, losing what was there.
so then i went into winrar options and checked "Keep broken files" and then tried unzipping again. i got the error again but the file unzipped anyway. i checked it in-game and teh region seemed fine.
for a different approach, i scrapped the zip file altogether and logged into the server. i wnet and explored the region in question, broke a couple blocks, then logged out and zipped the world again. when unzipping this one i got the error again but for a different region. so again, i scrapped the zip file and explored the second region in-game and zipped it up again. this time the resulting zip file unzipped just fine. so heres a list of things that apparently work around the error:
- use the world without worrying about the region file and allow the game to generate a new one, losing what was there.
- manually paste an older copy of the region file from a previous recent backup into the region folder, rolling back the region however far back the previous backup goes.
- force winrar to keep the file when unzipping, ignoring the error message
- repeatedly explore and alter the region(s) that are prompting errors then rezipping the world until the errors stop.
according to threads in some winrar support forums people are generally not concerned about this CRC error and often say to ignore it, and that its the utility screwing up, not the file. ive reinstalled my winrar twice now but my server host only offers me access to the server via its TCadmin console which has an integrated zipping feature within its file manager. for the past year ive been zipping backups but only now have i been getting this error. something may be up with the way they are zipping the world for me but i have no way to test that.
Have you tried downloading the zipped file twice and using some hash program, for example some md5summer to verify the files have the same md5sum? Does that TCadmin allow access to the server console?
I have my own minecraft server on a Linux box, on which I have a backup shell script (from wiki) running every night. It issues the save-off and save-all commands, then compresses the entire minecraft server directory, and then issues the save-on command. This has the benefit that the region files are not updated during compression. Without the save-off command, I had tar complaining about the files changing during compression.
So the point being, can you issue the save-off command before doing the zipping, and then issuing the save-on command after it is done to see if that helps?
zip file recovery helps you with damaged .zip archives. Tool repairs .zip files from floppy disks, CDs, DVDs, Zip drives, etc. It supports Win98 and higher. Software can work with zip archives more than 2GB. You may download demo version for checking tool features up.
every couple of days i backup my world. i zip the world via xafactor's TCadmin console then manually download the zip file. after downloading i unzip the world and test its integrity. unless teh world was corrupted somehow prior to the zipping ive never had an issue.. until now.
i attempted to unzip the world as i normally do but during the unpacking i get the following error in winrar:
-----------------------------------------------------------------------------------------------------------------------
! D:\minecraft stuff\Landsverge 1.1 1-30-12 original.zip: CRC failed in world\region\r.1.-1.mcr. The file is corrupt
-----------------------------------------------------------------------------------------------------------------------
the world folder i ended up with simply had this region file omitted. this has happened twice within a month. the first time it happened i took a copy of this region file from a previous backup of two days prior and plugged it into the world that failed to unzip properly. i then tested the world thoroughly in single player and found no apparent adverse effects in the world. I was further reassured when i noticed the game was updating the file as i played. also, the world folder was then able to be zipped and unzipped without issues.
things were fine for a couple weeks and well over a dozen more backups that passed my integrity testing. then today i got the CRC error again, and for the exact same region file. this time i tried a couple more things; again i took a previous, problem-free version of the file and plugged it into the world folder that failed to unzip properly. and again that worked as it did before. additionally i tried playing the world on single player without a copy of this file and i was confused by the results.
the world seemed fine, just as i left it prior to zipping it for download. so still no in-game changes through all of this. however, when i checked the region folder i found that the game had generated a new r.1.-1.mcr and it was about 400k in size. the previous, and supposedly corrupted, file by the very same name was about 5 megs.. quite a difference, but there was still no sign of any change in-game.
i decided the safest thing was to do what i did the first time and replace the file with a 2-day younger copy of itself, but more importantly, also about 5 meg in size.
ive read that CRC errors in winrar/winzip can be a result of problems with the zip utility itself. so i tried reinstalling winrar with the latest stable version for my OS. i still get this issue no matter how many times i try to rezip the world folders with the faulty region file.
im hoping someone else has experienced this and has more enlightening info for me. maybe its a quirky inconvenience im just going to have to deal with, or ignore. it would help if i understood the structure of the region files and what they mean exactly.. possibly how i can identify them with actualy regions in-game.
anyone have any insight?
When you say this
You mean you are zipping it always with the same software on the same machine (i.e. Using TCAdmin)?
So although you have updated YOUR version of zip, the backup is still being made with the same old version?
If you have shell access to your server machines, I would attempt to verify that it is consistent in situ.
Second things. Even if the server was updating the region the zip should still be consistent, even if MC considered the resulting region file corrupt. A corrupt zip could be caused by a bug in the zipper or unzipper, or from running out of disk space or from corruption during the ftp.
Last thing. A region file contains multiple chunks, and its size varies depending upon how many of the chunks have been generated... I believe the MCRegion format is documented on the Wiki.
i dont really have options for zipping. i have to use their TCadmin console interface to do that. so yeah, thre could be some kind of sporatic issue with that. and ive got no other way to access the server machine. if the problem is with the zip utility it would have to be on their end.
minecraft isnt showing me any signs of considering any part of the world as corrupt. ive had to deal with corruption in the past in the form of bad chunks mostly. fortunately server traffic has been extremely low in the past month so i am easily able to check every part of the world that has seen any play time. the game updating and increasing the file in question seems to confirm that im checking the right place.
what i dont get is when i replace the file with an older one or leave it out entirely to allow the game to generate a new, much smaller, file the resulting game world doesnt seem to change at all. i would think a sizable group of chunks would be recreated or at least rolled back when i do that.. whether the file is really corrupt or not.
on another note, we plan on starting the world over again when 1.2 hits. but some choice creations will be getting MCedited out of the current world and pasted into the new world. ill be starting fresh with a server reinstall as well. it would be nice to have a way to verify if any of these cut/paste areas include some kind of corruption before placing them in a fresh world. the only way i know how to test bad chunks is to generate a cartograph G map for the world and try to spot plain white blocks in the map instead of the terrain that should be there. and ive run that test on the current world and found nothing bad.
Given the same version of minecraft, a chunk will always come back the same way. So when you revert to an older file, the only things that will be lost are things like: entities (passive mobs), modifications (ore extracted, torches placed, buildings built), growth (wheat / mushrooms / saplings)
If those chunks are saved only because someone flew over them, then you won't notice any changes. Or if they were created because of someone spelunking, you would only notice changes underground.
so i had it wrong about where the region was. i had cartograph G generate a map with the world that unzipped without the r.1.-1 file and it showed me a huge block of chunks missing from an area. i loaded the map in single player and explored it to find that the game just generated new terrain in its place, losing what was there.
so then i went into winrar options and checked "Keep broken files" and then tried unzipping again. i got the error again but the file unzipped anyway. i checked it in-game and teh region seemed fine.
for a different approach, i scrapped the zip file altogether and logged into the server. i wnet and explored the region in question, broke a couple blocks, then logged out and zipped the world again. when unzipping this one i got the error again but for a different region. so again, i scrapped the zip file and explored the second region in-game and zipped it up again. this time the resulting zip file unzipped just fine. so heres a list of things that apparently work around the error:
- use the world without worrying about the region file and allow the game to generate a new one, losing what was there.
- manually paste an older copy of the region file from a previous recent backup into the region folder, rolling back the region however far back the previous backup goes.
- force winrar to keep the file when unzipping, ignoring the error message
- repeatedly explore and alter the region(s) that are prompting errors then rezipping the world until the errors stop.
according to threads in some winrar support forums people are generally not concerned about this CRC error and often say to ignore it, and that its the utility screwing up, not the file. ive reinstalled my winrar twice now but my server host only offers me access to the server via its TCadmin console which has an integrated zipping feature within its file manager. for the past year ive been zipping backups but only now have i been getting this error. something may be up with the way they are zipping the world for me but i have no way to test that.
not even close. about 350 meg
I have my own minecraft server on a Linux box, on which I have a backup shell script (from wiki) running every night. It issues the save-off and save-all commands, then compresses the entire minecraft server directory, and then issues the save-on command. This has the benefit that the region files are not updated during compression. Without the save-off command, I had tar complaining about the files changing during compression.
So the point being, can you issue the save-off command before doing the zipping, and then issuing the save-on command after it is done to see if that helps?
My mods on CurseForge. My Github page with mods, tools and other stuff.