FILE_IO_ERROR

muon

muon

muon

Soldato
Joined
8 Nov 2006
Posts
23,571
Location
London
[01:56:50] Completed 1080000 out of 1500000 steps (72)
[02:23:28] Writing local files
[02:23:28] Completed 1095000 out of 1500000 steps (73)
[02:26:56] - Checksums don't match (work/wudata_04.pdo)
[02:26:57] Premature end of file when checksumming (925050 bytes left)
[02:26:57] - Could not calculate checksum (work/wudata_04.pdo)
[02:26:58] Checksum not what expected.
[02:26:58]
[02:26:58] Folding@home Core Shutdown: FILE_IO_ERROR
[02:27:01] CoreStatus = 75 (117)
[02:27:01] Error opening or reading from a file.
[02:27:01] Deleting current work unit & continuing...
[02:27:05] Trying to send all finished work units
[02:27:05] + No unsent completed units remaining.
[02:27:05] - Preparing to get new work unit...
[02:27:05] + Attempting to get work packet

Anyone know what this means? Thats the second wu worth 556 thats been trashed inside 2 days. Last time the server reported a problem with my result. So i decided to remove my overclock but now i get this? Grrrrrr.

Thx
 
Last edited:
It essentially means that the client wasn't properly able to access the necessary files in the work directory. Sadly there isn't much that can be done about it. :(
 
BillytheImpaler said:
It essentially means that the client wasn't properly able to access the necessary files in the work directory. Sadly there isn't much that can be done about it. :(
Click to expand...

Oh ok, then. What about the server reporting problems with a unit? I dont think its due to my overclock. Its been running for 19 days straight and it reports a problem now?

E6300 at 2.8ghz
xms2 RAM at stock timings and pc2-6400

everything passed memtest and orthos when i tested it a month ago.
 
Many different things might have caused it. If it doesn't happen again soon I'd call it a fluke and move on.

Were you really crunching that same 556 pointer for 19 days on an OC'd E6300? If so, there's something more seriously wrong going on.
 
BillytheImpaler said:
Many different things might have caused it. If it doesn't happen again soon I'd call it a fluke and move on.
Click to expand...

Fine ill set it back upto 2.8ghz.
Were you really crunching that same 556 pointer for 19 days on an OC'd E6300? If so, there's something more seriously wrong going on.
Click to expand...

No, lots of different wus. Thx anyway. I hope they were flukes :) . Otherwise more boring stability testing. :(
 
Last edited:
ghost101 said:
Oh ok, then. What about the server reporting problems with a unit? I dont think its due to my overclock. Its been running for 19 days straight and it reports a problem now?
Click to expand...
F@H is one of the best long-term stability tests about. When I was overclocking this PC, I could dual prime overnight and do as many SuperPis as you'd care to mention, but it would fail a Gromacs test within about 2 minutes.

However, what you have there is probably a bit of bad luck. Watch your output for early unit ends (EUEs), but I would have thought it's fine.
 
You must log in or register to reply here.
Back
Top Bottom