Linux Mint 22.2 Persistence: The Complete and Stable Guide
Creating a persistent USB stick with Linux Mint 22.2 looks easy until you actually try it. On paper it should behave exactly like Ubuntu, but in practice Mint 22.2 introduces a problem that no one expects: persistence works, but on shutdown the system explodes into an endless stream of error messages. The result is a total freeze that forces you to power off the PC physically.
Many online guides are outdated, so it’s worth explaining what is really happening and what the correct procedure is to get a persistent live session that behaves as it should.
Why Mint 22.2 Does Not Work Like Ubuntu
Mint 22.2 is based on Ubuntu 24.04, which introduces a new version of Casper, the component that manages live mode and persistence. This version is more restrictive and handles overlayfs and shutdown in a different way.
On Ubuntu, persistence support is integrated directly in the UEFI boot menu. Mint doesn’t do this. In UEFI mode, the Mint menu displays only “Start Linux Mint” and completely hides the entry that normally enables persistence.
This pushes mkusb into a hybrid configuration that technically works, but leaves shutdown in an unstable state.
Anyone who wants to use Mint portably – for example on a Mini PC or multiple machines – should switch to an alternative method based on mkusb-plug. It’s more precise and, most importantly, compatible with how Casper behaves.
👉 Read here: Persistent Ubuntu guide on USB stick
The Correct Procedure to Create a Persistent Mint 22.2 USB
The most reliable method is using mkusb-plug. This avoids the “ISO directly” mode and forces a full extraction of the image. This makes persistence recognized correctly on first boot.
The essential steps are:
insert and format the USB stick
install mkusb (follow Ubuntu’s guide for installing mkusb)
launch mkusb-plug (enter administrator password)
select the Linux Mint ISO
choose Persistent live drive
In the window below, type “u” and press ENTER, then click on “y.”
In the other window that appears, click YES and then OK (here because we need EXT4).
In the other window that appears, click NO and OK (here because we do not want iso directly).
When this window appears, PHYSICALLY REMOVE THE KEY and click OK.
In the next window, reinsert the USB stick and click OK.
A window similar to this one should appear, indicating that the USB stick has been found. Click YES. If it does not appear, you must repeat the operation.
In this step, click on “GO Yes, I want to go ahead” and then on GO, and then click on “y” to continue.
At this point, the USB stick is written and persistence is achieved (with an Intel N series and a USB 3.0 stick, the procedure should be completed in 2 minutes).
click OK
Press ENTER to exit
Your USB stick is ready. Test it to check its persistence.
This procedure works in both BIOS and UEFI modes and is currently the most stable option with Mint 22.2.
If you want a reliable USB stick with dual USB-A / USB-C connector, this model is ideal for persistent systems:
https://incastropc.com/en/products/chiavetta-usb-doppia-interfaccia-usb-a-usb-c
The Shutdown Bug
The well-known shutdown bug does not depend on the USB stick and does not depend on persistence.
Mint tries to unmount overlayfs and the ISO in an order that is not compatible with detaching the USB device in UEFI mode.
The result: a loop of “access beyond end of device” errors that goes on forever.
The important thing is that persistence continues to work normally. Only shutdown is broken.
The real fix is simple: shut down the system with this command:
sudo poweroff -f
This bypasses the faulty sequence and closes everything cleanly.
There is no need to modify grub, and you do not need to recreate the USB stick.
This behaviour isn’t exclusive to Mint. It also affects several Ubuntu-based distros released in 2024.
Until Casper is updated or Mint changes its shutdown sequence, this remains the safest method.
👉 Read Here: https://incastro.altervista.org/en/mini-pcs-2025-which-mini-pc-should-you-choose-for-the-end-of-2025/
FAQ
Is persistence stable on Mint 22.2?
Yes. Once the writable partition is created, persistence works normally. Only shutdown has a known issue.
Do I need to recreate the USB stick to fix the bug?
No. Running “sudo poweroff -f” is enough to avoid shutdown problems.
Can I use this USB stick on Mini PCs or older computers?
Yes. A persistent USB works almost anywhere, and Mini PCs are ideal for this kind of portable setup.
Will Mint fix the bug?
Probably yes. It’s inherited from Ubuntu 24.04, and future Casper updates should improve the situation.
Is it possible to assign “poweroff -f” to Power Button?
Did it with Rufus and only problems are GRUB – you have to hit Enter
and ” The Shutdown Bug” .
Yes, you can assign shutdown to the power button by editing:
sudo nano /etc/systemd/logind.conf
Find or add this line:
HandlePowerKey=poweroff
Save, then restart the service:
sudo systemctl restart systemd-logind
Avoid using poweroff -f unless absolutely necessary, because it forces shutdown and may cause filesystem problems.
For the GRUB issue (waiting for Enter), edit:
sudo nano /etc/default/grub
Set for example:
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=3
Then run:
sudo update-grub
If the PC still doesn’t shut down correctly, it could be an ACPI or hardware driver issue rather than a poweroff problem.
Hi Mike,
Thank you for your advice.
Already did that but it seems that it doesn’t work on Linux Mint
Live USB with persistance made with Rufus 🙁
At the startup on a PC with BIOS, it starts after 10 seconds or so,
but on a PC with UEFI i have to hit the Enter button.
Without taking out the USB and only pressing Enter, PC shuts down
after some “access beyond end of device” errors…
Erasmus
Hi Erasmus,
thank you for the detailed explanation now it’s much clearer.
What you’re describing is not related to HandlePowerKey, but very likely to how Rufus creates the persistent partition in UEFI mode.
The message:
“access beyond end of device”
usually indicates a persistence overlay or partition size mismatch issue.
This happens more often with Live USB created via Rufus in UEFI, especially on some firmware implementations.
A few things you can try:
1. Recreate the USB using DD mode in Rufus instead of ISO mode.
2. Or better: create the persistent USB directly from Linux using:
mkusb (recommended for Mint/Ubuntu persistence)
3. Make sure Secure Boot is disabled in UEFI.
4. Check if the USB works correctly in pure UEFI (no CSM/Legacy mixed mode).
Regarding the GRUB behavior:
On UEFI systems, GRUB sometimes waits for input if it detects previous boot inconsistencies or persistence filesystem errors. That could explain why pressing Enter triggers the shutdown with errors.
If possible, I would test the same ISO with:
• Ventoy
• or mkusb
Just to rule out a Rufus persistence issue.
Let me know what firmware mode you are using (pure UEFI or mixed CSM), and we can narrow it down further.
Mike