Project: 6013 (Run 0, Clone 188, Gen 121)

[dchamberlain]

I am having the same problem with a 6013. Here is a snippet of the log.

Code: Select all

[10:37:45] Folding@Home Gromacs SMP Core
[10:37:45] Version 2.19 (Mar 12, 2010)
[10:37:45] 
[10:37:45] Preparing to commence simulation
[10:37:45] - Looking at optimizations...
[10:37:45] - Created dyn
[10:37:45] - Files status OK
[10:37:46] - Expanded 977973 -> 10427873 (decompressed 1066.2 percent)
[10:37:46] Called DecompressByteArray: compressed_data_size=977973 data_size=10427873, decompressed_data_size=10427873 diff=0
[10:37:47] - Digital signature verified
[10:37:47] 
[10:37:47] Project: 6013 (Run 0, Clone 188, Gen 121)
[10:37:47] 
[10:37:47] Assembly optimizations on if available.
[10:37:47] Entering M.D.
[10:38:12] Completed 0 out of 250000 steps  (0%)
[11:53:20] Completed 2500 out of 250000 steps  (1%)
[13:08:29] Completed 5000 out of 250000 steps  (2%)
[14:23:37] Completed 7500 out of 250000 steps  (3%)

Folding@Home Client Shutdown at user request.

The machine is an Intel Quad Q6600 at 2.4 Ghz with 2 GB of RAM running Windows XP.

I observe that, when looking in the Task Manager, that all 4 cores are running about 50-75% in Kernel time. I think I've seen others mention this happening.

My question is, how do I "delete this work unit and move on"? I've tried deleting the queue.dat file and the work directory and restarting the client, I just get the same work unit over and over again. Is this counting as an unfinished work unit? If so, I won't be getting any bonus points soon.

David Chamberlain

[dchamberlain]

Update: I never did get an answer on how to delete the work unit and move on to another one. I deleted the queue.dat file and work directory about 5 times and got the same WU every time.

What I did was to put a rule into my DSL router to block access to the work server I was getting assigned to and getting that WU from. After the client attempted to access that work server 6 or 7 times, it gave up and moved to a different work server and I got a different WU.

Just for others information.

[PantherX]

Normally, these are the steps:
Step 1: Stop the Client using Crtl+C.
Step 2: Locate the folder where the SMP2 Client is installed.
Step 3: Select the Work Folder, Queue.dat File and delete them both.
Step 4: Start the Client and hopefully, you will be assigned a new WU.

What you have stated is my first time hearing. If you really want to make sure that everything is deleted, you can delete these files but when you start the Client, you have to reconfigure it again and it will download the Core again: (This is short of reinstalling the Client)
work folder
client.cfg
FahCore_a3
FAHlog
FAHlog-Prev
queue
unitinfo

If the above methods still doesn't work, nuke everything F@H related and do a fresh installation.

[bruce]

There's a new version of FahCore_a3 for Windows which will help this issue, though I don't know how much. You should get it if you delete fahCore_a3.exe as PantherX suggested.
\