Running initial scan on new Plex library causes "ERROR : IO error: open file failed: googleapi: Error 403: The download quota for this file has been exceeded., downloadQuotaExceeded"
Latest beta as of 5-5-2021, v1.56.0-beta.5480.9ff6f48d7
Windows Server 2016, 64-bit (I know, I know...)
rclone mount --attr-timeout 1000h --dir-cache-time 1000h --poll-interval 0 --rc --read-only -v Google_Drive_Crypt: G:
type = drive
type = crypt
remote = Google_Drive:crypt
filename_encryption = standard
directory_name_encryption = true
Did not run with -vv
Never thought I'd create a post like this myself, but here I am
The last time I created a new library and ran the initial scan was back in late 2017, and I do not recall running into any issues. This is probably due to Google not having any API/quota limits at the time. Last night, I decided to make a new library for TV Shows. Media to be scanned in adds up to about 600 shows with roughly 22,000 episodes (144 TB).
I started the scan around 1 AM, and when I checked in the morning, only about 60 shows had been scanned in by Plex. Not only that, but also most of the media files had not been analyzed, because of the "download quota exceeded" error. I can't be sure as to when I hit the limit, exactly, but it sure didn't go very far. Anyway, I expected as much before I started all this.
I'm really only posting this here to see if there is anyone who recently ran an initial scan on a fairly large library without running into any issues. I have everything disabled in Plex that could cause extra API/quota strain, so my guess is that the initial media analysis is causing the temporary ban.
I usually give advice on Plex, but in this case I'm wondering if there is anything I could do to improve the initial scanning experience. In retrospect, I should not have attempted to scan in the entire library at once, but rather do each letter separately. Too late for that
Any and all input appreciated...