How to upgrade Nitrux

Upgrading Nitrux is easy. We support two methods: using a utility created specifically for this purpose, the Nitrux Update Tool System, or using Calamares—yes, you read that right.

In today’s tutorial, we’ll check how to do this.

Difficulty: ★☆☆☆☆

Upgrade Process Information

Below is the information we’ve deemed important for users to understand about this distribution and its upgrade process.

• We aim to release new upgrade archives for the Nitrux Update Tool System during the weeks following a new release. Sometimes, this period may extend. Either way, we announce the update archive’s availability on our social media, in our chat groups, and in the PSA section on this website.
  • ⚠️ Important: We recommend that users check the PSA for the release they’re updating to for additional information relevant to the OTA.
• The OTA update archives for the Nitrux Update Tool System are designed for updating only from the previous release to the latest release (e.g., 3.4.0 → 3.4.1 or 3.4.1 → 3.5.0). To upgrade from a non-continuous release, see Upgrade using Live media (Calamares).
  • 🔰 Information: Regarding the OTA archives, we delete the previous files whenever a new archive is uploaded. We do not maintain an online archive of these files or the ISOs.
• Starting with Nitrux 6.0.0, the Nitrux Update Tool System automatically checks for updates on launch. However, the utility doesn’t force updates (offline updates); users are still responsible for keeping their installations up to date.
• The Nitrux Update Tool System does not modify files in the user’s home directory or create backups of the user’s home directory.

Upgrade using the Nitrux Update Tool System

The Nitrux Update Tool System is a simple, minimalistic update and rollback utility. It performs three steps:

1. It backs up the XFS root partition and stores it locally.
2. Then, it downloads an OTA-style archive and updates the system atomically.
3. Rollbacks are handled offline and integrated into the Nitrux.

See the steps below to use the Nitrux Update Tool System.

Update Nitrux

1. Launch NUTS from the applications menu.
2. Click the “Update Now ” button to upgrade the distribution.
   • 🔰 Information: Update completion time depends on various factors, such as system specifications, connection speed, connectivity to GitHub, and connectivity to SourceForge or its mirrors.

Rollback Nitrux using NUTS

1. Boot a Nitrux Live ISO.
2. Launch NUTS from the applications menu.
3. Click the “Rescue” button to rollback the distribution.
   • 🔰 Information: The user can only use this operation during a Live session.

Rollback Nitrux using Rescue Mode

1. Boot Nitrux and press Escape after the manufacturer logo appears, but before the boot splash.
2. Select “Nitrux Rescue Mode” from the menu and press Enter.
3. Wait until the process completes.
   • 🔰 Information: For further details about Rescue Mode, see System Management → System Administration → Nitrux GRUB Modes.

Upgrade using Live media (Calamares)

Using an installer like Calamares to update the system is uncommon. In this approach, the system replaces the NX_ROOT and NX_VAR_LIB partitions while preserving user and other state partitions. This creates a new system image while keeping existing user data intact.

This procedure requires a separate root partition distinct from your user partitions. Most Linux distributions use a single partition that contains everything, making selective root replacement impossible. That’s why Nitrux uses a custom partition layout and emphasizes avoiding a single-partition layout during initial installation.

This process preserves the state of the root filesystem. Unlike a conventional reinstall that replaces all partitions, this method installs a new root filesystem from updated installation media while preserving existing user and data partitions.

• ⚠️ Important: This procedure is not supported in encrypted setups due to limitations in the installer’s partition handling.

To upgrade from previous versions of Nitrux using Calamares, do the following:

• Download and flash the latest ISO.
• Boot to the Live session and start Calamares.
• After completing the locale, keyboard, and user configuration, select “Manual partitioning.”
• Select and delete the previous NX_ROOT and NX_VAR_LIB partitions. Do not modify other partitions unless you explicitly want to; select “Keep” for them.
  • 🔰 Information: For further details about manual partitioning, see Getting Started → Installation Guide → Installing Nitrux → Non-automated Partitioning Options.

The table below defines our partition layout for EFI/UEFI-based computers with GPT (GUID Partition Table) storage devices.

• ⚠️ Important: The root directory is immutable. The system mounts it as read-only during normal operation. Do not use a single partition layout.

Finally, install the new root.

• ⚠️ Important: Replacing the root does not modify files in the user’s home directory, including desktop configuration and other user-specific settings.

Troubleshooting

Below is the information we deem necessary for users to troubleshoot problems during updates.

Unable to Create Redundant Backup of Root Partition

Nitrux requires XFS for the root partition. The Nitrux Update Tool System depends on XFS features to create redundant backups. Systems installed on other filesystems cannot use Rescue or Rescue Mode.

Unable to Access GitHub

If your computer can’t reach the domain raw.githubusercontent.com, you cannot proceed with the update process. We recommend using a VPN or a proxy, or contacting your ISP if they block access to these domains.

Update Failed due to External Factors (Power Outage, Hardware Failure, etc.)

If the Nitrux Update Tool System can’t apply an update because of an external factor, restore the XFS backup to maintain system integrity.

Persistent System State Conflicts (/var/lib)

NX_VAR_LIB stores persistent system state used by system services and applications, and it tightly couples this data to the specific software versions present in the root filesystem.

When you perform a root replacement with Calamares, reusing an existing NX_VAR_LIB partition may introduce incompatibilities between the preserved state and the newly installed system.

These incompatibilities can result in:

• Service initialization failures.
• Invalid or outdated internal data formats.
• Inconsistent runtime state.

Affected components may include:

• Distrobox.
• greetd.
• NetworkManager.
• Other software relying on NX_VAR_LIB for persistent state.

To ensure consistency, delete or format the NX_VAR_LIB partition during the upgrade process.

• ⚠️ Important: Deleting this partition will remove stored system data such as saved wireless networks and Bluetooth pairings. Back up this data beforehand if needed.

That’s it; this concludes today’s tutorial.