Did I just lose 4 days of folding?

I've been working for 4 days on a 381 point WU, but this morning I saw that the WU hasn't been sent back to. Did I lose the WU, or will I get the points next time F@H connects til stanford?

Here is the log: Finished Work Unit:
[06:49:01] - Reading up to 13848 from "work/wudata_08.arc": Read 13848
[06:49:01] - Reading up to 2233680 from "work/wudata_08.xtc": Read 2233680
[06:49:01] goefile size: 0
[06:49:01] logfile size: 571893
[06:49:01] Leaving Run
[06:49:04] - Writing 3445741 bytes of core data to disk...
[06:49:05] Done: 3445229 -> 2559032 (compressed to 74.2 percent)
[06:49:05] ... Done.
[06:49:05] - Shutting down core
[06:49:05]
[06:49:05] Folding@home Core Shutdown: FINISHED_UNIT
[06:49:07] CoreStatus = 64 (100)
[06:49:07] Sending work to server


[06:49:07] + Attempting to send results
[06:49:18] - Couldn't send HTTP request to server
[06:49:18] + Could not connect to Work Server (results)
[06:49:18] (171.65.103.160:8080)
[06:49:18] - Error: Could not transmit unit 08 (completed September 1) to work server.
[06:49:18] Keeping unit 08 in queue.


[06:49:18] + Attempting to send results
[06:49:34] - Couldn't send HTTP request to server
[06:49:34] + Could not connect to Work Server (results)
[06:49:34] (171.65.103.160:8080)
[06:49:34] - Error: Could not transmit unit 08 (completed September 1) to work server.


[06:49:34] + Attempting to send results
[06:49:49] - Couldn't send HTTP request to server
[06:49:49] + Could not connect to Work Server (results)
[06:49:49] (171.65.103.100:8080)
[06:49:49] Could not transmit unit 08 to Collection server; keeping in queue.
[06:49:49] - Preparing to get new work unit...
[06:49:49] + Attempting to get work packet
[06:49:49] - Connecting to assignment server
[06:50:09] - Couldn't send HTTP request to server
[06:50:09] + Could not connect to Assignment Server
[06:50:33] - Successful: assigned to (171.64.122.136).
[06:50:33] + News From Folding@Home: Welcome to Folding@Home
[06:50:34] Loaded queue successfully.


[06:51:06] + Attempting to send results
[06:51:21] - Couldn't send HTTP request to server
[06:51:21] + Could not connect to Work Server (results)
[06:51:21] (171.65.103.160:8080)
[06:51:21] - Error: Could not transmit unit 08 (completed September 1) to work server.


[06:51:21] + Attempting to send results
[07:04:42] - Server does not have record of this unit. Will try again later.
[07:04:42] Could not transmit unit 08 to Collection server; keeping in queue.
[07:04:42] + Closed connections
[07:04:42]
[07:04:42] + Processing work unit
[07:04:42] Core required: FahCore_7a.exe
[07:04:42] Core found.
[07:04:42] Working on Unit 09 [September 1 07:04:42]
[07:04:42] + Working ...
[07:04:42]
[07:04:42] *------------------------------*
[07:04:42] Folding@Home GB Gromacs Core
[07:04:42] Version 1.90 (March 8, 2006)
[07:04:42]
[07:04:42] Preparing to commence simulation
[07:04:42] - Looking at optimizations...
[07:04:42] - Created dyn
[07:04:42] - Files status OK
[07:04:42] - Expanded 16657 -> 141295 (decompressed 848.2 percent)
[07:04:42] - Starting from initial work packet
[07:04:42]
[07:04:42] Project: 2096 (Run 109, Clone 12, Gen 23)
[07:04:42]
[07:04:42] Assembly optimizations on if available.
[07:04:42] Entering M.D.
[07:04:48] Protein: p2096_A21_agbnp_amber99
[07:04:48]
[07:04:48] Writing local files
[07:04:49] GB activated
[07:04:49] Extra SSE boost OK.
[07:04:49] Writing local files
[07:04:49] Completed 0 out of 4000000 steps (0)
[07:17:30] Writing local files
[07:17:30] Completed 40000 out of 4000000 steps (1)
[07:30:13] Writing local files
[07:30:13] Completed 80000 out of 4000000 steps (2)
[07:42:57] Writing local files
[07:42:57] Completed 120000 out of 4000000 steps (3)
[07:55:38] Writing local files
[07:55:38] Completed 160000 out of 4000000 steps (4)
[08:08:20] Writing local files
[08:08:20] Completed 200000 out of 4000000 steps (5)
[08:21:04] Writing local files
[08:21:04] Completed 240000 out of 4000000 steps (6)

its likely that the server could be down atm
here are server stats
if its up or not idle since idle can sergest a hung server
ill have a look in an old thread some one once posted in it with some neet tools that can fix things our end.
http://fah-web.stanford.edu/serverstat.html

edit:

ChasR said:

Sometimes the queue.dat file becomes corrupt and as a result either the WU is sent and queue.dat doesn't recognize that has happened and keeps trying to send it until the deadline passes or it never sends it at all due to the corruption. There is a suite of programs designed to repair FAH problems and provide detailed information on progress located here . qfix is the program to have used in this case.

Click to expand...

http://www.boston.quik.com/rph/fah.html

ok that dosnt work any more


the new URL #
http://linuxminded.xs4all.nl/mirror/www.boston.quik.com/rph/fah.html

You've still got the WU as long as the log says keeping it in queue. Deleted and continuing is a message you never want to see. Check server stats before running qfix. If the server's you're trying to send to are up (full or accept) and you haven't got a firewall issue blocking transmission, then stop the client, disconnect from the internet, copy the Work folder and queue.dat to a subdirectory as a backup and then run qfix. It will report any errors in the queue.dat file. If running qfix doesn't corrupt the current WU delete the backup copies. If it does corrupt the current WU, restore the backups before connecting to the internet. In running qfix twenty or so times, I've only lost one current WU, when the queue.dat file was so corrupt it couldn't be repaired. In all likelyhood that WU would have been lost anyway but since then I make a backup. queue.dat on FAT32 drives is far more susceptable to corruption than on NTFS drives.