Live log, once turned on, shows live activity, errors, etc. If no activity, it’s empty.
I don’t know if it would have gotten any more. Your stored looks like the other in
Duplicati.Library.Main.Operation.Restore.VolumeDownloader
except they managed to find a little more. They said later that it was Backblaze.
So apparently it’s not just on Google Drive. Maybe I should test from OneDrive.
Alternatively, you could experiment if you have any other destinations available.
You’d have to move the backup files, but won’t need to mess with job database.
The point of this error looks like the new restore, so legacy-restore may help.
EDIT:
and note the talk over there of space issues. New restore can be /tmp-hungry.
Even if that’s it, error message could use improving, and error line isn’t known.
My small OneDrive file restore on Windows worked fine, but Temp is part of C:
If you suspect a /tmp problem, the other issue talks about --tempdir option.