Compatibility runs in one direction
U.3, defined by SFF-TA-1001, unifies SAS, SATA and NVMe signalling in a single physical slot and allows mixed population behind a tri-mode backplane. The important caveat is that compatibility is one-way: a U.3 drive can be installed in a U.2 backplane and operate as NVMe, while placing a U.2 drive in a U.3 tri-mode backplane depends on the specific backplane and HBA implementation. Reversing that statement is the most common source of selection error in real projects, and it often surfaces only on installation day.
The saving is in the chassis, not the drive
U.3's value accrues on the system side: backplanes no longer need protocol-specific zones, chassis SKUs collapse, service staff no longer distinguish slot types, and spare-parts management simplifies with them. For the drive itself the NVMe data path is identical between U.2 and U.3, so there is no performance difference — the 7,400 MB/s sequential read, 5,500 MB/s sequential write and 1,500 KIOPS 4KB random read planned for CORE 7's J750 and J770, all product-definition/EVT stage targets, do not change with the slot definition. Once a customer's backplane is fixed as NVMe-only, choosing between U.2 and U.3 becomes a procurement and spares question, and saying so early saves a discussion later.
The power arithmetic inside 15 millimetres
What actually drives selection is power and cooling. Taking J750 and J770 as the example, the U.2/U.3 15mm form factor is planned at 18 W typical, 22 W maximum and 6 W idle. At a front-panel density in the region of 24 bays, that figure multiplied by slot count sets the airflow and inlet-temperature margin for the chassis. If per-slot power delivery or airflow was designed around lower-power drives, the first thing to break at full population is usually not the interface but temperature: the drive throttles thermally and rated performance stops holding, a behaviour that a lightly loaded spot check will never reveal. Gen5 products draw more at the ceiling, so the same backplane may not sustain rated performance when fully populated, and that belongs in compatibility validation with measured data rather than copied from a datasheet.
A few system-level items that get missed
Beyond signalling and power delivery, three further things need confirming on the target machine: how hot-plug timing and link retraining actually behave, whether the NVMe-MI out-of-band management path is recognised properly by the BMC, and how online firmware update and rollback behave while the drive is in service. All of these belong to the enterprise feature baseline, but the baseline is a property of the drive while the validation has to happen in the system — a drive that passes standalone testing has not thereby qualified the chassis.
Beyond U.3: E3.S, E1.S and AIC
JH Semiconductor's U.2/U.3 coverage spans three lines: CORE 7, TITAN 7 and TITAN 9. Higher-density or OCP-aligned racks are served by FLEX 9, with J100E and J130E in E3.S and J100S and J130S in E1.S, while TITAN 7 additionally offers J200A and J230A in AIC form. These model names were fixed on 2026-07-22, after which capacity and bill-of-materials changes are handled through SKU, PN, Revision and ECN. Form factor decisions normally follow from backplane, power budget and service model together, not from which interface standard is newest.