Posts by reverendspam

    I've seen so many installs of piwigo and I could not get any of them to really work properly on OMV5.

    There are different ways to install this and you can upload your photos outside of the piwigo container, but I did not want to mess with symbolic links. I am totally ok with having piwigo and all my photos in one directory. This is just the quickest and easiest way to get piwigo up and running on OMV5.

    - This tutorial assumes you have OMV5 installed and running properly.

    - This tutorial assumes you have Portainer installed and running properly.

    - This tutorial assumes you know how to use OMV5 and Portaineer.

    1) Open portainer in your web browser.

    - Click on Stacks --> Add Stack

    - Give it a name such as piwigostack

    - Copy and paste the code below and add it to the stack's Web Editor section. You will need to change the environment and volume parameters to suit your system. I have noted the main points you need to edit. Take out the comments before you deploy the stack.

    ##remeber to remove the comments before you deploy the stack.

    - disable the "enable access control"

    - Click "Deploy the stack"

    You will now see 2 new containers named "piwidb" and "piwigo"

    2) If everything went as planned open a web browser and point to your OMV5 ip at port 8125

    for example, mine is :

    You should have the piwigo instaltion screen in front of you.


    3) Before you move forward you need to know the ip of your piwigo database.

    - Go back to Portainer and under containers you should see the new "piwidb" container. Under the "quick actions" column open the exec_console for piwidb then connect.


    - Once connected type in "hostname -I" without the quotation marks. This will give you your host database IP address.

    - you see in my example below mine is


    4) Go back to the piwigo installation install screen in your web browser and fill in the fields.

    In the "Database Configuration" section:

    - enter the host ip address of your database

    - User is piwigo

    - Password is piwigo

    - database name is piwigo

    - database tables prefix is piwigo_

    In the "Administration Configuration" section:

    - you enter whatever you want in this section


    When you have all the fields filled in then click on "start installation"

    If all goes well then you will get " Congratulations. Piwigo installation is completed"


    That's it.

    Note: I installed piwigo files to where my media files are housed because piwigo saves everything in one directory. The uploaded photos are saved in \www\gallery\upload.

    I set my system up different ways at first until I settled on what I did below and my system smokes with very little CPU overhead. Best practice is whatever works best for you :)

    SSD drives are cheap now. I bought a crucial 240 GB drive for $40. I installed OMV on it and expanded the partition with Gparted so I could run everything in a nice large partition drive.

    I have been running this 24/7 with no crashes. People will tell you that this will basically burn out the ssd, but they are so cheap I do not care.

    I purchased another ssd the same size and backed up my working system to it and set it aside for whenever it does crash. My system has been going strong for about 1 year now with no hiccups.

    I was initially having trouble with plex not playing back my videos and locking up. I found out plex was, by default, writing the transcoded files to my hard drives instead of to my ssd drive thus having i/o conflicts. I ended up making a transcode partition on the ssd drive and directed plex and omv to write to it. I think emby is the same.

    I can now play high def videos / audio with no issue. I even have one other person stream through the net off my system with no issues while I simultaneously stream through wifi at home.

    I also had plex write it's database to my hard drives because it will eat up the ssd drive space if you have lots of media.

    128gb ssd will be fine. I am only using about 40gb that includes omv, docker programs, and space for transcoding. This will increase during download activities.

    Be aware that if you use one big drive for everything and download to it, remember to delete orphaned files leftover in your download folder from various programs that may have not automatically deleted or moved these orphaned files.

    Good luck.


    • raid.PNG

      (14.04 kB, downloaded 165 times, last: )
    • system.PNG

      (17.07 kB, downloaded 193 times, last: )

    It could be any number of things. I have been running a nas at my house for 10 years now.

    What I have found through trial and error and a lot of pulling my hair out;

    1) I made the mistake of buying the cheapest sata cables and cursed my hard drives for being bad. I changed the cables out to better made ones and the drives worked flawlessly. Even new cables can be bad as it appears no one does quality control anymore to check products work out the door.

    2) Drives, even new ones, can have bad sectors. Usually your manufacturer will have software that can be downloaded from their
    website that will allow you to check the drives for bad sectors and 0 out any data that may be on them. This is a time consuming process.

    3) Bad memory. I bought more expensive ECC memory that my mb manufacturer recommended. I made the mistake of throwing in memory I had laying around. It initially appeared to run fine, but it was causing data rot and corruption. If you do use non ecc memory or something you have laying around, run it through your bios memory checker if available and software made to run memory through its paces.


    I could not get any of the solutions above to work. A post I found here worked for me and I updated sab to version 1.1.0

    1) install the sab plugin as normal through gui

    2) ssh into OMV and open the file /var/lib/dpkg/info/openmediavault-sabnzbd.postinst

    nano /var/lib/dpkg/info/openmediavault-sabnzbd.postinst

    change the line that looks similar to

    STABLE=`wget -q -O - | \grep sourceforge\.net | grep Linux | \sed 's/.*href=\"\(.*\)\".*/\1/' | sed 's/.*-\(.*\)-.*/\1/'`



    ctrl o to write/save the file

    then ctrl x to exit

    finally force install

    apt-get install -f