I just completed a minor update of Ubuntu on ARM machine. When I restarted, in the MATE interface, the BOINC icon was unresponsive. When I launched boincmgr from the command window, the BOINC window was blank, with the word 'disconnected' at the bottom. I then tried

% sudo /etc/init.d/boinc-client start
% sudo /etc/init.d/boinc-client status

from which I got this:

boinc-client.service - Berkeley Open Infrastructure Network Computing Client
Loaded: loaded (/lib/systemd/system/boinc-client.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2021-03-15 08:54:44 EDT; 14s ago
Docs: man:boinc(1)
Process: 18120 ExecStart=/usr/bin/boinc (code=exited, status=200/CHDIR)
Process: 18140 ExecStopPost=/bin/rm -f lockfile (code=exited, status=200/CHDIR)
Main PID: 18120 (code=exited, status=200/CHDIR)

Mar 15 08:54:44 Noether systemd[1]: Started Berkeley Open Infrastructure Network Computing Client.
Mar 15 08:54:44 Noether systemd[18120]: boinc-client.service: Changing to the requested working directory failed: No such file or directory
Mar 15 08:54:44 Noether systemd[18120]: boinc-client.service: Failed at step CHDIR spawning /usr/bin/boinc: No such file or directory
Mar 15 08:54:44 Noether systemd[1]: boinc-client.service: Main process exited, code=exited, status=200/CHDIR
Mar 15 08:54:44 Noether systemd[18140]: boinc-client.service: Changing to the requested working directory failed: No such file or directory
Mar 15 08:54:44 Noether systemd[18140]: boinc-client.service: Failed at step CHDIR spawning /bin/rm: No such file or directory
Mar 15 08:54:44 Noether systemd[1]: boinc-client.service: Control process exited, code=exited, status=200/CHDIR
Mar 15 08:54:44 Noether systemd[1]: boinc-client.service: Failed with result 'exit-code'.

I really don't know how to fix this.

Correction: the machine is an AMD Ryzen 7 2700x, and accounts for about 90% of my Rosetta contribution (and occasionally a 5% badge).

SOLVED: The Ubuntu upgrade had reassigned a hard drive to another /dev slot.

SOLVED: The Ubuntu upgrade had reassigned a hard drive to another /dev slot.

That would explain the "No such file or directory" error messages.

---

Grant
Darwin NT