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

Discussion in 'Proxmox VE: Installation and configuration' started by galopete, Apr 28, 2019.

  1. galopete

    galopete New Member

    Joined:
    Feb 27, 2019
    Messages:
    3
    Likes Received:
    0
    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:
    Captura de pantalla de 2019-04-28 22-17-16.png
    I have checked blkid using a live cd to check the UUID:
    blkid.png
    And fstab:
    fstab.png 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.
     
  2. oguz

    oguz Proxmox Staff Member
    Staff Member

    Joined:
    Nov 19, 2018
    Messages:
    604
    Likes Received:
    63
    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`
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. galopete

    galopete New Member

    Joined:
    Feb 27, 2019
    Messages:
    3
    Likes Received:
    0
    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. aa fstab.png aa gparted.png aa qm config.png
    Thanks for your time, oguz... i will wait your suggestions.

    Abraham
     
  4. oguz

    oguz Proxmox Staff Member
    Staff Member

    Joined:
    Nov 19, 2018
    Messages:
    604
    Likes Received:
    63
    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.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. Stoiko Ivanov

    Stoiko Ivanov Proxmox Staff Member
    Staff Member

    Joined:
    May 2, 2018
    Messages:
    1,271
    Likes Received:
    118
    * 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.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. galopete

    galopete New Member

    Joined:
    Feb 27, 2019
    Messages:
    3
    Likes Received:
    0
    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
     
  7. Stoiko Ivanov

    Stoiko Ivanov Proxmox Staff Member
    Staff Member

    Joined:
    May 2, 2018
    Messages:
    1,271
    Likes Received:
    118
    Glad the issue was resolved!
    Please mark the thread as 'SOLVED' so that others know what to expect.
    Thanks!
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    galopete likes this.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice