|Anonymous | Login | Signup for a new account||2019-03-19 22:26 PDT|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0010785||Dwarf Fortress||Technical -- Saving/Loading||public||2018-06-07 16:17||2018-06-08 13:10|
|Platform||PC||OS||windows 7||OS Version||Pro-64 bit|
|Target Version||Fixed in Version|
|Summary||0010785: Bugged Save|
|Description||After initiating a save, DF hung for just over three hours (2 hours and 56 mins longer than normal) before I had to reboot the machine in order to regain control. Save now hangs while "Loading local animal population".|
Have uploaded a copy of the save here:
Am I toast?
|Steps To Reproduce||Attempted to load within LNP0.13 and outside of it. Hangs every time in the same step.|
|Additional Information||No unusual activity prior to save. I did just buy out a Dwarf trader of a good many animals to bulk up bone production.|
|Tags||No tags attached.|
In my case the loading of the save cause DF to crash (just disappearing with DFHack, although that typically means non DFHack crashes with a message window popup). I'm on Windows 10.1.
LNP0.13 doesn't tell me much. I would guess that's the version of pyLNP used, but I assume you haven't assembled something yourself, but used a pack (e.g. PeridexisErrant's LNP). The relevant version is the pack version (and the pack name, of course).
Regardless, I would guess the save is corrupt and you do have to start anew, unless you have a backup from a previous point.
region3/world.sav: chunk 5212 (start=16774854, length=2783): Compression error: unexpected EOF region3/world.sav: 211641672 bytes unread, 16777641 bytes read
So world.sav is corrupted around 16 MB in. Are you short on disk space, or did anything unusual happen while saving last time?
I didn't check other files because there are too many (~20k) to check easily. I don't think it's possible to fix without a backup of at least world.sav, though.
edited on: 2018-06-08 08:58
Turns out world.sav starting at exactly 0x01000000 is entirely 0x00 bytes, which is definitely corrupted beyond repair. This is something I've seen before in one or two other reports, but I'm inclined to say it's a system factor, as that's an unusually round number.
|Thanks for the help folks. Lethosar I have lots of HD space. Absolutely nothing unusual happened prior to the eternal saving process that got hung. In fact, I had only been playing a short while since the last save. Unfortunately, no backup done. That was the learned lesson on this fort.|
I was asking about during the save, but apparently I didn't see that part of the original report - if it hung during a save, that might explain how the save got corrupted.
Was DF in the "cleaning game objects" stage yet? Usually a crash during saving doesn't corrupt a save, because DF writes to data/save/current first, then moves everything into the region folder. I'm surprised that a hang while saving could cause something like this.
|2018-06-07 16:17||Greyberyl||New Issue|
|2018-06-08 04:49||PatrikLundell||Note Added: 0038442|
|2018-06-08 08:55||lethosor||Note Added: 0038444|
|2018-06-08 08:57||lethosor||Note Added: 0038445|
|2018-06-08 08:58||lethosor||Note Edited: 0038445||View Revisions|
|2018-06-08 11:10||Greyberyl||Note Added: 0038446|
|2018-06-08 13:10||lethosor||Note Added: 0038447|
|Copyright © 2000 - 2010 MantisBT Group|