Why the same WU Twice?

Moderators: Site Moderators, FAHC Science Team

*hondo*
Posts: 102
Joined: Sat Mar 08, 2008 9:50 am
Hardware configuration: Geoforce 250 GTS Active for F@H

4 Core Intel not used at all for F@H
Location: England UK

Why the same WU Twice?

Post by *hondo* »

Could someone please advise?

And @ Stanford if I must do the same WU twice I'd be very grateful of being issued with 1325 points twice too.
BTW the set up of the PC is no different to what its been for weeks, the cooling is cleared of any dust etc weekly, no heat alerts have been issued whatsoever.


I knew for a fact at 9.15am UK time this morning that either the FAH Stats page was incorrect or alternatively a problem had occurred to a WU, I now can identify where things went pear shape.

Although for the first time in a long time I left the PC on last night Folding an SMP core, albeit I had stopped my GPU Folding prior to going to bed last night.

At the time the GPU WU was 97% complete on WU P: 6803 (Run 15, Clone 13, Gen 967)
@ [07:05:04] This morning I rebooted the PC to restart the above WU.

@ [07:07:59] I realised I’d dropped the Core usage % rate by 5% last night because it was slowing up other things I was doing at that time =

[07:07:59] + Restarting core (settings changed) Back to 100%

@ [07:12:25] The WU was completed & as far as I was concerned @ the time it was also returned


@ 9.00 Am I realised a WU was missing only one of two showed in the FAH Stats

Having now looked @ the Log @ [07:12:39] An error occurred which reads as follows [07:12:39] Folding@home Core Shutdown: FILE_IO_ERROR: Problem opening, closing or deleting a file
[07:12:41] CoreStatus = 75 (117)
[07:12:41] Error opening or reading from a file.
[07:12:41] Deleting current work unit & continuing...

The above is followed with the download of exactly the same WU again
[07:12:52] Project: 6803 (Run 15, Clone 13, Gen 967)

[07:12:52] Project: 6803 (Run 15, Clone 13, Gen 967)
[07:12:52]
[07:12:52] Assembly optimizations on if available.
[07:12:52] Entering M.D.
[07:12:54] Tpr hash work/wudata_08.tpr: 1509178850 3427663216 3663224481 3243715519 1447070008
[07:12:54] calling fah_main gpuDeviceId=0
[07:12:54] Working on ALZHEIMER'S DISEASE AMYLOID
[07:12:54] Client config found, loading data.
[07:12:54] Starting GUI Server
[07:13:55] Setting checkpoint frequency: 500000
[07:13:55] Completed 3 out of 50000000 steps (0%).
[07:14:59] Completed 500000 out of 50000000 steps (1%).
[07:16:04] Completed 1000000 out of 50000000 steps (2%).
[07:17:08] Completed 1500000 out of 50000000 steps (3%).
[07:18:13] Completed 2000000 out of 50000000 steps (4%).
[07:19:17] Completed 2500000 out of 50000000 steps (5%).

Etc

Code: Select all

The start of Wednesday


Launch directory: C:\Documents and Settings\hondo\Application Data\Folding@home-gpu


[07:05:04] - Ask before connecting: No
[07:05:04] - User name: *hondo* (Team 51078)
[07:05:04] - User ID: xxxxxxxxxxxxxxxxxx
[07:05:04] - Machine ID: 2
[07:05:04] 
[07:05:04] Gpu type=3 species=20.
[07:05:04] Loaded queue successfully.
[07:05:04] Initialization complete
[07:05:04] 
[07:05:04] + Processing work unit
[07:05:04] Core required: FahCore_15.exe
[07:05:04] Core found.
[07:05:04] Working on queue slot 07 [February 8 07:05:04 UTC]
[07:05:04] + Working ...
[07:05:05] 
[07:05:05] *------------------------------*
[07:05:05] Folding@Home GPU Core
[07:05:05] Version                2.20 (Tue Aug 2 12:06:37 PDT 2011)
[07:05:05] Build host             SimbiosNvdWin7
[07:05:05] Board Type             NVIDIA/CUDA
[07:05:05] Core                   15
[07:05:05] 
[07:05:05] Window's signal control handler registered.
[07:05:05] Preparing to commence simulation
[07:05:06] - Looking at optimizations...
[07:05:06] - Files status OK
[07:05:06] sizeof(CORE_PACKET_HDR) = 512 file=<>
[07:05:06] - Expanded 44959 -> 170279 (decompressed 378.7 percent)
[07:05:06] Called DecompressByteArray: compressed_data_size=44959 data_size=170279, decompressed_data_size=170279 diff=0
[07:05:06] - Digital signature verified
[07:05:06] 
[07:05:06] Project: 6803 (Run 15, Clone 13, Gen 967)
[07:05:06] 
[07:05:06] Assembly optimizations on if available.
[07:05:06] Entering M.D.
[07:05:08] Will resume from checkpoint file work/wudata_07.ckp
[07:05:08] Tpr hash work/wudata_07.tpr:  1509178850 3427663216 3663224481 3243715519 1447070008
[07:05:08] calling fah_main gpuDeviceId=0
[07:05:08] Working on ALZHEIMER'S DISEASE AMYLOID
[07:05:08] Client config found, loading data.
[07:05:08] Starting GUI Server
[07:06:11] Resuming from checkpoint
[07:06:11] fcCheckPointResume: retreived and current tpr file hash:
[07:06:11]    0   1509178850   1509178850
[07:06:11]    1   3427663216   3427663216
[07:06:11]    2   3663224481   3663224481
[07:06:11]    3   3243715519   3243715519
[07:06:11]    4   1447070008   1447070008
[07:06:11] fcCheckPointResume: file hashes same.
[07:06:11] fcCheckPointResume: state restored.
[07:06:11] fcCheckPointResume: name work/wudata_07.log Verified work/wudata_07.log
[07:06:11] fcCheckPointResume: name work/wudata_07.trr Verified work/wudata_07.trr
[07:06:11] fcCheckPointResume: name work/wudata_07.xtc Verified work/wudata_07.xtc
[07:06:11] fcCheckPointResume: name work/wudata_07.edr Verified work/wudata_07.edr
[07:06:11] fcCheckPointResume: state restored 2
[07:06:11] Resumed from checkpoint
[07:06:11] Setting checkpoint frequency: 500000
[07:06:11] Completed  48000001 out of 50000000 steps (96%).
[07:07:19] Completed  48500000 out of 50000000 steps (97%).
[07:07:59] CoreStatus = 62 (98)
[07:07:59] + Restarting core (settings changed) 
[07:07:59] 
[07:07:59] + Processing work unit
[07:07:59] Core required: FahCore_15.exe
[07:07:59] Core found.
[07:07:59] Working on queue slot 07 [February 8 07:07:59 UTC]
[07:07:59] + Working ...
[07:07:59] 
[07:07:59] *------------------------------*
[07:07:59] Folding@Home GPU Core
[07:07:59] Version                2.20 (Tue Aug 2 12:06:37 PDT 2011)
[07:07:59] Build host             SimbiosNvdWin7
[07:07:59] Board Type             NVIDIA/CUDA
[07:07:59] Core                   15
[07:07:59] 
[07:07:59] Window's signal control handler registered.
[07:07:59] Preparing to commence simulation
[07:07:59] - Ensuring status. Please wait.
[07:08:09] - Looking at optimizations...
[07:08:09] - Not checking prior termination.
[07:08:09] sizeof(CORE_PACKET_HDR) = 512 file=<>
[07:08:09] - Expanded 44959 -> 170279 (decompressed 378.7 percent)
[07:08:09] Called DecompressByteArray: compressed_data_size=44959 data_size=170279, decompressed_data_size=170279 diff=0
[07:08:09] - Digital signature verified
[07:08:09] 
[07:08:09] Project: 6803 (Run 15, Clone 13, Gen 967)
[07:08:09] 
[07:08:09] Assembly optimizations on if available.
[07:08:09] Entering M.D.
[07:08:11] Will resume from checkpoint file work/wudata_07.ckp
[07:08:11] Tpr hash work/wudata_07.tpr:  1509178850 3427663216 3663224481 3243715519 1447070008
[07:08:11] calling fah_main gpuDeviceId=0
[07:08:11] Working on ALZHEIMER'S DISEASE AMYLOID
[07:08:11] Client config found, loading data.
[07:08:11] Starting GUI Server
[07:09:12] Resuming from checkpoint
[07:09:12] fcCheckPointResume: retreived and current tpr file hash:
[07:09:12]    0   1509178850   1509178850
[07:09:12]    1   3427663216   3427663216
[07:09:12]    2   3663224481   3663224481
[07:09:12]    3   3243715519   3243715519
[07:09:12]    4   1447070008   1447070008
[07:09:12] fcCheckPointResume: file hashes same.
[07:09:12] fcCheckPointResume: state restored.
[07:09:12] fcCheckPointResume: name work/wudata_07.log Verified work/wudata_07.log
[07:09:12] fcCheckPointResume: name work/wudata_07.trr Verified work/wudata_07.trr
[07:09:12] fcCheckPointResume: name work/wudata_07.xtc Verified work/wudata_07.xtc
[07:09:12] fcCheckPointResume: name work/wudata_07.edr Verified work/wudata_07.edr
[07:09:12] fcCheckPointResume: state restored 2
[07:09:12] Resumed from checkpoint
[07:09:12] Setting checkpoint frequency: 500000
[07:09:12] Completed  48500001 out of 50000000 steps (97%).
[07:10:16] Completed  49000000 out of 50000000 steps (98%).
[07:11:21] Completed  49500000 out of 50000000 steps (99%).
[07:12:25] Completed  50000000 out of 50000000 steps (100%).
[07:12:25] Finished fah_main status=0
[07:12:25] Successful run
[07:12:25] DynamicWrapper: Finished Work Unit: sleep=10000
[07:12:35] Reserved 244460 bytes for xtc file; Cosm status=0
[07:12:35] Allocated 244460 bytes for xtc file
[07:12:35] - Reading up to 244460 from "work/wudata_07.xtc": Read 244460
[07:12:35] Read 244460 bytes from xtc file; available packet space=786186004
[07:12:35] xtc file hash check passed.
[07:12:35] Reserved 76080 76080 786186004 bytes for arc file=<work/wudata_07.trr> Cosm status=0
[07:12:35] Allocated 76080 bytes for arc file
[07:12:35] - Reading up to 76080 from "work/wudata_07.trr": Read 76080
[07:12:35] Read 76080 bytes from arc file; available packet space=786109924
[07:12:35] trr file hash check passed.
[07:12:35] Allocated 544 bytes for edr file
[07:12:35] Read bedfile
[07:12:35] edr file hash check passed.
[07:12:35] Allocated 37021 bytes for logfile
[07:12:35] Read logfile
[07:12:35] GuardedRun: success in DynamicWrapper
[07:12:35] GuardedRun: done
[07:12:35] Run: GuardedRun completed.
[07:12:39] + Opened results file
[07:12:39] - Writing 358617 bytes of core data to disk...
[07:12:39] Done: 358105 -> 326233 (compressed to 91.0 percent)
[07:12:39]   ... Done.
[07:12:39] DeleteFrameFiles: successfully deleted file=work/wudata_07.ckp
[07:12:39] Shutting down core Problem in delete frame file
[07:12:39] Shutting down core 
[07:12:39] 
[07:12:39] Folding@home Core Shutdown: FILE_IO_ERROR: Problem opening, closing or deleting a file 
[07:12:41] CoreStatus = 75 (117)
[07:12:41] Error opening or reading from a file.
[07:12:41] Deleting current work unit & continuing...
[07:12:45] - Preparing to get new work unit...
[07:12:45] Cleaning up work directory
[07:12:45] + Attempting to get work packet
[07:12:45] Passkey found
[07:12:45] Gpu type=3 species=20.
[07:12:45] - Connecting to assignment server
[07:12:46] - Successful: assigned to (171.67.108.54).
[07:12:46] + News From Folding@Home: Welcome to Folding@Home
[07:12:46] Loaded queue successfully.
[07:12:46] Gpu type=3 species=20.
[07:12:47] + Closed connections
[07:12:52] 
[07:12:52] + Processing work unit
[07:12:52] Core required: FahCore_15.exe
[07:12:52] Core found.
[07:12:52] Working on queue slot 08 [February 8 07:12:52 UTC]
[07:12:52] + Working ...
[07:12:52] 
[07:12:52] *------------------------------*
[07:12:52] Folding@Home GPU Core
[07:12:52] Version                2.20 (Tue Aug 2 12:06:37 PDT 2011)
[07:12:52] Build host             SimbiosNvdWin7
[07:12:52] Board Type             NVIDIA/CUDA
[07:12:52] Core                   15
[07:12:52] 
[07:12:52] Window's signal control handler registered.
[07:12:52] Preparing to commence simulation
[07:12:52] - Looking at optimizations...
[07:12:52] DeleteFrameFiles: successfully deleted file=work/wudata_08.ckp
[07:12:52] - Created dyn
[07:12:52] - Files status OK
[07:12:52] sizeof(CORE_PACKET_HDR) = 512 file=<>
[07:12:52] - Expanded 44959 -> 170279 (decompressed 378.7 percent)
[07:12:52] Called DecompressByteArray: compressed_data_size=44959 data_size=170279, decompressed_data_size=170279 diff=0
[07:12:52] - Digital signature verified
[07:12:52] 
[07:12:52] Project: 6803 (Run 15, Clone 13, Gen 967)
[07:12:52] 
[07:12:52] Assembly optimizations on if available.
[07:12:52] Entering M.D.
[07:12:54] Tpr hash work/wudata_08.tpr:  1509178850 3427663216 3663224481 3243715519 1447070008
[07:12:54] calling fah_main gpuDeviceId=0
[07:12:54] Working on ALZHEIMER'S DISEASE AMYLOID
[07:12:54] Client config found, loading data.
[07:12:54] Starting GUI Server
[07:13:55] Setting checkpoint frequency: 500000
[07:13:55] Completed         3 out of 50000000 steps (0%).
[07:14:59] Completed    500000 out of 50000000 steps (1%).
[07:16:04] Completed   1000000 out of 50000000 steps (2%).
[07:17:08] Completed   1500000 out of 50000000 steps (3%).
[07:18:13] Completed   2000000 out of 50000000 steps (4%).
[07:19:17] Completed   2500000 out of 50000000 steps (5%).
[07:20:21] Completed   3000000 out of 50000000 steps (6%).
[07:21:26] Completed   3500000 out of 50000000 steps (7%).
[07:22:30] Completed   4000000 out of 50000000 steps (8%).
[07:23:35] Completed   4500000 out of 50000000 steps (9%).
[07:24:39] Completed   5000000 out of 50000000 steps (10%).
[07:25:44] Completed   5500000 out of 50000000 steps (11%).
[07:26:49] Completed   6000000 out of 50000000 steps (12%).
[07:27:53] Completed   6500000 out of 50000000 steps (13%).
[07:28:57] Completed   7000000 out of 50000000 steps (14%).
[07:30:01] Completed   7500000 out of 50000000 steps (15%).
[07:31:06] Completed   8000000 out of 50000000 steps (16%).
[07:32:10] Completed   8500000 out of 50000000 steps (17%).
[07:33:14] Completed   9000000 out of 50000000 steps (18%).
[07:34:19] Completed   9500000 out of 50000000 steps (19%).
[07:35:23] Completed  10000000 out of 50000000 steps (20%).
[07:36:27] Completed  10500000 out of 50000000 steps (21%).
[07:37:31] Completed  11000000 out of 50000000 steps (22%).
[07:38:36] Completed  11500000 out of 50000000 steps (23%).
[07:39:40] Completed  12000000 out of 50000000 steps (24%).
[07:40:44] Completed  12500000 out of 50000000 steps (25%).
[07:41:49] Completed  13000000 out of 50000000 steps (26%).
[07:42:53] Completed  13500000 out of 50000000 steps (27%).
[07:43:58] Completed  14000000 out of 50000000 steps (28%).
[07:45:02] Completed  14500000 out of 50000000 steps (29%).
[07:46:06] Completed  15000000 out of 50000000 steps (30%).
[07:47:10] Completed  15500000 out of 50000000 steps (31%).
[07:48:15] Completed  16000000 out of 50000000 steps (32%).
[07:49:20] Completed  16500000 out of 50000000 steps (33%).
[07:50:24] Completed  17000000 out of 50000000 steps (34%).
[07:51:28] Completed  17500000 out of 50000000 steps (35%).
[07:52:33] Completed  18000000 out of 50000000 steps (36%).
[07:53:37] Completed  18500000 out of 50000000 steps (37%).
[07:54:41] Completed  19000000 out of 50000000 steps (38%).
[07:55:46] Completed  19500000 out of 50000000 steps (39%).
[07:56:50] Completed  20000000 out of 50000000 steps (40%).
[07:57:56] Completed  20500000 out of 50000000 steps (41%).
[07:59:02] Completed  21000000 out of 50000000 steps (42%).
[08:00:07] Completed  21500000 out of 50000000 steps (43%).
[08:01:11] Completed  22000000 out of 50000000 steps (44%).
[08:02:15] Completed  22500000 out of 50000000 steps (45%).
[08:03:19] Completed  23000000 out of 50000000 steps (46%).
[08:04:24] Completed  23500000 out of 50000000 steps (47%).
[08:05:28] Completed  24000000 out of 50000000 steps (48%).
[08:06:32] Completed  24500000 out of 50000000 steps (49%).
[08:07:37] Completed  25000000 out of 50000000 steps (50%).
[08:08:42] Completed  25500000 out of 50000000 steps (51%).
[08:09:47] Completed  26000000 out of 50000000 steps (52%).
[08:10:51] Completed  26500000 out of 50000000 steps (53%).
[08:11:56] Completed  27000000 out of 50000000 steps (54%).
[08:13:00] Completed  27500000 out of 50000000 steps (55%).
new08
Posts: 188
Joined: Fri Jan 04, 2008 11:02 pm
Hardware configuration: Hewlett-Packard 1494 Win10 Build 1836
GeForce [MSI] GTX 950
Runs F@H Ver7.6.21
[As of Jan 2021]
Location: England

Re: Why the same WU Twice?

Post by new08 »

I can't answer your main question directly, but I have had the same result on IO error [normally attributed to faulty o/clocking] on a recent unit. The bad news for me was it too 2 hours per step [ not 1 min] and over a week to complete before downing itself.
Still waiting to see a result on that- but luckily I didn't get it back fora re-run!
viewtopic.php?f=19&t=20712
However, from experience- it's not unusual for a faulty result to be re-run. This means, I suppose that it doesn't need immediate re-issue by the server and can help show up any repeat problems in coding etc.
Also- if the user has made an error [and who hasn't] in handling the client[s] or system management -then it's seems right to give them another shot at it. The user knows what's been done and can correct this quickly locally- reducing overheads to the work servers.
That's my personal take on some of your questions.
No doubt others will pile in ... :)
Image
7im
Posts: 10189
Joined: Thu Nov 29, 2007 4:30 pm
Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
Location: Arizona
Contact:

Re: Why the same WU Twice?

Post by 7im »

The log shows the work unit was deleted, so it was not completed. No returned data, no points.

When the client requests a work unit without returning the previouis WU, it sends the same WU again.
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
*hondo*
Posts: 102
Joined: Sat Mar 08, 2008 9:50 am
Hardware configuration: Geoforce 250 GTS Active for F@H

4 Core Intel not used at all for F@H
Location: England UK

Re: Why the same WU Twice?

Post by *hondo* »

7im wrote:The log shows the work unit was deleted, so it was not completed. No returned data, no points.
Hi 7im What I'm asking is what happened or went wrong after here [07:12:25] Finished fah_main status=0

[07:12:25] Successful run
[07:12:25] DynamicWrapper: Finished Work Unit: sleep=10000
sortofageek
Site Admin
Posts: 3111
Joined: Fri Nov 30, 2007 8:06 pm
Location: Team Helix
Contact:

Re: Why the same WU Twice?

Post by sortofageek »

Unless I misunderstand your question, this is what happened.
[07:12:41] CoreStatus = 75 (117)
[07:12:41] Error opening or reading from a file.
[07:12:41] Deleting current work unit & continuing...
If the results cannot be read, they are unusable. IOW, you completed the WU, but it was unusable, so it was deleted.

You appear to have had better fortune with the second try, however. If you continue to have problems like the above, you may want to do some troubleshooting on your end. If not, it's possibly just a fluke.

Hi *hondo* (team 51078),
Your WU (P6803 R15 C13 G967) was added to the stats database on 2012-02-08 02:05:10 for 1325 points of credit.
*hondo*
Posts: 102
Joined: Sat Mar 08, 2008 9:50 am
Hardware configuration: Geoforce 250 GTS Active for F@H

4 Core Intel not used at all for F@H
Location: England UK

Re: Why the same WU Twice?

Post by *hondo* »

sortofageek wrote:Unless I misunderstand your question, this is what happened.
[07:12:41] CoreStatus = 75 (117)
[07:12:41] Error opening or reading from a file.
[07:12:41] Deleting current work unit & continuing...
If the results cannot be read, they are unusable. IOW, you completed the WU, but it was unusable, so it was deleted.

You appear to have had better fortune with the second try, however. If you continue to have problems like the above, you may want to do some troubleshooting on your end. If not, it's possibly just a fluke.

Hi *hondo* (team 51078),
Your WU (P6803 R15 C13 G967) was added to the stats database on 2012-02-08 02:05:10 for 1325 points of credit.
Thank you very much sortofageek for the information :) I can't figure it out nothings been changed at this end for age's & the 68XX series of WUs I must have done +100s :?

BTW can you please supply a link from where you obtain the information that a WU has been uploaded & credited please. Odd think is I was going to request some time back that there maybe should be a link that can be accessed through the F@H using your Passkey that indicated which
Project: 68XX (Run xx, Clone XX, Gen xxx) had been uploaded IMO this would save time looking through F@H logs followed by asking you Guys the same questions :)
PantherX
Site Moderator
Posts: 7020
Joined: Wed Dec 23, 2009 9:33 am
Hardware configuration: V7.6.21 -> Multi-purpose 24/7
Windows 10 64-bit
CPU:2/3/4/6 -> Intel i7-6700K
GPU:1 -> Nvidia GTX 1080 Ti
§
Retired:
2x Nvidia GTX 1070
Nvidia GTX 675M
Nvidia GTX 660 Ti
Nvidia GTX 650 SC
Nvidia GTX 260 896 MB SOC
Nvidia 9600GT 1 GB OC
Nvidia 9500M GS
Nvidia 8800GTS 320 MB

Intel Core i7-860
Intel Core i7-3840QM
Intel i3-3240
Intel Core 2 Duo E8200
Intel Core 2 Duo E6550
Intel Core 2 Duo T8300
Intel Pentium E5500
Intel Pentium E5400
Location: Land Of The Long White Cloud
Contact:

Re: Why the same WU Twice?

Post by PantherX »

*hondo* wrote:...BTW can you please supply a link from where you obtain the information that a WU has been uploaded & credited please...
Unfortunately, access to the WU Database is only granted to Administrators and Moderators. The reason for this is that a few queries done by us is easier to handle than several that might be if it was open to the public.
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time

Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
*hondo*
Posts: 102
Joined: Sat Mar 08, 2008 9:50 am
Hardware configuration: Geoforce 250 GTS Active for F@H

4 Core Intel not used at all for F@H
Location: England UK

Re: Why the same WU Twice?

Post by *hondo* »

Thanks PantherX I guess thats understandable from a server load point of view albeit it would IMHO make life easier for folks like me, although no big deal providing you guys don't mind 8-)

One last thing I'd really like to know is how the OP WU went belly up? Because even now I still don't know, which is rather a waste of time for the project, plus not forgetting little Ole me. :)
7im
Posts: 10189
Joined: Thu Nov 29, 2007 4:30 pm
Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
Location: Arizona
Contact:

Re: Why the same WU Twice?

Post by 7im »

Any number of things can cause a write file error. Full hard drive. HD going bad. Memory overclocked too much, undervolted too much, timings set too aggressively. If running in a VM, the last person I helped only had a 2 GB virtual partition, and the lastest linux updates filled the partition and fah couldn't write out any more data. Or a PC running too hot corrupts the data, or a PC cooled well but overlocked too much can do the same. Or a stray Gamma Ray from outerspace flipped a bit in your computer, and caused a calculation error. Impossible to guess all the potential causes. ;) If this is a rare occurrence, not worth the effort to troubleshoot all the potential causes. If this becomes a regular problem, go after it with diagnostics, scans, tests, etc. :)
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
*hondo*
Posts: 102
Joined: Sat Mar 08, 2008 9:50 am
Hardware configuration: Geoforce 250 GTS Active for F@H

4 Core Intel not used at all for F@H
Location: England UK

Re: Why the same WU Twice?

Post by *hondo* »

7im wrote:Any number of things can cause a write file error. Full hard drive. HD going bad. Memory overclocked too much, undervolted too much, timings set too aggressively. If running in a VM, the last person I helped only had a 2 GB virtual partition, and the lastest linux updates filled the partition and fah couldn't write out any more data. Or a PC running too hot corrupts the data, or a PC cooled well but overlocked too much can do the same. Or a stray Gamma Ray from outerspace flipped a bit in your computer, and caused a calculation error. Impossible to guess all the potential causes. ;) If this is a rare occurrence, not worth the effort to troubleshoot all the potential causes. If this becomes a regular problem, go after it with diagnostics, scans, tests, etc. :)
How bizarre, I was expecting an answer. :shock:

The Hd is 7% utilised
The PC is no more than 4 months old
The overclocking is no different to 100s of other WUs that have been completed.
I couldn't setup & don't know what benefit if any, a VM would be.
I'm running Windows
The temps are OK
Dan Dare or Ray Gamma haven't been this way since the 50s :roll:
7im
Posts: 10189
Joined: Thu Nov 29, 2007 4:30 pm
Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
Location: Arizona
Contact:

Re: Why the same WU Twice?

Post by 7im »

The answer is "I don't know what caused it" and we may never know. Sorry, not all answers are the one you're looking for. :?

Like I said, probably an isolated fluke, like a drunk hitting a power pole down the road and causing a power spike at the wrong time. But if it happens again and again, then we can start testing for the cause.
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
*hondo*
Posts: 102
Joined: Sat Mar 08, 2008 9:50 am
Hardware configuration: Geoforce 250 GTS Active for F@H

4 Core Intel not used at all for F@H
Location: England UK

Re: Why the same WU Twice?

Post by *hondo* »

7im wrote:The answer is "I don't know what caused it" and we may never know.
OK 7im thanks, it looks like we wikll all have to pass on this one. :)
Jesse_V
Site Moderator
Posts: 2851
Joined: Mon Jul 18, 2011 4:44 am
Hardware configuration: OS: Windows 10, Kubuntu 19.04
CPU: i7-6700k
GPU: GTX 970, GTX 1080 TI
RAM: 24 GB DDR4
Location: Western Washington

Re: Why the same WU Twice?

Post by Jesse_V »

7im wrote:Or a stray Gamma Ray from outerspace flipped a bit in your computer, and caused a calculation error.
A mistake of some real programmer who was trying to unleash the power of the butterfly? Too bad there's an Emacs command for that...
http://xkcd.com/378/
:lol:
F@h is now the top computing platform on the planet and nothing unites people like a dedicated fight against a common enemy. This virus affects all of us. Lets end it together.
new08
Posts: 188
Joined: Fri Jan 04, 2008 11:02 pm
Hardware configuration: Hewlett-Packard 1494 Win10 Build 1836
GeForce [MSI] GTX 950
Runs F@H Ver7.6.21
[As of Jan 2021]
Location: England

Re: Why the same WU Twice?

Post by new08 »

I thought that was quite a fulsome explain from 7im, actually!
The work has been credited too, I thought?
My week long effort is still sitting in the dust somewhere and the next unit not sending up either- so a lot of pesky Gamma rays about today!
Image
7im
Posts: 10189
Joined: Thu Nov 29, 2007 4:30 pm
Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
Location: Arizona
Contact:

Re: Why the same WU Twice?

Post by 7im »

We're approaching the strongest solar maximum in 50 years at the end of 2012, so don't discount solar flares screwing up the ionosphere as a cause... :lol:

Say, isn't there some other important event near the end of 2012? Winter solstice? Nah. Galactic alignment? Nope. Presidential election? Naa. End of the world? NO. Oh, I know, V7 public release!!! 8-)
How to provide enough information to get helpful support
Tell me and I forget. Teach me and I remember. Involve me and I learn.
Post Reply