tangofoxtrot Posted February 4, 2018 Posted February 4, 2018 Ran out of disk space while updater copying files. Is this forum an appropriate place to ask for help? If so, I have data and can post it.
tangofoxtrot Posted February 4, 2018 Author Posted February 4, 2018 A small amount of additional info: I misunderstood the available space requirement and started the update with only 10GB of overhead using the command line: DCS_updater.exe update @openbeta. The process aborted during the update while copying Nevada/Clipmaps leaving zero available space on my ssd. I have the run log if its needed.
Frederf Posted February 5, 2018 Posted February 5, 2018 Once sufficient space is generated before trying again, perhaps a repair will fix the issue. Also it may be helpful to forcibly update to the same version explicitly in the command line or even explicitly update to the previous version and then again back to the latest version.
tangofoxtrot Posted February 5, 2018 Author Posted February 5, 2018 Two questions for anyone who knows the details of updating: 1. How much free space is required to do a repair of just the 2.2.0 open alpha? 2. When the update detects an out of space condition while copying clip maps does it abort without corrupting the existing open alpha and if so, is it possible to reclaim any space involved in the copying?
tangofoxtrot Posted February 5, 2018 Author Posted February 5, 2018 Frederf: thanks for the ideas - I'm trying to figure out how to make space. BTW, the abort seemed to leave the 1.5.8 Release untouched. It still works. I haven't tried to run 2.2.0 since the update was copying some of its files when it aborted and I'm worried that something vital has been corrupted.
QuiGon Posted February 5, 2018 Posted February 5, 2018 Two questions for anyone who knows the details of updating: 1. How much free space is required to do a repair of just the 2.2.0 open alpha? That entirely depends on the status of your DCS installation and how many files are missing/corrupted. The final size of 2.2 OA also depends on what modules you have, maps especially. Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing!
tangofoxtrot Posted February 5, 2018 Author Posted February 5, 2018 Thanks QuiGon for the response. I have the Nevada Test Area and Normandy maps, about 10 study grade acft modules, FC module and combined arms module. The problem I'm trying to solve is to get enough free space to run a repair. Without moving 1.5.8 to another drive I probably can't get more than 28GB of free space for the 2.2.0 repair - thus my interest in reclaiming "debris" produced by the aborted copy. I wasn't sure if this was the correct forum for getting help, so I didn't start my original post with a data dump. Since, as you suggest, details are important, I'll post some of it now. Here are my system stats: Processor: Intel® Core i7-4770K CPU @ 3.50 Ghz 3.50 GHz Installed RAM: 16.0 GB System Type: 64-bit operating system, x64-based processor GPU: Nvidia 770 OS: Windows 10 Home Version: 1709 OS Build 16299.192 Storage: C: SSD 238GB 227GB used (after moving some stuff) D: HD 931 GB 361GB used E: (Backup) HD 931 GB 361GB used DCS World: C: Release Version of 1.5.8 most recent updates C: 2.2.0 most recent version with Nevada and Normandy maps Disk Savvy Analysis of C: C: usage Major Consumers Program Files: 60% Eagle Dynamics 97.9% of 60% Program Files (x86) 14% 777 35% of 14% Steam 31% of 14% Users 12% Windows 9.5% I am hoping that the abort during copy hasn't corrupted anything vital and that I can recover by surgically removing debris from the copy. Whether this is possible, I leave to wiser minds and help would really be appreciated.
tangofoxtrot Posted February 5, 2018 Author Posted February 5, 2018 Sorry, the disk analysis formatting was screwed up. I'll try without tabs. Disk Savvy Analysis of C: C: usage Major Consumers Program Files: 60% Eagle Dynamics 97.9% of 60% Program Files (x86) 14% 777 35% of 14% Steam 31% of 14% Users 12% Windows 9.5%
Frederf Posted February 5, 2018 Posted February 5, 2018 If you need some overhead space to run the repair which is not needed after the repair consider moving a big folder like 777 to your HDD which has almost 600GB free and then back after the repair.
tangofoxtrot Posted February 6, 2018 Author Posted February 6, 2018 Thanks Frederf for taking a look. The data I posted is slightly dated, I've already moved 777 as you suggest along with everything else of any size. I'm really out of things to move and still I only have freed up a little over 27GB. Some additional factoids: both 1.5.8 and 2.2.0 seem to be intact - I've been able to run missions in both. The Normandy map seems a little jerky, but I have not tried to tweek the system settings. I'm thinking my attempt to update ended when the update process tried to make a copy of the Nevada map and aborted and except for the space occupied by the partial copy, everything else was ok. When all is said and done, all I want is a 2.5 with the Normandy, Nevada, and new Caucasus maps. I have no reason to keep a "final" version of the remains of an openbeta 2.5 derived from 1.5.8. So, maybe I should run what I currently have (without updating anything) and wait for stage 2 when I can dump 1.5.8 and update 2.2.0 to the final 2.5. Following this path will give me 100GB plus space for the final update. Does this seem like a reasonable path to you, or am I missing something obvious? Your advice would be welcome.
Recommended Posts