# USB09 post-Windows-format Pi health baseline

Status: complete
Type: evidence
Updated: 2026-08-01
Next Action: none; independent verification and the complete broad-baseline sequence passed

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
Incident: work/incidents/incident-usb09-false-write-failure-and-usb-compatibility-architecture-correction.md

## Identity and state

After the explicitly authorized full Windows FAT32 format, the Raspberry Pi
identified USB09 without ambiguity:

- canonical label `USB09`;
- new FAT UUID `50D2-5C43`;
- DOS partition-table identifier `0x9d4ee4ca`;
- General UDisk serial `2512300955508200677718`;
- USB/SCSI revision `5.00`, ANSI level 2;
- 15,728,640 logical blocks at 512 bytes, totaling 8,053,063,680 bytes;
- one FAT32 LBA partition from sector 32 through sector 15,728,639;
- unmounted before and after every check.

The stable serial, capacity, model, and revision match the incident specimen.
The new filesystem identifiers prove this is the newly formatted baseline, not
the preserved failed filesystem.

## Read-only health gate

- `fsck.fat -n -v` reached the final filesystem sector, found two FATs, and
  reported 4 files using 4 of 245,631 data clusters. It reported no structural
  corruption and left the filesystem unchanged. Exit status 1 is solely the
  known Windows convention that stores label `USB09` in the root directory
  while leaving the boot-sector label blank.
- FAT1 and FAT2 are byte-identical. Each 983,040-byte FAT hashes to
  `F061B8BA501CD07629DE2D2F4006DF6FFB6B9C61655C78D252C56F919C4B2732`.
- Read-only content inspection found only Windows' `System Volume Information`
  directory with `WPSettings.dat` and `IndexerVolumeGuid`; no prior CSV,
  `HPTE.TMP`, or controller output remains.
- A direct, unmounted read covered all 8,053,063,680 device bytes in 283.639
  seconds at approximately 28.4 MB/s. `dd` returned 0.
- Standard SCSI READ CAPACITY reported final LBA 15,728,639, 512-byte blocks,
  and the same 8,053,063,680-byte total. The drive rejects optional READ
  CAPACITY(16) with ILLEGAL REQUEST; this is not needed for its capacity and is
  recorded as compatibility evidence against unnecessary optional commands.
- The kernel log for the current insertion contains no USB reset, timeout,
  SCSI medium error, device-offline, buffer-I/O, or block-I/O error.

## Evidence location

Raw read-only outputs remain under the ignored generated directory:

`work/evidence/generated/usb09-post-windows-format-pi-health-20260731/`

## Disposition

USB09 passes the clean-media Pi gate and remains unmounted. It is ready for
the Controller A incident regression using the exact deployed isolated 32 KiB
candidate. This health result does not predict or substitute for controller
publication and independent post-export verification.

The subsequent Controller A regression passed the identical prior failure
range with 8,540 healthy records, 429,175 published bytes in 14 writes, zero
close delay, and zero errors. See
`work/evidence/usb09-32k-recovery-controller-pass-20260731.md`.
