[SOLVED] edit the VM.conf file [SOLVED]
Hi guys,
Ill start this with. Never do admin audit stuffs when sick and your head is not 100% lesson learned.
So today I was doing some updates and spring cleaning on my Proxmox install. This includes approx 5 VMs
3 running Ubuntu 20.04
2 running Ubuntu 22.04
I deleted the 20.04 ISO within storage, this is the ISO I would have used for the install of the VMs.
I then also did an apt upgrade and reboot of the host machine.
The only machine to come back online is the 22.04
If I ssh onto the node what I get is below
Further digging or trying to start the VMs via CLI results in.
Now my initial thought is find the iso, re-download it, install in back into storage and reboot or restart and away we go. However, before I do that I wanted to be sure that this wouldnt break anything so
1. Is it as simple as getting the ISO and uploading it?
2. If not am I in bigger trouble?
3. Is there a risk of lost data?
On point 1. I wonder if this is the fix, why? Isnt the OS installed, why would it be using the live-server iso?
Another strange issue I came across was that the promox GUI on 8006 didnt seem responsive, hence the CLI usage. However one issue at a time.
Cheers in advance
/Rattle
Hi guys,
Ill start this with. Never do admin audit stuffs when sick and your head is not 100% lesson learned.
So today I was doing some updates and spring cleaning on my Proxmox install. This includes approx 5 VMs
3 running Ubuntu 20.04
2 running Ubuntu 22.04
I deleted the 20.04 ISO within storage, this is the ISO I would have used for the install of the VMs.
I then also did an apt upgrade and reboot of the host machine.
The only machine to come back online is the 22.04
If I ssh onto the node what I get is below
Code:
root@vm:~# qm list
VMID NAME STATUS MEM(MB) BOOTDISK(GB) PID
100 pi.mgmt.xxxx stopped 2048 64.00 0
101 greylog.xxxxx stopped 8192 400.00 0
102 cacti.xxxxx stopped 6144 100.00 0
103 web.xxxxx running 4096 32.00 1377
104 ha.xxxxx running 4096 32.00 38217Further digging or trying to start the VMs via CLI results in.
Code:
root@vm:~# qm start 100
volume 'Storage:iso/ubuntu-20.04.3-live-server-amd64.iso' does not existNow my initial thought is find the iso, re-download it, install in back into storage and reboot or restart and away we go. However, before I do that I wanted to be sure that this wouldnt break anything so
1. Is it as simple as getting the ISO and uploading it?
2. If not am I in bigger trouble?
3. Is there a risk of lost data?
On point 1. I wonder if this is the fix, why? Isnt the OS installed, why would it be using the live-server iso?
Another strange issue I came across was that the promox GUI on 8006 didnt seem responsive, hence the CLI usage. However one issue at a time.
Cheers in advance
/Rattle
Last edited: