Failed to start The Proxmox VE cluster filesystem after apt update

[drthrax232]

Recently one of our mashines started automatic update. Later this day we are unable to access it. After we finaly had phisycal access node changed it's hostname to one of VM's hostnames (previously node3-pl now VM1002) and started to act as if it is VM but in the same time it isn't VM. Data is not corrupted, we performed lvscan that shows all VM disks untouched.

Other nodes from cluster works fine just this one has some issues.

We does not changed anything in server's configuration it just suddenly changed it's hostname and stated to act weirdly.

 

[oguz]

hi,

After we finaly had phisycal access node changed it's hostname to one of VM's hostnames (previously node3-pl now VM1002) and started to act as if it is VM but in the same time it isn't VM.

that's weird, not sure what would cause that...

Recently one of our mashines started automatic update.

what kind of automatic update? PVE doesn't have automatic updates...

We does not changed anything in server's configuration it just suddenly changed it's hostname and stated to act weirdly.

can you check the /etc/hosts file? you'll probably have to reset the hostname back to the original value (for things to start working normally again).

you should probably also take a look at the syslog and journals on that node to narrow down the cause of the problem.