# Hardware Transition Plan

## Phase 0 — Current hardware

- Existing 1 TB HDD retains Ubuntu and gains a separate ext4 data volume from
  the currently unallocated space.
- Git, catalogs, releases, and artifacts share the disk.
- Protection status: single disk, not backed up.

## Phase 1 — First purchases

Target the previously accepted low-cost internal SATA layout:

- 1 TB SATA TLC SSD for Ubuntu, Git service, repositories, service database,
  manifests, and active small files;
- 8 TB CMR SATA HDD for firmware, disc images, Git LFS objects, accepted analyzer
  packages, emulator traces, and historical releases;
- reuse the existing 1 TB HDD as a backup of the critical subset after migration.

The 1 GbE network and no-analyzer constraint make SAS and high-end storage
controllers poor value for this server.

## Phase 2 — Full local archive redundancy

Add a second 8 TB CMR SATA HDD as an independent archive backup. Do not use it as
one half of a RAID-0 set. A simple independently verifiable copy is preferred.

## Phase 3 — Off-server or offline copy

Add an offline or off-server copy of A0/A1 material. This completes the intended
three-copy model: working, local independent backup, and off-server/offline.

## Migration rule

Every storage move must use copy, hash verification, service cutover, independent
readback, and only then retirement of the old copy. Device names are deliberately
absent from this plan; exact commands must be generated from the server's actual
`lsblk`, filesystem, partition-table, and mount state.
