Disk discovery
Identify block devices, partitions, labels, UUIDs and mount state before you touch storage.
Boot • inspect • recover
SystemRescueCd Download & Recovery Toolkit
SystemRescueCd is a bootable rescue environment for disk inspection, data recovery, filesystem work and system troubleshooting. This independent guide keeps the workflow focused and safety-first.
- Bootable Linux
- Disk & filesystem tools
- UEFI + BIOS workflows
- Independent guide
What is SystemRescueCd?
A portable recovery workspace.
SystemRescueCd is a Linux-based environment designed to boot separately from the operating system installed on a computer. That makes it useful when the main OS is damaged, inaccessible or unsafe to modify directly.
- Inspect before writingIdentify disks, partitions, filesystems and logs before repair actions.
- Work across common filesystemsUse tools for Linux and Windows storage formats in one environment.
- Keep recovery portableBoot from prepared media instead of depending on the installed OS.
Features
Core rescue tools, grouped by the job.
A minimal utility layout puts the important capabilities first instead of burying them in decorative panels.
Filesystem tools
Work with common Linux and Windows filesystems using the appropriate included utilities.
Backup & imaging
Copy valuable data or create images before attempting risky repair operations.
Partition management
Inspect and manage partition layouts with command-line or graphical tools such as GParted.
Networking
Configure connectivity for remote administration or secure data transfer when needed.
Linux administration
Mount installed systems, inspect logs and use chroot-based maintenance for authorized repairs.
How it works
Four deliberate steps.
Rescue work is safer when discovery and data protection happen before modification.
STEP 01
Prepare media
Use a verified ISO or approved package and create bootable media carefully.
STEP 02
Boot separately
Select the rescue device from UEFI or BIOS without relying on the installed OS.
STEP 03
Inspect first
Confirm disks, partitions and filesystem state with non-destructive discovery tools.
STEP 04
Recover or repair
Protect important data, then use the right tool for the specific repair.
Compatibility
Built for modern x86-64 rescue work.
Current SystemRescueCd releases focus on 64-bit AMD/Intel systems. Older 32-bit releases are historical rather than current.
AreaCurrent fitNotes
AMD64 / x86-64CurrentPrimary architecture
UEFISupportedFirmware boot menu
Legacy BIOSSupportedClassic boot path
32-bit x86HistoricalOld releases only
Filesystem coverage
Common rescue workflows include ext4, XFS, Btrfs, FAT and NTFS. ZFS requires particular care because pool import choices can modify state; inspect the exact environment and modules before acting.
Use cases
Use the environment for focused recovery tasks.
Recover files
Copy important data from a system that no longer boots normally.
Repair Linux boot
Inspect filesystems, mount an installation and repair configuration where authorized.
Check storage
Identify partitions, filesystems and disk health signals before deciding what to do next.
Prepare partitions
Create or adjust storage layouts when you understand the destructive implications.
Download
Download SystemRescueCd
The button below uses the download URL supplied for this website: a GitHub archive for systemrescue-zfs. It is not the official numbered SystemRescue ISO mirror.
Download SystemRescueCdFor upstream context, The current upstream release 13.02 was published on August 1, 2026 for amd64. Verify checksums and signatures whenever you use an official ISO.
Installation / Setup
Prepare rescue media with a verification step.
- Identify the exact fileKnow whether you have an ISO image, source archive or customized build before writing media.
- Verify integrityCompare checksums or signatures when the publisher provides them.
- Create bootable mediaUse a reputable imaging tool suitable for your platform and the file type.
- Test the boot pathUse the one-time firmware boot menu and confirm the rescue environment starts correctly.
Important file-type note
The supplied download URL is a ZIP source archive, not an ISO image. Do not write a ZIP archive to a USB device and expect it to behave like the official SystemRescue ISO. Read the package contents and build instructions first.
Safety notice
Recovery tools can also destroy data.
Work only on systems and data you own or are authorized to administer. Confirm the target device before every write, avoid unnecessary mounts on damaged storage, and keep an untouched backup or image whenever possible. Password recovery guidance on this site favors supported, authorized account-recovery methods.
Pros and cons
Why a rescue environment helps—and where caution matters.
Pros
- Boots independently from the installed operating system.
- Brings many storage and Linux administration tools together.
- Useful for both terminal and graphical recovery workflows.
- Can protect data by enabling inspection before repair.
Cons
- Powerful tools can make irreversible changes.
- Device names and repair commands require careful interpretation.
- 32-bit current hardware support is no longer a focus.
- Some specialist filesystems and hardware need extra validation.
Release information
Current upstream reference.
These details describe the upstream SystemRescue release, not the separate ZIP archive used by this site's main download button.
Release13.02
DateAug 1, 2026
Architectureamd64
KernelLinux 6.18.41 LTS
Troubleshooting
Check the simple failure points first.
Won’t bootVerify the image, rewrite the USB, try a different device or port, then re-check UEFI/BIOS boot mode and priority.
Blank displayTry a basic graphics path such as the
nomodeset boot option, then investigate the graphics stack.Random errorsTest memory and consider bad removable media. Inconsistent failures often point to hardware or corrupted media.
Disk missingInspect controllers, encryption, RAID layers and firmware settings before assuming the storage device has failed.
Guides preview
Targeted SystemRescueCd guides.
FAQ
SystemRescueCd questions, organized by task.
Exactly twenty practical answers covering the environment, compatibility, setup and recovery workflow.
It is a bootable Linux rescue environment used to inspect disks, copy data, repair filesystems, work with partitions and troubleshoot computers that may not boot normally.
SystemRescue is the current project name; SystemRescueCd is a widely searched legacy name. This independent site uses SystemRescueCd for discoverability while describing the current rescue workflow.
Yes. The usual workflow is to boot the rescue environment from prepared removable media so the installed operating system does not need to start.
Current SystemRescue media supports modern UEFI and classic BIOS boot workflows. Firmware settings and removable-media priority still need to be configured correctly.
The rescue environment includes tools for common Linux and Windows filesystems, including ext family filesystems, XFS, Btrfs, FAT and NTFS. Tool availability can vary by release.
ZFS availability depends on the image, included modules and the workflow you use. Treat pool imports carefully and prefer read-only inspection before making changes.
No current 32-bit release is maintained. Older i686 builds existed historically, but modern SystemRescue focuses on 64-bit AMD/Intel systems.
It can inspect and mount common Windows filesystems such as NTFS, subject to disk state, encryption and filesystem health.
Yes. The environment includes networking tools and can be used for tasks such as remote access or copying data, provided the network and firewall are configured safely.
For current releases, 2 GB is a practical minimum for normal booting, while workflows that copy the system into RAM require more memory.
Use a trusted USB imaging method to write the ISO as bootable media, then select that device from the computer firmware boot menu.
Verify the download, rewrite the USB, try another port or device, review BIOS or UEFI settings, and test memory if failures are inconsistent.
Start with non-destructive discovery commands such as lsblk, blkid, findmnt and journalctl. Confirm device names before running any command that writes to disk.
Yes. Read-only inspection reduces accidental changes while you identify the correct device, assess damage and decide how to protect recoverable data.
Use only authorized recovery on computers you own or administer. Prefer Microsoft's supported account recovery, an approved administrator workflow, or organization IT procedures before considering offline methods.
Compare device size, model, partition layout, filesystem labels and UUIDs before mounting, imaging or repairing anything. Never assume /dev/sda is the intended disk.
The copytoram boot option loads the rescue system into memory so the original boot media can be removed after startup. It needs additional RAM.
A basic display mode such as nomodeset can help when the optimal graphics path does not display correctly. You can then troubleshoot drivers or hardware separately.
Yes. Checksum or signature verification helps detect an incomplete or altered download before you rely on the media for recovery.
Back up or image important data when practical, identify the exact filesystem and tool, review repair implications, and avoid writing to the only copy of valuable data.