system-rescue.org

SystemRescue (formerly SystemRescueCd) is a Linux system rescue toolkit that runs from a bootable CD/DVD or USB stick, used to administer or repair a computer and its data after a crash. It fits situations where the installed operating system won't boot or needs offline maintenance, and it works on both Linux and Windows machines, desktops and servers. No installation is required to use it — you boot the medium directly — though it can optionally be installed to a hard disk.

What you get when you boot it

SystemRescue bundles Linux system utilities rather than a general-purpose desktop. The homepage lists these core tools:

The kernel supports the important filesystems — ext4, xfs, btrfs, vfat, and ntfs — plus network filesystems such as Samba and NFS. That coverage is what makes it usable for both Linux and Windows disks from a single boot.

Typical uses

• Repairing a system that won't boot. Boot from the medium, then work on the disks directly — for example, resizing or recreating partitions, or repairing GRUB.
• Partition and filesystem work. Create, edit, resize, move, or copy partitions with GParted or GNU Parted, including GPT disks.
• Backing up data from an unbootable machine. The documentation covers backing up data from an unbootable Windows computer and backing up or transferring data with rsync.
• Filesystem-level archiving. FSArchiver lets you save and restore filesystems rather than individual files.
• LVM administration. The site provides guides on LVM overview, how it works, booting, root filesystem on LVM, and snapshots and backups.
• Network-based recovery. Configure networking and use Samba/NFS, or boot over the network with PXE.

How you run it

The basic path is: download the image, write it to a USB stick or burn it to CD/DVD, boot the machine from that medium, then start working. The project's Quick Start Guide is aimed at first-time users and covers downloading and burning, installing to a USB stick, boot options, and initial network configuration.

Two things worth knowing before you start:

• Booting is the normal mode; installing to disk is optional. The rescue system is designed to run from removable media, so you don't need to touch the target machine's existing installation to use it.
• Changes don't persist by default. The documentation describes creating a "backing-store" to keep your modifications between sessions, and using YAML configuration files plus autorun scripts to customize startup — useful if you'll use it repeatedly.

Is it the right fit?

Choose SystemRescue when you need an offline environment to repair partitions, filesystems, boot loaders, or to recover data from a machine that won't start, and you're comfortable working with disk-level tools. It is not a general desktop and not an automated repair wizard — the outcome depends on you selecting the right tool and operation. If your task is simply copying files off a working system, ordinary tools will do; if the system won't boot or the disk needs structural repair, a bootable rescue toolkit like this is the appropriate starting point.

SystemRescue can back up data from a Windows computer that no longer boots because it runs entirely from a CD/DVD or USB stick, so the installed operating system is never started. Once booted, it can mount the Windows NTFS partition with full read-write support and copy your files to an external disk or over the network using tools such as rsync. This applies to desktops and servers, and the rescue system requires no installation on the hard disk.

Why it works when Windows won't start

SystemRescue is a Linux system rescue toolkit designed for administering or repairing a system and its data after a crash. Because it boots from removable media, it does not depend on the broken Windows installation. Its kernel supports the important file systems, including NTFS, vfat, ext4, xfs and btrfs, as well as network file systems such as Samba and NFS. That means the disk holding your Windows files can be read directly, and the backup can be written to a USB drive, an external disk or a network share.

The project documentation lists a chapter specifically on backing up data from an unbootable Windows computer, alongside a guide on mounting an NTFS partition with full read-write support. Those two pages are the most direct references for this task.

Step-by-step outline

1. Prepare bootable media. Download SystemRescue and write it to a USB stick or burn it to a CD/DVD. The documentation includes chapters on downloading and burning and on installing SystemRescue on a USB stick.
2. Boot the machine from that media. Use the boot options described in the documentation if the default boot does not work. The system runs live and needs no installation.
3. Identify the Windows disk. Use the included partitioning and file system tools to see which device holds the NTFS partition. GParted (the GUI for GNU Parted) and the command-line tools can both show this.
4. Mount the NTFS partition with read-write support. Follow the dedicated guide so the partition is mounted in a way that allows reading files and, if needed, writing changes.
5. Connect a backup destination. Attach an external USB disk or configure networking. The documentation covers network configuration and programs, and the kernel supports Samba and NFS shares.
6. Copy the data. You can copy files directly, or use rsync for backup and transfer as described in the project's guide on backing up and transferring data with rsync.
7. Verify before you finish. Confirm the copied files are present and readable on the destination, then unmount the partitions cleanly before shutting down.

Tools that help with the backup

Practical points to keep in mind

• Work from a copy where possible. Mounting NTFS with full read-write support is documented, but the safest approach for a failing disk is to copy data off first and avoid unnecessary writes.
• Have a destination ready. A large enough external USB disk is the simplest option; a network share works if networking is configured.
• Use the documentation. The Quick Start Guide is the recommended first read, and the chapters on booting, mounting NTFS and backup cover the specific steps in more detail.
• The same media can repair as well as rescue. Beyond backup, SystemRescue includes tools for partition editing and guides on repairing Grub, so a single bootable stick covers both data recovery and system repair.

Yes. SystemRescue is designed to boot from a CD/DVD or USB stick without installation, but the project documentation also covers installing it on a hard disk, adding software packages with pacman, configuring it through YAML files, keeping your changes with a backing-store, and running your own scripts at start-up with autorun. These options are documented as advanced usage, so they assume you are already comfortable booting the toolkit and working from its command line.

Installing SystemRescue on the Disk

The default and simplest way to use SystemRescue is as a bootable medium: you write it to a USB stick or burn it to a disc and boot from that. The homepage states that no installation is required for this, but that the system can be installed on the hard disk if you wish.

Installing to disk makes sense when a machine is dedicated to rescue and maintenance work and you want the toolkit available without carrying a USB stick. The project documentation lists "Installing SystemRescue on the disk" as a separate advanced chapter, so treat it as a deliberate procedure rather than a quick copy: follow that chapter rather than improvising, because a disk install changes how the system boots and where its files live.

Adding Software with pacman

SystemRescue ships with a large set of Linux system utilities, including GParted, GNU Parted, FSArchiver, filesystem tools, editors, midnight commander, and network tools. If you need something beyond that set, the documentation covers "Installing additional software packages with pacman."

The practical constraint is persistence. A plain boot from read-only media starts fresh each time, so packages you install during one session are gone after reboot. To keep added software, combine pacman installs with the backing-store described below, or with a disk installation. The documentation treats these as related advanced topics for exactly this reason.

Keeping Changes with a Backing-Store

SystemRescue runs as a live system, so by default any configuration you change or software you add disappears when you shut down. The documented remedy is "Creating a backing-store to keep your modifications." A backing-store is a file that holds your changes so they survive reboots.

This is the option to choose when you want a customized rescue environment — your own tools, your network settings, your scripts — without committing a whole disk to SystemRescue. The trade-off is that the backing-store lives on some storage medium you must keep available and boot with; if that medium is missing or damaged, you are back to a default session.

Configuring with YAML Files and Autorun

Two further customization mechanisms are documented:

• YAML configuration files — "Configuring SystemRescue with YAML files" lets you define system settings in a structured file instead of changing them by hand each boot.
• Autorun scripts — "Run your own scripts at start-up with autorun" lets you execute custom commands automatically when the system starts, which is useful for repetitive setup tasks such as mounting specific partitions or starting network services.

Both are natural companions to a backing-store or disk install: the configuration and scripts persist, and the system applies them on every boot.

Choosing Between the Options

Where to Start

The homepage points to a Quick Start Guide for first-time users, and the advanced chapters above sit alongside it in the project documentation, together with guides on disk partitioning, LVM, networking, and backing up data from an unbootable Windows computer. If you are new to SystemRescue, boot it from a USB stick first and confirm the tools you need are present; only then decide whether a backing-store or a disk installation is worth setting up.

SystemRescue is a Linux rescue toolkit that boots from a CD/DVD or USB stick and bundles disk, filesystem, archiving, and networking utilities for repairing a system or its data after a crash. Its kernel supports ext4, xfs, btrfs, vfat, and ntfs, plus network filesystems such as Samba and NFS, so the same medium can work on Linux and Windows machines, desktops and servers. No installation is required to boot it, though it can also be installed to a hard disk if you prefer.

Disk and partition tools

The toolkit centers on partitioning and filesystem work:

• GNU Parted — creates, resizes, moves, and copies partitions and filesystems.
• GParted — the graphical front end built on the GNU Parted library, useful when you want to see the layout before changing it.
• FSArchiver — a flexible archiver for filesystem-level backup and restore.
• Filesystem tools — the standard utilities for checking and working with the supported filesystems.

These are the tools to reach for when the task is creating or editing hard disk partitions, which the project describes as a core purpose of the rescue medium.

Basic and network tools

Beyond partitioning, the image includes everyday utilities so you can work inside the live environment:

• Editors and Midnight Commander for browsing and editing files.
• Network tools for configuration and transfers.
• Support for mounting an NTFS partition with full read-write access, and guides for backing up data from an unbootable Windows computer or transferring it with rsync.

Supported filesystems

The kernel covers "all important file systems," per the project, which is why the same stick can handle both Linux and Windows disks.

Deciding whether it fits your task

Choose SystemRescue when you need to boot a machine that won't start and then partition, repair, back up, or transfer data — the included GParted, GNU Parted, FSArchiver, and filesystem tools cover those jobs without installing anything. If your work is limited to a filesystem type outside the list above, or you need software not bundled in the image, note that additional packages can be installed with pacman, and configuration can be extended with YAML files or a backing-store that keeps your changes between boots. For first use, the project's Quick Start Guide covers downloading, burning, USB installation, and boot options.

SystemRescue is a Linux rescue toolkit that runs entirely from bootable media, so you can download the image from system-rescue.org, write it to a USB stick or burn it to a CD/DVD, then boot your computer from that medium. No installation is required, though the project notes it can be installed on a hard disk if you prefer. This guide covers the download, the two media options, boot options, and first-boot steps.

Before You Start

• A working computer to prepare the media, plus a USB stick or a blank CD/DVD.
• The target machine must be able to boot from USB or from its optical drive (check the firmware/boot menu).
• Back up important data before doing rescue or partitioning work on any disk.
• For first-time users, the project's own advice is to read the Quick Start Guide before booting.

Step 1: Download the Image

Go to the SystemRescue homepage at system-rescue.org and use the Download link in the site navigation. The homepage also links to the ChangeLog so you can see what changed between versions. Download the bootable image file offered there; the site does not publish pricing details, so treat availability and any access conditions as stated on the download page itself.

Step 2: Create the Bootable Medium

Option A: USB Stick

The project documents installing SystemRescue on a USB stick as a standard procedure (linked from the homepage under "How to install SystemRescue on an USB-stick"). In practice this means writing the downloaded image to the stick so it becomes bootable — the exact tool and commands are covered in that project page, so follow it rather than guessing at menu locations.

Option B: CD/DVD

The homepage lists "Downloading and burning" as a documentation chapter. Burn the downloaded image to the disc using your usual disc-burning software, then use that disc as the boot medium.

Comparison

Choose USB if your machine boots from it and you expect to use the toolkit more than once; choose CD/DVD if USB boot isn't available or you want a simple one-off disc.

Step 3: Boot from the Medium

1. Insert the USB stick or disc and restart the computer.
2. Open the firmware boot menu (or change the boot order) so the machine starts from your medium instead of the internal disk.
3. At the SystemRescue boot prompt, review the available boot options — the homepage links a dedicated "Boot options" page and a "Booting SystemRescue" documentation chapter. Defaults are fine for most rescues; special options exist for things like different video modes or specific hardware needs.
4. Let the system finish starting. You'll land in the live environment with the included tools.

Expected result: a running SystemRescue session where you can work on disks and data without touching the installed operating system.

Step 4: First Steps Inside SystemRescue

• Read the Quick Start Guide if this is your first time — the project explicitly recommends it for new users.
• Configure networking if you need to transfer data or download packages; the homepage links "Network: configuration and programs."
• Mount partitions as needed. For Windows disks, the project documents "Mounting an NTFS partition with full Read-Write support" — read it before writing to NTFS.
• Use the included tools: GParted (GUI partitioning), GNU Parted, FSArchiver, filesystem tools, editors, Midnight Commander, and network tools. The kernel supports ext4, xfs, btrfs, vfat, and ntfs, plus Samba and NFS network filesystems.
• Optional persistence: if you want changes to survive reboots, the docs cover creating a backing-store; you can also install extra packages with pacman or run startup scripts via autorun.

Common Sticking Points

• Machine won't boot from the medium: check the firmware boot order and whether USB boot or the optical drive is enabled.
• Unsure which boot option to pick: start with the default; consult the Boot options page only if hardware isn't detected or the display misbehaves.
• NTFS writes: don't write to a Windows partition until you've read the read-write mounting guide.
• Needing tools not included: the docs explain installing additional software packages with pacman, which typically requires working network access.
• Wanting to keep settings: set up a backing-store rather than expecting changes to persist automatically.

Where to Go Next

The homepage's documentation section is the authoritative reference: Quick Start Guide, downloading and burning, USB installation, boot options, networking, NTFS mounting, disk partitioning and LVM guides, PXE network booting, and data backup with rsync. The Manual, FAQ, and Forums links are also available from the site for deeper troubleshooting.