PCRT Diagnostics
Portable Linux diagnostics

PCRT Diagnostics
for Linux

Run the PCRT scanner directly from the command line, use the same five-character session codes as the Windows and macOS clients, and upload the finished technician reports to the existing PCRT portal.

Version 0.1.0 AMD64 + ARM64 Portable binary
Download Linux 0.1.0 View quick start

No runtime or installation is required. Run the matching self-contained binary with sudo and a PCRT session code.

No installationRun it from Downloads, a tools folder, or USB storage.
Same PCRT workflowClaim a session, report progress, and upload four report files.
Safe by designPhysical drives are opened read-only for distributed sampling.
Quick start

Run the portable scanner

Download and extract the ZIP, choose the binary that matches the computer, make it executable, and provide the five-character code created in the PCRT portal.

Nothing is installed. The included install.sh is optional convenience only. The normal workflow is to run the binary directly.
1

Extract the download

unzip PCRTDiagnosticsLinux-0.1.0-binaries.zip
cd PCRTDiagnosticsLinux-0.1.0-binaries/dist
2

Run on a normal x64 Linux computer

chmod +x pcrt-diagnostics-linux-amd64
sudo ./pcrt-diagnostics-linux-amd64 --code ABCDE
3

Run on an ARM64 system

chmod +x pcrt-diagnostics-linux-arm64
sudo ./pcrt-diagnostics-linux-arm64 --code ABCDE
What it checks

Linux-focused hardware and health coverage

The server selects the scan preset. The Linux client applies Linux-appropriate inventory, testing, status logic, and evidence collection.

CPU

Processor validation

CPU inventory, deterministic prime validation, and sustained all-logical-processor calculations.

RAM

Memory testing

DMI module inventory, deterministic application-level patterns, and server-controlled sustained workload.

SSD

Storage checks

SMART/NVMe evidence, filesystem review, read-only physical-drive samples, and temporary hash verification.

PCI

Devices and thermals

PCIe, USB, GPU/display, TPM, RTC, battery, hwmon, and thermal-zone information.

LOG

Linux event evidence

Kernel MCE, EDAC, AER, storage, filesystem, GPU, USB, and before/after workload review.

RPT

PCRT reporting

Separate hardware, stability, Linux integrity, maintenance, security, and network/power results.

Optional diagnostic tools

Improve coverage without changing the portable client

PCRT does not install packages or alter the customer’s Linux configuration. Missing tools produce reduced evidence or a Not Available result—not a false hardware failure.

Command Package Additional PCRT evidence
smartctlsmartmontoolsSMART, SATA, SCSI, and NVMe drive-health details
dmidecodedmidecodeInstalled memory-module size, manufacturer, part number, serial, and speed
lspcipciutilsExpanded PCIe and GPU inventory, device IDs, and driver evidence
tpm2_getcaptpm2-toolsAdditional TPM 2.0 capabilities
mokutilmokutilUEFI Secure Boot state
glxinfomesa-utils or glx-utilsActive OpenGL renderer and graphics-driver information
nvidia-smiNVIDIA driver utilitiesNVIDIA model, driver, VRAM, temperature, and power-state evidence
getenforcelibselinux-utilsSELinux enforcement state on SELinux-based distributions
Base-system commands: PCRT also uses commands such as lsblk, journalctl, systemctl, dmesg, and uname. These are normally already present on supported systemd-based distributions.
Package directions

Install optional tools by distribution

These commands are optional and should be run only when the technician wants the additional coverage shown above.

Ubuntu / Debian

Ubuntu, Debian, Linux Mint, Pop!_OS, Zorin OS, and similar distributions.

sudo apt update
sudo apt install smartmontools dmidecode pciutils tpm2-tools mokutil mesa-utils
Fedora / RHEL-based

Fedora and compatible RPM distributions using DNF.

sudo dnf install smartmontools dmidecode pciutils tpm2-tools mokutil glx-utils libselinux-utils
Arch-based

Arch Linux, EndeavourOS, and similar distributions using pacman.

sudo pacman -Syu smartmontools dmidecode pciutils tpm2-tools mokutil mesa-utils
NVIDIA systems: Do not install a random NVIDIA package only for PCRT. When the proprietary NVIDIA driver is already installed correctly, nvidia-smi is normally provided by that driver stack.
Verify coverage

Check which tools are available

This command lists the optional and base utilities PCRT may use. 

for tool in \
  smartctl dmidecode lspci tpm2_getcap mokutil \
  glxinfo nvidia-smi getenforce journalctl \
  systemctl lsblk dmesg
do
  if command -v "$tool" >/dev/null 2>&1; then
    printf "%-16s available: %s\n" "$tool" "$(command -v "$tool")"
  else
    printf "%-16s not available\n" "$tool"
  fi
done
Command-line options

Simple arguments for repair-bench use

The production server address is compiled into the client. The normal command requires only the session code.

--code ABCDEFive-character PCRT session code
-c ABCDEShort form of the session-code argument
ABCDEThe session code can also be supplied positionally
--output PATHChoose a local report output directory
--verbosePrint detailed diagnostic log messages
--versionPrint the client version and exit
Report output

Four files are created and uploaded

system-info.html

Linux, hardware, device, storage, network, and power inventory.

test-results.html

Technician-facing status, domain results, evidence, and recommendations.

raw-data.json

Complete structured data and command evidence.

run-log.txt

Client workflow, server communication warnings, and diagnostic log entries.

Why root is required

Raw drive reads, SMART, DMI, TPM, kernel logs, and some hardware sensors are restricted on Linux.

Drive safety

Physical block devices are opened read-only. Temporary write verification uses a normal file and removes it afterward.

No package changes

The client does not refresh repositories, install updates, or install optional diagnostic utilities.

Need a PCRT beta account?

Request free beta access, create a Linux session, and test the portable scanner.

Request free beta access Login