Hostname change on interface causes raspberry os lite to fail on boot

[GloriousGloria23]

Describe the bug
Installed omv on Raspberry os lite. After setup, I changed the hostname in the UI. System went into reboot but got stuck and did not finish. ssh failed to connect.
Even after directly connecting monitor, system was not responsive and screen turned black after initial boot sequence.
Mounted the drive on another linux machine, manually reverting the hostname in the /etc/hostname file solved the issue and system rebooted normally.

To Reproduce

Steps to reproduce the behavior:

1. Go to omv -> Network -> General -> Hostname
2. Change Hostname
3. click Save
4. automated reboot failed

Expected behavior

successful reboot with new hostname

openmediavault Server (please complete the following information):

• OS version: Linux 6.6.20+rpt-rpi-v8 Prevent fatal error in autoloader #1 SMP PREEMPT Debian 1:6.6.20-1+rpt1 (2024-03-07) aarch64 GNU/Linux
• openmediavault version: 7.0.5-1

Client (please complete the following information):

• Device: PC
• OS: Win 11
• Browser firefox
• Version 124

[votdev]

OMV is more or less exactly doing the same like raspi-config.

• https://github.com/RPi-Distro/raspi-config/blob/351366eaf28416fce1253a7a2569457e3d7570a4/raspi-config#L855

• openmediavault/deb/openmediavault/srv/salt/omv/deploy/hostname/default.sls

  Line 25 in 0a326a2

  configure_hostname:

• openmediavault/deb/openmediavault/srv/salt/omv/deploy/hosts/10default.sls

  Line 34 in 0a326a2

  configure_hosts_header:

If the problem is only on Raspi hardware, then it will be hard for me to reproduce and fix it without having such hardware.
In that case the community must provide a fix.

[votdev]

Can not reproduce this issue. So it seems to me that this problem is specific to your system or Raspi OS based systems in special.

[votdev]

Where exactly does the system hang? What service is not starting or reports an error?

[GloriousGloria23]

I wish I knew, the problem is that as soon as it happened I completely lost access to the device. Ping would not respond (and therefore I couldn't SSH into the machine), and hooking it up to a monitor ended up with a blank screen (I tried two different monitor). I tried taking a video to see where it would hang but it went so fast it came out blurry.

Is there a way to find out where it hangs by reading a log file? I can try to reproduce it again on a new SD card sometimes next week (I dare not do it again on my running NAS :D )

[votdev]

You can use journalctl -b to get the last boot log or use journalctl --since today for the whole day.