1.92 TB 2.5-inch SATA mixed-use SSD, ordering codes MZ7L31T9HENA-00A07 / -00B07
| Capacity | 1.92 TB |
|---|---|
| Interface | SATA |
| Form Factor | 2.5-inch 7mm |
| PCIe Version | Not applicable |
| NAND Type | TLC |
| Endurance (DWPD) | 3 |
| TBW | 10,512 TB |
| Sequential Read | 560 MB/s |
| Sequential Write | 530 MB/s |
| Random Read IOPS | 97K IOPS |
| Random Write IOPS | 60K IOPS |
| Power | 2.3 W |
| DRAM Cache | Yes |
| Power Loss Protection | Yes |
| Encryption | Opal 2.0 |
| Condition | New · Used |
Samsung PM897a 1.92 TB, 2.5-inch 7 mm SATA, catalogue code MZ7L31T9HENA, ordering codes MZ7L31T9HENA-00A07 and MZ7L31T9HENA-00B07. 560 MB/s sequential read, 530 MB/s sequential write, 97K random read and 60K random write IOPS at 4 KB, 10,512 TBW — 3.0 drive-writes-per-day over five years — on Samsung 3-bit TLC V-NAND, with TCG Opal 2.0 and capacitor-backed power-loss protection. Stocked new or as tested pulls with a 1-year warranty from us.
This capacity carries the one build code in the range that does not identify a single drive: HENA belongs to both the 1.92 TB and the 3.84 TB member. Their model numbers differ only in the capacity block, 1T9 against 3T8, and that is a difference worth 1.92 TB — which makes it the most expensive mis-read in the range and the reason this page starts with how to tell them apart.
The a-build splits its four capacities into three codes: HELT at 480 GB, HELA at 960 GB, and HENA shared by 1.92 TB and 3.84 TB. The earlier PM897 build splits them two and two instead — HBLT across 480 GB and 960 GB, HBNA across the top two. So on the a-build, half the range sits behind one code, and on the earlier build all of it does.
What that means in practice is that a build code is a build identifier, not a part identifier. The part is the full string: MZ7L3 prefixes every PM897a capacity, the next three characters give the capacity in a compressed form — 480 and 960 literally, 1T9 for 1.92 TB, 3T8 for 3.84 TB — and the last four are the build. Two drives can share every character except the middle three and differ by 1.92 TB.
The commercial consequence is straightforward. A receiving process that matches on the build code will accept a 1.92 TB drive against a 3.84 TB PO line, or the reverse, and neither will show up as an error until somebody tries to provision a datastore. Match on the capacity block, or on the full string, and the ambiguity disappears.
| Product family | Samsung PM897a (V-NAND SSD, data centre / mixed-use) |
|---|---|
| PN | MZ7L31T9HENA (catalogue code) |
| Ordering code | MZ7L31T9HENA-00A07 / MZ7L31T9HENA-00B07 |
| Capacity | 1.92 TB (512-byte sectors, decimal capacity) |
| Form factor | 2.5-inch, 7.00 mm (100.20 × 69.85 × 7.00 mm, max 70 g) |
| Interface | SATA 6 Gb/s, Serial ATA 3.3, ATA/ATAPI ACS-4 |
| NAND | Samsung V-NAND, 3-bit (TLC) |
| Sequential read / write | 560 MB/s / 530 MB/s (128 KB, QD32) |
| Random 4 KB (QD32) | 97K IOPS read / 60K IOPS write |
| Random 8 KB (QD32) | 57K IOPS read / 40K IOPS write |
| IOPS consistency | 95% read / 90% write at 4 KB, sustained |
| Latency and QoS | 105 µs read / 30 µs write at QD1; 99.99th percentile 0.2 ms read, 0.05 ms write at QD1; 0.6 ms and 0.7 ms at QD32 |
| Endurance | 10,512 TBW — 3.0 DWPD over five years (TBW = DWPD × 365 × 5 × capacity) |
| Power | Active read 2.3 W; active write 3.0 W; idle 1.4 W (DIPM off); supply 5 V ±5% |
| Power-loss protection | Yes — capacitor hold-up transfers cached DRAM data to flash on failure; no hold-up time published |
| Data security | AES-XTS 256-bit encryption engine, TCG Opal 2.0 compliant |
| Features | TRIM, NCQ to depth 32, S.M.A.R.T., end-to-end data integrity, RoHS |
| Reliability | MTBF 2.0 million hours; UBER 1 sector per 1017 bits read |
| Environmental | Operating 0 °C to 70 °C (case); non-operating −40 °C to 85 °C; humidity 5–95% non-condensing |
| Code | Type | Condition | Quote |
|---|---|---|---|
| MZ7L31T9HENA | Catalogue code | New / used | Enquire |
| MZ7L31T9HENA-00A07 | Ordering code | New / used | Enquire |
| MZ7L31T9HENA-00B07 | Ordering code | New / used | Enquire |
All three describe one 1.92 TB 2.5-inch 7 mm SATA drive with 10,512 TBW. The suffixes are customer and firmware identities rather than capacity or endurance grades, and both appear on parts in circulation. If a platform pins firmware to a code, name it on the PO; if not, either will do and we ship from the batch in hand.
One line of care on the suffix family: -00A07 and -00B07 also appear on the read-intensive PM893a, while -00B7C belongs to the earlier PM897 build. A PO written against the wrong suffix is a different line item even where the drive underneath performs identically.
Three fields on the label are enough. The model number carries 1T9 for this capacity and 3T8 for the 3.84 TB member, in the same position, followed by the same HENA. The capacity line printed above the part number states it in full, "1.92 TB" or "3.84 TB", and the ordering suffix sits on the same label. Reading the capacity block and the capacity line together takes a second and removes the only ambiguous step in receiving this range.
Weight and height do not help. Both capacities are 7 mm 2.5-inch drives in the same case at the same 70 g maximum, and both draw the same power, so nothing physical separates them. A bay that mixes the two by accident will not fail to train; it will simply present 1.92 TB where 3.84 TB was expected, and the discrepancy surfaces at the array rather than at the bench.
The same logic applies to the two builds. A PM897 1.92 TB carries HBNA and a -00B7C suffix where this drive carries HENA and -00A07 or -00B07. Those are interchangeable in performance terms and should still be kept apart in an asset register, because a firmware baseline pinned to one will not match the other.
10,512 TB over five years is 5.76 TB of writes every day. Written flat out at 530 MB/s the rating would last about 230 days, so the ceiling is far outside anything a 1.92 TB volume produces in service. The daily allowance covers a node's whole write load — database files, WAL, hypervisor swap, container logs, a staging area — rather than one application's share of it.
The number that decides this capacity against the one above is the rebuild. A full 1.92 TB rewrite at 530 MB/s takes about an hour; the 3.84 TB member takes about two. That is the whole argument for stopping here when an array has to stay inside a maintenance window: the larger drive halves the device count and halves the idle draw, and doubles the time the array spends unprotected after a failure.
Against the capacity below, the step from the 960 GB member doubles both the bytes and the budget to 10,512 TB without moving a single performance figure — 560/530 MB/s and 97K/60K IOPS are identical at both, as they are at every capacity in this range. So the choice between them is room and rebuild time, not speed.
Within the mixed-use group this drive is second on endurance rather than first. The SM863a at 1.92 TB carries 3.5 DWPD and 12,320 TBW, about 17% more budget on 2-bit MLC, at 510/485 MB/s and 28K random write. If the workload queues writes, this drive completes more than twice the write operations per second; if it writes steadily and never queues, the older drive's extra budget is the better purchase.
| Model | Capacity | Sequential read / write | Random 4K read / write | Endurance | Class |
|---|---|---|---|---|---|
| PM897a 1.92 TB | 1.92 TB | 560 / 530 MB/s | 97K / 60K IOPS | 10,512 TB (3.0 DWPD) | Mixed-use |
| PM897 1.92 TB | 1.92 TB | 560 / 530 MB/s | 97K / 60K IOPS | 10,512 TB (3.0 DWPD) | Mixed-use, earlier build |
| SM883 1.92 TB | 1.92 TB | 540 / 520 MB/s | 97K / 29K IOPS | 10,512 TB (3.0 DWPD) | Mixed-use, MLC |
| SM863a 1.92 TB | 1.92 TB | 510 / 485 MB/s | 95K / 28K IOPS | 12,320 TB (3.5 DWPD) | Mixed-use, MLC |
| PM893a 1.92 TB | 1.92 TB | 560 / 530 MB/s | 97K / 31K IOPS | 3,504 TB (1.0 DWPD) | Read-intensive |
| PM893 1.92 TB | 1.92 TB | 550 / 520 MB/s | 98K / 30K IOPS | 3,504 TB (1.0 DWPD) | Read-intensive |
| PM883 1.92 TB | 1.92 TB | 550 / 520 MB/s | 98K / 25K IOPS | 2,733 TB (0.78 DWPD) | Read-intensive |
The first two rows are one drive under two build codes, identical in every column. The next two are the MLC comparison, and between them they cover the whole endurance argument at this capacity: the SM883 matches this drive's 10,512 TBW with roughly half the random write, and the SM863a exceeds the budget by 17% with less than half of it. Neither wins on both lines.
The three read-intensive rows sit at a third of this budget or less, and they are the right purchase for a volume that is filled once and read for five years. Their random read is a match or slightly better, and their price per device is lower; what they cannot do is absorb a daily rewrite for five years without reaching end of life early.
Every drive carries a 1-year warranty from us against defects in workmanship and function. Verified faulty units are replaced or refunded and we cover return shipping. Stock is held in both new and used condition; the condition you order is confirmed before dispatch, and used units are pull-tested rather than untested lots. Stock is held in our own warehouse and normally dispatches within three to seven working days, with tracking issued at dispatch.
This capacity is quoted rather than listed, because price moves with condition, quantity and batch. Send the quantity, the condition you need, the platform the drives are going into and — if it matters to your firmware baseline — which ordering code you need, and you will get a quote with lead time the same working day. Matched sets for mirroring or parity are selected from a single build and batch where stock allows, including firmware revision and wear level.
Tell us who you are — we reply within one working day with a firm quote, stock status and lead time. Volume discounts available.
15.36 TB E1.L 1U long ruler NVMe SSD, PCIe 4.0, ordering code MZEL215THBLA-00AMV
7.68 TB E1.S 1T NVMe SSD, PCIe 4.0, ordering codes MZCL27T6HBLA-00AMV / MZTL27T6HBLA-00A07
3.84 TB E1.S 1T NVMe SSD, PCIe 4.0, ordering codes MZCL23T8HCLS-00AMV / MZTL23T8HCLS-00A07
1.92 TB E1.S 1T (9.5 mm) NVMe SSD, PCIe 4.0, ordering code MZCL21T9HCJR-00AMV