Spin-up has been stopped since my server error! how to right this serious mistake?

[LIN]

Hello,@oleson . I ran the spin up for long days with "./xmlchange NTASKS=46", and when I thought it's almost done, my school server has some problems lead to the stopped of my docker. And I was stupid to run the "./case.submit" when I restart docker. I found the first file of "BGC_QTP.....2000-01-01-0000.nc" had been overwritten,so I stopped the program immediately and downloaded the file of 2020 and 2040. The records are still in the original log file as follows blue box in the picture.

One idea I have now is to start over with the same spin up, download it after finishing the first file, and replace the first file in that directory. And then start again from the original log file.

I don't know if it works, and I don't know how to restart the spin up process. And opening "continue run inside env run does not work. No rpointer file is reported.

 

[slevis]

Before starting over, I suggest trying the CONTINUE option again. You're missing the rpointer files for some reason, but you can make new ones manually. You probably need these four files (or the first three if you are not using the river model):
rpointer.atm
rpointer.cpl
rpointer.lnd
rpointer.rof

Each file should contain the name of the last corresponding restart file as follows. Here I share an example from one of my cases:
i2000sp_4x5.datm.r.2000-01-03-00000.nc
i2000sp_4x5.cpl.r.2000-01-03-00000.nc
./i2000sp_4x5.clm2.r.2000-01-03-00000.nc
./i2000sp_4x5.mosart.r.2000-01-03-00000.nc

If the CONTINUE option still fails for some reason, then you should alternatively be able to do a startup run with user_nl_clm containing
finidat = 'the last clm restart file'