Posts by hulmul

  • LUKS disk encryption plugin

    Hi,


    just for the sake of interest i was playing around a little bit with LUKS plugin. But I was not able to finalize the process. What I did


    1. Installed the Plugin

    2. Wiped /dev/sda and /dev/sdb

    3. created 2 new encryptions for sda and sdb.

    4. Unlocked both

    5. created a new File system for both. SDA was called "LUKS encrypted container on /dev/sda" while SDB was called "Device Mapper sdb-crypt"


    What does that mean? Why are they in a different status? Can I format both of them with ext4-filesystem?

  • How to integrate my Volume into Jellyfin (Docker compose)

    So far I have always installed Jellyfin directly on my server. But i used the chance when upgrading my server to test a bit with docker compose. I have no previous experience with Docker.

    I used a standard compose file and just edited the volumes section to fit to my device. In my case it is:

    Code
    /path/to/movies:/srv/dev-disk-by-uuid-XXX/JellyFinMedia/Movies

    When adding a new library i can select that volume as a directory but when scanning the new library no media was found.


    Do you have any useful tips for me? I guess it is a stupid newbie thing on my side :-I

  • omv-extras 6.3 / openmediavault-compose 6.7

    Quote

    I wrote the plugin. I know what works. root should be the default for group and user.


    I appreciate your fantastic work. And i dont want to stress this any further. So if it is fine for you it is fine for me as well. Then maybe i have an unusual rare situation after installing the plugin on a complete new machine, when it tells me that "this field is required" in red letters


  • omv-extras 6.3 / openmediavault-compose 6.7

    Quote

    Those are new fields. Leaving them at the default settings is a better idea unless you have a good reason to change them. 99.9% of users do not have a good reason to change them.

    You can not leave them default. It is mandatory to select an user account and a group. YOu can not leave them empty. Maybe it should be in the getting started guide.

    Quote

    Depends on what the error message is.

    In my case restart before applying was the only working way. Maybe it should be in the getting started guide. Others might be confused as well as me :)

  • omv-extras 6.3 / openmediavault-compose 6.7

    I just set up a blank OMV installation in my Raspi and struggling a bit with the usage of compose. I followed the guide. Here is where i was strugglling:

    Quote
    2. Create a folder called "compose". If this is a new install, create a folder called "containers".

    Does this mean when it is a new install i need both folders? Or does it mean I need the containers folder instead of a compose folder?


    Quote

    If you are setting up for the first time, you'll also need the absolute path to this folder (click the 4 squares in the upper right, put a check next to absolute path)

    To be more precise, the 4 squares icon is in the shared folders tab not in the "create shared folder"-tab.


    The guide says nothing about the mandatory fields of User and Group. I created a user account called "compose_user" and choose the group "users".


    Between step 12 and 13: Is it necessary to apply changes after saving and before restarting? [applying before restarting ends in an error message]


    Quote


    After docker starts and says it is installed and running..


    To be more precise: You can see the status: Compose=>Settings => Docker => Status.

  • Fresh installed system with 503 an 404 errors?

    Bought a new SD Card and as I had already feared. It was not the SD Card. If it would be the sd card the error will be more erratic and less reproductive.


    But nevertheless i changed the ip adress of the raspberry and it seems that it would work. So my best guess is, that it has something to do with the ssl certificate binded to the old ip adress. I think I imported it in the certificate cache in my windows client. However I hope it will be the solution and the error will not show up again. Lets continue with compose. I am excited :)

  • Fresh installed system with 503 an 404 errors?

    Code
    pi@raspberrypi:~ $ dpkg -l | grep openmedia
ii  openmediavault                       6.4.8-1                          all          openmediavault - The open network attached storage solution
ii  openmediavault-compose               6.9.4                            all          OpenMediaVault compose plugin
ii  openmediavault-flashmemory           6.2                              all          folder2ram plugin for openmediavault
ii  openmediavault-keyring               1.0.2-2                          all          GnuPG archive keys of the openmediavault archive
ii  openmediavault-omvextrasorg          6.3.1                            all          OMV-Extras.org Package Repositories for OpenMediaVault
ii  openmediavault-sharerootfs           6.0.2-1                          all          openmediavault share root filesystem plugin

  • Fresh installed system with 503 an 404 errors?

    After crashing my old OMV on my Raspberry 4 i followed the advise in the forum here and started with a clean installation. I followed strictly the guide. Including formatting my SD Card. But to my big surprise the system is very unstable in that way that even the first login didnt succeed. When entering the ip adress I am forwarded to a 503 site


    I deleted website and cookie data but still the same.

    Clicking on the error messages took me to login screen again where i can enter my credentials and log in.

    But on the dashboard i only could open a couple of menus. Clicking in OMV-Extras for example give me a 404.



    Again i formatted the sd-card. Installed fresh from the green and again the same errors.

    I tried different browsers which works for a couple of minutes but the the same. 404 and 503.


    I am not sure what I should change during the installation process.

  • Trying to install compose results in a long error message containing: "The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ..."

    Quote from Soma

    Running jellyfin OR plex (you don't need both, either one or the other) should be ran on docker, NOT host.

    And PLEX on a Pi takes a huge amount of resources.

    Stick to jellyfin. If configured properly, the Pi will deal with most of the files you throw at it without hogging the board.

    I started with plex but then realized that jellyfin fits better to my demands.


    It was my first try with Raspberry/OMV. So i tried a lot of stuff I saw on the internet which might lead to that "mess" system.


    Unfortunatly I have a working backup but I would need the grandfather generation.


    In that case i agree to start over again.


    Thank you all for you help!



    Code
    root@raspberrypi:~# getconf LONG_BIT
32

root@raspberrypi:~# uname -m
aarch64

  • Trying to install compose results in a long error message containing: "The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ..."

    No i did not changed he architecture from 32 to 64 bit. I was always on 64 Bit. I guess I might have recognized a change. I just did regular updates using apt update && apt upgrade. And the last thing i did before that happend was the update to OMV 6.4.8 (and updated all other stuff)


    Code
    root@raspberrypi:~# cat /etc/apt/sources.list
deb http://raspbian.raspberrypi.org/raspbian/ bullseye main contrib non-free rpi
# Uncomment line below then 'apt-get update' to enable 'apt-get source'
# deb-src http://raspbian.raspberrypi.org/raspbian/ bullseye main contrib non-free rpi
root@raspberrypi:~# ^C

  • Trying to install compose results in a long error message containing: "The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ..."

    Code
    root@raspberrypi:~# dpkg -l | grep openm
ii  libopenmpt0:armhf                    0.4.11-1                         armhf        module music libra                                                    ry based on OpenMPT -- shared library
ii  openmediavault                       6.4.8-1                          all          openmediavault - T                                                    he open network attached storage solution
ii  openmediavault-cputemp               6.1.3                            all          cpu temperature pl                                                    ugin for openmediavault
ii  openmediavault-diskstats             6.0.3-1                          all          openmediavault dis                                                    k monitoring plugin
ii  openmediavault-flashmemory           6.2                              all          folder2ram plugin                                                     for openmediavault
ii  openmediavault-keyring               1.0.2-2                          all          GnuPG archive keys                                                     of the openmediavault archive
ii  openmediavault-luksencryption        6.0                              all          OpenMediaVault LUK                                                    S encryption plugin
ii  openmediavault-minidlna              6.0.3                            all          OpenMediaVault min                                                    iDLNA (DLNA server) plugin
ii  openmediavault-omvextrasorg          6.3.1                            all          OMV-Extras.org Pac                                                    kage Repositories for OpenMediaVault


    Code
    root@raspberrypi:~# dpkg -l | grep keyring
ii  openmediavault-keyring               1.0.2-2                          all          GnuPG archive keys of the openmediavault archive
ii  raspberrypi-archive-keyring          2021.1.1+rpt1                    all          GnuPG archive keys of the Raspberry Pi OS archive
ii  raspbian-archive-keyring             20120528.2                       all          GnuPG archive keys of the raspbian archive


    Code
    root@raspberrypi:~# uname -a
Linux raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023 aarch64 GNU/Linux

  • Trying to install compose results in a long error message containing: "The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ..."

    Quote from NullIndent

    https://docs.openmediavault.or…/various/fs_env_vars.html

    Maybe you can solve the problem by reinstalling

    I could not connect the errormessages with the missing Publickey and the the missing debian-archive-bullseye-automatic.gpg file with the link you gave me, concerning about environmental variables and shared folders.


    What do you mean with "reinstalling"? Reinstallting OMV? Reinstalling RaspianOS?

  • Trying to install compose results in a long error message containing: "The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ..."

    Quote from NullIndent
    Code
    /usr/share/keyrings/docker.gpg
/usr/share/keyrings/omvextras.gpg
/etc/apt/trusted.gpg.d/debian-archive-bullseye-automatic.gpg

    Please check if these three files exist.

    It is recommended to post the error directly, because people are afraid that unknown files may carry viruses

    Thank you for your help. The first two files exist. The last one not. Is there a way to generate that file? (I am not sure why this file is missing).


    PS: I Used a txt-file cause of the size of the error message. Saw it here in the forum.

  • Trying to install compose results in a long error message containing: "The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ..."

    Sorry for the long title but i wanted to make clear what the error is.

    Just updated my OMV (on a raspi) using SSH to 6.4.8 and realized that compose is now an integral component. I wanted to migrate to compose following the manual in this forum. But i struggle with different error messages. Whatever i do (update plugins, update OMV via GUI, update OMV via ssh) i reveived a long error message where i believe the main part ist the one with the missing public key. I tried some solutions that helped others here in the forum but it doesnt work for me.


    I put the error message in a text file and attached it.


    So maybe you have a good hint for me?


    Thanks in advance

  • What does that anacron error message "no space left on device" mean

    Quote from votdev

    Please run df -h as root user and post the output here.

    Seems that /var/log is 100 % in use. Which is weired because ls -h shows me that only 29 MB of are used in that directory.

  • What does that anacron error message "no space left on device" mean

    Hi,


    since a couple of weeks i receive weekly error messages from anacron via email. But i did't understand where that error message is from, and how to handle it.


    Code
    /etc/cron.daily/openmediavault-cron-apt:
cat: write error: No space left on device

/usr/sbin/cron-apt: 119: printf: printf: I/O error
fold: write error: No space left on device
sendmail: fatal: root(0): No recipient addresses found in message header

    I have enough space left on my raspberry. I even could not remember that i set up such a job. Checking my configuration in webgui of omv I could not found such menu.


    So I would be happy if you can give me a hint, what to do with that error email.


    Greets