cheesemarathon

Ok in that case i'm not sure I can help you. You're in uncharted waters with regards to ZFS on unRAID as I'm sure your aware. I also couldn't find a huge amount of info on zvol's & minio so looks like you might have to do some more digging there too. TrueNAS forums might be a good place for info. Unfortunately for you this is way beyond my area of expertise. Good Luck and please report back if you do make any success!

I know very little about ZFS but a quick google suggested this may work to create a zvol: If you can get it mounted then you should be able to pass that through to minio by setting the mount point of the disk as the /data directory in the minio container config in unRAID

Ghost updated their docker image 2 days ago so i'm guessing this issue was created then. Quick fix would be to change the image to ghost:5.105 I'd then post your issue to the ghost forum as there are much more knowledgeable people there for ghost specific issues: https://forum.ghost.org/c/help/self-hosting/18

try this in extra parameters --user UID:$GUID replace UID and GUID with whatever you need for Nextcloud

If you have it working, I'd consider it supported at this time!

Sounds good! Perhaps there have been some changes to minio. But if you have it working thats great!

Have you actually connected to your database from another machine? Using something like MariaDB or DBeaver

Yes it works, but its not as easy as it once was. You can use mergefs to merge multiple hard disks, and then minio uses the merged directory Then map /mnt/addons/minio to the minio container Note that it must be mounted in the /mnt/addons/ directory mkdir -p /mnt/addons/minio mergerfs /mnt/disk1/minio:/mnt/disk2/minio /mnt/addons/minio

Create another variable in the container config in unRAID called database__connection__port Set that to the port used by your MySQL container

Thanks @itimpi that worked a treat. Lesson learnt today, research before you do something you are not 100% sure of. Close call today.

System diagnostics for reference derek-diagnostics-20240508-0832.zip

I had a disk fail so needed to replace it. In the process of replacing it I was hoping to switch to ZFS from XFS but I think I may have screwed myself. Before replacing the disk, the system was emulating it without issue. I stopped the array, installed the new disk, set its file system to ZFS and started the array and let it rebuild from parity. Rebuild complete I have a Unmountable: Unsupported or no file system error. I have not at any point formatted the drive. I'm hopping I have not lost any data here but want to ask for help prior to taking any more steps to ensure I don't mess it up any more.

Ok so the issue must exist somewhere between Ghost and MySQL. I would enable the general query log on your MySQL container, which should show logs when Ghost attempts to connect. It might shed some more light on the situation.

Had a look through the logs and nothing jumps out at me. Only thing is that the errors are all at the same sort of time: 01:17, 02:17, 06:17, 07:16, 21:26, 22:26, 23:26 which leads me to think, something is happening on a regular interval to cause this issue. When you say you reinstalled the containers, did you delete the appdata directories for the containers as well, as any misconfiguration in there will just be carried over into the reinstall if not removed. The other thing I would check is, when you have the error, check to see if you can connect to MySQL from another service. Id install the Adminer container on UnRAID and something like DBeaver on another machine and test both.

Sorry having some issues with my server right now. Hopefully backup by Monday. In the meantime the way back archive has a copy: https://web.archive.org/web/20231227043755/https://squishedmooo.com/

Head to {your blog domain}/ghost and the UI should guide you through the setup

Thanks for the update and fix. I had spotted the issue myself but had not had time to look into a fix!

Cool I think I understand what is going on here. My first suggestion would be to not install MySQL. MariaDB is an opensource implementation of MySQL, so 99% of the time any application that can connect and use a MySQL database can also use a MariaDB database. So what I would do is set Ghost to use your MariaDB instance. Setup is the same. I'll put a screenshot of my config below for reference. Database IP is the IP address of the machine running MariaDB. I assume your unRAID machine. So something like 192.168.1.45 or whatever your IP scheme is. Database user and password are self explanatory. Database name is the name of the database within MariaDB you wish Ghost to use. The other issue you seem to be having is with the URL setting. If you are running a blog that can not be accessed from a domain name then leave it blank. If that fails then I would remove the variable entirely. Just click the remove button on the right hand side. If you ever plan to open your Ghost blog up to the internet, you will need to set this to the domain name your site will be reachable from. In my case it is `https://squishedmooo.com/` Note that as the error suggests, you need to include a protocol in the URL. https is correct for the most part. I hope that helps, but if you have any more questions, just shout.

I have had a further play with Minio and I have not been able to get it to run at all now. With the way Minio is being developed, it looks like they are tailoring it to be run on dedicated machines. As such I would not recommend you use it. I did find the last 100% working version somewhere in this thread which you could use if you wish but you wont get any updates. Sorry I couldn't be of more help. If you want to have a play with Minio more then I can give you a few theoretical answers. Mounting a specific disk `/mnt/disk1` for example to the `/data` directory should allow it to work. In theory you could mount `/mnt/disk1` to `/disk-1` and `/mnt/disk2` to `/disk-2` etc. You also need to set the environment variable `MINIO_VOLUMES="/data-{1...4}"` I believe another user had a play trying to get this work but did not succeed but in theory it should work. Docs on this type of setup are here. Also, with all the above minio is mounted to the root of the drives. Minio then could wipe all the data on that drive, so I'd mount it into a minio directory on each drive. I have no experience with a V-Disk at all, but again you should be able to get it to work similarly to how I have just described but with a V-Disk instead of a physical one. Speed would be very dependant on your system specs.

If I’m honest i don’t have answers to all your questions right now. I’ll spin up an instance of minio and have a play over the next couple of days and see what I can recommend!

OK so in the docker screen, tick the switch in the uptime column to enable auto start. Unraid will start the containers in the order they are on the screen. Make sure your database starts before ghost or it will fail to start.

Yes those are all my templates. You mentioned you couldn't get one to autostart. Which one could you not get to start. You have none of the templates in your screenshot installed.

Which constrainer are you referring to. This thread is for support of all the containers I have written an unRAID template for.

appologies that I didn’t get chance to message you the commands! Glad you worked it out though 😊

I haven't created any templates for unRAID for any other S3 storage services. I don't believe there are any in community applications. This is the best collection of potential alternatives that may work with unRAID but would need further investigation: