2004-10-02 16:25:56 [---] General prefs: from SETI@home (last modified 2004-10-02 15:54:08)
2004-10-02 16:25:56 [---] General prefs: using separate prefs for home
2004-10-02 16:26:07 [climateprediction.net] Resuming computation for result 0238_400027693_0 using hadsm3 version 4.03
2004-10-02 16:26:08 [SETI@home] Deferring computation for result 01mr04ab.2990.18690.579834.182_1
2004-10-02 16:26:08 [LHC@home] Deferring computation for result v64lhc1000pro39s4_6556.52_1_sixvf_62566_0
2004-10-02 16:27:03 [climateprediction.net] Result 0238_400027693_0 exited with zero status but no \'finished\' file

Above occurred after a system restart (scheduled, not a crash)

Meaning I lost a WU at 83%.

Can someone tell me why this happened?

I've had this error happen at home and it wasn't "fatal" (i.e. if you quit & restart it may start the workunit again?)

> I've had this error happen at home and it wasn't "fatal" (i.e. if you quit
> & restart it may start the workunit again?)
>
>
>

Heya Carl,

Tried that, also tried restoring the client_state.xml from the backup copy - also tried a Windows XP "System restore" but it was futile.

The client showed that the CPU time as still being 500 hours, and the To Completion time as 80 hours, but it was like the checkpoint side of things had failed.....very strange indeed.

I guess that this, if anything, is the downside of CPDN. If a SETI/LHC WU vanishes you only lose a few minutes - few hours worth of work....but with CPDN a whole months worth of work is lost if ANYTHING goes wrong.

I also did noticed that the hadsm programs being used before the crash were 4.03, and now when I reattached I received 4.04.