Several work units have terminated early for me since I moved folding to a flash drive. This may be coincidental, of course. I was wondering if others had seen similar results?
Here is an example what the log says:
[12:09:59] Folding@Home Gromacs Core
[12:09:59] Version 1.80 (March 16, 2005)
[12:09:59]
[12:09:59] Preparing to commence simulation
[12:09:59] - Looking at optimizations...
[12:09:59] - Created dyn
[12:09:59] - Files status OK
[12:09:59] - Expanded 135940 -> 650585 (decompressed 478.5 percent)
[12:09:59] - Starting from initial work packet
[12:09:59]
[12:09:59] Project: 1602 (Run 4, Clone 79, Gen 9)
[12:09:59]
[12:09:59] Assembly optimizations on if available.
[12:09:59] Entering M.D.
[12:10:05] Protein: p1602_NTL4MUreGS
[12:10:05]
[12:10:05] Writing local files
[12:10:05] Testing CPU type...
[12:10:05] Done testing.
[12:10:05] Extra AltiVec boost OK.
[12:10:06] Writing local files
[12:10:06] Completed 0 out of 1000000 steps (0)
[12:11:54] Quit 101 - Fatal error:
[12:11:54] Step 2467, time 4.934 (ps) LINCS WARNING
[12:11:54] relative constraint deviation after LINCS:
[12:11:54] max 0.001621 (between atoms 768 and 770) rms 0.000074
[12:11:54]
[12:11:54] Simulation instability has been encountered. The run has entered a
[12:11:54] state from which no further progress can be made.
[12:11:54] This may be the correct result of the simulation, however if you
[12:11:54] often see other project units terminating early like this
[12:11:54] too, you may wish to check the stability of your computer (issues
[12:11:54] such as high temperature, overclocking, etc.).
[12:11:54] Going to send back what have done.
[12:11:54] logfile size: 7884
[12:11:54] - Writing 8562 bytes of core data to disk...
[12:11:54] ... Done.
[12:11:58]
[12:11:58] Folding@home Core Shutdown: EARLY_UNIT_END
[12:12:07] CoreStatus = 72 (114)
[12:12:07] Sending work to server
Any info would be appreciated
Here is an example what the log says:
[12:09:59] Folding@Home Gromacs Core
[12:09:59] Version 1.80 (March 16, 2005)
[12:09:59]
[12:09:59] Preparing to commence simulation
[12:09:59] - Looking at optimizations...
[12:09:59] - Created dyn
[12:09:59] - Files status OK
[12:09:59] - Expanded 135940 -> 650585 (decompressed 478.5 percent)
[12:09:59] - Starting from initial work packet
[12:09:59]
[12:09:59] Project: 1602 (Run 4, Clone 79, Gen 9)
[12:09:59]
[12:09:59] Assembly optimizations on if available.
[12:09:59] Entering M.D.
[12:10:05] Protein: p1602_NTL4MUreGS
[12:10:05]
[12:10:05] Writing local files
[12:10:05] Testing CPU type...
[12:10:05] Done testing.
[12:10:05] Extra AltiVec boost OK.
[12:10:06] Writing local files
[12:10:06] Completed 0 out of 1000000 steps (0)
[12:11:54] Quit 101 - Fatal error:
[12:11:54] Step 2467, time 4.934 (ps) LINCS WARNING
[12:11:54] relative constraint deviation after LINCS:
[12:11:54] max 0.001621 (between atoms 768 and 770) rms 0.000074
[12:11:54]
[12:11:54] Simulation instability has been encountered. The run has entered a
[12:11:54] state from which no further progress can be made.
[12:11:54] This may be the correct result of the simulation, however if you
[12:11:54] often see other project units terminating early like this
[12:11:54] too, you may wish to check the stability of your computer (issues
[12:11:54] such as high temperature, overclocking, etc.).
[12:11:54] Going to send back what have done.
[12:11:54] logfile size: 7884
[12:11:54] - Writing 8562 bytes of core data to disk...
[12:11:54] ... Done.
[12:11:58]
[12:11:58] Folding@home Core Shutdown: EARLY_UNIT_END
[12:12:07] CoreStatus = 72 (114)
[12:12:07] Sending work to server
Any info would be appreciated