Google Drive: 404 / Revision not found -> Disk read error

I am creating this topic because I am curious if others have experienced this problem with Google Drive as well?

Since the file can be downloaded from the web gui without any problems, is it possible that rclone might be able to automatically "unlock" the file to make it readable again?

What is the problem you are having with rclone?

Some files cannot be opened, even though they are present at the Google Drive.

The files in question cannot be opened with i.e. Google File Stream either.

But, the files can be downloaded just fine through a web browser from http://drive.google.com/.

See this thread for details:

https://support.google.com/a/thread/11614681?hl=en

Which cloud storage system are you using? (eg Google Drive)

Google Drive

The command you were trying to run (eg rclone copy /tmp remote:tmp)

rclone mount

A log from the command with the -vv flag (eg output from rclone -vv copy /tmp remote:tmp)

I am reusing the http response from the topic at support.google.com, I can not find an example from the rclone debug log right now.

https://www.googleapis.com/drive/v2internal/files/xxxxxxxxxx?alt=media&revisionId=xxxxxxxx
Request headers:
Host: www.googleapis.com
Authorization:
User-Agent: GoogleDriveFS/32.0.11.0 (Windows;OSVer=10.0.17134;)
Range: bytes=0-2584

{
"error": {
"errors": [
{
"domain": "global",
"reason": "notFound",
"message": "Revision not found: xxxxxxxxxx",
"locationType": "other",
"location": "revision"
}
],
"code": 404,
"message": "Revision not found: 0BwLbw7OAyN11SldaNVZVeWhZaHc2OHhPN01GK1lIREdJbFM4PQ"
}
}

Do these files start working after a while?

If you want to see http from rclone then use -vv --dump bodies. It might be rather verbose.