• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Bigadv UNKOWN ERROR at 100% every time

jebo_4jc

[H]ard|DCer of the Month - April 2011
2FA
Joined
Apr 8, 2005
Messages
14,572
My server has lost five freaking consecutive bigadv units at 100%.

X5650
4GB DDR3
Windows Home Server

It turns in regular SMP2 units fine.

I deleted Work, queue.dat, unitinfo. No luck.
I nuked the install and tried again, no luck.

[13:49:58] Completed 247500 out of 250000 steps (99%)
[14:20:42] Completed 250000 out of 250000 steps (100%)
[14:20:56] DynamicWrapper: Finished Work Unit: sleep=10000
[14:21:06]
[14:21:06] Finished Work Unit:
[14:21:06] Could not allocate memory for arcfile
[14:21:06]
[14:21:06] Folding@home Core Shutdown: UNKNOWN_ERROR
[14:21:10] CoreStatus = 77 (119)
[14:21:10] Client-core communications error: ERROR 0x77
[14:21:10] Deleting current work unit & continuing...
[14:21:36] - Preparing to get new work unit...
[14:21:36] Cleaning up work directory
[14:21:36] + Attempting to get work packet
[14:21:36] Passkey found
[14:21:36] - Connecting to assignment server
[14:21:37] - Successful: assigned to (171.67.108.22).
[14:21:37] + News From Folding@Home: Welcome to Folding@Home
[14:21:37] Loaded queue successfully.
[14:22:31] + Closed connections
[14:22:36]
[14:22:36] + Processing work unit
[14:22:36] Core required: FahCore_a3.exe
[14:22:36] Core found.
[14:22:36] Working on queue slot 02 [August 19 14:22:36 UTC]
[14:22:36] + Working ...
[14:22:36]
[14:22:36] *------------------------------*
[14:22:36] Folding@Home Gromacs SMP Core
[14:22:36] Version 2.22 (Mar 12, 2010)
[14:22:36]
[14:22:36] Preparing to commence simulation
[14:22:36] - Looking at optimizations...
[14:22:36] - Created dyn
[14:22:36] - Files status OK
[14:22:42] - Expanded 26639765 -> 32993889 (decompressed 123.8 percent)
[14:22:42] Called DecompressByteArray: compressed_data_size=26639765 data_size=32993889, decompressed_data_size=32993889 diff=0
[14:22:42] - Digital signature verified
[14:22:42]
[14:22:42] Project: 2685 (Run 4, Clone 24, Gen 13)
[14:22:42]
[14:22:42] Assembly optimizations on if available.
[14:22:42] Entering M.D.
[14:22:51] Completed 0 out of 250000 steps (0%)
[14:52:07] Completed 2500 out of 250000 steps (1%)
[15:22:49] Completed 5000 out of 250000 steps (2%)
 
Not sure.... I'm running my first -bigadv on my WHS (3gb of RAM). To bad it's a 2684 :mad: but I'll see if it dumps with me too.

I'm wondering if it is a memory issue.
 
Not sure about admin rights.

I'm wondering the same thing about memory. O tried 6hb but saw some strange stability issues so I pulled one stick.

I'm thrilled you're testing this too.
Posted via [H] Mobile Device
 
Not sure about admin rights.

I'm wondering the same thing about memory. O tried 6hb but saw some strange stability issues so I pulled one stick.

I'm thrilled you're testing this too.
Posted via [H] Mobile Device

Well WHS is only 32 bit, so it can only see so much RAM. I wonder if WHS throws errors if you give it more than 3GB of RAM and run F@H.....

I've got 3x1gb sticks. I'm currently 3% though this frigg'n thing. So it willb e a while. Just run normal A3 till I get back with ya.
 
I had the same thing a bit ago - were these P2682's by chance? This was one of my logs:

Code:
[19:26:23] Completed 235000 out of 250000 steps  (94%)
[19:56:22] Completed 237500 out of 250000 steps  (95%)
[20:26:25] Completed 240000 out of 250000 steps  (96%)
[20:56:17] Completed 242500 out of 250000 steps  (97%)
[21:26:24] Completed 245000 out of 250000 steps  (98%)
[21:56:22] Completed 247500 out of 250000 steps  (99%)
[22:26:39] Completed 250000 out of 250000 steps  (100%)
[22:26:56] DynamicWrapper: Finished Work Unit: sleep=10000
[22:27:06] 
[22:27:06] Finished Work Unit:
[22:27:06] - Reading up to 52713120 from "work/wudata_04.trr": Read 52713120
[22:27:06] trr file hash check passed.
[22:27:06] Could not allocate memory for xtcfile
[22:27:06] 
[22:27:06] Folding@home Core Shutdown: UNKNOWN_ERROR
[22:27:10] CoreStatus = 77 (119)
[22:27:10] Client-core communications error: ERROR 0x77
[22:27:10] Deleting current work unit & continuing...
[22:27:56] - Preparing to get new work unit...
[22:27:56] Cleaning up work directory
[22:28:01] + Attempting to get work packet
[22:28:01] Passkey found
[22:28:01] - Connecting to assignment server

http://foldingforum.org/viewtopic.php?f=55&t=15620

The last few of these have processed fine for me, so i assumed the problem was fixed. Apparently not...
 
Well WHS is only 32 bit, so it can only see so much RAM. I wonder if WHS throws errors if you give it more than 3GB of RAM and run F@H.....

I've got 3x1gb sticks. I'm currently 3% though this frigg'n thing. So it willb e a while. Just run normal A3 till I get back with ya.
that's the plan sir. I've been tempted to try a swap to 3x1gb, so I'm very curious to hear your results.

I had the same thing a bit ago - were these P2682's by chance?
The last few of these have processed fine for me, so i assumed the problem was fixed. Apparently not...
Nope. The wu that died in my log above was an 85
 
Well..... that doesn't bode well.....

Do you all want me to run this awful thing though or do we have enough to say WHS & -bigadv is a nogo?
 
Well, it's not my CPU time being wasted, but I'm interested in the outcome. :)
 
Well, it's not my CPU time being wasted, but I'm interested in the outcome. :)

LOL....

We know he is going to run head first into a wall, but we are going to sit here and watch him do it anyways....

:p
 
I'm still not convinced this is a losing proposition (but I'm also the guy who wasted 5 WUs thinking "there must be something I'm missing).

Do me a favor and follow through so I'll know for sure
 
I'm sorry to hear about that. Losing a bigadv at any point after 60% is rough, but losing 5 in a row at 100% is devastating. I can't help you, but I hope you get your problem resolved.
 
Lol

I'm thinking it's a running out of memory issue, similar to the 82's. Maybe a few new gen's of some other family of big adv units are hitting the same problem on 3 gig systems?
Posted via [H] Mobile Device
 
It is probably worth posting on FF. The problem is that 32bit OSs and 3Gb memory is not the recommended setup for bigadv. Don't they make a 64 bit WHS?
 
It might be a bad wu. Is it always a 2685? In the past they had to delete wu that did the same thing.
 
System probably isn't using more than 500 megs, rite?
 
Yeah I have nothing special running. Whs doesn't use much.

64 bit whs "vail" is still in beta, not ready to subject my family pics and vids to it yet.
Posted via [H] Mobile Device
 
I knew about that in concept, but i didn't know it had to be enabled . that could actually explains a lot
Posted via [H] Mobile Device
 
I got a client core communication error last night, it died and dl-ed another one.... I think I'm switching back to normal WU.
 
Back
Top