# Cannot detect the 2nd NVMe SSD on Jetson AGX Orin 32 Jetpack 6.1

**URL:** <https://forums.developer.nvidia.com/t/cannot-detect-the-2nd-nvme-ssd-on-jetson-agx-orin-32-jetpack-6-1/316516>\
**Category:** Jetson AGX Orin\
**Tags:** ssd\
**Created:** [December 11, 2024, 11:37am UTC](https://forums.developer.nvidia.com/t/cannot-detect-the-2nd-nvme-ssd-on-jetson-agx-orin-32-jetpack-6-1/316516 "2024-12-11T11:37:27Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![khanh.nguyen1](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@khanh.nguyen1](https://forums.developer.nvidia.com/u/khanh.nguyen1)\
**Post date:** [December 11, 2024, 11:37am UTC](https://forums.developer.nvidia.com/t/cannot-detect-the-2nd-nvme-ssd-on-jetson-agx-orin-32-jetpack-6-1/316516/1 "2024-12-11T11:37:27Z")

</div>

I have recently flashed our Jetson AGX Orin to JP6.1 but the system only detect 1 of the 2 NVMe SSD (2tb each). Below is my system info:

```auto
uname -a
Linux orin 5.15.148-tegra #1 SMP PREEMPT Mon Nov 11 12:45:39 +03 2024 aarch64 aarch64 aarch64 GNU/Linux

jetson@orin:~$ sudo cat /sys/kernel/debug/bpmp/debug/uphy/config
[sudo] password for jetson: 
0x00000000
jetson@orin:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 4K 1 loop /snap/bare/5
loop1 7:1 0 174.6M 1 loop /snap/chromium/2998
loop2 7:2 0 174.6M 1 loop /snap/chromium/3004
loop3 7:3 0 68.8M 1 loop /snap/core22/1666
loop4 7:4 0 68.8M 1 loop /snap/core22/1720
loop5 7:5 0 64.7M 1 loop /snap/cups/1069
loop6 7:6 0 251.1M 1 loop /snap/firefox/5360
loop7 7:7 0 483.3M 1 loop /snap/gnome-42-2204/178
loop8 7:8 0 91.7M 1 loop /snap/gtk-common-themes/1535
loop9 7:9 0 33.7M 1 loop /snap/snapd/21761
loop10 7:10 0 38.6M 1 loop /snap/snapd/23259
loop11 7:11 0 16M 1 loop 
mmcblk0 179:0 0 59.3G 0 disk 
├─mmcblk0p1 179:1 0 57.8G 0 part /media/jetson/5a68f905-5eae-490a-89fe-9a93c6cec226
├─mmcblk0p2 179:2 0 128M 0 part 
├─mmcblk0p3 179:3 0 768K 0 part 
├─mmcblk0p4 179:4 0 31.6M 0 part 
├─mmcblk0p5 179:5 0 128M 0 part 
├─mmcblk0p6 179:6 0 768K 0 part 
├─mmcblk0p7 179:7 0 31.6M 0 part 
├─mmcblk0p8 179:8 0 80M 0 part 
├─mmcblk0p9 179:9 0 512K 0 part 
├─mmcblk0p10 179:10 0 64M 0 part /boot/efi
├─mmcblk0p11 179:11 0 80M 0 part 
├─mmcblk0p12 179:12 0 512K 0 part 
├─mmcblk0p13 179:13 0 64M 0 part 
├─mmcblk0p14 179:14 0 400M 0 part 
└─mmcblk0p15 179:15 0 479.5M 0 part 
mmcblk0boot0 179:32 0 31.5M 1 disk 
mmcblk0boot1 179:64 0 31.5M 1 disk 
zram0 252:0 0 1.9G 0 disk [SWAP]
zram1 252:1 0 1.9G 0 disk [SWAP]
zram2 252:2 0 1.9G 0 disk [SWAP]
zram3 252:3 0 1.9G 0 disk [SWAP]
zram4 252:4 0 1.9G 0 disk [SWAP]
zram5 252:5 0 1.9G 0 disk [SWAP]
zram6 252:6 0 1.9G 0 disk [SWAP]
zram7 252:7 0 1.9G 0 disk [SWAP]
nvme0n1 259:0 0 1.8T 0 disk 
└─nvme0n1p1 259:1 0 1.8T 0 part /

jetson@orin:~$ lspci -vvv
0001:00:00.0 PCI bridge: NVIDIA Corporation Device 229e (rev a1) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 193
	IOMMU group: 58
	Bus: primary=00, secondary=01, subordinate=ff, sec-latency=0
	I/O behind bridge: 00000000-00000fff [size=4K]
	Memory behind bridge: 40000000-400fffff [size=1M]
	Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff [disabled]
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport

0001:01:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 128 bytes
	Interrupt: pin A routed to IRQ 193
	IOMMU group: 58
	Region 0: Memory at 20a8000000 (32-bit, non-prefetchable) [size=512K]
	Region 2: I/O ports at 300000 [disabled] [size=32]
	Region 3: Memory at 20a8080000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: igb

0004:00:00.0 PCI bridge: NVIDIA Corporation Device 229c (rev a1) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 195
	IOMMU group: 59
	Bus: primary=00, secondary=01, subordinate=ff, sec-latency=0
	I/O behind bridge: 0000f000-00000fff [disabled]
	Memory behind bridge: 40000000-400fffff [size=1M]
	Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff [disabled]
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport
	Kernel modules: tegra_pcie_dma_test

0004:01:00.0 Non-Volatile memory controller: KIOXIA Corporation Device 0018 (rev 01) (prog-if 02 [NVM Express])
	Subsystem: KIOXIA Corporation Device 0018
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 195
	IOMMU group: 59
	Region 0: Memory at 2428000000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: nvme
	Kernel modules: nvme

```

[dmesg.txt](https://forums.developer.nvidia.com/uploads/short-url/sg1tqX21TH2Y8iUbuT7vilOHRu8.txt) (99.5 KB)

---

<div class="post-metadata">

**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\
**Post date:** [December 12, 2024, 2:45am UTC](https://forums.developer.nvidia.com/t/cannot-detect-the-2nd-nvme-ssd-on-jetson-agx-orin-32-jetpack-6-1/316516/4 "2024-12-12T02:45:57Z")

</div>

Custom board or Devkit?

Which PCIe controller are you using for that 2nd NVMe?

---

<div class="post-metadata">

**Author:** ![khanh.nguyen1](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@khanh.nguyen1](https://forums.developer.nvidia.com/u/khanh.nguyen1)\
**Post date:** [December 12, 2024, 8:23am UTC](https://forums.developer.nvidia.com/t/cannot-detect-the-2nd-nvme-ssd-on-jetson-agx-orin-32-jetpack-6-1/316516/5 "2024-12-12T08:23:49Z")

</div>

Yes, custom board from Connect Tech. It seems we have similar issue with the Ethernet ports: 2 10Gb and 2 1Gb but only one 1Gb is recognized after flashing to JP6.1

```auto
~$ sudo lshw -class network

*-network

description: Ethernet interface

product: I210 Gigabit Network Connection

vendor: Intel Corporation

physical id: 0

bus info: [pci@0001](mailto:pci@0001):01:00.0

logical name: enP1p1s0

version: 03

serial: 00:0c:8b:b8:46:17

size: 1Gbit/s

capacity: 1Gbit/s

width: 32 bits

clock: 33MHz

capabilities: pm msi msix pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation

configuration: autonegotiation=on broadcast=yes driver=igb driverversion=5.15.148-tegra duplex=full firmware=0. 0-0 ip=10.0.3.109 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s

resources: irq:193 memory:20a8000000-20a807ffff ioport:300000(size=32) memory:20a8080000-20a8083fff

*-network:0

description: Ethernet interface

physical id: d

logical name: eth0

serial: 48:b0:2d:a8:b1:6a

capacity: 1Gbit/s

capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation

configuration: autonegotiation=on broadcast=yes driver=nvethernet driverversion=5.15.148-tegra link=no multicast=yes port=twisted pair

*-network:1

description: Ethernet interface

physical id: e

logical name: usb0

serial: 46:d7:7f:2e:91:19

capabilities: ethernet physical

configuration: broadcast=yes driver=g_ether driverversion=29-May-2008 firmware=tegra-xudc link=no multicast=yes

[jetson@orin](mailto:jetson@orin):~$ lspci | grep -i eth

0001:01:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)

```

---

<div class="post-metadata">

**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\
**Post date:** [December 12, 2024, 8:25am UTC](https://forums.developer.nvidia.com/t/cannot-detect-the-2nd-nvme-ssd-on-jetson-agx-orin-32-jetpack-6-1/316516/6 "2024-12-12T08:25:29Z")

</div>

How did you flash this board?

---

<div class="post-metadata">

**Author:** ![khanh.nguyen1](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@khanh.nguyen1](https://forums.developer.nvidia.com/u/khanh.nguyen1)\
**Post date:** [December 12, 2024, 8:27am UTC](https://forums.developer.nvidia.com/t/cannot-detect-the-2nd-nvme-ssd-on-jetson-agx-orin-32-jetpack-6-1/316516/7 "2024-12-12T08:27:17Z")

</div>

I flashed it using SDK manager from a host computer connecting to Jetson by usb cable

---

<div class="post-metadata">

**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\
**Post date:** [December 12, 2024, 8:27am UTC](https://forums.developer.nvidia.com/t/cannot-detect-the-2nd-nvme-ssd-on-jetson-agx-orin-32-jetpack-6-1/316516/8 "2024-12-12T08:27:53Z")

</div>

Did ConnectTech tell you their board support sdkmanager ?

---

<div class="post-metadata">

**Author:** ![khanh.nguyen1](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@khanh.nguyen1](https://forums.developer.nvidia.com/u/khanh.nguyen1)\
**Post date:** [December 12, 2024, 8:28am UTC](https://forums.developer.nvidia.com/t/cannot-detect-the-2nd-nvme-ssd-on-jetson-agx-orin-32-jetpack-6-1/316516/9 "2024-12-12T08:28:39Z")

</div>

We have contacted them but haven’t got reply yet

---

<div class="post-metadata">

**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\
**Post date:** [December 12, 2024, 8:29am UTC](https://forums.developer.nvidia.com/t/cannot-detect-the-2nd-nvme-ssd-on-jetson-agx-orin-32-jetpack-6-1/316516/10 "2024-12-12T08:29:30Z")

</div>

Nothing I can help here. Sdkmanager didn’t guarantee to work with a custom board.

---

<div class="post-metadata">

**Author:** ![khanh.nguyen1](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@khanh.nguyen1](https://forums.developer.nvidia.com/u/khanh.nguyen1)\
**Post date:** [December 12, 2024, 8:31am UTC](https://forums.developer.nvidia.com/t/cannot-detect-the-2nd-nvme-ssd-on-jetson-agx-orin-32-jetpack-6-1/316516/11 "2024-12-12T08:31:50Z")

</div>

To be more precise I followed this instruction to flash: [JetPack-6.x Installation for DSBOARD-AGX](https://www.forecr.io/blogs/installation/jetpack-6-x-installation-for-dsboard-agx)

It is a combination of SDKmanager and Script

---

<div class="post-metadata">

**Author:** ![WayneWWW](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/waynewww/32/14043_2.png) [@WayneWWW](https://forums.developer.nvidia.com/u/WayneWWW)\
**Post date:** [December 12, 2024, 8:33am UTC](https://forums.developer.nvidia.com/t/cannot-detect-the-2nd-nvme-ssd-on-jetson-agx-orin-32-jetpack-6-1/316516/12 "2024-12-12T08:33:47Z")

</div>

Why are you flashing a ConnectTech board with a method from Forecr…?

---

<div class="post-metadata">

**Author:** ![khanh.nguyen1](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@khanh.nguyen1](https://forums.developer.nvidia.com/u/khanh.nguyen1)\
**Post date:** [December 12, 2024, 8:38am UTC](https://forums.developer.nvidia.com/t/cannot-detect-the-2nd-nvme-ssd-on-jetson-agx-orin-32-jetpack-6-1/316516/13 "2024-12-12T08:38:12Z")

</div>

Good question! Perhaps, I need to reflash with ConnecTech method

---

<div class="post-metadata">

**Author:** ![khanh.nguyen1](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@khanh.nguyen1](https://forums.developer.nvidia.com/u/khanh.nguyen1)\
**Post date:** [December 13, 2024, 9:58am UTC](https://forums.developer.nvidia.com/t/cannot-detect-the-2nd-nvme-ssd-on-jetson-agx-orin-32-jetpack-6-1/316516/14 "2024-12-13T09:58:05Z")

</div>

I confirm that using ConnectTech’s BSP for reflash JP6.1 solved the problem

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/system/32/68080_2.png) [@system](https://forums.developer.nvidia.com/u/system)\
**Post date:** [December 27, 2024, 9:58am UTC](https://forums.developer.nvidia.com/t/cannot-detect-the-2nd-nvme-ssd-on-jetson-agx-orin-32-jetpack-6-1/316516/15 "2024-12-27T09:58:55Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.