After updating to Jetpack 6.2.1, my SATA SSD has stopped showing up.
There is no sda device in lsblk output, and I can’t see the SATA bridge in lspci output either.
Has anyone seen this before / know how to solve the issue?
Hi there,
So, It’s not Normal but updating often can have this arise if the Seeed builds DeviceTree isn’t included or if the hardware, like the sata controller or driver changes.
I pretty sure that is why the Vanilla Nvidia’s “upgrade” doesn’t work on most clones.
also why the wiki advises using a ubuntu host for the build or update (the generic DT) just works.
Since the platform is Seeed Studio reServer AI NVR (Jetson Orin NX 16GB), the SATA drives in that system are not native SATA from the SoC. They are exposed through a PCIe-to-SATA bridge on the carrier board. So the storage chain looks like this:
Jetson Orin NX
│
└─ PCIe root port
│
└─ PCIe → SATA bridge chip
│
└─ SATA drives (sda, sdb, etc.)
If the bridge disappears from lspci, the problem is before Linux storage drivers — it means the PCIe device is not being enumerated.
On Jetson systems this almost always comes down to one of three things after a JetPack upgrade.
Carrier-board Device Tree got replaced
JetPack updates frequently install a new kernel + default NVIDIA DTB.
The NVIDIA JetPack update can overwrite the carrier-board specific device tree that enables:
- PCIe lanes
- PCIe reset GPIOs
- slot power rails
- bridge devices
The NVIDIA Jetson Orin NX dev kit DTB does not contain the hardware definitions for the reServer carrier board, so if that DTB gets used instead, the PCIe bridge powering the SATA controller never comes up.
Result:
lspci → bridge missing
lsblk → no drives
BSP / overlay package not reinstalled
Seeed’s Jetson systems usually ship with a custom BSP layer that includes:
- carrier-board DT overlays
- PCIe configuration
- GPIO power enable
- fan + LED controls
After upgrading to JetPack 6.2.1, the system may now be running the generic NVIDIA kernel + DTB, not the Seeed BSP.
Reinstalling the board support package normally fixes it.
PCIe power-enable GPIO not configured
Some carriers use a GPIO to power the SATA bridge chip.
If that GPIO is not configured by the DT anymore, the bridge simply never powers on.
Linux then behaves exactly like you described.
Check which device tree is loaded:
cat /proc/device-tree/model
If this is a reServer system, the model should reference the reServer carrier board, not just the Jetson module.
If the wrong DTB is being used, reinstalling the Seeed BSP / device-tree overlays for JetPack 6.2.1 should restore the PCIe bridge and the SATA devices. 
HTH
GL 
PJ 