[SOLVED] After kernel upgrade in Ubuntu 18.04 error: Alert! UUID=xxxx does not exist

[galopete]

Hello

My cluster:
Two servers running Proxmox 5.3-8 and a server running NAS, not HA configured.

I'm having a trouble with a VM in my cluster, recently this VM running Ubuntu 18.04 made a kernel upgrade (4.15.0-48) and before reboot the VM doesn't start with an error:

I have checked blkid using a live cd to check the UUID:

And fstab:
All seems to be ok, but the VM doesn't start...

I'm looking for solutions, and i was try some solutions that i find in www, but no luck. I have some machines running Ubuntu 18.04 upgraded with that kernel and no trouble with it, for that reason i think that this behaviour of the vm is a Proxmox problem... (not sure, but i think that...)

Any idea?

Many thanks.

Abraham.

 

[oguz]

Did you try changing the names of the drives in the /etc/fstab to the old format? (/dev/sda1 etc.) Does that solve your problem?

If not, could you post your VM config? `qm config VMID`

 

[galopete]

Did you try changing the names of the drives in the /etc/fstab to the old format? (/dev/sda1 etc.) Does that solve your problem?

If not, could you post your VM config? `qm config VMID`

Hello oguz.
Many thanks for your response.
Answering your first question: Yes i was try to modify fstab changing the UUID for /dev/sda1, but no change... same error booting the VM.
In the pics you can see the vm config, fstab and gparted info.
Thanks for your time, oguz... i will wait your suggestions.

Abraham

 

[oguz]

Hi.

Probably something went wrong during the kernel upgrade which made it not recognize the boot partition I guess. You can try booting your VM with a boot-repair live ISO and try to fix it. I can't think of anything else.

 

[Stoiko Ivanov]

* what's the output of `blkid` when run in the initramfs shell?
* regarding the change in the '/etc/fstab' you would need to run `update-initramfs -k all -u` after making that in order to put an updated fstab into the initramfs as well.

 

[galopete]

Hello Stoiko.
Thanks for your answer and sorry for the delay in my answer.
Finally i was upgrade to the new versión of the kernel (from 4.15.48 to 4.15.50) and all works normally again.
Seems to be an error in kernel 4.15.48.

BR to all
Abraham

 

[Stoiko Ivanov]

Glad the issue was resolved!
Please mark the thread as 'SOLVED' so that others know what to expect.
Thanks!