Page 1 of 1

Project: 2498 (Run 123, Clone 14, Gen 2)

Posted: Fri May 22, 2009 12:22 pm
by el salmantino
Failed twice, once at 12% and again at 52% completion.
Log:

Folding@Home Gromacs Core
[11:34:20] Version 1.90 (March 8, 2006)
[11:34:20]
[11:34:20] Preparing to commence simulation
[11:34:20] - Ensuring status. Please wait.
[11:34:37] - Looking at optimizations...
[11:34:37] - Working with standard loops on this execution.
[11:34:37] - Previous termination of core was improper.
[11:34:37] - Files status OK
[11:34:47] - Expanded 2971395 -> 15085645 (decompressed 507.6 percent)
[11:34:48] - Checksums don't match (work/wudata_03.bed)
[11:34:49] - Starting from initial work packet
[11:34:49]
[11:34:49] Project: 2498 (Run 123, Clone 14, Gen 2)
[11:34:49]
[11:34:49] Entering M.D.
[11:34:57] Protein: Translocon_GLX2

Should I just try again?

Re: Project: 2498 (Run 123, Clone 14, Gen 2)

Posted: Fri May 22, 2009 8:06 pm
by susato
Estimado Salmantino, welcome to the forum!

From your user stats it looks as if you're folding Windows classic (single-processor) work units, unless this problem is happening on a machine that hasn't yet submitted a WU.

I'm not sure which version of the client and core you're using, but you might try trashing all copies of FahCore**.exe in your Folding directory, and allowing F@H to download another one. Also, check the version of the client that you have. The version number appears between the lines of ##### marks at the beginning of each FAHlog.txt. On the project's Downloads page, you will see the current client version for your equipment. Please consider upgrading if your client is out of date; new clients have better error handling than the older ones.

Since you've reached an early end at two different places in the WU, I think it's worth giving it another try, particularly if you have updated your client or core. If the third try fails, though, you should delete your queue.dat and change machineID in order to get a different WU.

Hoping that helps.

Re: Project: 2498 (Run 123, Clone 14, Gen 2)

Posted: Sat May 23, 2009 10:59 am
by el salmantino
That was the Windows console version, with -advmethods and requesting WU's with large memory usage.
It didn't report an EUE, so maybe the problem was that I closed the client right in the middle of a checkpoint. Can the WU get corrupted 'cause of that? I deleted the cores anyway, and checked that I have the last version
Thanks!