Unsupported type nvme ssd jetson agx xavier

Robotics & Edge Computing Jetson Systems Jetson AGX Xavier
1

is this true that my ssd is not supported? or is there another problem?

my error :
aj@icardo:~/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh -c tools/kernel_flash/flash_l4t_external.xml --external-device /dev/sdb --direct jetson-agx-xavier-devkit external
/home/aj/nvidia/nvidia_sdk/JetPack_5.1.2_Linux_JETSON_AGX_XAVIER_TARGETS/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh --no-flash -c tools/kernel_flash/flash_l4t_external.xml --external-device /dev/sdb --direct jetson-agx-xavier-devkit external

  •                              *
  • Step 1: Generate flash packages *
  •                              *

/dev/sdb is not a supported external storage device
Cleaning up…

i was try to flash my vgen nvme ssd with usb connected to host, and this happens when i try to flash. i was intend to make my jetson booting in nvme and make it as rootfs

ssd type : vgen 256gb

3

Hi muhammadfakhriajrillah,

Are you using the devkit or custom board for AGX Xavier?

Why you specify /dev/sdb for NVMe SSD?
Please use nvme0n1p1 instead.

4

I am using emmc devkit 32gb. A little story that at first I intended to make Jetson boot on the SSD. I inserted the SSD into the Jetson then entered recovery mode and connected the Jetson to the host using a USB cable. but when doing the command
$ lsblk -d -p | grep nvme | cut -d\ -f 1 on host.
The host does not detect the NVME installed on Jetson, even though when in LSUSB, Jetson is detected as connected to the host.
The host only detects the SSD installed in the laptop (host). Therefore I intend to flash the SSD by removing it from the Jetson and flashing it using a USB cable.

so I use /dev/sdb for NVMe SSD.

what do you think?

5

Hi,

The host does not detect the NVME installed on Jetson, even though when in LSUSB, Jetson is detected as connected to the host.

The parameter “–external-device” is from the point of Jetson’s view. Not your host.

For Jetson, it is nvme0n1p1. If you use /dev/sdb, actually it is more like a USB drive to Jetson. Thus it goes wrong.

The host does not detect the nvme from it. Host only needs to recognize Jetson. Thus, it is sufficient if lsusb on host PC can list out Jetson.

I think you could try to flash nvme on Jetson again. But not putting it on host PC directly. It is a more common way.

If you fail, attach the full log.

6

I will try your recommendation. but I’m still confused, maybe I’ll ask some questions before doing it.

  1. the command(sudo ./tools/kernel_flash/l4t_initrd_flash.sh -c tools/kernel_flash/flash_l4t_external.xml --external-device /dev/sdb --direct jetson-agx-xavier-devkit external) executed from host terminal or jetson terminal?

if I run the command from the host terminal, I’m afraid that the nvme0n1p1 parameter will select my nvme on my laptop (host).

  1. if i run the command from the host terminal, Is it necessary to put Jetson in recovery mode?

just want to let you know that all this is to make my root size bigger than before, because previously I tried to install jetpack 5.1.2 using sdk manager and pointing to nvme, but there was no partition APP configuration session

7

Hi,

Just want to clarify one point first.

just want to let you know that all this is to make my root size bigger than before, because previously I tried to install jetpack 5.1.2 using sdk manager and pointing to nvme, but there was no partition APP configuration session

If ignoring the size of nvme, is sdkmanager able to flash to nvme successfully?

9

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