DBStorage chain is invalid. Unable to start previously working server

Are you able to upload a zip of your server files. This will likely be too big for the tracker so you may have to use a service such as OneDrive or Google Drive and share a link.

Are you able to upload a zip of your server files. This will likely be too big for the tracker so you may have to use a service such as OneDrive or Google Drive and share a link.

Here is the zip file of the server on Google Drive, https://drive.google.com/open?id=1pIeB6U_na_v3nwo0ad18VrGJpE-YugU1

Thanks in advance

Here is the zip file of the server on Google Drive, https://drive.google.com/open?id=1pIeB6U_na_v3nwo0ad18VrGJpE-YugU1

Thanks in advance

It looks like your world files are corrupted. Please tell me you have backups?

You have a bunch of null size files that should have data in them (for example the level.dat which holds the settings etc for your world).

Did you stop the server gracefully before you did updates and restarted?

It looks like your world files are corrupted. Please tell me you have backups?

You have a bunch of null size files that should have data in them (for example the level.dat which holds the settings etc for your world).

Did you stop the server gracefully before you did updates and restarted?

Yikes, nope I only had it up for about 2 weeks with my girlfriend, I probably should have backed it up right before the updates but I had done a manual hard restart of the VM server and than rebooted through putty to reconnect to where I accepted the updates and then when I commanded the server to start it got the error. 

There's no way of recovering the world eh? We only had built a lot mostly in a few chunks near spawn like 400 or so blocks from spawn.

Yikes, nope I only had it up for about 2 weeks with my girlfriend, I probably should have backed it up right before the updates but I had done a manual hard restart of the VM server and than rebooted through putty to reconnect to where I accepted the updates and then when I commanded the server to start it got the error. 

There's no way of recovering the world eh? We only had built a lot mostly in a few chunks near spawn like 400 or so blocks from spawn.

Having the same issue after upgrading from 1.14.30.2 to 1.14.60.5.

I use a Docker container (https://github.com/itzg/docker-minecraft-bedrock-server) in Linux and noticed that I was unable to start my container after perfoming some maintenance on the underlying server:

I have 90 files in my "data/worlds/Bedrock level/db" folder, however it appears that the latest three files are all zero bytes, including the MANIFEST, which appears to be referencing an LDB which doesn't exist (111120).

My "data/worlds/Bedrock level" folder appears to contain a populated level.dat:

Having the same issue after upgrading from 1.14.30.2 to 1.14.60.5.

I use a Docker container (https://github.com/itzg/docker-minecraft-bedrock-server) in Linux and noticed that I was unable to start my container after perfoming some maintenance on the underlying server:

I have 90 files in my "data/worlds/Bedrock level/db" folder, however it appears that the latest three files are all zero bytes, including the MANIFEST, which appears to be referencing an LDB which doesn't exist (111120).

My "data/worlds/Bedrock level" folder appears to contain a populated level.dat:

Look at this message:

[2020-05-20 19:43:26 ERROR] Network port occupied, can't start server.

It's saying that the game network port is occupied for other process. I think you have the server open twice. One of the processes is in the background and hidden, using the database. When you try to open the server a second time, the application cannot open and decrypt the database because it is being used by the first one. Try to restart the VM (rebooting linux), so that any possible hidden session of the server is closed. You can also check in the running processes that the bedrock_server application is not running twice.

Look at this message:

[2020-05-20 19:43:26 ERROR] Network port occupied, can't start server.

It's saying that the game network port is occupied for other process. I think you have the server open twice. One of the processes is in the background and hidden, using the database. When you try to open the server a second time, the application cannot open and decrypt the database because it is being used by the first one. Try to restart the VM (rebooting linux), so that any possible hidden session of the server is closed. You can also check in the running processes that the bedrock_server application is not running twice.

@pablo Me and my friend tried to diagnose that part of the error "[2020-05-20 19:43:26 ERROR] Network port occupied, can't start server." as being how you said even before I made this post but we had made sure nothing else was running on the VM at all and even went as far as creating a new Cloud Server with a new IP and everything and it running completely fine on a freshly made server world but as soon as I transfer the world file in than both errors would be outputted every time and like the mod above said I think it comes down to a corruption problem. 

@pablo Me and my friend tried to diagnose that part of the error "[2020-05-20 19:43:26 ERROR] Network port occupied, can't start server." as being how you said even before I made this post but we had made sure nothing else was running on the VM at all and even went as far as creating a new Cloud Server with a new IP and everything and it running completely fine on a freshly made server world but as soon as I transfer the world file in than both errors would be outputted every time and like the mod above said I think it comes down to a corruption problem. 

Thanks for the suggestion Pablo, however, just like in Trivi's case, the "Network port occupied, can't start server" appears to be a false flag. I've verified that there is only one instance of the Bedrock server running, and in my case, Docker provides full network isolation. On a properly working BDS instance (port 19132 bound via UDP) this is what should be displayed, but in my case is not:

Thanks for the suggestion Pablo, however, just like in Trivi's case, the "Network port occupied, can't start server" appears to be a false flag. I've verified that there is only one instance of the Bedrock server running, and in my case, Docker provides full network isolation. On a properly working BDS instance (port 19132 bound via UDP) this is what should be displayed, but in my case is not:

I came across this link on Gamepedia related to recovering corrupted worlds. When attempting to load my level.dat, a world does load, but I have no inventory and I start in a location that I'm unfamiliar with. This is not entirely unexpected, as the instructions specifically state:

The things you were wearing and carrying at the time the world got corrupted are not (recoverable).

You will start in a random location and have to find your way back to your settlement.

While I don't know much about the LevelDB format, I'm skeptical that any features (settlements) that we built in our world before it became corrupted, could possibly be captured within the 2.1KB level.dat alone. My expectation is that the level.dat contains the seed for the world, but that the LDB files contain the vast majority of changes to the base world.

I also found issue BDS-4597 which closely resembles the issue that Trivi and I have experienced, and the OP was able to resolve their issue by opening the map in Minecraft directly, before migrating it back to their BDS. I'm not sure of the process that they followed to accomplish this though, as I don't see a way to directly open either the level.dat or individual LDB files within Minecraft.

I came across this link on Gamepedia related to recovering corrupted worlds. When attempting to load my level.dat, a world does load, but I have no inventory and I start in a location that I'm unfamiliar with. This is not entirely unexpected, as the instructions specifically state:

The things you were wearing and carrying at the time the world got corrupted are not (recoverable).

You will start in a random location and have to find your way back to your settlement.

While I don't know much about the LevelDB format, I'm skeptical that any features (settlements) that we built in our world before it became corrupted, could possibly be captured within the 2.1KB level.dat alone. My expectation is that the level.dat contains the seed for the world, but that the LDB files contain the vast majority of changes to the base world.

I also found issue BDS-4597 which closely resembles the issue that Trivi and I have experienced, and the OP was able to resolve their issue by opening the map in Minecraft directly, before migrating it back to their BDS. I'm not sure of the process that they followed to accomplish this though, as I don't see a way to directly open either the level.dat or individual LDB files within Minecraft.

I managed to recover my world, after a fair bit of trial and error. 😃

I made note of the last LDB file which had data in it (111116.ldb) and renamed the 0-byte MANIFEST-111120 to MANIFEST-111116. I then edited the 0-byte CURRENT file to contain "MANIFEST-111116". Upon starting my Bedrock server, it provided a warning that the database was corrupt, but it subsequently repaired it:

[2020-05-27 21:09:42 INFO] Starting Server
[2020-05-27 21:09:42 INFO] Version 1.14.60.5
[2020-05-27 21:09:42 INFO] Session ID 4e3ddebe-963a-411e-a90d-08542c93ce9a
[2020-05-27 21:09:42 INFO] Level Name: Bedrock level
[2020-05-27 21:09:42 INFO] Game mode: 0 Survival
[2020-05-27 21:09:42 INFO] Difficulty: 1 EASY
[2020-05-27 21:09:42 INFO] opening worlds/Bedrock level/db
[2020-05-27 21:09:42 WARN] LevelDB worlds/Bedrock level/db status NOT OK(Corruption: no meta-nextfile entry in descriptor). Trying repair.
[2020-05-27 21:09:51 INFO] IPv4 supported, port: 19132
[2020-05-27 21:09:51 INFO] IPv6 not supported
[2020-05-27 21:09:51 INFO] IPv4 supported, port: 55936
[2020-05-27 21:09:51 INFO] IPv6 not supported
[2020-05-27 21:09:52 INFO] Server started.

Naturally, I'll work to prevent this from happening in the future by making daily backups, but I'm still unsure as to what the underlying cause of the DB corruption was. I've seen an increased number of reports related to v1.14.60 worlds becoming corrupted due to non-graceful shutdowns of the game/BDS instance (eg. MCPE-62153, BDS-4597), so I'd be interested to know if there were any functional changes made to LevelDB as part of the release.