Summary
Encountering ‘Unable to use the drive /storage: file access denied: Invalid arguments specified’ error in Minio pod after upgrading to version 0.56.0. Attempted solution of deleting Minio and PVC not working. Seeking help to resolve the issue.
Question
Hey folks :meow_fingerguns:, we are continuing our slow upgrade from 0.50.xx up to the latest version. We just hit 0.56.0 and have hit another issue.
This time we’re getting the error in the Minio pod Unable to use the drive /storage: file access denied: Invalid arguments specified. I see in the issues to delete the Minio and the PVC.
However, this does not seem to be working. Has anyone else run into this issue and resolved it? 
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.
Join the conversation on Slack
["error", "minio-pod", "upgrade", "0.56.0", "file-access-denied"]
so what I did is to create a replica
Nice. You got any hints as to what some of the issues you debugged and how to solve them? I’ve got a few more steps to go… 
mostly it was a database migration
had to run ALTER type job_config_type owner to airbyte_usr;
with a master account postgres
or run on --low-resource-mode
Yeah, that was the issue when I made the big jump as well but then I couldn’t recover when I rolled back to the previous version due to one of the many migrations that were applied.
Thanks, I’ll keep this in mind!
no need to slowly upgrade just lunch yourself to the newest version 
I did that already and it broke our database 
same here but got it running debuging
Really? The biggest hurdle so far was between 0.53.1 -> 0.54.0 but this one is a pain. When I upgraded to the latest, this issue appeared and deleting the pod and PVC fixed it
I just jumped straight on, although really hoping for v1
How are you deploying? We’re using manifests
ahh, I am just doing EC2 AWS
all my data is in external RDS postgres
so that was a bit of a pain to connect to the newest version