# Installing openBalena on Linux Mint 21 failed bad

**URL:** <https://forums.balena.io/t/installing-openbalena-on-linux-mint-21-failed-bad/375020>\
**Category:** openBalena\
**Created:** [October 30, 2025, 5:31pm UTC](https://forums.balena.io/t/installing-openbalena-on-linux-mint-21-failed-bad/375020 "2025-10-30T17:31:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jussi.savola](https://avatars.discourse-cdn.com/v4/letter/j/9e8a1a/32.png) [@jussi.savola](https://forums.balena.io/u/jussi.savola)\
**Post date:** [October 30, 2025, 5:31pm UTC](https://forums.balena.io/t/installing-openbalena-on-linux-mint-21-failed-bad/375020/1 "2025-10-30T17:31:13Z")

</div>

Getting to know openBalena, but I did not get very before catastrophic failure.  
I have a Linux Mint 21 laptop that I decided to use as server. I reckon its powers are adequate for one BalenaOS device in the same LAN.

Once in my life I decided to follow instruction by the letter, and did as it says:

**Install openBalena on the server**

1. First [Change cgroup version](https://docs.docker.com/config/containers/runmetrics/#changing-cgroup-version) to v1 for compatibility with systemd in containers on modern Linux distributions, where cgroups v2 are enabled by default:

After reboot I had a laptop with the following display content:

grub\>

… and nothing more.

It took me hours to fix the laptop, as I am no expert with grub. In addition, this is a first time when I need to mess with grub when installing software in a server computer.

The filesystem is zfs.

Here, for reference is what the situation looked on the console before the reboot.

root@koodauskone:/home/jsavola/balena-steps# source /etc/default/grub  
root@koodauskone:/home/jsavola/balena-steps# sudo sed -i ‘/GRUB\_CMDLINE\_LINUX/d’ /etc/default/grub  
root@koodauskone:/home/jsavola/balena-steps# echo GRUB\_CMDLINE\_LINUX=$(printf ‘\ “%s systemd.unified\_cgroup\_hierarchy=0”\n’ “${GRUB\_CMDLINE\_LINUX}”)  
| sudo tee -a /etc/default/grub  
GRUB\_CMDLINE\_LINUX=" systemd.unified\_cgroup\_hierarchy=0"  
root@koodauskone:/home/jsavola/balena-steps# sudo update-grub  
Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/50\_linuxmint.cfg’  
Sourcing file `/etc/default/grub.d/init-select.cfg’  
Generating grub configuration file …  
Found linux image: vmlinuz-5.15.0-151-generic in rpool/ROOT/ubuntu\_fa5ugm  
Found initrd image: initrd.img-5.15.0-151-generic in rpool/ROOT/ubuntu\_fa5ugm  
Found linux image: vmlinuz-5.15.0-140-generic in rpool/ROOT/ubuntu\_fa5ugm  
Found initrd image: initrd.img-5.15.0-140-generic in rpool/ROOT/ubuntu\_fa5ugm  
Found linux image: vmlinuz-5.15.0-41-generic in rpool/ROOT/ubuntu\_fa5ugm  
Found initrd image: initrd.img-5.15.0-41-generic in rpool/ROOT/ubuntu\_fa5ugm  
/etc/grub.d/10\_linux\_zfs: 934: GRUB\_CMDLINE\_LINUX\_DEFAULT: parameter not set  
Warning: os-prober will be executed to detect other bootable partitions.  
Its output will be used to detect bootable binaries on them and create new boot entries.  
done  
root@koodauskone:/home/jsavola/balena-steps# sudo reboot

I could not guess that the comment about GRUB\_CMDLINE\_LINUX\_DEFAULT being something or another would break up my system.

This is what ChatGPT had to say about the matter:

sudo sed -i ‘/GRUB\_CMDLINE\_LINUX/d’ /etc/default/grub

That command **deleted every line containing `GRUB_CMDLINE_LINUX`** — including both:

GRUB\_CMDLINE\_LINUX\_DEFAULT=“quiet splash”  
GRUB\_CMDLINE\_LINUX=“…”

So yes — **it wiped out** your `GRUB_CMDLINE_LINUX_DEFAULT` line entirely.

---

<div class="post-metadata">

**Author:** ![klutchell](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/klutchell/32/861_2.png) [@klutchell](https://forums.balena.io/u/klutchell)\
**Post date:** [November 6, 2025, 8:40pm UTC](https://forums.balena.io/t/installing-openbalena-on-linux-mint-21-failed-bad/375020/2 "2025-11-06T20:40:54Z")

</div>

Hey @jussi.savola , sorry to hear you had a bad experience. We have updated the instructions and removed those steps entirely as they are no longer required any more with the current services versions.

I’m glad you were able to recover your grub at the end of the day, what a stressful few hours that must have been!

---

<div class="post-metadata">

**Author:** ![jussi.savola](https://avatars.discourse-cdn.com/v4/letter/j/9e8a1a/32.png) [@jussi.savola](https://forums.balena.io/u/jussi.savola)\
**Post date:** [November 9, 2025, 9:19pm UTC](https://forums.balena.io/t/installing-openbalena-on-linux-mint-21-failed-bad/375020/3 "2025-11-09T21:19:35Z")

</div>

> [@klutchell](#):
>
> what a stressful few hours that must have been!

Indeed. The only positive thing was that I was doing the repairs on my company time, meaning that someone paid for the deed.  
I was getting to know Balena (OpenBalena) for a real purpose, as we have a fleet of … let’s say thousands of linux boxes in the wild and we are planning on doings thing better than they are now.  
A/B boot is one of the main concerns and it seems to me that with OpenBalena there is no “by the book” solution and commercial Balena is not suitable for us due to the size of our fleet.  
Next I’ll be studying swupdate and her kind.  
Anyway, I’m glad that my reporting of the problem helped someone else along the way. I’ve been working as IT quality consultant for a decade and know from experience that things won’t get fixed if nobody tells there is a problem …
