LHC@home

Hi, the first task went well. Other tasks refuse to continue - Postponed:VM environment needs to be clean up.
https://lhcathome.cern.ch/lhcathome/result.php?resultid=358665589 OK.
https://lhcathome.cern.ch/lhcathome/result.php?resultid=358671171 Error. FATAL: Could not read from the boot medium! System halted. Canceled via gui.

Guess you highlighted the wrong line.
The real issue is this:

Host system reported disk full.

Host ?

Hi, the first task went well. Other tasks refuse to continue - Postponed:VM environment needs to be clean up.
https://lhcathome.cern.ch/lhcathome/result.php?resultid=358665589 OK.
https://lhcathome.cern.ch/lhcathome/result.php?resultid=358671171 Error. FATAL: Could not read from the boot medium! System halted. Canceled via gui.

Saw the same Yesterday. Stopped Atlas for me Win11pro.

Looks like your vdi file is attached to a VM in VirtualBox media manager and that VM doesn't exist any more.
You may
- ensure no ATLAS task is running
- stop BOINC
- open the VirtualBox media manager and remove the disk entry "ATLAS_vbox_2.01_image.vdi" (but keep the image file!)
- restart BOINC
- resume ATLAS tasks


You may periodically check the "load average" on the host using "top".
What are the maximum values when ATLAS has set up all threads?

It seems this version is causing many failures, so I have reverted back to v2.00 while we debug the problems.

It seems this version is causing many failures...

hm, strange. Here it worked well on all of my machines (Windows).

This can be on your side as well as on the Cloudflare/CERN side but since many other computers are running fine it's more likely the issue is on your side.

If you run a (Linux) CVMFS client inside your LAN you may manually run "cvmfs_config probe" from that client.

I get all six Probings... OK

It seems this version is causing many failures...

hm, strange. Here it worked well on all of my machines (Windows).

Yes, it seems to work on some machines and not others. It all looked ok when we tested it on the dev project too.

But many hosts fail immediately with an error like this:

2022-06-28 10:54:08 (153184): Error in start VM for VM: -1073741819
Command:
VBoxManage -q startvm "boinc_bb7752aa79a5ff69" --type headless
Output:
Waiting for VM "boinc_bb7752aa79a5ff69" to power on...
VBoxManage.exe: error: The virtual machine 'boinc_bb7752aa79a5ff69' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine

2022-06-28 10:54:08 (153184): VM failed to start.
2022-06-28 10:54:08 (153184): Could not start 
2022-06-28 10:54:08 (153184): ERROR: VM failed to start

And because the tasks fail straight away these hosts rapidly fail many tasks in succession so we were getting around 98% failure rate for the new version.

A list of measures that may help to solve "E_FAIL (0x80004005)" on Windows:
https://www.technewstoday.com/result-code-e_fail-0x80004005/

It seems this version is causing many failures, so I have reverted back to v2.00 while we debug the problems.

+1

Thank you David and your Team,
first two Atlas Vers.2.0 are running in Win11pro!

David wrote:

It seems this version is causing many failures, so I have reverted back to v2.00 while we debug the problems.

David - any idea when the problems will be straigthened out and the new version will again be in place?

We need more Investigation-Time.
We have atm Atlas-Version 2.00.