# USB 32 KiB matrix Round 3 Pi result: USB02_8G and USB03_32G

Status: complete
Result: complete; PASS
Type: evidence
Updated: 2026-08-01
Next Action: none; retain as historical round evidence for the completed matrix
Campaign: 003-complete-bounded-hpt-slow-export-firmware-ticket

Project Map: work/maps/map-smi-firmware-stabilization-and-qualification.md
Workpackage: work/wp/completed/wp-restore-broad-usb-compatibility-baseline.md
Checklist: work/checklists/checklist-stage-1b-four-drive-usb-compatibility-baseline.md
Controller result: work/evidence/usb-32k-round3-controller-usb02-usb03-20260731.md

## Returned identity and filesystem gate

The Raspberry Pi identified both returned drives without ambiguity and kept
them unmounted except for temporary read-only content inspection:

| Canonical label | Pi device | Capacity | Partition identity | FAT UUID |
| --- | --- | ---: | --- | --- |
| `USB03_32G` | `/dev/sda` | 31,042,043,904 bytes | PNY serial `071C49DE25C08808`; MBR `0xa46783c6`; FAT32 LBA `8,064..60,628,991` | `BCE4-0E61` |
| `USB02_8G` | `/dev/sdb` | 8,053,063,680 bytes | General UDisk serial `1003112253528015858612`; MBR `0x8fe2a284`; FAT32 LBA `32..15,728,639` | `D499-DF4E` |

Model, revision, serial, capacity, partition table, label, and UUID match the
established specimen identities. `sg_readcap` independently returned final
LBAs `60,628,991` and `15,728,639` with 512-byte logical blocks.

`fsck.fat -n -v` reached the final filesystem sector on both drives, found no
structural corruption, and left each filesystem unchanged. Exit status `1`
is solely the preserved Windows root-directory label versus blank boot-sector
label convention. Both FAT copies are byte-identical:

- `USB03_32G`: each 7,574,016-byte FAT SHA-256
  `2B6E2CD23AF657DA8E2A7BC47D59B43AFC4BFBA5AB00A76CFEA9935BA3262E4E`;
- `USB02_8G`: each 7,847,936-byte FAT SHA-256
  `C91FC1FC9CF387B9A38E8AB880B354949BBBB5648A7478996E69405E0E3F490A`.

The current insertion kernel log contains normal high-speed enumeration,
capacity, partition, and removable-disk attachment events. It contains no
reset, timeout, medium, offline, buffer/block-I/O, sense-key,
descriptor-read, rejecting-I/O, or other error. Both drives are unmounted
after validation.

## Exact output validation

| Output | USB02_8G | USB03_32G |
| --- | --- | --- |
| New HPT CSV | `K3A_USB02.csv`; 444,942 bytes; SHA-256 `DEADF5596CF576EFD2BD8241AF360BF35760281F093F5C1C297964835CE6FD2D` | `K3B_USB03.csv`; 445,562 bytes; SHA-256 `45A61A6746ED0D74CE3B69C773CB79423935A30FE53E30DD22C70A5E01D97386` |
| Data lines | exact sequence `1..8855`; no missing or duplicate line | exact sequence `1..8865`; no missing or duplicate line |
| Metadata | requested/actual range `301739760..302288100`; 8,855 healthy, 0 degraded, 0 gaps | requested/actual range `301741860..302288160`; 8,784 healthy, 81 degraded, 0 gaps |
| Completion | snapshot `COMPLETE`; `Export completion: COMPLETE; records published: 8855` | snapshot `COMPLETE`; `Export completion: COMPLETE; records published: 8865` |
| New PID | `MainPid 2026-07-31 16-47.txt`; 225 bytes; SHA-256 `6BCB89F2EFACC503B950EF00151A51AF8353C40B53781110C14DDC441737FC3A` | same name, size, and hash |
| Recovery image | 8,388,864 bytes; SHA-256 `F2C11398416DF829078BD960E67D0AE6E54AE1EB8D361A49DB273A6180048E52` | same size and hash |

The 81 degraded Controller B records are the same HPT source-data
classification reported by the controller; they are present in the complete
CSV and are not a USB or filesystem failure.

The replacement image on each drive has title/version
`Version 00-05-00  7520553_SMI_00_05_00.imx`, update version `1`, and SMI
machine mask `1`. Independent read-only validation using the configured
Renesas CRC-32, MSB-first, 32-bit-word input convention passed:

- exact expected size: 256-byte header plus 4,194,304-byte main image plus
  4,194,304-byte audio image;
- header CRC stored/calculated: `0xA5ECD768`;
- main-image CRC stored/calculated: `0xDF597832`;
- audio-image CRC stored/calculated: `0xB2FE8C3B`;
- I/O image length and CRC both zero, as required for SMI.

Both retained WAV files remain exact and valid mono PCM, 44.1 kHz, 16-bit:

- `W00.wav`: 198,566 bytes; SHA-256
  `37A9DC665366F06D8081B23ECF88BDB30CF81546C3A10EDA1BE827DE2D006B92`;
- `W01.wav`: 176,516 bytes; SHA-256
  `E22FC8FFF2CF68878C56EA87660CA2325E0FBF04CF091AAEB112A7F274B1B2F7`.

All earlier CSV and PID filenames remain present. No `.tmp`, `.part`, or
`.bak` artifact exists on either drive.

## Disposition

32 KiB Round 3 passes end to end: WAV load/playback, PID, full image
replacement, full-range 32 KiB HPT publication, filesystem consistency, exact
content, internal image CRCs, and independent removal/reinsertion validation
all pass.

Controller B's initial below-class `USB03_32G` enumeration miss and the single
clean powered reseat remain part of the result; they are not erased by the
successful FileX and Pi gates. No VBUS, controller power, format, repair,
optional-SCSI, firmware retry, or drive-specific code path was used. Rounds 1
through 3 now supply six of the required eight 32 KiB controller/drive
observations. Broad promotion remains blocked on Round 4 and final disposition
of the repeated first-insertion enumeration pattern.
