Hi everyone, hope this is the right forum to post this in. I am trying to install Minio on Unraid, but it doesn't seem to be working. I go through the docker settings and select the data location, and enter in the user/pass, but it is failing. I get this error when I look at the logs:

API: SYSTEM()
Time: 18:03:24 UTC 09/12/2022
DeploymentID: 9cf9a52e-76d8-4d7e-937c-5bafd3xxxxx
Error: write /data/.minio.sys/tmp/8e40c609-f983-40da-874d-53e8f8xxxxx/xl.meta: invalid argument (*fs.PathError)
       6: internal/logger/logger.go:259:logger.LogIf()
       5: cmd/storage-errors.go:174:cmd.osErrToFileErr()
       4: cmd/xl-storage.go:2387:cmd.(*xlStorage).RenameData()
       3: cmd/xl-storage-disk-id-check.go:373:cmd.(*xlStorageDiskIDCheck).RenameData()
       2: cmd/erasure-object.go:736:cmd.renameData.func1()
       1: internal/sync/errgroup/errgroup.go:123:errgroup.(*Group).Go.func1()
Waiting for all MinIO sub-systems to be initialized.. possible cause (Unable to initialize config system: migrateConfigToMinioSys: Storage resources are insufficient for the write operation .minio.sys/config/config.json)

 

Not sure exactly what I need to do to fix it. Has anyone experienced this issue before? 
Thanks!

My guess is that the docker volume is mapped incorrectly to the host. Can you post an image of the container setup? 

I thought that maybe the issue as well, but it's not mapped incorrectly. Here is the setup. Nothing much you have to configure from the details listed in the screenshot. Thanks!

 

Try changing '/mnt/user/minio/' to '/mnt/user/minio'

Tried that and it didn't work.  I did install it in Windows and got it to work that way tho. I'm testing it to see if it will do what I need it to do. Thanks!

I'm experiencing this same issue right now, same error and everything.

Yeah, I'm lost sorry. I'll check later if I can get the container to run on my system. 

 

Edit. It runs fine on my system without issue. 

 

You could try creating a new minio share and mapping to that. 

Edited September 12, 20223 yr by Jturner
Update

That's what I did. Created a dedicated Minio share, no cache, and mapped it to /data. I even went into the docker console and manually tried creating files in /data, and it works fine. Just the Minio process (which seems to be running as root?) can't do it.

Yeah I don't know why it works fine for me. Last thing you could try would be to change the folder permissions in the unraid CLI using 

chmod 777 -R /mnt/user/minio

 

Does the container install but just not run, or see does it spit the error out when trying to install?

16 minutes ago, Jturner said:

Yeah I don't know why it works fine for me. Last thing you could try would be to change the folder permissions in the unraid CLI using 

chmod 777 -R /mnt/user/minio

 

Just tried that. No good.

 

16 minutes ago, Jturner said:

Does the container install but just not run, or see does it spit the error out when trying to install?

 

It installs, starts, but errors repeatedly thus:

 

API: SYSTEM()
Time: 23:38:20 UTC 09/12/2022
DeploymentID: 948e6b12-d5c6-40b3-8f64-87a1dd562abd
Error: write /data/.minio.sys/tmp/84585580-0ec3-440d-860f-924ef3cf14ba/xl.meta: invalid argument (*fs.PathError)
       6: internal/logger/logger.go:259:logger.LogIf()
       5: cmd/storage-errors.go:174:cmd.osErrToFileErr()
       4: cmd/xl-storage.go:2387:cmd.(*xlStorage).RenameData()
       3: cmd/xl-storage-disk-id-check.go:373:cmd.(*xlStorageDiskIDCheck).RenameData()
       2: cmd/erasure-object.go:736:cmd.renameData.func1()
       1: internal/sync/errgroup/errgroup.go:123:errgroup.(*Group).Go.func1()
Waiting for all MinIO sub-systems to be initialized.. possible cause (Unable to initialize config system: migrateConfigToMinioSys: Storage resources are insufficient for the write operation .minio.sys/config/config.json)

 

Interestingly, the /data/.minio.sys/tmp directory all gets created by Minio at first start. It's the GUID and below that fails. And yes there's plenty of space!

You are probably best going to the authors thread and asking there. It looks like other people have had the same issue. 

https://forums.unraid.net/topic/54183-support-cheesemarathons-repo/page/30/

17 hours ago, Jturner said:

You are probably best going to the authors thread and asking there. It looks like other people have had the same issue. 

https://forums.unraid.net/topic/54183-support-cheesemarathons-repo/page/30/

Thanks, will take a look at this link!

Looks like it's the SHFS layer, according to the Github issue.

 

Makes Minio a bit of a dead-end for me if I have to point it as a specific disk.

I have considered one more thing that may/may not work. Try the following:

1. Stopping the container (if it's running)
2. Remove the existing 'minio' share. Confirm the folder "/mnt/user/minio/" no longer exists on the host system.
3. Recreate the minio share (even better, call it something else like 'minio-data', you can change the name back later if you get the container working)
4. Delete the persistent appdata folder "/mnt/user/appdata/minio/".
5. Start the container again (make if you change the share name you correct the mapped directory).

 

I suspect that it is possible that something went wrong when the container set up and this is causing permission errors. I had a similar experience the other day settings up PostgreSQL db.

 

Edited September 16, 20223 yr by Jturner
Formatting

I was having the same issue. This is what I did to fix it.

 

1. Created minio share /mnt/user/minio

2. Started minio and let it create /.minio.sys/config

3. Stopped minio

4. Created config.json in config folder

5. Pasted this config file into it: https://raw.githubusercontent.com/cheesemarathon/docker-templates/master/cheesemarathon/minio.xml

6. Started again

 

Works for me now. Hope this helps someone else.

Thanks! I will give this a try tomorrow. Hopefully it will work for me as well! I’ll report back tomorrow and let you know how it goes. Thanks for providing some steps to try! I actually had given up on messing with it, but this gives me hope!

On 10/20/2022 at 6:55 PM, Vault 687 said:

I was having the same issue. This is what I did to fix it.

 

1. Created minio share /mnt/user/minio

2. Started minio and let it create /.minio.sys/config

3. Stopped minio

4. Created config.json in config folder

5. Pasted this config file into it: https://raw.githubusercontent.com/cheesemarathon/docker-templates/master/cheesemarathon/minio.xml

6. Started again

 

Works for me now. Hope this helps someone else.

This method worked for me as well! thank you.

On 10/28/2022 at 4:57 AM, JOSEPH ENGELMANN said:

This method worked for me as well! thank you.

Starts up and I'm able to log in. But get errors when I try to change or add something in settings. Did not try uploading stuff.

 

I ended up adding more cache pools, one with spinning disks and btrfs, where I installed without errors.

On 10/20/2022 at 8:55 PM, Vault 687 said:

I was having the same issue. This is what I did to fix it.

 

1. Created minio share /mnt/user/minio

2. Started minio and let it create /.minio.sys/config

3. Stopped minio

4. Created config.json in config folder

5. Pasted this config file into it: https://raw.githubusercontent.com/cheesemarathon/docker-templates/master/cheesemarathon/minio.xml

6. Started again

 

Works for me now. Hope this helps someone else.

 

This worked for me. Thanks.

 

On 10/20/2022 at 8:55 PM, Vault 687 said:

I was having the same issue. This is what I did to fix it.

 

1. Created minio share /mnt/user/minio

2. Started minio and let it create /.minio.sys/config

3. Stopped minio

4. Created config.json in config folder

5. Pasted this config file into it: https://raw.githubusercontent.com/cheesemarathon/docker-templates/master/cheesemarathon/minio.xml

6. Started again

 

Works for me now. Hope this helps someone else.

I followed this and while the server could start, I was unable to upload files more than about 100kb.

 

I found this in a thread where I learned that there are some issues with how Unraid mounts drives. While not ideal because it will only store on a single disk, it resolved the problems I was having.