How to Unmount a Drive in Bazzite Without Losing Data or Files

by

Bazzite is designed to make gaming, handheld use, and desktop Linux maintenance feel smoother, but it is still Linux underneath. That means removable drives, secondary disks, SD cards, USB storage, and network mounts should be disconnected carefully. When a user unmounts a drive the right way, Bazzite finishes pending writes, releases file handles, and reduces the risk of corrupted files or damaged file systems.

TLDR: To unmount a drive in Bazzite safely, the user should first close any apps using files on that drive, then unmount it from the file manager, KDE/GNOME disk utility, or the terminal. If the drive reports that it is busy, they should identify the process using it with tools like lsof or fuser, close that process, and try again. A drive should not be physically removed until Bazzite confirms that it has been unmounted or safely ejected.

Why Safe Unmounting Matters in Bazzite

Unmounting a drive is not the same as simply unplugging it. When files are copied, moved, downloaded, extracted, or edited, Bazzite may temporarily keep some data in memory before writing it fully to the drive. This behavior improves performance, but it also means that removing a drive too quickly can interrupt unfinished writes.

If a drive is unplugged before unmounting, the user may experience missing files, corrupted saves, broken Steam library folders, or a file system that requires repair. This is especially important for external SSDs, SD cards used with handheld devices, USB flash drives, and large game storage drives.

Because Bazzite is based on Fedora Atomic technologies, some system areas are managed differently than on traditional Linux distributions. However, external and secondary storage still follows standard Linux mount behavior. The safest approach is to treat every removable drive as active until Bazzite says it is safe to remove.

Common Types of Drives a User May Need to Unmount

A Bazzite user may need to unmount several kinds of storage devices, including:

  • USB flash drives used for transferring files, ROMs, documents, or backups.
  • External SSDs or HDDs used for Steam games, media, or large archives.
  • MicroSD cards used with handheld gaming PCs or portable installations.
  • Internal secondary drives mounted for game libraries or shared storage.
  • Network shares such as SMB or NFS mounts.
  • Encrypted drives that require both unmounting and locking before removal.

Each type follows the same core principle: files should be closed, writes should be finished, and the mount should be released before the device is removed.

Image not found in postmeta

Method 1: Unmounting from the File Manager

For most users, the easiest method is the file manager. On Bazzite systems using KDE Plasma, the file manager is usually Dolphin. On GNOME-based setups, it is typically Files, also known as Nautilus.

To unmount a drive through the file manager, the user should follow these steps:

  1. Open the file manager.
  2. Look in the sidebar for the external drive, SD card, or mounted partition.
  3. Make sure no file transfer is still running.
  4. Close any document, game, emulator, terminal, or media player using files on the drive.
  5. Click the eject or unmount icon beside the drive name.
  6. Wait until the drive disappears from the sidebar or Bazzite confirms it is safe to remove.

This method is recommended for normal removable drives because it handles the mount cleanly and gives the user visual feedback. If the drive is busy, the desktop environment may show a warning. That warning should not be ignored.

Method 2: Unmounting from the System Tray or Device Notifier

On KDE Plasma, Bazzite often shows removable devices in the system tray. This is especially convenient for USB drives and SD cards. The user can open the device notifier, locate the mounted device, and select the eject or unmount action.

This approach is useful when the file manager is not open. It also gives a clear list of active removable devices. If multiple partitions exist on the same physical drive, the user may need to unmount each mounted partition before unplugging the device.

For example, an external SSD may contain one partition for games and another for backups. Both should be unmounted before the physical drive is disconnected.

Method 3: Unmounting with GNOME Disks or KDE Partition Manager

Graphical disk utilities provide more detail than the file manager. They can show partitions, file systems, labels, device paths, and mount points. In Bazzite, a user may use tools such as GNOME Disks or KDE Partition Manager, depending on the desktop environment and installed packages.

To unmount from a disk utility, the user generally does the following:

  1. Open the disk utility.
  2. Select the correct physical drive from the device list.
  3. Select the mounted partition.
  4. Click the stop, unmount, or eject button.
  5. Wait for the partition to show as unmounted.

This method is helpful when the user needs to confirm which partition is mounted. It is also useful for checking whether a drive is encrypted, mounted automatically, or formatted with a file system such as ext4, Btrfs, exFAT, or NTFS.

Method 4: Unmounting from the Terminal

More advanced users may prefer the terminal. The terminal is also useful when the graphical desktop does not show a drive properly or when a drive reports that it is busy.

First, the user should identify the mounted drive:

lsblk

This command shows disks, partitions, sizes, and mount points. A mounted external drive may appear as something like /dev/sdb1 mounted at /run/media/username/DriveName.

The user can also check mounted file systems with:

findmnt

After identifying the correct mount point, the user can unmount it with:

umount /run/media/username/DriveName

Alternatively, the device path can be used:

umount /dev/sdb1

If permission is required, the command may need sudo:

sudo umount /run/media/username/DriveName

The user should be careful when typing device names. Unmounting the wrong partition can interrupt active work. It is safer to use the mount point when the drive label is clear and recognizable.

Using UDisks for Removable Drives

On many desktop Linux systems, including Bazzite setups, removable drives are managed through UDisks. The command udisksctl is often a clean way to unmount and power off external drives.

To unmount a partition, the user can run:

udisksctl unmount -b /dev/sdb1

After unmounting, the user can power off the drive:

udisksctl power-off -b /dev/sdb

It is important to notice the difference between /dev/sdb1 and /dev/sdb. The first usually refers to a partition, while the second refers to the whole disk. The partition is unmounted first, and then the physical device can be powered off.

This method is especially useful for external USB hard drives and SSDs because it tells the system to stop using the device before physical removal.

What to Do When Bazzite Says the Drive Is Busy

A “device is busy” message means some process is still using the drive. This may be a file manager window, terminal session, game launcher, emulator, media player, backup tool, torrent client, or indexing service. The user should not force removal unless absolutely necessary.

First, they should close obvious programs. If a terminal is open inside a folder on the drive, even that can prevent unmounting. The user can move the terminal away from the mounted folder by running:

cd ~

If the drive is still busy, the user can identify active processes with:

lsof +f -- /run/media/username/DriveName

Another useful command is:

fuser -vm /run/media/username/DriveName

These commands show which processes are using the mount. After identifying them, the user can close the applications normally. If a process is frozen, it may be ended carefully through the system monitor or with a terminal command. However, killing processes should be done cautiously, especially if they are writing files.

Syncing Data Before Unmounting

Linux normally flushes pending writes during unmounting, but a cautious user may manually run:

sync

This command asks the system to write cached data to storage. It does not replace unmounting, but it can be helpful after copying large files to USB drives or SD cards. Once sync finishes, the user should still unmount or eject the drive normally.

This is particularly important when copying large game folders, backup archives, videos, or disk images. A progress bar may disappear before all cached writes have reached slower removable media.

Special Notes for Steam Libraries and Game Drives

Many Bazzite users attach external drives for Steam libraries. Before unmounting a drive containing games, Steam should be closed or at least not actively downloading, validating, or running a game from that drive. If Steam is still using the library folder, Bazzite may refuse to unmount it.

The user should check for:

  • Active downloads or updates in Steam.
  • Games still running in the background.
  • Shader pre-caching activity.
  • Emulators or launchers using ROMs or prefixes on the drive.
  • Compatibility tools, such as Proton processes, still running.

Once Steam and related processes are closed, the drive can usually be unmounted safely. This helps avoid damaged game files and prevents Steam from needing to verify large libraries later.

Unmounting Encrypted Drives

Encrypted drives require an extra step. The user must first unmount the mounted file system, then lock the encrypted container. In a graphical environment, this may appear as an eject or lock option. In the terminal, the exact command depends on how the encrypted drive was opened.

For a typical LUKS encrypted device, the user may unmount the file system first:

sudo umount /run/media/username/EncryptedDrive

Then they may close the mapped encrypted device with a command similar to:

sudo cryptsetup close mapped_name

The mapped name will vary, so the user should confirm it with tools such as lsblk. Removing an encrypted drive before closing it can cause the same data-loss problems as removing any other active drive.

Network Mounts and Remote Shares

Network shares should also be unmounted properly. If a user has mounted an SMB or NFS share, they can unmount it through the file manager or with umount. Although unplugging a network cable is different from removing a USB drive, active writes can still fail if the connection is interrupted.

For example:

sudo umount /mnt/sharedfolder

If the network mount is configured through systemd or /etc/fstab, the user may need to stop the related mount unit or adjust automount settings. For normal desktop use, however, the file manager’s unmount option is usually enough.

Best Practices to Avoid Data Loss

To reduce the risk of file corruption, a Bazzite user should follow these habits:

  • Wait for file transfers to fully complete before unmounting.
  • Close files and applications that are using the drive.
  • Use eject or unmount instead of unplugging immediately.
  • Run sync after very large transfers if extra caution is desired.
  • Do not ignore “drive is busy” warnings.
  • Unmount every mounted partition on a multi-partition device.
  • Back up important files, especially before repartitioning or formatting.

These steps may seem simple, but they are the difference between safe storage management and avoidable file damage.

What Not to Do

The user should avoid several risky habits. They should not unplug a USB drive while files are copying. They should not remove an SD card while a game, emulator, or media player is using it. They should not force unmount a drive unless they understand the consequences. They should also avoid shutting down or rebooting during active file writes unless the system is responding normally and can complete the shutdown process cleanly.

Forced unmounting options exist, but they are not the preferred solution for everyday use. A forced unmount may stop access immediately, but it can also interrupt active writes. It is better to find the process using the drive, close it, and unmount normally.

FAQ

Can a drive be unplugged after clicking eject in Bazzite?

Yes, if Bazzite confirms the drive has been ejected or it disappears from the mounted devices list, it is generally safe to unplug. The user should still wait a few seconds if the drive has an activity light that is blinking.

What does “device is busy” mean?

It means a program, terminal, background service, or file operation is still using the drive. The user should close related applications or use lsof or fuser to find the process.

Is running sync enough before unplugging a drive?

No. sync helps flush cached writes, but the user should still unmount or eject the drive. Unmounting releases the file system properly.

Can Steam prevent a game drive from unmounting?

Yes. Steam, Proton, game processes, shader caching, or downloads can keep files open. Closing Steam usually resolves the issue.

Should the user unmount or eject an external SSD?

The user should unmount the mounted partition first. For USB SSDs, using eject or udisksctl power-off afterward is also a good practice.

Is it safe to force unmount a drive?

Force unmounting should be a last resort. It can cause data loss if files are being written. The safer approach is to close the process using the drive and then unmount normally.

How can the user see where a drive is mounted?

They can run lsblk or findmnt in the terminal. These commands show device names, partitions, and mount points.

Does Bazzite handle external drives differently because it is atomic?

The system itself is managed differently, but removable and secondary drives still use standard Linux mounting behavior. Safe unmounting remains important.