Forum > GPU crunching
CPU <-> GPU rebranding
Geek@Play:
Could it be trying to reschedule an abandoned Boinc installation?
Samuel:
Thanks for a nice utility, Marius!
One issue with v1.8 and it could well be isolated to my Vista64 installation. The first time I ran it (only V*AR), I stopped BOINC myself to make a backup and it ran fine, moving 21 V*ARs to CPU. I restarted BOINC and three CPU MBs started along with the CUDA and an Einstein unit without a problem.
Having managed to download a few more tasks, I suspended computation (I prefer doing this even if it's not necessary), hit Run and BOINC was stopped, 37 tasks moved and BOINC restarted. Great, I thought. Upon resuming computation however, two VLARs that had earlier been moved to the CPU (AK_v8_win_x64_SSE41) exited with 'SETI@home error -1 Can't create file -- disk full?' The CUDA task and two Einstein tasks restarted fine.
There's no problem with disk space, BOINC is using ~500MB of its allocated 10GB and the partition has more than 100GB free.
For a while, I've had to start BOINC with elevated privileges, otherwise the manager just can't start boinc.exe. I'll try and reduce the upload queue to download some new tasks. Then run your program as administrator to see if that fixes it.
The host is #4719981 and the errors were tasks #1289669959 and #1289669920
Raistmer:
@Marius
BTW, how your tool will handle systems with SETI +SETI beta installations?
Can it be used in such situation? will it rebrand beta tasks?
MarkJ:
--- Quote from: samuel7 on 05 Jul 2009, 06:18:41 am ---Having managed to download a few more tasks, I suspended computation (I prefer doing this even if it's not necessary), hit Run and BOINC was stopped, 37 tasks moved and BOINC restarted. Great, I thought. Upon resuming computation however, two VLARs that had earlier been moved to the CPU (AK_v8_win_x64_SSE41) exited with 'SETI@home error -1 Can't create file -- disk full?' The CUDA task and two Einstein tasks restarted fine.
There's no problem with disk space, BOINC is using ~500MB of its allocated 10GB and the partition has more than 100GB free.
The host is #4719981 and the errors were tasks #1289669959 and #1289669920
--- End quote ---
There was a bug fix in 6.6.31 for output file errors, which might have something to do with this. Your errors indicate you have 6.6.28 running. Current release version of BOINC is 6.6.36.
Samuel:
--- Quote from: MarkJ on 05 Jul 2009, 07:55:30 am ---
--- Quote from: samuel7 on 05 Jul 2009, 06:18:41 am ---Having managed to download a few more tasks, I suspended computation (I prefer doing this even if it's not necessary), hit Run and BOINC was stopped, 37 tasks moved and BOINC restarted. Great, I thought. Upon resuming computation however, two VLARs that had earlier been moved to the CPU (AK_v8_win_x64_SSE41) exited with 'SETI@home error -1 Can't create file -- disk full?' The CUDA task and two Einstein tasks restarted fine.
There's no problem with disk space, BOINC is using ~500MB of its allocated 10GB and the partition has more than 100GB free.
The host is #4719981 and the errors were tasks #1289669959 and #1289669920
--- End quote ---
There was a bug fix in 6.6.31 for output file errors, which might have something to do with this. Your errors indicate you have 6.6.28 running. Current release version of BOINC is 6.6.36.
--- End quote ---
Umm... Refrained from installing 6.6.36 due to the bad press on Seti fora and the 'do not fix if it works' policy. 6.6.28 had worked perfectly. Will try .36 if other methods fail.
Thanks.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version