After uninstalling flashmemory plugin with GUI for a test, reinstalling plugin again, i got nginx.service startup error, coming up on server console!

  • ryecoaaron

    Just to keep you informed:

    /var/log/smbd was missing, too. But during boot, there is no error coming up! Taking a look with journalctl was showing me this problem.

    So i was able to create the missing folder again....


    Do you have any advice, how to clear all generated logs (and log-rotates) on the system? This may be a solution for getting rid of the nginx

    error, with the old flashmemory plugin. I installed it again (Now it´s working without nginx boot error logging).


    This strange Linux thing:

    Mär 16 09:57:57 pr-srv-01 kernel: ERST: Failed to get Error Log Address Range.

    ......

    Mär 16 09:57:57 pr-srv-01 kernel: APEI: Can not request [mem 0xbff9a740-0xbff9a793] for APEI BERT registers


    I surfed around a lot...

    With my stupid understanding: Linux system is trying to report an system error to permanent ACPI Database, that isn´t present on this

    system/BIOS... Linux system should clear this (don´t know, at what time, state or how).... Ok my system is very old...

    6.12.x kernel is throwing CPU warnings during boot i´m not seeing with 6.1.x stable kernel... (May be normal due old hardware)

    But i had no bootup errors with both kernels before the 03/15/2025 (and i´m not taking a look with journalctl before).


    Solutions offered:

    - Ignore!

    - Disable ACPI with command "acpi=off" in boot grub 2 (I guess, not a good solution)


    At this time, i guess: There must be a solution for kernel/system ERST error logging. They must be saved permanent anywhere!? It´s not in BIOS.

    I will try do a clean new installation of OMV... Taking a look, if errors will go away. Need some time for this...


    I don´t want to bother you with this stuff, because it´s a kernel/system specific problem...

    But i´m still learning all the necessary Linux stuff at this time... But this issue is for the experts!


    Debugging was one of my skills, when i was working in the past... But my knowledge is not great enough, right now....

    (Most people will choose 'Ignore', i´m different... ;) )


    Best regards

    and thanks for all of your work here!

    prtigger

    Old (2011) Supermicro 1U Rackserver X7SPA-HF, Intel Atom D510, 4GB RAM (maximum) | System: Supermicro SATA DOM 64GB SSD | Data: 3*Samsung 870 QVO 4TB SATA (Btrfs Raid1) | OMV 8.x services: SSH, SMB, NFS, MiniDLNA | 6.12.x kernel | Bare-metal

  • This strange Linux thing:

    Mär 16 09:57:57 pr-srv-01 kernel: ERST: Failed to get Error Log Address Range.

    ......

    Mär 16 09:57:57 pr-srv-01 kernel: APEI: Can not request [mem 0xbff9a740-0xbff9a793] for APEI BERT registers

    Information: Clean reinstall of OMV is not solving this (with Clearing CMOS and reconfiguring the Bios)... No idea anymore...


    Solutions offered:

    - Ignore!

    - Disable ACPI with command "acpi=off" in boot grub 2 (I guess, not a good solution)

    Setting acpi=off is working (no errors displayed anymore, but when i´m initiating a shutdown, system is not powering 'off' anymore....

    I have to press the power button at the server.... No Solution!


    Finally:

    I know, i hadn´t this output before. No idea what changed... Nobody knows....

    A friend of mine has got the same system, but he is running XignaNAS at this time. So i can´t compare my system with his server...


    At this time i had to ignore this!


    Do you have any advice, how to clear all generated logs (and log-rotates) on the system? .........

    I find a solution....


    Best regards

    prtigger

    Old (2011) Supermicro 1U Rackserver X7SPA-HF, Intel Atom D510, 4GB RAM (maximum) | System: Supermicro SATA DOM 64GB SSD | Data: 3*Samsung 870 QVO 4TB SATA (Btrfs Raid1) | OMV 8.x services: SSH, SMB, NFS, MiniDLNA | 6.12.x kernel | Bare-metal

    • Official Post

    Clean reinstall of OMV is not solving this (with Clearing CMOS and reconfiguring the Bios)..

    It isn't a bad install or OMV causing it. It is an incompatibility in your bios with the linux kernel. A kernel update or different version of the kernel could cause this. But I don't know why this is bugging you so much. Is it causing a problem other than the message?

    omv 8.0.10-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.4 | compose 8.1.2 | cterm 8.0 | borgbackup 8.1 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Hi Aaron

    I only know that i don't have since i installed 7.0.x... from scratch....

    It's coming up with the older kernel

    from OMV Iso, too... It's just bothering me.

    ...

    More interesting are the CPU warnings

    in the bootlog when using 6.12.12bpo kernel.

    The 6.1.x stable kernel is showing nothing like that. Maybe, The Atom D510 is to old...

    But it's only a "cut here" warning and system is running... But this is Linux stuff...


    Best regards

    prtigger

    Old (2011) Supermicro 1U Rackserver X7SPA-HF, Intel Atom D510, 4GB RAM (maximum) | System: Supermicro SATA DOM 64GB SSD | Data: 3*Samsung 870 QVO 4TB SATA (Btrfs Raid1) | OMV 8.x services: SSH, SMB, NFS, MiniDLNA | 6.12.x kernel | Bare-metal

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!