09 Jun Top Reasons You Can’t Unmount a Drive in Bazzite and How to Fix It

Your drive wants to leave. Bazzite says, “Not yet, buddy.” If you have ever clicked Unmount and got a grumpy error, you are not alone. Drives can be stubborn on Linux, especially on a gaming focused system like Bazzite.

Why Bazzite Can Be Picky About Unmounting

Bazzite is based on Fedora Atomic. It is made for gaming, daily use, and handheld PCs. It is stable. It is clever. It also uses modern Linux tools that try to protect your data.

That means it will not let you yank a drive away if files are still open. This is good. Annoying, yes. But good.

Think of it like this. Your drive is a pizza. If an app is still holding a slice, Bazzite will not let you take the box away.

Unmounting is not the same as unplugging. Unmounting tells the system to stop using the drive. Unplugging removes it from the machine. You want to unmount first. That keeps your files safe.

1. A File Manager Window Is Still Open

This is the classic one. It is also very sneaky.

You may have opened the drive in Dolphin, Nautilus, or another file manager. Even if you are not copying files, the file manager may still be looking at the folder.

Fix it:

• Close all file manager windows.
• Check tabs too.
• Do not forget split views.
• Try unmounting again.

If you are using KDE on Bazzite, Dolphin may keep previews active. Tiny thumbnails can be tiny troublemakers.

Turn off previews for that folder if needed. Or just close Dolphin fully. Simple. Effective. Slightly dramatic.

2. Your Terminal Is Sitting Inside the Drive

This one fools many people.

You may have a terminal open. Its current folder may be inside the mounted drive. That counts as “in use.” Linux sees the terminal standing in the doorway. So the drive cannot leave.

Check your terminal prompt. If it shows something like this, you found the goblin:

/run/media/yourname/DriveName

Fix it:

cd ~

That moves the terminal back to your home folder.

Then try:

udisksctl unmount -b /dev/sdX1

Replace /dev/sdX1 with your real device path. Do not guess if you are unsure.

You can list drives with:

lsblk

Look for the mount point. It will show where the drive is mounted.

3. Steam Is Using the Drive

Bazzite is popular with gamers. So Steam is often the main suspect.

If your drive contains a Steam library, Steam may keep it busy. Even when no game is running, Steam may scan files. It may update shaders. It may check downloads. It may just stare at your drive like a suspicious cat.

Fix it:

• Exit any running game.
• Pause downloads.
• Close Steam completely.
• Check the system tray.
• Try unmounting again.

On KDE, Steam may hide in the bottom right tray. Right click it. Choose Exit Steam. Do not only close the window. That often just sends Steam to the background.

If you use Heroic Games Launcher, Lutris, or Bottles, close those too. Game launchers love keeping folders open.

4. A Game Is Still Running in the Background

Sometimes a game “closes” but does not really close. Very sneaky. Very rude.

Wine, Proton, and game launchers can leave helper processes behind. These may still access the drive.

Fix it:

Open System Monitor. Search for the game name. Also search for:

• wine
• proton
• steam
• lutris
• heroic

End the process if you are sure it is safe. Do not attack random system processes like a caffeinated raccoon.

You can also use the terminal:

ps aux | grep steam

Or:

ps aux | grep wine

If something is clearly stuck, close it from the app first. Use “kill” only when needed.

5. A File Is Open in an App

A document can block unmounting. So can a song. So can a video. So can a picture.

If you opened a file from the drive in an app, that app may still be holding it. This includes:

• VLC
• LibreOffice
• GIMP
• Krita
• Audacity
• Code editors
• Archive managers

Fix it:

• Save your work.
• Close the file.
• Close the app if needed.
• Unmount again.

Some apps keep a “recent files” preview or lock. If unmounting still fails, close the whole app. Yes, the whole thing. Be brave.

6. A Copy or Sync Is Still Happening

File transfers can take longer than they look. The progress bar may disappear, but Linux may still be writing data in the background.

This is called caching. It makes things feel faster. But your drive may still be receiving data.

Fix it:

Wait a little. Then run:

sync

This tells the system to flush pending writes to disk.

After that, try unmounting again.

This is extra important for USB drives. If you unplug too soon, files may become sad confetti.

7. Indexing or Search Is Scanning the Drive

Desktop search tools can scan files. KDE may use file indexing. GNOME may use Tracker. These services help search work faster.

But sometimes they grab your external drive and start reading everything. Like a librarian with no chill.

Fix it:

• Wait for indexing to finish.
• Check system monitor for indexing services.
• Disable indexing for removable drives if it keeps happening.

On KDE, check System Settings, then search for File Search. You can adjust what gets indexed.

On GNOME, look for search settings. You may be able to exclude locations.

8. A Background Service Mounted It

Sometimes a service uses the drive. This may happen if the drive contains backups, media folders, containers, virtual machines, or network shares.

Common suspects include:

• Backup tools
• Podman containers
• Virtual machines
• Media servers
• Sync apps

Bazzite users may also run apps through Flatpak. A Flatpak app may still be using a folder on the drive.

Fix it:

• Close backup apps.
• Stop containers.
• Shut down virtual machines.
• Stop media scans.
• Quit sync clients.

For Podman, check running containers with:

podman ps

Stop one with:

podman stop container_name

Use the real container name. Do not stop random things unless you know what they are.

9. You Need to Find the Busy Process

If guessing does not work, ask Linux who is holding the drive. Linux knows. Linux always knows.

First, find where the drive is mounted:

lsblk

You may see something like:

/run/media/alex/MyDrive

Now use lsof:

lsof +f -- /run/media/alex/MyDrive

This lists open files on that drive.

You can also use fuser:

fuser -vm /run/media/alex/MyDrive

This shows processes using the mount point.

Fix it:

• Read the process names.
• Close those apps normally.
• Try unmounting again.

If a process is stuck, you can end it. First try:

kill PID

Replace PID with the process number.

If it refuses, you can use:

kill -9 PID

But be careful. kill -9 is the “dragon hammer.” It does not ask nicely. Use it only when needed.

Image not found in postmeta

10. You Are Trying to Unmount the Wrong Thing

Drives can have several partitions. One disk may contain many mount points.

For example, a USB drive may show:

• /dev/sdb1
• /dev/sdb2
• /dev/sdb3

If one partition is still mounted, the whole device may seem busy.

Fix it:

Use:

lsblk

Look for all mounted partitions on that drive. Unmount each mounted partition safely.

You can unmount by mount point:

udisksctl unmount -p /run/media/yourname/DriveName

Or by block device:

udisksctl unmount -b /dev/sdb1

After unmounting, you can power off the drive:

udisksctl power-off -b /dev/sdb

Notice the difference. /dev/sdb1 is a partition. /dev/sdb is the whole drive.

11. The Drive Has a Filesystem Problem

If the drive has errors, unmounting may act weird. This can happen after a bad unplug, power loss, or ancient USB stick drama.

Fix it:

First, unmount it if you can. Then check the filesystem.

For Linux filesystems like ext4:

sudo fsck /dev/sdX1

For Windows style drives like NTFS or exFAT, it may be better to repair them from Windows. Especially if the drive is shared between systems.

On Linux, tools exist for NTFS and exFAT, but be careful. Back up important files first.

If the drive keeps misbehaving, check its health:

sudo smartctl -a /dev/sdX

You may need to install smart tools depending on your setup. Since Bazzite is atomic, you may prefer a toolbox or distrobox environment for extra utilities.

12. Flatpak Permissions Are Making Things Confusing

Bazzite uses Flatpak a lot. Flatpak apps run in sandboxes. This is good for safety. It can also make drive access feel strange.

A Flatpak app may have access to your external drive. It may keep a file open. But it may not look obvious from the desktop.

Fix it:

• Close Flatpak apps that used the drive.
• Check apps like VLC, retro launchers, editors, and emulators.
• Use Flatseal to review permissions if needed.

Emulators are common suspects. ROM folders on external drives are often kept open. Save states may also be written in the background.

13. Your Shell, Script, or AppImage Is Running From the Drive

If you launched an app from the external drive, it may block unmounting. This includes scripts and AppImages.

Linux cannot remove the floor while the app is dancing on it.

Fix it:

• Close the app.
• Stop the script.
• Move portable apps to your home folder if you use them often.

If you run tools from a USB stick, remember this. The tool itself may be the reason the USB stick cannot leave.

A Simple Safe Unmount Checklist

Use this mini checklist when a drive refuses to unmount:

1. Close file manager windows.
2. Close files opened from the drive.
3. Exit Steam and game launchers.
4. Stop games, emulators, and media apps.
5. Move terminals away with cd ~.
6. Run sync.
7. Use lsblk to find the mount point.
8. Use lsof or fuser to find busy processes.
9. Close or stop the process.
10. Unmount with udisksctl.

Best Commands to Remember

Here are the useful little spells:

• lsblk shows drives and mount points.
• sync writes pending data to disk.
• lsof +f -- /mount/path shows open files.
• fuser -vm /mount/path shows busy processes.
• udisksctl unmount -b /dev/sdX1 unmounts a partition.
• udisksctl power-off -b /dev/sdX powers off a removable drive.

Important: Always double check device names. A wrong command can cause a bad day.

What Not to Do

Do not just pull the drive if files were recently copied. Do not run random commands from the internet without understanding them. Do not use force every time.

Linux may let you force unmount with commands like:

sudo umount -l /mount/path

That is a lazy unmount. It detaches the drive from the file tree, but busy processes may still exist. It can be useful. It can also hide the real problem.

There is also:

sudo umount -f /mount/path

But force unmount is usually for network mounts. It is not magic. Use it with care.

The best fix is still simple. Find what is using the drive. Close it. Then unmount cleanly.

Final Thoughts

When Bazzite will not unmount a drive, it is usually trying to protect you. Something is still using that drive. It may be obvious. It may be a tiny background gremlin.

Start with easy fixes. Close windows. Exit Steam. Stop games. Move your terminal. Then use lsof and fuser if the mystery continues.

Once you learn the pattern, it gets easy. Your drive stops being stubborn. Bazzite stops yelling. Your files stay safe. Everyone gets snacks.