Lost Disk Storage After Host Name Change No Containers/VMs Boot

[Zac8236]

Hello,

I tried to change my host name, after I did that, I tried to move all the files from /etc/pve/nodes/OldHost to /etc/pve/nodes/NewHost. But some files wouldn't copy. I tried to restart the server and it has messed up the config.db, the GUI wouldn't work etc.

After deleting the config.db and letting Proxmox rebuild it on a boot, I copied the VM config files into /etc/pve/nodes/Host and restarted. My containers and VMs now show up in the GUI.

But when I try to run the VM or container I get an error

Job for pve-container@101.service failed because the control process exited with error code.
See "systemctl status pve-container@101.service" and "journalctl -xe" for details.
TASK ERROR: command 'systemctl start pve-container@101' failed: exit code 1

So I ran systemctl status pve-container@101.service

● pve-container@101.service - PVE LXC Container: 101
   Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2018-04-27 21:29:25 BST; 5s ago
     Docs: man:lxc-start
           man:lxc
           man:pct
  Process: 2871 ExecStart=/usr/bin/lxc-start -n 101 (code=exited, status=1/FAILURE)

Apr 27 21:29:24 mercury systemd[1]: Starting PVE LXC Container: 101...
Apr 27 21:29:25 mercury lxc-start[2871]: lxc-start: 101: lxccontainer.c: wait_on_daemonized_start: 815 No such file or directory - Failed to receive the container state
Apr 27 21:29:25 mercury lxc-start[2871]: The container failed to start.
Apr 27 21:29:25 mercury lxc-start[2871]: To get more details, run the container in foreground mode.
Apr 27 21:29:25 mercury lxc-start[2871]: Additional information can be obtained by setting the --logfile and --logpriority options.
Apr 27 21:29:25 mercury systemd[1]: pve-container@101.service: Control process exited, code=exited status=1
Apr 27 21:29:25 mercury systemd[1]: Failed to start PVE LXC Container: 101.
Apr 27 21:29:25 mercury systemd[1]: pve-container@101.service: Unit entered failed state.
Apr 27 21:29:25 mercury systemd[1]: pve-container@101.service: Failed with result 'exit-code'.

This happens on all of the VMs or containers.

I think the disk containing the VM image is missing as it doesn't seem to be mounted (shown in pic).


If anyone could point me in the right direction that would be awesome!

Thanks very much,
Zac.

 

[Richard]

Hello,

I tried to change my host name, after I did that, I tried to move all the files from /etc/pve/nodes/OldHost to /etc/pve/nodes/NewHost. But some files wouldn't copy. I tried to restart the server and it has messed up the config.db, the GUI wouldn't work etc.

After deleting the config.db and letting Proxmox rebuild it on a boot, I copied the VM config files into /etc/pve/nodes/Host and restarted. My containers and VMs now show up in the GUI.

But when I try to run the VM or container I get an error

Job for pve-container@101.service failed because the control process exited with error code.
See "systemctl status pve-container@101.service" and "journalctl -xe" for details.
TASK ERROR: command 'systemctl start pve-container@101' failed: exit code 1

So I ran systemctl status pve-container@101.service

● pve-container@101.service - PVE LXC Container: 101
   Loaded: loaded (/lib/systemd/system/pve-container@.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2018-04-27 21:29:25 BST; 5s ago
     Docs: man:lxc-start
           man:lxc
           man:pct
  Process: 2871 ExecStart=/usr/bin/lxc-start -n 101 (code=exited, status=1/FAILURE)

Apr 27 21:29:24 mercury systemd[1]: Starting PVE LXC Container: 101...
Apr 27 21:29:25 mercury lxc-start[2871]: lxc-start: 101: lxccontainer.c: wait_on_daemonized_start: 815 No such file or directory - Failed to receive the container state
Apr 27 21:29:25 mercury lxc-start[2871]: The container failed to start.
Apr 27 21:29:25 mercury lxc-start[2871]: To get more details, run the container in foreground mode.
Apr 27 21:29:25 mercury lxc-start[2871]: Additional information can be obtained by setting the --logfile and --logpriority options.
Apr 27 21:29:25 mercury systemd[1]: pve-container@101.service: Control process exited, code=exited status=1
Apr 27 21:29:25 mercury systemd[1]: Failed to start PVE LXC Container: 101.
Apr 27 21:29:25 mercury systemd[1]: pve-container@101.service: Unit entered failed state.
Apr 27 21:29:25 mercury systemd[1]: pve-container@101.service: Failed with result 'exit-code'.

This happens on all of the VMs or containers.

I think the disk containing the VM image is missing as it doesn't seem to be mounted (shown in pic).
View attachment 7364

I guess storage configuration is missed (note: after deleting the db all pve configuration except network is lost).