Posts by Mic2024

  • After OMV update, RAM temperature is no longer accessible

    I just made the latest updates offered by OMV7. I remember there also have eben some Kernel Header Updates in it.


    I think these are the last OMV updated before the problem occured:


  • After OMV update, RAM temperature is no longer accessible

    Hi everyone,


    I’m running OMV 7 on a system with DDR5 memory, and I’ve been using the OMV Kernel plugin to stay on recent Debian Backports kernels. Until last week, the RAM temperature sensor was working correctly. My monitoring stack (running in Docker) could read the DDR5 SPD temperature without any issues.

    After the most recent kernel update through the OMV Kernel plugin, the RAM temperature sensor disappeared completely. Nothing else changed on the system.


    Current kernel:

    6.14.11-5-bpo12-pve


    What I’ve verified:

    • The SPD EEPROM is still fully accessible on the I²C bus (0x50 responds normally).
    • The I²C bus itself is healthy.
    • Other SMBus/I²C devices respond correctly.
    • lsmod shows no DDR5 SPD driver loaded.
    • modinfo shows that the DDR5 SPD drivers are no longer present:
    Code
    modinfo ddr5_spd → not found
modinfo jedec_spd → not found
    • dmesg contains no references to SPD or DDR5 sensor initialization.


    Conclusion:

    It looks like the latest Backports kernel build shipped through the OMV Kernel plugin no longer includes the DDR5 SPD temperature driver. The previous 6.14.x build did include it, so this appears to be a regression in the kernel configuration.


    Request:

    Could you please check the kernel configuration for the current 6.14.x-bpo12 builds and ensure that the DDR5 SPD temperature driver is enabled again in future releases?

    This affects monitoring setups that rely on RAM temperature readings, and the hardware itself is functioning correctly.

    If needed, I can provide full logs, I²C scans, or any additional diagnostic information.

    Thanks a lot for your work and for looking into this!

    Regards
    Mic.

  • After OMV update, RAM temperature is no longer accessible

    Hello everyone,


    Today there was a major OpenMediaVault 7 update, which I installed on my PC. This included updates for the Proxmox kernel.


    Unfortunately, since the update, I've been having a problem where the RAM temperature can no longer be read. It seems as if the I²C bus of the RAM module is no longer accessible. I have installed lm-sensors to test it.


    Could this be related? Is anyone else experiencing this problem? Has anyone found a solution?


    Thank you!


    Regards
    Mic.

  • PC does not switch off after Docker Plugin updates

    Hi everyone,


    You're right, what I read online might have been wrong after all. I was able to connect a monitor. After entering `sudo halt`, the screen goes black, and after a few seconds, an excessive log appears: iptables input: ... and iptables output: .... I initially thought it was just logging and disabled it for testing purposes. However, this didn't shorten the shutdown time. It seems there's still a significant amount of network traffic during shutdown. The PC only restarts once this traffic has stopped.


    But even after the network traffic has stopped, the PC still doesn't shut itself down. That doesn't seem to work at all anymore.


    Regards,

    Mic.

  • Experience usage trash-cli on OMV7

    Hello OMV Experts,


    I habe a crazy question again but I don’t want to install anything which causes troubles in my OMV7 system. Did anybody install the tooling trash-cli on an OMV7 system? Is there anything which could cause failures in combination beween OMV7 and trash-cli? Or is there already any trash functionality in OMV7 (independent from SMB trash)? Maybe an OMV7 plugin?


    trash-cli: https://linuxnews.de/trash-cli…herere-alternative-zu-rm/


    I want to have this function to avoid deleting files by mistake in a SSH session on the command line of OMV7.


    Thank you for your feedback.


    Regards

    Mic.

  • PC does not switch off after Docker Plugin updates

    Hello together,


    in the last weeks I got some updates w.r.t. Docker Compose Plugin on my Open Media Vault 7 system (x86 Intel N100 system). I don’t know at which update it has happened but I now face the issue, that the PC is not switched off anymore after I shut it down and in case, I do a reboot it takes extremely long untils shut down is finished and a reboot does happen.


    I saw some information that this can be caused by Docker or Docker configuration. Is this a known issue? Will it be investigated and will the be an update to solve it? Or may there be another reason for this behavior?


    Thank you and regards

    Mic

  • Is it possible to install dnsutils on OMV7?

    Hello,


    I would like to use nslookup for a DynDNS update check script. It's not natively installed in OMV7. It's included in the dnsutils package. However, since I know that OMV doesn't always support the installation of tools via the command line, I wanted to ask the experts here in the forum first. Can I safely install dnsutils on an OMV7 system? Do you have any experience with this? Or better yet: Is there an plug-in from OMV or OMV extras that dnsutils automatically includes?


    Thank you!


    Regards,

    Mic.

  • Using .env file for Docker plugin

    Hello everyone,


    I wasn't sure if this would really provide security, especially since this data is still stored unencrypted in the .env file on the hard drive. Still, I was surprised that it didn't work.


    I haven't tried it yet, but I think I found how to do it correctly in the web GUI. I overlooked the little checkbox below the input field for Docker Compose, which then opens an additional input field for environment variables. Feel free to add a note to the documentation (maybe a screen shot).


    When I have time, I'll try it out and get back to you if I have any further questions. 🙂


    Thanks and regards,

    Mic.

  • Using .env file for Docker plugin

    Hello together,


    thank you for your input. According the documentation on OMV-Extras page you only can define global environmental variables (c.f. chapter 4) but no container-specific environmental variables (like using an .env file), right?


    Why did I want to use the .env file? For some containers you need to set things like a password or other “confidential” information you can see in clear text in the WebGUI. My idea was to move them in the .env file to give a (small) bit of extra security.


    Regards

    Mic.

  • Using .env file for Docker plugin

    Hi together,

    Hi ryecoaaron ,


    I wanted to use a .env file to store my environmental variables of my Docker Compose Containers (defined in the OMV7 WebGUI). According to the information I found you need to store this file in the compose folder of your container e.g., …/dockerCompose/mycontainer/.env In the Compose you use VARIABLE=${MyVariableInFile}.


    But if I do so and try to "up" the container in the WebGUI I get the response that the variable is not defined.


    Is this feature not implemented in OMV7 Docker Compose Plugin or what do I do wrong? How can I use this feature?


    Thank you in advance.


    Regards

    Mic.

  • Self-build container image status marked as "failed"

    Hello,


    thank you for your feedback. I can imagine that handling Docker from the OMV7 WebGUI is not easy.


    Here ist the output of  sudo docker image ls --all --digests --no-trunc --format "json":



    I fixed the "double images" by using docker system prune -a.


    Will you implement the fix described here on GitHub or do I need to do it as a workaround on my system? I would prefer to get it implemented in an official update. If I need to do it manually which file on my system, do I have to edit?


    Thank you and regards

    Mic.

  • Self-build container image status marked as "failed"

    Hello ryecoaaron,


    there have been updates for the Docker Compose Plugin in OMV7 and there is a small bug in the tab Images in the WebGUI. For self-build containers (defined in the tab Dockerfiles) the status is set to failed now. This is confusing. In the past I could read there just n/a which was a better information.


    Ans also due to any reason it seems when you make an update of a container available for download (by pulling it again) you get a second entry in the Images list.



    Could you kindly fix this please or tell me how to fix it on my system?


    Thank you and regard

    Mic.

  • CTerm service on Dashboard. What is it?

    Quote from ryecoaaron

    It is a system group. I didn't want people editing it in the OMV web interface. I will be listed in the list of groups when you edit your user in the omv web interface to add the user to the cterm group. No need to use the command line.

    This is fine. But which user do I need to edit. In the WebGUI I just can see my manually created docker user and smb user. No system user is listed there.