Proxmox gets stuck at startup systemd[1]: Set hostname <pve>
- Thread starter flav28
- Start date
-
- Tags
- boot set hostname stuck
there was a recent post about exact same thing which the poster, unfortunately, deleted (@TheRemiDev).
the summary of my reply to it was that if you plug the last line of your screenshot into google with some keywords (boot failure linux), you will come across a lively discussion on a redhat mailer where the final solution was to update bios and firmware on the server.
https://www.google.com/search?q=boot+failure+set+hostname+to+<>
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
the summary of my reply to it was that if you plug the last line of your screenshot into google with some keywords (boot failure linux), you will come across a lively discussion on a redhat mailer where the final solution was to update bios and firmware on the server.
https://www.google.com/search?q=boot+failure+set+hostname+to+<>
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Last edited:
without knowing what you tried its hard to provide any specific guidance as from the search above it appears there could be multiple causes.
ChatGPT seems to be pretty spot on with where to start investigation
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
ChatGPT seems to be pretty spot on with where to start investigation
Code:
linux boot stuck on line "set hostname to <>"
If your Linux server is getting stuck on the boot process with the message "set hostname to <>" it can be due to a problem with the hostname configuration. Here are a few things you can check to try and resolve the issue:
Check the /etc/hostname file, it should contain the correct hostname for the system. If this file is empty or contains the default hostname, the system may be unable to set the hostname. Edit this file and set the hostname you want.
Also, check the /etc/hosts file, it should contain an entry for the hostname and IP address of the system. Make sure that the IP address and hostname match the settings you want to use.
Check the network configuration files in /etc/sysconfig/network-scripts/ or /etc/network/ for any issues, especially if you're using DHCP and the hostname is not properly resolved.
Make sure that there are no other devices on your network with the same hostname.
If you've done all this and still facing the problem. Reboot the server and check if it helps, usually, after a reboot or a hostname change you need to reboot to take effect.
If none of the above works, and you are stuck on this message for a long time, try to boot the server in rescue mode and check the hostname and network configuration files, then proceed from there.
If you continue to have issues, please provide the exact error message and any additional details about your server and network configuration that might be relevant.Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
you can find a basic guide here https://pve.proxmox.com/wiki/Recover_From_Grub_Failure
you only need a subset of the steps described in the wiki
As an experiment, I would unplug the network cable and try to boot without it.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
you only need a subset of the steps described in the wiki
As an experiment, I would unplug the network cable and try to boot without it.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
https://youtu.be/4s22pqfgu1c?t=216
Alternatively you can try to boot from any Live ISO, or, if my hunch is correct, disable network card in the bios and try to boot without it.
You should try to get in touch with OP here: https://forum.proxmox.com/threads/pve-startup-problem.120623/#post-524621
perhaps their solution will be helpful to you
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
It could be many things. A change in driver that introduced a bug, or exposed a firmware bug in your hardware, or introduced an incompatibility, or...
To find the answer you need to understand which change caused the problem. One way is to review kernel Change Log, another is to go over all the commits, 3rd option is "kernel bisect" - https://wiki.ubuntu.com/Kernel/KernelBisection
If you are not comfortable with these tasks then you have limited options:
a) Update all the firmware on every hardware piece.
b) new hardware. Either completely new server or you can start with a new NIC.
c) Stay on a known good kernel
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox