Posts by oopenmediavault

    Yeah, I understand, just wanted to show that this exists, in case someone has interest in it. I use it and it works flawlessly to setup connections between servers. The Firewall can be configurated via ACLs online. I don't combine it with the OMV plugin though. Just by itself via cli.

    I am using the wd elements 12TB and I do have SMART via USB. Maybe it is not supported on smaller ones.

    You could try taking a look at the inside model, it is easy to get the casing away without damage. Just look up some youtube videos. Then google the model of your disk

    I am not at all an expert in this, but heres what I would do just to make sure everything is as it should be...

    1) Check if the disk is successfully recognized by your server, you can search through the output of this command

    sudo fdisk -l

    2) Check if the smart services are running


    systemctl status smartmontools.service

    systemctl status smartd.service

    3) Start them if necessary (and enable)


    systemctl start smartmontools.service

    systemctl start smartd.service

    systemctl enable smartmontools.service

    systemctl enable smartd.service

    4) Reboot (just for good measure)

    5) check output of "sudo smartctl -a /dev/sdx" (with x being the wd disk) and see if it works and gives back results

    6) Check in WebGUI if smart monitoring is enabled

    7) Check in WebGUI if you can view the smart details

    Try deleting the databases. They will be recreated

    rm -r /var/lib/rrdcached/db/localhost
    systemctl restart rrdcached.service

    I think this solved it. Starting the Monitoring in the WebGUI and checking syslog output doesnt show any error like before anymore. I can also visit the monitoring graphs normally. So I would say this is solved.

    Thank you a lot!

    You should start a transcode and check the logs in jellyfin. you Can do something like

    cat /config/log/FFmpeg.Transcode.find-our-own.log | grep "Stream map" -A2

    This will give an output of how it was transcoded, if it shows hevc or qsv or something, or whatever hwa you are using, it works.

    For me it gives out this:


    Stream mapping:

    Stream #0:0 (hevc) -> setparams:default

    overlay_qsv:default -> Stream #0:0 (h264_qsv)


    Da du noch angibst, Anfänger zu sein, gebe ich dir folgenden Rat: Ändere nichts, wovon Du noch nicht verstanden hast was es tut.

    Ich würde nicht das System, das du geklont hast, verwenden, da es vermutlich, auch wenn es noch halbwegs läuft, sämtliche Fehler hat, die unkorrigierbar sind und das System unvorhersehbar crashen können.

    Es ist besser eine frische Installation zu machen. Mach screenshots oder schreib dir auf, welche Plugins du schon installiert hattest. und merk dir die wichtigen Dinge, die du geändert hast. (wie. z.B. automatische Backups mit dem backup-plugin)

    Dann nimm dir einen frischen USB stick und installiere neu. Die Festplatten, die am server angeschlossen sind, werden dabei nicht verändert!

    I was running the omv-salt deploy command, unfortunately, it did not help, as shown below. What I find weird is that I did not change anything regarding the Monitoring or something connected to it, so I wonder why it started doing this now?!

    Syslog also showed following.

    Dec  2 21:50:06 openmediavault monit[487322]: There is no service named "collectd"
    Dec  2 21:53:12 openmediavault monit[1457]: Monit daemon with PID 1457 awakened
    Dec  2 21:53:12 openmediavault monit[1457]: Awakened by User defined signal 1
    Dec  2 21:53:17 openmediavault monit[1457]: HttpRequest: error -- client []: HTTP/1.0 400 There is no service named "proftpd"
    Dec  2 21:53:17 openmediavault monit[501297]: There is no service named "proftpd"
    Dec  2 21:53:19 openmediavault monit[1457]: HttpRequest: error -- client []: HTTP/1.0 400 There is no service named "rrdcached"
    Dec  2 21:53:19 openmediavault monit[501337]: There is no service named "rrdcached"

    After I ran the omv-salt command, I started the Monitoring from the Web-GUI again, with following result in syslog spammed again.

    yes, but sometimes it is possible to see that a process was tried to be killed because it uses too much ram or other things,

    I'm using pretty many containers (around 30-40) so maybe one of them is doing something it shouldnt. I also check my usage with node_exporter and grafana, but shortly before the system crashed, there was still enough RAM... unfortunately, also there, there was the last 10 minutes missing.

    Im still pretty sure it was a RAM issue, since in the OMV CLI (via a screen attached to the server), it was lagging pretty much, wasnt able to type anything, but it still reacted sometimes on keystrokes.

    My solution to check what could be the cause now, is to periodically write the output of the top command of the top 5 memory consuming processes via cron to another server. With this I may be able to determine what could be the cause if it happens again

    OMV isn't crashing though. Linux is.

    I only recommended that because it seemed like it wasn't an instant crash and you could see logs leading up to the crash.

    If only the OS is on the usb stick and other things like docker are running from data disks/ssds and the flashmemory plugin is installed, the only reason the system should crash is a junk usb stick or running out or memory or hardware is unstable.

    Thats why I want to see the logs to determine what would use up the RAM.

    Anyways, so if I will symlink /var to another drive, the flashmemory plugin will still create the folder2ram fs, is that correct? So in order to have them written directly, I would still have to disable the plugin ( may it even just be for the period until I found out what crashes my "linux"