Had an error on a task from batch 1006 which had been running for about 12hrs. This is the STDRR

<core_client_version>7.24.1</core_client_version>
<![CDATA[
<message>
The system cannot find the drive specified.
(0xf) - exit code 15 (0xf)</message>
<stderr_txt>
modelGetExecutables: check control files, strTemp0 & 1 :
C:\ProgramData\BOINC/projects/climateprediction.net/wah2_eas25_h484_201912_24_1006_012264284/jobs/xadae.namelists
C:\ProgramData\BOINC/projects/climateprediction.net/wah2_eas25_h484_201912_24_1006_012264284/jobs/xacxf.namelists
modelGetExecutables: unzipping control files : strInput & strTmp
wah2_eas25_h484_201912_24_1006_012264284.zip
wah2_eas25_h484_201912_24_1006_012264284/jobs
gstrDump[0] = generic_phase1_spinup_eas25_global_aabaka
gstrDump[1] = generic_phase1_spinup_eas25_regional_aabaka
global model: command string: "C:\ProgramData\BOINC/projects/climateprediction.net/wah2am3m2_um_8.29_windows_intelx86.exe" wah2_eas25_h484_201912_24_1006_012264284 generic_phase1_spinup_eas25_global_aabaka ic19610807_10_N96 ALLclim_ancil_82months_OSTIA_temp_2017-01-01_2023-10-30 ALLclim_ancil_82months_OSTIA_ice_2017-01-01_2023-10-30 SO2DMS_N96_cmip6ssp245_2019-2030 oxi.addfa ozone_cmip6hist-ssp245_N96_1979_2031
regional model: command string: "C:\ProgramData\BOINC/projects/climateprediction.net/wah2rm3m2t_um_8.29_windows_intelx86.exe" wah2_eas25_h484_201912_24_1006_012264284
cpdn_check_running: got RM PID of zero; ignoring this call and waiting for PID via shMem.
executeModelProcess: MonID=8284, GCM_PID=9744, RCM_PID=7216
Global Worker:: CPDN process is not running, exiting, bRetVal = T, checkPID = 9744, selfPID = 9744, iMonCtr = 1
No Process Handle
Regional Worker:: CPDN process is not running, exiting, bRetVal = T, checkPID = 9744, selfPID = 7216, iMonCtr = 1

</stderr_txt>
]]>

Had an error on a task from batch 1006 which had been running for about 12hrs. This is the STDERR

<core_client_version>7.24.1</core_client_version>
<![CDATA[
<message>
The system cannot find the drive specified.
 (0xf) - exit code 15 (0xf)</message>
]]>

The problem is "The system cannot find the drive specified". It's exactly what it says, Windows couldn't find the filesystem and the process died. Google the error message and you'll find lots of info.

p.s. can I ask you start a new thread for this error rather than post to the 'New Work Thread'. It makes searching easier, plus keeps this thread for posts about new work, not errors/problems. Thanks.

---

---
CPDN Visiting Scientist

I had the same error on my 1006 task today. No idea what it is. Hopefully someone can give better advice than just "Google it"

---

It is good advice to Google it, there are plenty of YouTube videos and help pages with long explanations that I'm not going to copy here. It's a common Windows issue. Possible failing drive but check out all the help online.

---

---
CPDN Visiting Scientist

This is one of what I think is the most useful pages for this error. (I am much better at reading instructions in printed form than following videos for this sort of thing.)

I do find it odd that I was unable to find anything about it on the BOINC forums. I admit I only did a simple search and didn't try the advanced search options. I will say though that when the problem is not CPDN specific, those forums are often a better place to go than the CPDN ones.

Just had one fail with,

<core_client_version>8.0.4</core_client_version>
<![CDATA[
<message>
Invalid drive.
 (0xf) - exit code 15 (0xf)</message>
<stderr_txt>

I suspect this is the same as cannot find the drive specified but for WINE under Linux. Ryzen9 with 64GB RAM, BOINC8.0.4 Xubuntu24.04. Running chkdsk does not come up with any errors. First failure on this machine. I will keep a close eye on remaining and future tasks from this batch.

Yes, this is the same error. The error code, 15, is the same in both cases. It's probably Wine or Windows 10.

I had 3 such failures on one of my wine setups, happened when the processes were starting up. It could be a software issue with the model, but I need more output from the model logs to see what it complaining about.

---

---
CPDN Visiting Scientist

Thanks Glenn. Looking at computing preferences, I wonder if it is related to BOINC switching between tasks. I hadn't changed the setting from the default 120 minutes. I have now changed it to longer than the task duration.

I doubt it. There's no point trying to second guess the problem until we get a better message from the model what file it's trying to access.

I doubt it. There's no point trying to second guess the problem until we get a better message from the model what file it's trying to access.

Maybe but minimising tasks starting and stopping seems like a good idea to me. It would be nice if one could just turn off the ability of BOINC to switch which tasks are running at any particular time.

The error points to a disk issue of some sort. Best to run a disk scan on the wine windows drive to check for any errors. And on the underlying drive. Perhaps also check for any issues in the Windows registry.

I don't run any other projects when I'm running CPDN and don't have a big 'task cache', so my tasks don't switch. That's why I don't think it's the cause of my error code 15.

---

---
CPDN Visiting Scientist

That's why I don't think it's the cause of my error code 15.

My thinking wasn't that it was the root cause of the problem, rather that the conditions where it might occur might happen more frequently if there is task switching going on.

In my case, it happened when the tasks all started up when I started wine on a powered up 5900X. That's 11 tasks under wine, each starting 3 processes. I lost a couple but not all. I thought at first it might be a timeout given 33 tasks all starting at once trying to read files, but the disk timeout is set to 60secs on Windows so I don't think it's that. I'm adding more diagnostics from the model logs to the stderr task log then I'll be able to see what file/directory it's complaining about. Whether it's the same one or different.

---

---
CPDN Visiting Scientist

This is the sort of annoying thing that I can imagine not happening when you are looking for it!

I have task switching set to 1 week and never see them switch. But I also on a occasion will have a task fail with this disk error. I haven't run a disk check yet. The simplest troubleshooting step I saw recommended for this type of error is a system reboot, I think that's what I've done after seeing one of these failures.