Bigadv problem?

lehmann

[H]ard|Gawd
Joined
Feb 8, 2005
Messages
1,362
[14:52:35] Completed 232500 out of 250000 steps (93%)
[15:24:54] Completed 235000 out of 250000 steps (94%)
[15:57:13] Completed 237500 out of 250000 steps (95%)
[16:29:31] Completed 240000 out of 250000 steps (96%)
[17:01:48] Completed 242500 out of 250000 steps (97%)
[17:34:06] Completed 245000 out of 250000 steps (98%)
[18:06:24] Completed 247500 out of 250000 steps (99%)
[18:08:33] - Autosending finished units... [September 14 18:08:33 UTC]
[18:08:33] Trying to send all finished work units
[18:08:33] + No unsent completed units remaining.
[18:08:33] - Autosend completed
[18:38:40] Completed 250000 out of 250000 steps (100%)
[18:38:52] DynamicWrapper: Finished Work Unit: sleep=10000
[18:39:02]
[18:39:02] Finished Work Unit:
[18:39:02] - Reading up to 52713120 from "work/wudata_02.trr": Read 52713120
[18:39:02] - Checksum of file (work/wudata_02.trr) read from disk doesn't match
[18:39:02]
[18:39:02] Folding@home Core Shutdown: FILE_IO_ERROR
[18:39:05] CoreStatus = 75 (117)
[18:39:05] Error opening or reading from a file.
[18:39:05] Deleting current work unit & continuing...
[18:39:25] Trying to send all finished work units
[18:39:25] + No unsent completed units remaining.
[18:39:25] - Preparing to get new work unit...
[18:39:25] Cleaning up work directory
[18:39:25] + Attempting to get work packet
[18:39:25] Passkey found
[18:39:25] - Will indicate memory of 4087 MB
[18:39:25] - Connecting to assignment server
[18:39:25] Connecting to http://assign.stanford.edu:8080/
[18:39:26] Posted data.
[18:39:26] Initial: 40AB; - Successful: assigned to (171.64.65.54).
[18:39:26] + News From Folding@Home: Welcome to Folding@Home
[18:39:26] Loaded queue successfully.
[18:39:26] Sent data
[18:39:26] Connecting to http://171.64.65.54:8080/
[18:39:26] Posted data.
[18:39:26] Initial: 0000; - Receiving payload (expected size: 1765577)
[18:39:29] - Downloaded at ~574 kB/s
[18:39:29] - Averaged speed for that direction ~1941 kB/s
 
Happened to me once or twice in the past. Never figured it out. Please tell me this wasn't a P2684... :(
 
52mb so not big adv. The other giveaway is the TPF.

I have had issue before. No way to figure it out.
 
52mb so not big adv. The other giveaway is the TPF.

I have had issue before. No way to figure it out.
Yeah, you're right, didn't bother looking at the TPF. Well, at least it wasn't a -bigadv. That would have been much worse....

Is your disk subsystem operating perfectly, lehmann?
 
Its a 2686 32 minute fram times. where do you see the mb's. disk seems to be working. is there any way to check it? everything i run is fairly new not that it matters
 
Last edited:
I guess your hardware should be OK if it's new and not giving you other issues. Which WU was it?
 
Here's the key bit:

[18:39:02] Finished Work Unit:
[18:39:02] - Reading up to 52713120 from "work/wudata_02.trr": Read 52713120
[18:39:02] - Checksum of file (work/wudata_02.trr) read from disk doesn't match
[18:39:02]
[18:39:02] Folding@home Core Shutdown: FILE_IO_ERROR
[18:39:05] CoreStatus = 75 (117)
[18:39:05] Error opening or reading from a file.
[18:39:05] Deleting current work unit & continuing...

My last bigadv was around 100MB, so it looks like it was corrupted halfway through? Never had this happen personally.
 
I saw that on a few a while ago. I think it was the 2682s before they switch to 2692. Haven't seen one do that in a while though. They were also on an smp 16 machine.
 
I got a couple of 2682s on my SR-2 and they refused to even start. Never had a WU complete and then fail with a read/checksum error.
 
I hope this doesn't mean there are bad WUs in the wild...
 
52mb so not big adv. The other giveaway is the TPF.

I have had issue before. No way to figure it out.

I believe i've had 2 bigadv's in the past that were right around the 52 or 56mb mark when it successfully uploaded. If my memory serves me correctly, one was a 2692 and the other may have been a 2686. Those TPF's don't look off to me as it looks like a non 2684 bigadv running on a very fast Bloomfield.
 
Its a lynnfield. 860@4.0 my 920@4.0 is minute faster.

Damn........I forgot about the "other" Core i7's. Those are some incredible times though as a 2686 has a TPF of 36 minutes on folding1. 2685's have a TPF of 39 minutes, and of course 2684's have a TPF of 51-52 minutes on the Bloomfield.
 
here's my 920 doing a 2686, [10:42:38] Project: 2686 (Run 8, Clone 3, Gen 16)
[10:42:38]
[10:42:38] Assembly optimizations on if available.
[10:42:38] Entering M.D.
[10:42:46] Completed 0 out of 250000 steps (0%)
[11:13:47] Completed 2500 out of 250000 steps (1%)
[11:26:41] - Autosending finished units... [September 15 11:26:41 UTC]
[11:26:41] Trying to send all finished work units
[11:26:41] + No unsent completed units remaining.
[11:26:41] - Autosend completed
[11:44:46] Completed 5000 out of 250000 steps (2%)
[12:15:45] Completed 7500 out of 250000 steps (3%)
[12:46:44] Completed 10000 out of 250000 steps (4%)
[13:17:44] Completed 12500 out of 250000 steps (5%)
[13:48:44] Completed 15000 out of 250000 steps (6%)
 
Last edited:
here's my 920 doing a 2684, [10:42:38] Project: 2686 (Run 8, Clone 3, Gen 16)
[10:42:38]
[10:42:38] Assembly optimizations on if available.
[10:42:38] Entering M.D.
[10:42:46] Completed 0 out of 250000 steps (0%)
[11:13:47] Completed 2500 out of 250000 steps (1%)
[11:26:41] - Autosending finished units... [September 15 11:26:41 UTC]
[11:26:41] Trying to send all finished work units
[11:26:41] + No unsent completed units remaining.
[11:26:41] - Autosend completed
[11:44:46] Completed 5000 out of 250000 steps (2%)
[12:15:45] Completed 7500 out of 250000 steps (3%)
[12:46:44] Completed 10000 out of 250000 steps (4%)
[13:17:44] Completed 12500 out of 250000 steps (5%)
[13:48:44] Completed 15000 out of 250000 steps (6%)


How come your log file says 2686 then? :D

I originally looked at those and was gonna ask you what your ancient chinese secret was considering that my Gulftown can't hit those TPF's on those pesky 2684's.
 
typo! fixed i must have 2684 fears on the brain?

We all do man. Nothing is more of a bummer than getting those pesky things that take almost 4 days to complete on a i7. I still prefer them to the even peskier 6701/6702's though.
 
Back
Top