No mmcblk0p1 when I do $lsblk

Hi, when I boot-up my Xavier in recovery mode, I don’t see a mmcblk0p1. But when I do a lsusb, I see:

Bus 001 Device 059: ID 0955:7e19 NVIDIA Corp. APX
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

So can anyone let me know if I am missing something here?


It isn’t possible to boot up in recovery mode and interact with the Jetson other than flashing. Is the lsblk and/or lsusb from a host PC? When fully booted, what do you see from “lsblk -f”? Is this an SD card model (a dev kit)?

Yes it is from a host machine. lsblk -f shows:

NAME   FSTYPE   LABEL      UUID                                 FSAVAIL FSUSE% MOUNTPOINT
loop0  squashfs                                                       0   100% /snap/core18/2284
loop1  squashfs                                                       0   100% /snap/bare/5
loop2  squashfs                                                       0   100% /snap/gnome-3-34-1804/77
loop3  squashfs                                                       0   100% /snap/gtk-common-themes/1519
loop4  squashfs                                                       0   100% /snap/core20/1405
loop5  squashfs                                                       0   100% /snap/snap-store/547
loop6  squashfs                                                       0   100% /snap/core20/1434
loop7  squashfs                                                       0   100% /snap/gtk-common-themes/1515
loop8  squashfs                                                       0   100% /snap/gnome-3-38-2004/87
loop9  squashfs                                                       0   100% /snap/core18/2344
loop10 squashfs                                                       0   100% /snap/gnome-3-38-2004/99
loop11 squashfs                                                       0   100% /snap/snap-store/558
loop12 squashfs                                                       0   100% /snap/gnome-3-34-1804/72
loop13 squashfs                                                       0   100% /snap/snapd/15534
loop14 squashfs                                                       0   100% /snap/snapd/15177
├─sda1 vfat                CABC-AB04                               511M     0% /boot/efi
└─sda5 ext4                56e0e42b-2462-47b5-b7ba-74b0253dcbf6   90.6G    49% /
sdb    vfat     L4T-README 6536-E270                              15.9M     1% /media/abhigyan/L4T-README

Yes it is an SD card model.


The host PC does not use the eMMC. You would see mmcblk0p1 from “lsblk -f” if it was running on a fully booted eMMC model of Jetson. You might also get mmcblk0p1 under other circumstances on a Jetson. However, the host PC only sees USB devices from the Jetson, and those will never use the “mmcblk#p#” convention over USB.

Also, note that a recovery mode Jetson is not a mass storage device, and that only USB devices programmed to be mass storage will show up as a storage device. A recovery mode Jetson is a custom device and is understood only by the custom driver (conveniently called the “driver package” in the flash software).

You didn’t miss anything… Host side won’t see jetson Xavier as mmcblk0p1…

Not quite sure where did you get such idea.

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