How to Fix “Drive Busy” When Trying to Unmount in Bazzite

Trying to unmount a drive in Bazzite and being greeted by a stubborn “drive is busy” message can feel confusing, especially when no obvious app is using the disk. The good news is that this error is usually not a sign of a broken drive. It simply means that some process, terminal session, file manager, mount point, or background service still has a handle open on the device.

Why Bazzite Says a Drive Is Busy

Bazzite is a Fedora-based Linux distribution designed with gaming, handheld PCs, and desktop usability in mind. It often uses modern desktop components such as KDE Plasma or GNOME, along with background services that make removable drives easier to handle. When you plug in an external SSD, USB flash drive, SD card, or secondary internal drive, Bazzite may automatically mount it through the desktop file manager or via udisks.

The “drive busy” message appears when Linux refuses to unmount a filesystem because it is currently in use. This is a safety feature. If the system allowed the drive to disappear while files were open or writes were unfinished, you could end up with corrupted data, broken saves, damaged media files, or an inconsistent filesystem.

Common reasons include:

• A terminal window is currently inside a folder on the drive.
• Dolphin, Nautilus, or another file manager has the drive open.
• A game launcher, emulator, or Steam library is using files on the disk.
• A media player is playing a file from the drive.
• A background indexing service is scanning the filesystem.
• A copy, move, extraction, or download operation is still running.
• A Flatpak app has access to the drive and has not released it yet.

Start With the Simple Fixes

Before opening a terminal, try the obvious solutions. They work more often than you might expect.

1. Close file manager windows that are viewing the drive.
2. Close all apps that may have opened files from it, including image viewers, video players, editors, IDEs, and game launchers.
3. Check for copy operations that are still finishing in the background.
4. Wait a few seconds after large file transfers. Linux may still be flushing cached writes to the disk.
5. Empty the trash if you deleted files from that drive. Some desktop environments keep a hidden trash folder on the same filesystem.

If you are using Bazzite on a handheld gaming device or living-room PC, also make sure Steam is not still scanning or updating a library on that drive. A game update, shader cache operation, or library verification can keep the mount busy even if no game is visibly running.

Check If Your Terminal Is the Problem

One of the sneakiest causes is the terminal itself. If your shell’s current working directory is somewhere inside the mounted drive, Linux considers the drive busy.

For example, this can block unmounting:

cd /run/media/$USER/MyDrive/roms

If that terminal remains open, the drive cannot be cleanly unmounted. The fix is simple:

cd ~

Then try unmounting again. If you have multiple terminal tabs, check each one. A single forgotten tab sitting inside a mount point is enough to trigger the error.

Find the Mount Point

To fix the issue properly, you first need to know where the drive is mounted. Removable drives in Bazzite are commonly mounted under:

/run/media/yourusername/DriveName

You can list mounted filesystems with:

findmnt

Or search for your drive name:

findmnt | grep DriveName

You can also run:

lsblk -f

This shows block devices, filesystems, labels, UUIDs, and mount points. Look for your USB drive, SD card, or external disk in the output. It may appear as something like /dev/sda1, /dev/sdb1, /dev/nvme0n1p3, or /dev/mmcblk0p1.

Use lsof to See What Is Using the Drive

The most useful command for diagnosing a busy drive is lsof, which stands for list open files. In Linux, almost everything is treated like a file, so lsof can show which programs are keeping the filesystem active.

Run:

sudo lsof +f -- /run/media/$USER/DriveName

Replace DriveName with the actual name of your mounted drive. If the path contains spaces, wrap it in quotes:

sudo lsof +f -- "/run/media/$USER/My External Drive"

The output may show a process name, process ID, user, and the file or directory being accessed. For example, you might see steam, dolphin, vlc, bash, python, or tracker.

Once you know the culprit, close the application normally if possible. If the process is a terminal shell, change its directory or close it. If it is a file manager, close the window. If it is a game platform, wait for downloads or updates to complete.

Use fuser for a Quick Process Check

Another helpful command is fuser. It can show which process IDs are using a mount point:

sudo fuser -vm /run/media/$USER/DriveName

The -v option gives verbose output, while -m checks the whole mounted filesystem. This is useful when lsof output is too long or when you want a compact list of processes.

If you identify a process that is safe to stop, you can terminate it by process ID:

kill PID

Replace PID with the actual number. Start gently with kill, which asks the process to exit. Only use kill -9 as a last resort:

kill -9 PID

Be careful: killing a process that is writing data can cause incomplete files or corruption. If the process is copying files, downloading updates, or performing disk operations, it is better to wait.

Unmount the Drive the Right Way

In a desktop Bazzite session, removable drives are often managed by udisks. If the graphical eject button fails, try using udisksctl from the terminal:

udisksctl unmount -b /dev/sdX1

Replace /dev/sdX1 with the correct partition, such as /dev/sda1 or /dev/sdb1. You can find it with lsblk -f.

You can also power off a USB drive after unmounting:

udisksctl power-off -b /dev/sdX

Notice the difference: unmounting usually targets the partition, such as /dev/sdb1, while powering off targets the whole disk, such as /dev/sdb. Do not guess. Check the device name first.

The traditional Linux command is:

sudo umount /run/media/$USER/DriveName

or:

sudo umount /dev/sdX1

If it succeeds, wait for the activity light on the drive to stop blinking before unplugging it.

Watch Out for Steam Libraries and Game Data

Bazzite is popular with gamers, so one frequent cause of busy drives is a Steam library on an external disk or SD card. Steam may keep the drive active while it:

• Downloads game updates.
• Verifies installed files.
• Syncs shader caches.
• Scans library folders.
• Runs compatibility tools such as Proton.

If your drive contains Steam games, exit Steam completely before unmounting. On KDE or GNOME, closing the Steam window may only minimize it to the tray. Use Steam > Exit, or right-click its tray icon and choose Exit Steam. Then wait a moment and try again.

Emulators and ROM managers can cause the same issue. If an emulator recently loaded a ROM, save file, texture pack, BIOS file, or configuration from the drive, close it before unmounting.

Consider File Indexers and Background Services

Desktop environments often index files to make search faster. On GNOME, services related to Tracker may scan drives. On KDE Plasma, Baloo may index files, depending on your settings. These services can temporarily hold files open.

If you see indexing processes in lsof or fuser, wait a short time and try again. If this happens constantly with a large media drive, consider excluding that drive from desktop search indexing through your system settings.

Flatpak applications can also be involved. Bazzite uses Flatpak heavily for desktop apps, and some Flatpaks may retain file access through portals. Close apps like media editors, file sync tools, torrent clients, or document editors if they accessed the drive.

Lazy Unmount and Force Unmount: Use With Caution

Linux provides more aggressive unmount options, but they should not be your first choice. A lazy unmount detaches the filesystem from the visible directory tree immediately, then cleans it up once processes stop using it:

sudo umount -l /run/media/$USER/DriveName

This can be useful when a mount is stuck but you know no critical write operation is happening. However, it can hide the problem rather than truly solving it.

A force unmount may be available in some situations:

sudo umount -f /run/media/$USER/DriveName

Force unmounting is generally more appropriate for unreachable network filesystems than for local USB drives. On local drives, it may fail or increase the chance of data problems. If the drive contains important data, avoid this unless you have no better option.

If the Drive Still Will Not Unmount

If all else fails, try logging out of your desktop session and logging back in. This closes most user applications and releases many file handles. If you are on a handheld device, switch out of game mode if necessary and handle the drive from desktop mode.

You can also reboot Bazzite. A reboot is not the most elegant fix, but it is safe and effective when you cannot identify the busy process. Before rebooting, make sure file transfers are complete. After the system restarts, unmount the drive before opening apps that might access it again.

Preventing the Problem in the Future

To avoid repeated “drive busy” errors, build a simple habit around removable storage:

• Close files before ejecting the drive.
• Exit Steam, emulators, and media apps that use the disk.
• Do not leave terminal tabs inside mounted folders.
• Wait after large transfers before unplugging hardware.
• Use udisksctl or the desktop eject button instead of pulling the cable.
• Keep backups of important files, especially on portable drives.

You should also keep your filesystem healthy. If you frequently move a drive between Linux and Windows, consider using a well-supported format. For simple cross-platform storage, exFAT is often a practical choice. For Linux-only game libraries or large collections, ext4 may be more reliable. Whatever you choose, always unmount cleanly before unplugging.

Final Thoughts

The “Drive Busy” message in Bazzite is not an enemy; it is a warning system protecting your data. The key is to identify what still has access to the drive, close or stop that process, and then unmount cleanly. In most cases, the fix is as simple as closing a file manager, exiting Steam, changing out of a terminal directory, or waiting for background activity to finish.

For tougher cases, lsof, fuser, findmnt, lsblk, and udisksctl give you the tools to see exactly what is happening. Once you understand that “busy” means “still in use,” the error becomes much less mysterious—and much easier to solve.