Fix GRUB for AWS EC2 LVM

I'm working on an AWS EC2 instance where I'm using Packer with an ebs-surrogate builder to create images. My setup includes utilizing the Logical Volume Manager (LVM), but I’ve opted to exclude the /boot directory from the LVM group. Though my system still employs the legacy BIOS, I've successfully migrated /boot. However, I'm currently encountering a significant hurdle with configuring GRUB, specifically an incorrect boot order issue. Interestingly, my operating system of choice is Ubuntu 18, and I haven't made any alterations to the GRUB configuration file located at /etc/default/grub. Ideal Skills and Experience: - Proficient with AWS EC2, specifically with using Packer (ebs-surrogate). - Solid background in managing systems with Legacy BIOS setups. - Extensive experience in configuring and troubleshooting GRUB on Ubuntu systems. - Familiarity with LVM setup on EC2 instances, and the nuances of arranging partition boot order. - Capability to work with and modify the GRUB configuration file without existing custom modifications. To ensure an efficient and precise resolution to the incorrect boot order, I'm looking for a freelancer who can bring the right mix of technical knowledge, hands-on experience, and problem-solving skills to the table. Adjusting the GRUB configuration effectively to accommodate the changes made by excluding /boot from LVM, and ensuring a seamless boot process on my Ubuntu 18 system is crucial. Your expertise will be instrumental in overcoming this challenge and further optimizing our EC2 instance setup for better performance and reliability.