VMware Aria

 View Only

  • 1.  Patching ASLCM with 8.18 PATCH3 ends up with "Failed to mount /boot"

    Posted 2 days ago

    Patching a ASLCM 8.18.0 PATCH1 or PATCH2 to PATCH3 ends up with my ASLCM not booting; it's suddenly not able to mount /boot. Anyone experienced that? I have started a support case (SR 36510492) earlier today, but just wanted to check if anyone else have had the same problem, and if it was solved.

    After about 30 minutes of the script installing the PATCH3 the VM reboots, and it goes into emergency mode like this:

    If I log in with root password, I can mount /boot just fine with "mount /dev/sda2 /boot" manually.

    Followed the instructions from the release notes about temp folders and symlinking it. (/tmp/ partition will fill up if not).



    -------------------------------------------


  • 2.  RE: Patching ASLCM with 8.18 PATCH3 ends up with "Failed to mount /boot"
    Best Answer

    Posted 2 days ago

    So I got at it again this morning, and I found the problem. You need to edit fstab and remove "noacl" from /dev/sda2 line.

    I wrote a blog post about it: https://vmnic.com/2025/07/31/preventing-failed-to-mount-boot-after-aria-suite-lifecycle-8-18-0-patch3-upgrade/

    -------------------------------------------

    Original Message