惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

WordPress大学
WordPress大学
G
Google Developers Blog
M
MIT News - Artificial intelligence
Vercel News
Vercel News
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
GbyAI
GbyAI
B
Blog RSS Feed
Blog — PlanetScale
Blog — PlanetScale
Microsoft Security Blog
Microsoft Security Blog
V
Visual Studio Blog
Stack Overflow Blog
Stack Overflow Blog
雷峰网
雷峰网
The Cloudflare Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
F
Fortinet All Blogs
L
LangChain Blog
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
A
About on SuperTechFans
T
The Blog of Author Tim Ferriss
B
Blog
J
Java Code Geeks
Hugging Face - Blog
Hugging Face - Blog
I
InfoQ
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com

Proxmox Support Forum

[SOLVED] - Github Auth for Mirrors-Kernel Repo? [Automation] Mass migration tool for MS Win11/Server Proxmox GUI hang - not response is it possible to reject or quarantine spam based on conditions I set ? The PVENode task list in PVE9 is partially obscured due to the terminal font being too large. About 100% error reporting due to pveproxy.service hooks Kubernetes overlay networking breaks when upgrading from PVE 9.1 to PVE 9.2.3 Zentraler Speicher No space left on device Combine datastore and direct file archival to tape Kernel panic VFS: Unable to mount root fs on unknown-block (0,0) sobald ein 7.x Kernel verwendet wird. How to migrate disk of a VM from one ZFS to another Windows Server 2025 fails to boot after PVE 9.2 / Linux 7.0 Kernel upgrade Cannot Install Proxmox on T610 Poweredge with H700 PERC card sdn Config. gateway not reachable How to safely change domain/FQDN? Welche Filterquote erreicht ihr? NFS Share status unknown on 2 of 5 nodes Can't connect to PVE9 consoles [solved] Can't connect to PVE9 consoles [solved] [SOLVED] - Use secondary network for PVE commands Created cluster, one node storage gone BUG: proxmox mail gateway FROM = null bypass spam filtering Moving existing PBS from VMWare workstation to PVE cluster Does eBGP SDN fabric support external peering? Bug: PDM 1.1 not recognizing valid license status Proxmox GUI hang - not response PVE crashes unexpectedly Proxmox Backup Server 4.2 released! Advice
dmesg flooded by SysV generator
invalid@exam · 2026-06-13 · via Proxmox Support Forum

Good day
so I just upgraded my PVE host to version 9 and it worked super nice. pve8to9 gave no warnings or errors and so I figured the update will be fine.
Which it was to 99.9% ;-)
After this upgrade, my dmesg gets flooded with the messages like below. I see it has something to do with the MPT and also IPMI driver, but there are also others that give a similar warning.
So I do to 100% not understand this warning and I wonder what it is. By googling I found similar warnings, but all of them are very old (<2023) and related to Fedora, which is something almost completely different. So I wonder what this is and what is the problem here. Do I need to fix this? No clue what it actually means.

Code:

[  215.891885] systemd-sysv-generator[9266]: SysV service '/etc/init.d/mpt-statusd' lacks a native systemd unit file, automatically generating a unit file for compatibility.
[  215.891890] systemd-sysv-generator[9266]: Please update package to include a native systemd unit file.
[  215.891892] systemd-sysv-generator[9266]: ! This compatibility logic is deprecated, expect removal soon. !
[  215.893787] systemd-sysv-generator[9266]: SysV service '/etc/init.d/openipmi' lacks a native systemd unit file, automatically generating a unit file for compatibility.
[  215.893790] systemd-sysv-generator[9266]: Please update package to include a native systemd unit file.
[  215.893792] systemd-sysv-generator[9266]: ! This compatibility logic is deprecated, expect removal soon.

systemd wants to remove their legacy init script compatibility layer at some point, so it now gets noisy to get projects and distro packagers to write native systemd units as replacement for init scripts. as a user, you can't really do much there other than ignore them - unless you know the service in question and systemd well, then feel free to write your own unit and submit it upstream or with the Debian maintainers ;)

perfect! thanks for the info. So I will go ahead and just ignore these SysV messages.
Thanks!

This is still a thing in PVE 9.2.3
Removing and reinstalling openipmi does not fix it.
I guess the advice is still to ignore it.
Ok.