What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
If a Linux update leaves the system unbootable or breaks essential software, you can often return to a snapshot created before the update. On openSUSE Leap 15.6, the supported process is to boot a listed read-only snapshot, test it, run sudo snapper rollback when it is the correct state, and reboot into the new default system.
This is not a universal Linux procedure. It requires a pre-update snapshot, a supported Btrfs subvolume layout, and bootloader integration. Other distributions may use different tools, menus, or recovery methods; use their documentation when the screens or commands below do not match your installation.
What you need before attempting a rollback
Rollback can only select a state that was captured earlier. A snapshot made after the failed update, or no snapshot at all, cannot reconstruct the old system. Before changing anything, establish that the machine has a usable snapshot and that the installed boot path can start it.
A snapshot from before the failure
Identify when the update ran and choose a snapshot dated earlier than the first symptom. Snapper may create pre- and post-change snapshots when it is configured to do so, but automatic creation is a policy, not a property of Btrfs itself. If no suitable snapshot exists, this guide cannot create one retroactively.
#1 Best Overall
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
A supported filesystem and subvolume layout
The demonstrated openSUSE workflow expects Btrfs with the system root in the layout supported by Snapper. The openSUSE Leap 15.6 reference describes bootable rollback for a Btrfs root subvolume; it does not promise equivalent behavior for arbitrary custom subvolumes, encrypted arrangements, or another filesystem. The default openSUSE setup documentation discusses a root partition of approximately 16 GB, but that figure is a version-specific setup note, not a general Linux requirement.
A bootloader that knows about snapshots
The bootloader must be able to display and start the snapshot entries. A system can use Btrfs and Snapper yet have no snapshot menu if bootloader integration was not installed or configured. You also need a way to reach that bootloader; firmware settings, a remote console, or a rescue environment may be necessary on headless machines.
Data you cannot afford to lose
Copy important personal files to a separate backup destination before experimenting. A rollback changes the operating-system root; it is not a substitute for an independent backup of documents, databases, virtual machines, or configuration files.
What a Snapper rollback actually changes
In the Leap 15.6 model, a snapshot is a point-in-time view of the directories included in the root subvolume. Booting that snapshot lets you inspect the older state without immediately replacing the current writable root. If you confirm it is the state you want, snapper rollback creates a fresh read-write snapshot based on the selected state and makes that new snapshot the default root after reboot. The state that was running before the rollback is also preserved as a snapshot.
The operation is therefore a root-subvolume rollback, not a promise that every byte on the computer returns to an earlier date. Some directories are excluded from root snapshots, and bootloader data is not rolled back because its separate stages must remain compatible. Other subvolumes, user data, and application-specific storage may continue to contain newer content.
OpenSUSE Leap 15.6: step-by-step rollback
Use these steps only when your installation follows the documented openSUSE Snapper arrangement. The wording of boot menus can vary with firmware and bootloader configuration.
1. Reboot to the snapshot menu
- Save work and reboot the computer.
- At the bootloader, choose the entry that lists bootable or read-only snapshots. On a correctly integrated Leap installation, snapshots appear as boot choices; the newest listed snapshot is shown first.
- Select a snapshot whose date and time are before the update that caused the problem. If several candidates exist, start with the most recent one that predates the failure.
If the bootloader shows only the current system, do not guess a menu command or edit entries blindly. The absence of snapshot entries indicates that the installed integration or layout may not match this workflow.
Rank #2
- Easily store and access 5TB of content on the go with the Seagate portable drive, a USB external hard Drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
2. Inspect the candidate snapshot
Let the selected snapshot boot completely. Check the symptom that motivated the rollback: can the graphical session start, do networking and storage work, and do the affected applications behave as they did before the update? The snapshot is read-only for the directories it contains, so treat this boot as an inspection and test state. Installing packages or making permanent configuration changes here does not turn it into the new writable root.
Test enough of the system to make a reasoned choice, but do not mistake a successful login for proof that every application and data set is consistent. Files outside the captured root, services using separate subvolumes, and data written by a newer application version require additional checking.
3. Commit the selected state with Snapper
When the snapshot is the state you want to keep, open a terminal in that booted environment and run:
sudo snapper rollbackEnter your administrator credentials when prompted. Snapper prepares a new default root as a writable snapshot based on the selected state. It also keeps the pre-rollback running state as a snapshot, giving you a way to inspect or return to it if the result is not acceptable.
Free tools Windows power users keep installed
One-click scans. No signup required.
Do not substitute this command into an unrelated distribution or a custom filesystem layout. A command that is valid on Leap can fail, or produce an unexpected result, when Snapper configuration does not define the same root and snapshot relationships.
4. Reboot into the new default root
- Finish the command without interrupting it.
- Reboot normally.
- Allow the bootloader to choose its default entry. The default should now be the fresh read-write root created from the selected snapshot.
- Confirm the original update problem is gone, then check services, network connections, user accounts, and essential applications.
5. If the snapshot was not the right one
If inspection shows that the candidate is also broken, simply reboot to the current state without running snapper rollback, then try another older snapshot or a distribution-supported rescue system. If you already committed a rollback and dislike the result, the pre-rollback state is retained as a snapshot and can be inspected from the boot menu when the integration is working. Keep notes about which snapshot you tested; repeatedly switching states without checking application data can make diagnosis harder.
Why a rollback may not restore everything
The openSUSE Leap 15.6 documentation states: “A complete system rollback, restoring the complete system to the identical state as it was in when a snapshot was taken, is not possible.” Several mechanisms explain that warning.
Rank #3
- Easily store and access 1TB to content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop. Reformatting may be required for Mac
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Excluded paths and separate subvolumes
Root snapshots omit some directories. Their contents continue to reflect later changes, so a service may run older code while reading newer configuration or data. The exact excluded paths depend on the distribution’s Snapper configuration; inspect that configuration rather than assuming every directory is included.
Applications split between captured and excluded locations
An application whose executable files are in the root snapshot but whose state is elsewhere can stop working after rollback. The reverse is also possible: newer state can be presented to an older program. Preserve application data before rolling back and test each critical service afterward.
Permissions, ownership, and data formats
Files may retain permission or ownership changes that occurred after the snapshot. A program restored to an older version may also be unable to read a database or other file written in a newer format. Do not downgrade a data-producing application without verifying that its files remain compatible.
Bootloader data
Bootloader files are not rolled back with the root snapshot. Their stages must fit together, so a root rollback does not guarantee that every boot component matches the selected user-space state. If boot fails after a rollback, use the distribution’s documented rescue procedure rather than assuming another Snapper command will repair firmware or bootloader files.
Snapshots consume space and are not backups
Snapshots are stored on the same partition or subvolume as the captured state in the setup described by openSUSE. At creation they reference the same blocks; as files change, Btrfs retains changed blocks for the snapshots. Space consumption can therefore grow over time even when the live system appears small.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsDeleting a file from the current system may not free its blocks while an older snapshot still references them. Monitor available space and follow the distribution’s Snapper cleanup policy. Do not delete snapshots merely to recover space until you have verified that you no longer need them for recovery.
Because snapshots share the source storage, a failed disk, damaged partition, or accidental deletion can destroy both the live system and its snapshots. Keep irreplaceable files on an independent destination, such as an external SSD for Linux backups. That separate backup is for data recovery; it does not create a bootable Snapper rollback by itself.
Rank #4
- Easily store and access 4TB of content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
How distributions differ
Filesystem choice alone does not tell you whether rollback is available. Compare the actual snapshot policy, bootloader integration, subvolume layout, and excluded paths on your installation.
| Distribution or document | Automatic snapshots before package updates | Bootloader snapshot boot | Supported layout | Result of rollback | Important qualification |
|---|---|---|---|---|---|
| OpenSUSE Leap 15.6 documented setup | Snapper can create pre/post package snapshots when configured; verify the policy on the machine. | Supported when the installed bootloader integration lists bootable snapshots. | Btrfs root subvolume in the layout described by the Leap documentation. | A fresh read-write default root based on the selected snapshot; the previous running state is also snapshotted. | Some directories and bootloader data are outside the rollback; this is not a complete system restore. |
| Fedora Btrfs-by-default proposal (target Fedora 33; updated 2021-02-03) | The proposal explicitly described no automatic snapshots or rollbacks. | Not established by that proposal as a ready-to-use snapshot menu. | The proposal kept /boot on a small ext4 volume. |
Not specified as an implemented workflow. | This is historical planning material, not current release instructions. |
Ubuntu Focal snapper(8) manual |
Not established by the older manual as a default package-update policy. | Not established as a universal boot-menu feature. | Requires Btrfs and proper Snapper configuration. | Depends on the configured system; no universal result is stated. | The manual is version-specific and older; do not treat it as current Ubuntu setup guidance. |
The Ubuntu Focal manual summarizes the requirement as “Rollback is only supported with btrfs and requires a properly configured system.” That statement is a useful boundary, not a guarantee that an Ubuntu installation already has the required configuration. Likewise, the Fedora proposal shows why selecting Btrfs by default would not automatically provide snapshot creation or rollback menus.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Troubleshooting and safe decision points
The boot menu has no snapshots
Check whether Snapper snapshots exist and whether the installed bootloader was configured to discover them. If the root is not a supported Btrfs subvolume, or the machine boots through a different loader than the one integrated with Snapper, the Leap procedure does not apply. Consult your distribution’s recovery documentation for that layout; do not manufacture entries by copying commands from another release.
No snapshot predates the update
A snapshot made after the failure cannot restore the earlier package set. Preserve logs and important data, then use your distribution’s documented package-repair, downgrade, or rescue process. Creating a new snapshot now records the broken state; it does not recreate the missing pre-update state.
snapper rollback reports a configuration or subvolume error
Stop rather than repeating the command with altered paths. Such an error usually means the active configuration, root subvolume, or bootloader arrangement differs from the supported openSUSE setup. Verify the distribution and release documentation, especially when the system uses custom subvolumes, containers, encryption, or a nonstandard root.
The system boots, but an application is broken
Check whether its data directory is excluded from the snapshot or lives on another subvolume. Look for ownership and permission changes, and verify that the rolled-back program understands the existing data format. Restore or convert data only according to that application’s documentation; a second blind rollback can worsen a format mismatch.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallDisk space is unexpectedly low
List retained snapshots and review the configured cleanup policy before deleting anything. Changed blocks remain referenced by snapshots, and removing files from the live root may therefore have little effect. Keep at least one known-good recovery point until the replacement system has been tested and your independent backups are current.
The machine cannot reach the bootloader
This guide assumes the installed boot path is usable. If firmware settings, remote access, or a damaged bootloader prevents the menu from appearing, use the distribution’s documented rescue media and bootloader-repair instructions. Snapshot commands cannot repair a boot path that never starts the operating system.
Post-rollback verification checklist
- Confirm the running root is the new writable state and record its snapshot identifier.
- Check package-manager health and review the update logs for the change that caused the failure.
- Start critical services manually and verify they remain enabled after reboot.
- Test networking, storage mounts, scheduled jobs, authentication, and hardware drivers.
- Open applications that use databases or other structured files and validate recent records.
- Compare permissions and ownership on security-sensitive files.
- Copy newly created or irreplaceable data to an independent backup destination.
- Keep the pre-rollback snapshot until you are confident it is no longer needed, then apply the documented cleanup policy.
Bottom line
A snapshot-based rollback is a controlled way to return an openSUSE Leap 15.6 system to a known pre-update root: boot and test the older read-only snapshot, run sudo snapper rollback, and reboot into the newly created writable default. It works only when the snapshot, Btrfs layout, and bootloader integration already exist, and it cannot restore excluded paths, bootloader data, or every application’s data state. Treat snapshots as fast local recovery points and maintain separate backups for files that must survive a disk or configuration failure.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
