DriveCk

DriveCk validates removable and USB storage devices, checks read/write integrity on sampled regions, and generates a human-readable report.

Platforms

• Linux: GTK GUI and CLI
• macOS: native app and native CLI
• Windows: native Win32 app with an embedded CLI mode

Screenshots

Current screenshots cover the Linux GTK frontend and the native Win32 frontend.

Linux GTK

Windows Win32

Features

• validates removable and USB whole-disk devices
• live 18 x 32 validation grid during a run
• human-readable report with verdict and usable-size summary
• Linux GTK app, Linux CLI, native macOS app/CLI, and native Win32 app with an embedded CLI mode

Before you run it

• Validate only whole devices, not partitions or image files.
• Sampled regions are temporarily overwritten and then restored.
• DriveCk checks whether the target is safe to validate and blocks mounted or in-use disks until they are ready.
• The tool is designed to restore the sampled regions it touches, but you should still back up important data before validating any real device.
• Raw-device access may require administrator privileges.

How validation works

1. DriveCk discovers removable and USB whole-disk targets.
2. It checks target state and only proceeds when the device can be validated safely.
3. It samples regions across the device, performs the write / read-back / restore cycle, and updates the live validation grid as it goes.
4. It generates a final report with the verdict, validated size, and other summary details.

Quick start

Linux GTK

Run from source:

cargo run -p driveck-gtk

If you use the packaged Linux GTK release, extract the archive and run:

./driveck

When the GTK app needs elevated access on Linux, it requests it through a GUI authentication prompt.

Linux installer

To install the Linux GUI package into standard locations:

./script/install_linux.sh --user target/release/DriveCk-gui-linux-x86_64-v0.1.0.tar.gz

To install only the Linux CLI package:

./script/install_linux.sh --user target/release/DriveCk-cli-linux-x86_64-v0.1.0.tar.gz

Use --system instead of --user if you want the files installed under /usr/local instead of ~/.local.

After installation:

• GUI install: launch DriveCk from the desktop menu, or run driveck-gui
• GUI install with CLI arguments: driveck-gui --list
• CLI-only install: driveck --list

To uninstall again:

./script/uninstall_linux.sh --user --all
./script/uninstall_linux.sh --system --gui

CLI

Run from source:

cargo run -p driveck-cli -- --list
cargo run -p driveck-cli -- --yes /dev/sdb
cargo run -p driveck-cli -- --yes --output report.txt /dev/sdb

CLI release packages also extract to a short executable name:

./driveck --list
./driveck --yes /dev/sdb

The Linux GUI package now also understands these CLI arguments. After a GUI install, use driveck-gui --list or driveck-gui --yes /dev/sdb.

Windows Win32

Run from a Windows shell initialized with the MSVC toolchain, such as Developer PowerShell for VS 2022:

cargo run -p driveck-win32
cargo build --release -p driveck-win32

The same source build also supports CLI mode:

cargo run -p driveck-win32 -- --list
cargo run -p driveck-win32 -- --yes \\.\PhysicalDrive2

If you use the packaged Windows GUI release, extract the archive and run:

.\DriveCk.exe

To package the Windows release from PowerShell, prefer:

.\script\package_release.ps1 win32

The same DriveCk.exe also supports CLI mode when launched from a terminal:

.\DriveCk.exe --list
.\DriveCk.exe --yes \\.\PhysicalDrive2
.\DriveCk.exe --gui

The Win32 frontend:

• discovers removable and USB whole-disk targets
• blocks mounted disks until every volume on the physical disk has been unmounted
• shows the live validation grid, progress, summary, and report preview during a run
• can switch into the existing list / validate / save-report CLI flow when launched with CLI arguments

macOS

• macOS uses native frontends: a SwiftUI + AppKit app and a native CLI.

Release package names

Release archives are normalized by distribution edition rather than the frontend implementation detail.

• CLI packages: DriveCk-cli-<platform>-<arch>-v<version>
• GUI packages: DriveCk-gui-<platform>-<arch>-v<version>

Examples:

• DriveCk-cli-linux-x86_64-v0.1.0.tar.gz
• DriveCk-gui-linux-x86_64-v0.1.0.tar.gz
• DriveCk-cli-windows-x86_64-v0.1.0.zip
• DriveCk-gui-windows-x86_64-v0.1.0.zip
• DriveCk-cli-macos-arm64-v0.1.0.zip
• DriveCk-gui-macos-arm64-v0.1.0.zip

Developer docs

Build, packaging, and platform-specific developer details now live here:

• Developer guide
• macOS requirements
• macOS design notes

Reference

• GRC ValiDrive