Keep getting Unknown error with foldy

Associate
Joined
5 Aug 2003
Posts
1,145
Location
Lazytown
Hi all,

Keep getting this error

[06:35:06] Folding@home Core Shutdown: FINISHED_UNIT
[06:35:06]
[06:35:06] Folding@home Core Shutdown: FINISHED_UNIT
[06:35:10] CoreStatus = 64 (100)
[06:35:10] Sending work to server


[06:35:10] + Attempting to send results
[06:36:15] + Results successfully sent
[06:36:15] Thank you for your contribution to Folding@Home.
[06:36:15] + Number of Units Completed: 124

[06:38:19] - Preparing to get new work unit...
[06:38:19] + Attempting to get work packet
[06:38:19] - Connecting to assignment server
[06:38:20] - Successful: assigned to (171.64.65.56).
[06:38:20] + News From Folding@Home: Welcome to Folding@Home
[06:38:20] Loaded queue successfully.
[06:38:37] + Closed connections
[06:38:37]
[06:38:37] + Processing work unit
[06:38:37] Core required: FahCore_a1.exe
[06:38:37] Core found.
[06:38:37] Working on Unit 04 [July 3 06:38:37]
[06:38:37] + Working ...
[06:38:37]
[06:38:37] *------------------------------*
[06:38:37] Folding@Home Gromacs SMP Core
[06:38:37] Version 1.74 (March 10, 2007)
[06:38:37]
[06:38:37] Preparing to commence simulation
[06:38:37] - Ensuring status. Please wait.
[06:38:41] - Starting from initial work packet
[06:38:41]
[06:38:41] Project: 2609 (Run 0, Clone 385, Gen 0)
[06:38:41]
[06:38:42] Assembly optimizations on if available.
[06:38:42] Entering M.D.
[06:39:04] 1 percent)
[06:39:04] - Starting from initial work packet
[06:39:04]
[06:39:04] Project: 2609 (Run 0, Clone 385, Gen 0)
[06:39:04]
[06:39:04] Entering M.D.
[06:39:11] Rejecting checkpoint
[06:39:12] Gromacs error.
[06:39:12]
[06:39:12] Folding@home Core Shutdown: UNKNOWN_ERROR
[06:39:12]
[06:39:12] Folding@home Core Shutdown: UNKNOWN_ERROR

Folding@Home Client Shutdown at user request.

Folding@Home Client Shutdown.

With my quad core and don't know what it means, it wasn't shut down on a user request unlike what it says.

Any ideas Babyface UK
 
Based on the "Gromacs error" bit a quick look around suggests the client can open the core for use or something. This could be a permissions problem, disk access or disk full problem.

The log also says it is rejecting the checkpoint. This sounds like possible corruption either with the checkpoint itself or the core. Is your quad overclocked at all? The OC may be iffy or your memory is unstable.

Probably the easiest thing you can try is to completely nuke the client and and work units [assuming it isn't in the middle of one] and then reinstall.
 
looks like a job for uncle - Oh uncle F where art thou?

Edit: or as SB rightly said standard IT protocal 1 - turn it off and switch it on again :D
 
Last edited:
SiriusB said:
Based on the "Gromacs error" bit a quick look around suggests the client can open the core for use or something. This could be a permissions problem, disk access or disk full problem.

The log also says it is rejecting the checkpoint. This sounds like possible corruption either with the checkpoint itself or the core. Is your quad overclocked at all? The OC may be iffy or your memory is unstable.

Probably the easiest thing you can try is to completely nuke the client and and work units [assuming it isn't in the middle of one] and then reinstall.

"nuked Client " a week ago with the same results this week ( Hence why me output has dived ) but yes its overclocked so calmed it down a bit and left it running - but i won't be near it for another week so will have to hope it works.

Babyface
 
Back
Top Bottom