the error log you posted above hints that the hard disk size was too small for the case you were running.
Looking at your case, it is pretty obvious that the case should not be too large to be run on an instance with a couple of hundred GB of hard disk space available.
I was checking it with a newer version of the solver which we will roll out soon (within the next weeks) and there the problem disappears - you might have run into a case with a particularly poor disk space handling, which was resolved in a later release.
Until the new version is rolled out to everyone, you could improve the situation by reducing the “number of parallel processes”, I saw you were for example 8 on a 16-core instance (which is the default setup and usually the fastest). Using 4 instead of 8 will not reduce your run time too drastically (since we will still use all the processors available, but then more with shared memory parallelism and less with MPI parallelization), but the disk utilization will be reduced significantly in your case.
My guess is that this odd behavior is caused by the remote force loads you are using. You might also want to switch to “undeformable” remote force which should also fix the issue.
Edit: I just restarted your last run with the new solver version and it finished successfully: https://www.simscale.com/workbench/?pid=6320004496950706254&mi=run%3A2%2Csimulation%3A7&mt=SIMULATION_RUN
If you want I can manually activate the new version for you (everything should already work, but be aware that the testing is not finalized yet).