Both use the SFF-8639 connector and the same 2.5-inch shape, so you cannot tell them apart by looking. U.3 remaps pins so one bay can run NVMe, SAS or SATA - a property of the backplane and controller, not of the drive, and not a speed difference. Check the backplane’s own documentation before buying the drive.
Prices updated · 14 carriers and adapters in stock · 8 claim U.3 or tri-mode support
Sources agree that U.2 and U.3 share the SFF-8639 connector and that U.3 remaps pins for tri-mode operation. They do NOT speak with one voice on the compatibility direction. SNIA-derived coverage states that U.3 devices are required to be backwards-compatible with U.2 hosts; vendor and reseller material more often states the converse - that U.3 bays accept U.2 drives while U.2 bays do not accept U.3 drives. Both directions are asserted in print and we have not found one document that settles it for every implementation. So this page tells you to check the backplane's own documentation for the specific machine, rather than handing you a rule that is right most of the time and expensive when it is not.
12 in-stock listings · a carrier is a passthrough - it does not convert protocols, whatever the listing implies · every specification here is the maker’s own claim, read from the listing · refreshed every few hours
| Adapter | Does what | Form | U.3 / tri-mode claimed | Price | |
|---|---|---|---|---|---|
10Gtek 10Gtek-u2-carrier 10Gtek U.2 SFF-8639 to PCIe NVMe SSD Adapter Card, PCIe 3.0 x4 Expansion Car | U.2 / U.3 carrier | 2.5-inch bay | not claimed | $18.12 | Buy Now |
10Gtek 10Gtek-u2-carrier 10GTEK PCIe 3.0 x8 to Dual U.2 NVMe SSD Adapter Card, SFF-8639 Interface wit | U.2 / U.3 carrier | PCIe card | not claimed | $21.64 | Buy Now |
StarTech StarTech-u2-carrier StarTech U.2 to PCIe 4.0 x4 Adapter for 2.5in U.2 NVMe SSD, SFF-8639, TAA | U.2 / U.3 carrier | 2.5-inch bay | seller states yes | $33.37 | Buy Now |
StarTech StarTech-u2-carrier StarTech M.2 NVMe to U.3 Adapter, PCIe M.2 SSD, TAA (1M25-U3-M2-ADAPTER) | U.2 / U.3 carrier | PCIe card | seller states yes | $39.93 | Buy Now |
ICY DOCK MB601VK-B ICY DOCK 2.5" U.2 NVMe SSD PCIe 3.0/4.0 Mobile Rack for External 3.5" Drive | U.2 / U.3 carrier | 2.5-inch bay | not claimed | $136.95 | Buy Now |
ICY DOCK MB111VP-B ICYDOCK ToughArmor MB111VP-B U.2 / U.3 NVMe SSD Mobile Rack for PCIe Expansi | U.2 / U.3 carrier | 2.5-inch bay | seller states yes | $144.99 | Buy Now |
ICY DOCK MB601VK-1B ICY DOCK 2.5” U.2 NVMe SSD PCIe 3.0/4.0 Mobile Rack for External 3.5” Drive | U.2 / U.3 carrier | 2.5-inch bay | not claimed | $152.63 | Buy Now |
ICY DOCK MB852M2PO-B ICY DOCK 2 x M.2 NVMe SSD PCIe 4.0 Mobile Rack for 9.5mm Ultra Slim ODD Bay | U.2 / U.3 carrier | 2.5-inch bay | seller states yes | $169.95 | Buy Now |
ICY DOCK MB092VK-B ICY DOCK Rugged 2 Bay 2.5” U.2/U.3 NVMe SSD(7mm) PCIe 4.0 Mobile Rack for Ex | U.2 / U.3 carrier | 2.5-inch bay | seller states yes | $225.40 | Buy Now |
ICY DOCK MB324V4P-B ICY DOCK ExpressCage MB324V4P-B 4 Bay 15mm U.2/U.3 SSD Mobile Rack for 5.25” | U.2 / U.3 carrier | 2.5-inch bay | seller states yes | $239.12 | Buy Now |
ICY DOCK MB491V5K-B ICY DOCK ToughArmor EX MB491V5K-B 2.5" U.2/U.3 NVMe SSD PCIe 5.0 Mobile Rack | U.2 / U.3 carrier | 2.5-inch bay | seller states yes | $438.01 | Buy Now |
ICY DOCK MB118VP-B ICY DOCK 6 Bay U.2 / U.3 NVMe SSD(7mm) PCIe 4.0 Mobile Rack Enclosure for 5. | U.2 / U.3 carrier | 2.5-inch bay | seller states yes | $449.79 | Buy Now |
2 in-stock listings · puts an M.2 NVMe SSD into an SFF-8639 bay · every specification here is the maker’s own claim, read from the listing · refreshed every few hours
| Adapter | Does what | Form | U.3 / tri-mode claimed | Price | |
|---|---|---|---|---|---|
StarTech StarTech-u2-to-m2 StarTech U.2 to M.2 Adapter, U.2 PCIe NVMe SSD, M.2 x4, TAA (M2E4SFF8643) | U.2 to M.2 carrier | PCIe card | not claimed | $26.17 | Buy Now |
StarTech StarTech-u2-to-m2 StarTech M.2 PCIe NVMe to U.2 SFF-8639 Adapter, 2.5in, TAA (U2M2E125) | U.2 to M.2 carrier | 2.5-inch bay | not claimed | $31.36 | Buy Now |
U.2 and U.3 look identical because they are identical where you can see them. Both use the SFF-8639 connector, a 2.5-inch drive form factor, and the same physical bay. You cannot tell them apart by looking, and neither can the person selling you one.
The difference is in what the pins carry. U.3 is specified as SFF-TA-1001 and remaps several of those pins so that a single bay can carry NVMe, SAS or SATA, with the host able to work out which one has arrived. That capability is what the word tri-mode refers to: SAS, SATA and NVMe drives all supported through one SFF-8639 connector when used with a tri-mode backplane and controller.
The consequence people miss is that this is a property of the BACKPLANE, not of the drive. A U.3 drive is a drive. What makes a bay universal is the backplane's wiring plus a controller that can switch protocols plus, usually, the Universal Backplane Management specification that lets the backplane report what it found. The drive is the passive party in the arrangement, and this is why adapters in this space can promise less than their listings suggest.
It is also why the difference is not about speed. Nothing in the specifications describes U.3 as faster than U.2 at the same link width, and there is no performance claim anywhere on this page, because our sources do not describe one. What U.3 buys a datacentre is consolidation - one backplane, one controller, one spares pool for three drive types - which matters enormously at fleet scale and very little in a single machine.
This is the part where most pages hand you a confident one-line rule, and we are not going to, because the sources do not agree and the disagreement is expensive.
SNIA-derived coverage of SFF-TA-1001 states the requirement in one direction: devices that are U.3-based are required to be backwards-compatible with U.2 hosts. Read plainly, that says a U.3 drive should work in a U.2 bay.
A great deal of vendor and reseller material states something close to the converse - that a U.3 backplane will happily take U.2 drives, while a U.2 backplane will not take U.3 drives. Read plainly, that says the opposite thing about which side is the safe one.
Both statements appear in print, repeatedly, from sources that are not obviously wrong. We have not found a single document that settles the question for every implementation, and it is entirely possible that both are true of different real-world backplanes, because a specification describing what an implementation is required to do is not the same as a survey of what shipping hardware actually does.
So the honest instruction is the annoying one: check the documentation for the specific backplane in the specific machine, and if you are buying drives for a server you already own, check the server vendor's own drive compatibility list rather than a general rule about the standard. That is more work than reading a rule. It is also the only advice on this subject we can give without guessing.
Mismatches in this space do not usually produce smoke. They produce a drive that is present and does nothing, which is harder to diagnose than a failure.
The most common outcome of a protocol mismatch is a bay that reports nothing. The drive spins up, draws power, and never enumerates - which looks exactly like a dead drive to a person who has just spent money on it. Before concluding anything about the hardware, check whether the backplane was ever wired for the protocol you are feeding it.
The second common outcome is partial function: the drive enumerates, but at a narrower link than expected, because a bay that is physically x4 has been wired for x2 or x1 upstream. That happens on both U.2 and U.3 backplanes and it has nothing to do with the specification - it is a wiring decision the machine's designer made, documented in the machine's own manual and nowhere else.
And the third, which is the one specific to tri-mode: a tri-mode controller costs more and needs the right firmware. A card advertised as tri-mode that has not been configured for it will not sprout the capability because you plugged in a U.3 drive. If you are building rather than buying a complete machine, the controller is where to check first, because it is the expensive part of the chain and the part sellers describe most loosely.
There are three genuinely different products in this category and the listings do not always make it obvious which one is in the box.
A CARRIER OR MOBILE RACK puts a 2.5-inch U.2 or U.3 drive into a bay in a chassis and routes its SFF-8639 connector to a cable or a backplane. It is a mechanical and electrical passthrough. It does not convert protocols, and if the far end of the cable is not wired for what the drive speaks, the carrier changes nothing. This is the largest group in the table below and it is the one whose listings most often imply more than a passive part can do.
A U.2-TO-PCIe ADAPTER is a card that puts a U.2 drive on a PCIe slot directly, bypassing the backplane question entirely. For a workstation or a desktop with spare slots and no hot-swap bays, this is frequently the simplest way to run an enterprise NVMe drive, and it sidesteps the entire U.2-versus-U.3 argument because there is no backplane involved.
A U.2-TO-M.2 ADAPTER goes the other way: it takes an M.2 NVMe SSD and presents it in the SFF-8639 shape so it can occupy a U.2 bay. That is useful when a chassis has 2.5-inch NVMe bays and the drive you want to use is M.2, which is a real situation in second-hand servers. Note that the M.2 drive's thermals in a sealed carrier are the M.2 drive's problem, and consumer M.2 drives were not designed for a backplane's airflow.
Where a listing in the table below claims U.3 or tri-mode support, that claim is rendered as the seller's claim and is badged as one. A passive carrier asserting tri-mode capability is describing the wiring it passes through rather than a capability it adds, and the distinction is the difference between a working bay and an expensive puzzle.
If you are adding an enterprise NVMe drive to a machine you already have, work in this order and the U.2-versus-U.3 question mostly evaporates.
First, establish what the machine actually provides. Hot-swap 2.5-inch NVMe bays wired to a backplane? Free PCIe slots and no bays? A mixture? The answer decides the product category before any specification does.
Second, if there are bays, find the machine's own documentation for what those bays are wired for. Server vendors publish this per model and it is authoritative in a way that a general rule about the standard is not. If there are no bays, a PCIe adapter card is the whole answer and you can stop reading about backplanes.
Third, buy the drive to match what you found rather than buying the drive first and then hunting for an adapter that rescues the decision. The adapters in this category are cheap; the drives are not, and a U.2 drive in a machine with no NVMe path is an expensive object.
Fourth, if the drive and the bay do not match and there is a free PCIe slot, the slot is the escape hatch. A U.2-to-PCIe card turns a backplane compatibility problem into a slot availability problem, and slot availability is something you can check by opening the case.
U.2 enterprise SSDs are the drives these carriers exist for · M.2 to PCIe · HBAs and tri-mode cards are the controller half of the question · used servers and part numbers for identifying what a machine actually has · enclosures if the answer is an external shelf · drive docks for testing a drive before it goes in anything.
They share the SFF-8639 connector and the 2.5-inch form factor - you cannot tell them apart by looking. U.3, specified as SFF-TA-1001, remaps several pins so one bay can carry NVMe, SAS or SATA when paired with a tri-mode backplane and controller. It is a property of the backplane rather than of the drive, and it is about consolidation rather than speed: nothing in the specifications describes U.3 as faster than U.2.
The sources disagree and we are not going to pick one for you. SNIA-derived coverage states that U.3 devices are required to be backwards-compatible with U.2 hosts. Much vendor and reseller material states the converse - U.3 bays take U.2 drives, U.2 bays do not take U.3 drives. Both appear in print and we have found no document that settles it for every implementation. Check the specific backplane's own documentation, or the server vendor's drive compatibility list for that model.
Usually nothing dramatic, which is what makes it hard to diagnose. The most common outcome is a bay that reports nothing at all - the drive spins up, draws power and never enumerates, which looks exactly like a dead drive. The second is a drive that works at a narrower link than expected, which is usually a wiring decision by the machine's designer rather than anything to do with the standard.
No. A carrier or mobile rack is a mechanical and electrical passthrough: it puts the drive in a bay and routes its connector onward. If the far end is not wired for what the drive speaks, the carrier changes nothing. Where a listing claims U.3 or tri-mode support we render it as the seller's claim, because a passive part is describing the wiring it passes through rather than a capability it adds.
Yes, if the machine has a free PCIe slot. A U.2-to-PCIe adapter card puts the drive directly on the bus with no backplane involved, which turns a compatibility question into a slot-availability question you can answer by opening the case. For workstations and desktops with no hot-swap bays, this is usually the simplest route to running an enterprise NVMe drive.
Yes, with a U.2-to-M.2 adapter, and it is a real solution for second-hand servers with 2.5-inch NVMe bays. Watch the thermals: a consumer M.2 drive inside a sealed carrier was not designed for a backplane's airflow, and sustained writes in that environment are where it will show.
Specification claims on this page were checked against the pages below on 4 August 2026. Where a widely-repeated figure did not survive that check, we report what the source says now and say so in the text rather than repeating the familiar number.