# Mender-convert creating unbootable Ubuntu Server image

**URL:** <https://hub.mender.io/t/mender-convert-creating-unbootable-ubuntu-server-image/4853>\
**Category:** General Discussions\
**Tags:** ubuntu\
**Created:** [April 12, 2022, 2:53pm UTC](https://hub.mender.io/t/mender-convert-creating-unbootable-ubuntu-server-image/4853 "2022-04-12T14:53:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![tt\_pp](https://avatars.discourse-cdn.com/v4/letter/t/e5b9ba/32.png) [@tt\_pp](https://hub.mender.io/u/tt_pp)\
**Post date:** [April 12, 2022, 2:53pm UTC](https://hub.mender.io/t/mender-convert-creating-unbootable-ubuntu-server-image/4853/1 "2022-04-12T14:53:17Z")

</div>

Hello!

I have attempted using the mender ecosystem in different setups (raspberry & qemu) and these have worked, however, running `mender-convert` on an Ubuntu Server image fails to boot.

What I have done is:

- Install an Ubuntu Server image on a x86\_64 gateway (Ubuntu 20.04)
- Clone the image (following the “golden image” principle), using `dd` to an external drive (the image size is around 100GB)
- Run `sgdisk -e /iso/ubuntu-server-clone-from-gateway.img` (as listed in the `x86-64-hdd-config`)
- Run `mender-convert` with the following command:

```auto
sudo MENDER_ARTIFACT_NAME=base-release-1 ./docker-mender-convert --disk-image input/ubuntu-server-clone-from-gateway.img --config configs/generic_x86-64_hdd_gateway_config --overlay rootfs_overlay_demo/

```

Variables set in the config:

```auto
MENDER_STORAGE_TOTAL_SIZE_MB="102400"
MENDER_BOOT_PART_SIZE_MB="256"
MENDER_DATA_PART_SIZE_MB="256"
IMAGE_ROOTFS_SIZE="-1"

```

- Putting the finished `mender-convert` image onto the gateway using `sudo dd if=/usb/mender-image.img of=/dev/sda bs=1M status=progress`
- Run `sgdisk -e /dev/sda`

After finishing, rebooting the gateway.

On boot-up, the device drops back to the grub menu:

![image](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/2X/6/67c3190455130bf03073f422a0bfa96de355a704.jpeg)

I have come across this topic: [Can't create Mender images for Ubuntu Server x64 - #16 by krystof](https://hub.mender.io/t/cant-create-mender-images-for-ubuntu-server-x64/1897/16) which listed issues when using `mender` with Ubuntu Server, however, I haven’t managed to get it working on my end. (The grub menu fallback, is the same as in the linked forum topic)

Any help would be appreciated

---

<div class="post-metadata">

**Author:** ![tt\_pp](https://avatars.discourse-cdn.com/v4/letter/t/e5b9ba/32.png) [@tt\_pp](https://hub.mender.io/u/tt_pp)\
**Post date:** [April 19, 2022, 8:12am UTC](https://hub.mender.io/t/mender-convert-creating-unbootable-ubuntu-server-image/4853/2 "2022-04-19T08:12:43Z")

</div>

Hi,  
Still running into this issue, would anyone have any possible ideas?

Thanks

---

<div class="post-metadata">

**Author:** ![tt\_pp](https://avatars.discourse-cdn.com/v4/letter/t/e5b9ba/32.png) [@tt\_pp](https://hub.mender.io/u/tt_pp)\
**Post date:** [May 9, 2022, 12:44pm UTC](https://hub.mender.io/t/mender-convert-creating-unbootable-ubuntu-server-image/4853/3 "2022-05-09T12:44:10Z")

</div>

For anyone reading and running into this issue.

A solution was found, by going into the Bios settings (on boot) and removing all the boot order options. This forces it to run the “fallback” Bios file, on boot, that `mender-convert` actually produces.

This would be nicer if a specific UEFI option would be created instead (or in addition) that would allow the selection of the file in the Bios settings (currently everything needs to be removed in the boot order, so as to call the “fallback” file)