phezzan Posted September 19, 2020 Share Posted September 19, 2020 (edited) Commands file: S:\phezz\AppData\Roaming\Avorion\galaxies\Kmod\commands.txt Initializing sector database... FileSecurer error: Reading of file "S:\phezz\AppData\Roaming\Avorion\galaxies\Kmod\sectors\archive2.db" failed, moving on to the next instance. Error: Unexpected end of file FileSecurer error: Reading of all instances of S:\phezz\AppData\Roaming\Avorion\galaxies\Kmod\sectors\archive2.db failed. "S:\phezz\AppData\Roaming\Avorion\galaxies\Kmod\sectors\meta.db": All instances have the same timestamp. This can lead to issues when loading. Initializing faction database... "S:\phezz\AppData\Roaming\Avorion\galaxies\Kmod\players\player_1.dat": All instances have the same timestamp. This can lead to issues when loading. "S:\phezz\AppData\Roaming\Avorion\galaxies\Kmod\players\player_1.dat": All instances have the same timestamp. This can lead to issues when loading. Steps Enable clustering Load Quit (Error disk full: 1GB galaxy and ?1GB? free) Load - errors as shown. Load (restored galaxy from a complete backup and freed up space) Quit (no errors) Load - errors as shown below. Initializing sector database... "S:\phezz\AppData\Roaming\Avorion\galaxies\Kmod\sectors\meta.db": All instances have the same timestamp. This can lead to issues when loading. Initializing faction database... "S:\phezz\AppData\Roaming\Avorion\galaxies\Kmod\alliances\alliance_43.dat": All instances have the same timestamp. This can lead to issues when loading. "S:\phezz\AppData\Roaming\Avorion\galaxies\Kmod\players\player_1.dat": All instances have the same timestamp. This can lead to issues when loading. "S:\phezz\AppData\Roaming\Avorion\galaxies\Kmod\players\player_1.dat": All instances have the same timestamp. This can lead to issues when loading. Starting up 10 worker threads... Avorion clustering appears to build the archive files, then copy them and it requires a lot of free space? Why not just rename them? The game seems to run fine despite the timestamp warnings - but they (timestamp warnings) appear to come and go. Edited September 20, 2020 by phezzan Explain that the corrupted (OOS) galaxy had to be restored from backups. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now