Project: 3903 (Run 406, Clone 4, Gen 2)

[MDCRL]

Hello again,

Completely finished this WU and then It went poof ....

[01:32:55] - User name: MDCRL (Team 35275)
[01:32:55] - User ID: 11B0CB407960F6BB
[01:32:55] - Machine ID: 1
[01:32:55]
[01:32:56] Loaded queue successfully.
[01:32:56] + Benchmarking ...
[01:32:58]
[01:32:58] + Processing work unit
[01:32:58] Core required: FahCore_79.exe
[01:32:58] Core found.
[01:32:58] Working on Unit 04 [January 15 01:32:58]
[01:32:58] + Working ...
[01:32:58]
[01:32:58] *------------------------------*
[01:32:58] Folding@Home Double Gromacs Core
[01:32:58] Version 1.91 (April 11, 2006)
[01:32:58]
[01:32:58] Preparing to commence simulation
[01:32:58] - Looking at optimizations...
[01:32:58] - Files status OK
[01:33:10] - Expanded 9481064 -> 34524104 (decompressed 364.1 percent)
[01:33:11]
[01:33:11] Project: 3903 (Run 406, Clone 4, Gen 2)
[01:33:11]
[01:33:11] Assembly optimizations on if available.
[01:33:11] Entering M.D.
[01:33:35] (Starting from checkpoint)
[01:33:35] Protein: IBX in water
[01:33:35]
[01:33:36] Writing local files
[01:33:36] Completed 1780 out of 25000 steps (7)
↕
[11:08:31] Completed 25000 out of 25000 steps (100)
[11:08:31] Writing final coordinates.
[11:08:33] Past main M.D. loop
[11:09:33]
[11:09:33] Finished Work Unit:
[11:09:33] - Reading up to 6176768 from "work/wudata_04.arc": Read 6176768
[11:09:33] - Reading up to 959028 from "work/wudata_04.xtc": Read 959028
[11:09:33] goefile size: 0
[11:09:33] logfile size: 66885
[11:09:33] Leaving Run
[11:09:34] - Writing 7307032 bytes of core data to disk...
[11:09:36] Done: 7306520 -> 6914215 (compressed to 94.6 percent)
[11:09:36] - .
[11:09:36] - Error: Could not write out results to file
[11:09:36] - Shutting down core
[11:09:36]
[11:09:36] Folding@home Core Shutdown: FILE_IO_ERROR
[11:09:47] CoreStatus = 75 (117)
[11:09:47] Error opening or reading from a file.
[11:09:47] Deleting current work unit & continuing...
[11:10:01] - Preparing to get new work unit...
[11:10:01] + Attempting to get work packet
[11:10:01] - Connecting to assignment server
[11:10:02] - Successful: assigned to (171.64.122.83).
[11:10:02] + News From Folding@Home: Welcome to Folding@Home
[11:10:02] Loaded queue successfully.
[11:10:50] + Closed connections

Did I do something wrong?
.... I have plenty of space to write to, all other WU on this machine have been going in fine before and after this one without any problems


Do you want me to send the files into you( or whoever)? & if so where do I send them?
- or is there another way to get all that work and it's results back into the collective.....

[7im]

Hello again,

Completely finished this WU and then It went poof ....

...

Did I do something wrong?
.... I have plenty of space to write to, all other WU on this machine have been going in fine before and after this one without any problems.

No. Nothing in the log indicates any problem with the client, and if you have plenty of HD space, and this is an isolated failure, then the problem is mostly likely in the work unit. A search of that WU shows no one else has completed it either, but that Gen 1 of that WU was completed more than a month ago. Sorry, that deleted message in the log means that it is gone. Fold on.

[MDCRL]

That's what I was afraid of.... Good thing It went through that WU fast, didn't waste too much time on it..

Any way to pull any useful info from the remaining logs/work files?
I isolated it and didn't do anything past what I quoted....hate to see any work go for nothing

[bruce]

I....hate to see any work go for nothing

We all do.

The critical message is [11:09:36] - Error: Could not write out results to file and it's not a common message. Possible causes include things like
1) Hardware errors (is the disk controller overclocked? . . or RAM?)
2) Something else opening the same files (like an anti-virus scan at the wrong time)
3) File ownership issues (Were any of the files created under a different Windows userID?)
4) ???

[MDCRL]

Not OC'd - actually no probs on Low OC'd systems I have....
All under same user
Other program opening might have been possible - overnight issue when this unit failed - that's when most scans are scheduled
.... No problems w/ any units on any of the systems since - think they got the issues corrected

I have finished two all 3906/7 WU since then....