Cannot create or write into the data directory /minio

Support intro

Sorry to hear you’re facing problems :slightly_frowning_face:

help.nextcloud.com is for home/non-enterprise users. If you’re running a business, paid support can be accessed via portal.nextcloud.com where we can ensure your business keeps running smoothly.

In order to help you as quickly as possible, before clicking Create Topic please provide as much of the below as you can. Feel free to use a pastebin service for logs, otherwise either indent short log examples with four spaces:

example

Or for longer, use three backticks above and below the code snippet:

longer
example
here

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can :heart:

Nextcloud version (eg, 20.0.5): fresh install from stable its 20 something
Operating system and version (eg, Ubuntu 20.04): Ubuntu 20.04
Apache or nginx version (eg, Apache 2.4.25): nginx
PHP version (eg, 7.4): php8.0

The issue you are facing:
i know this probably isn’t supported but i’m trying to set the data directory as a mounted minio s3

the mount is working fine the perms are unrestricting.

i know it all comes down to the code nothing is impossible in the world of code.

Is this the first time you’ve seen this error? (Y/N):Y

Steps to replicate it:

  1. mount as s3 compatible as a directory / folder converting rpm to .deb if needed using alien
  2. sudo chown -R www-data:www-data /minio/* sudo chown -R www-data:www-data /minio chmod -R 777 /minio chmod -R 777 /minio/* (ik 777 bad but that prooves its not perm related right?)

The output of your Nextcloud log in Admin > Logging:
image
image

The output of your config.php file in /path/to/nextcloud (make sure you remove any identifiable information!):

PASTE HERE

The output of your Apache/nginx/system log in /var/log/____:

PASTE HERE

ok so it appeared to be related to to minio / minfs. its working now. the issue was i didnt change to version number in the json config for minfs it was set to 1 and it needed to be somthing else i dont rememer. if anyone else has this issue just look in sys logs it says was it wants it always does but its not smart enuff to make the change its self.

i never got that is the system knows thats its expecting code to be a certain way why dont it automatically fix???

i always have that problem with nginx config like if you want a “[” bracket somewhere put it there urself lol. the system knows more than me but yet im the one controlling it.

if i figre out how ill close this issue myself