You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The grub.cfg file lives in /boot/grub/grub.cfg. This will work without an issue when grub.cfg is in the / filesystem (as the case for Ubuntu 22.04 cloud image). However with Ubuntu 24.04, the grub.cfg file lives in /grub/grub.cfg in
BLOCK_DEVICE: {{ formatPartition ( index .Hardware.Disks 0 ) 16 }}
and it boots until it says Boot arguments must include a root= parameter.
Expected Behaviour
When the /boot directory is mounted and not part of the / filesystem, allow an extra parameter for the location. When /dev/sda16 is mounted as /boot, we can have an extra parameter that defaults to /boot/grub/grub.cfg but could be changed to /grub/grub.cfg. Maybe something like GRUB_CFG_PATH?
Current Behaviour
After specifying the BLOCK_DEVICE for the /boot directory, the assumption is that the /boot/grub/grub.cfg file lives relative to /.
Unable to use Ubuntu 24.04 cloud image because it mounts /boot on a different partition. This is not an issue with Ubuntu 22.04 as the /boot directory is not on a partition on its own.
Your Environment
Operating System and version (e.g. Linux, Windows, MacOS):
How are you running Tinkerbell? Using Vagrant & VirtualBox, Vagrant & Libvirt, on Packet using Terraform, or give details:
Using an environment with Mini PC (N95 Celeron) and Mikrotik router
Link to your project or a code example to reproduce issue:
The text was updated successfully, but these errors were encountered:
The grub.cfg file lives in
/boot/grub/grub.cfg
. This will work without an issue whengrub.cfg
is in the/
filesystem (as the case for Ubuntu 22.04 cloud image). However with Ubuntu 24.04, thegrub.cfg
file lives in/grub/grub.cfg
inI manged to specify these values:
and it boots until it says
Boot arguments must include a root= parameter
.Expected Behaviour
When the
/boot
directory is mounted and not part of the/
filesystem, allow an extra parameter for the location. When/dev/sda16
is mounted as/boot
, we can have an extra parameter that defaults to/boot/grub/grub.cfg
but could be changed to/grub/grub.cfg
. Maybe something likeGRUB_CFG_PATH
?Current Behaviour
After specifying the
BLOCK_DEVICE
for the/boot
directory, the assumption is that the/boot/grub/grub.cfg
file lives relative to/
.Possible Solution
Steps to Reproduce (for bugs)
Use Ubuntu 24.04 cloud image from https://cloud-images.ubuntu.com/daily/server/noble/current/
Context
Unable to use Ubuntu 24.04 cloud image because it mounts
/boot
on a different partition. This is not an issue with Ubuntu 22.04 as the/boot
directory is not on a partition on its own.Your Environment
Operating System and version (e.g. Linux, Windows, MacOS):
How are you running Tinkerbell? Using Vagrant & VirtualBox, Vagrant & Libvirt, on Packet using Terraform, or give details:
The text was updated successfully, but these errors were encountered: