Regarding /etc/sysctl.conf, from ChatGPT:
After updating from 7.7.24-4 to 8.x i figured out, that on the server console screen, the login screen is not cleared again, when it´s
updated (after OMV version update) with new omv-version number, at beep signal.
Run omv-salt deploy run issue to update it or reboot the system.
Nevertheless, try to remember that despite great efforts and precautions, the /etc/issue text is not always generated at the right time, which is due to the fact that the boot process and the scripts are executed asynchronously.
Here is the photo right after update to latest version and reboot (Login coming up on cosole):
Here is the photo 10 seconds later, when 'beep' signal is coming up:
with the older OMV versions the new output always overwrites the exiting bootup output...
That´s what i mean...
Best regards
prtigger
I have no idea. I only can say that OMV populates the /etc/issue file, everything else is default Debian behaviour.
As long as it works, I don't see any problem with this output being displayed multiple times. It could be a bug in Debian 13 or intentional behavior.
You may execute systemctl list-units | grep getty and post the output here.
This what I see when I ssh in - there is no mention of OMV - /etc/issue is not being displayed
Linux omv 6.14.8-3-bpo12-pve #1 SMP PREEMPT_DYNAMIC PMX 6.14.8-3~bpo12+1 (2025-09-12T11:29Z) x86_64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
You do not have any new mail.
Last login: Sun Dec 28 14:54:35 2025 from 192.168.1.50
fred@omv:~$If I take an IPMI console I get this and then the expected screen after logging out.
fred@telescope ~ $ ipmi
[SOL Session operational. Use ~? for help]
omv login: fred
Password:
Linux omv 6.14.8-3-bpo12-pve #1 SMP PREEMPT_DYNAMIC PMX 6.14.8-3~bpo12+1 (2025-09-12T11:29Z) x86_64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
You do not have any new mail.
fred@omv:~$ exit
logout
openmediavault 8.0-12 (Synchrony) omv ttyS0
Copyright (C) 2009-2025 by Volker Theile. All rights reserved.
To manage the system visit the openmediavault workbench:
br-2418a40832e0: 172.24.0.1
br-4781f1039f4d: 172.29.0.1
br-75610e35226a: 172.28.0.1
br-a8136fa38e02: 192.168.16.1
enp101s0np0: 192.168.1.51
By default the workbench administrator account has the
username 'admin' and password 'openmediavault'.
It is recommended that you change the password for this account
within the workbench or using the 'omv-firstaid' CLI command.
For more information regarding this appliance, please visit the
web site: https://www.openmediavault.org
omv login:You may execute systemctl list-units | grep getty and post the output here.
Hi
here it is:
root@pr-srv-01:~# systemctl list-units | grep getty
getty@tty1.service loaded active running Getty on tty1
system-getty.slice loaded active active Slice /system/getty
getty.target loaded active active Login Prompts
root@pr-srv-01:~#Another question:
Where is the place of generating the 'beep' signal (systemd?).
Best regards
prtigger
According to my research things have changed in Debian which results into the behaviour you can see now.
It's not great that the text is displayed twice, but it's not the end of the world. I can't see any quick and easy way to fix it. The cost-benefit factor here is simply too low to invest a lot of time in it.
Where is the place of generating the 'beep' signal (systemd?).
It is a systemd service: openmediavault-beep-up.service or openmediavault-beep-down.service
OK, i checked the screenshots again and the issue text has been changed. The OMV version has been changed, so agetty is reloaded which results in dhowing the old and new issue text. On the next reboot the problem does not appear anymore because the issue text will not change and agetty is NOT reloaded. So at the end, this behaviour is totally expected and can not be changed.
Don’t have an account yet? Register yourself now and be a part of our community!
