Jetson Orin NX 16GB in Nvidia Carrier Board Creating Custom System Image for Production fails

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin NX
1

I am trying to do

sudo ./Linux_for_Tegra/tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -r jetson-orin-nano-devkit

I have run the

sudo systemctl stop udisks2.service
sudo ./tools/l4t_flash_prerequisites.sh
sudo service nfs-kernel-server start

and I have shorted FC REC and GND, but on step two I get the following error

****************************************************
*                                                  *
*  Step 2: Boot the device with flash initrd image *
*                                                  *
****************************************************
/home/kallah/nvidia/nvidia_sdk/JetPack_6.1_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/temp_initrdflash/bootloader0 /home/kallah/nvidia/nvidia_sdk/JetPack_6.1_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra
./tegraflash.py --bl uefi_jetson_with_dtb_aligned_blob_w_bin_sigheader.bin.encrypt --bct br_bct_BR.bct --securedev  --bldtb tegra234-p3768-0000+p3767-0000-nv.dtb --applet rcm_2_encrypt.rcm --applet_softfuse rcm_1_encrypt.rcm --instance 1-1 --cmd "rcmboot"  --cfg secureflash.xml --chip 0x23 --mb1_bct mb1_bct_MB1_sigheader.bct.encrypt --mem_bct mem_rcm_sigheader.bct.encrypt --mb1_cold_boot_bct mb1_cold_boot_bct_MB1_sigheader.bct.encrypt --mb1_bin mb1_t234_prod_aligned_sigheader.bin.encrypt --psc_bl1_bin psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --mem_bct_cold_boot mem_coldboot_sigheader.bct.encrypt  --bins "psc_fw pscfw_t234_prod_sigheader.bin.encrypt; mts_mce mce_flash_o10_cr_prod_sigheader.bin.encrypt; tsec_fw tsec_t234_sigheader.bin.encrypt; mb2_applet applet_t234_sigheader.bin.encrypt; mb2_bootloader mb2_t234_with_mb2_cold_boot_bct_MB2_sigheader.bin.encrypt; xusb_fw xusb_t234_prod_sigheader.bin.encrypt; pva_fw nvpva_020_sigheader.fw.encrypt; dce_fw display-t234-dce_sigheader.bin.encrypt; nvdec nvdec_t234_prod_sigheader.fw.encrypt; bpmp_fw bpmp_t234-TE980M-A1_prod_sigheader.bin.encrypt; bpmp_fw_dtb tegra234-bpmp-3767-0000-a02-3509-a02_with_odm_sigheader.dtb.encrypt; rce_fw camera-rtcpu-t234-rce_sigheader.img.encrypt; ape_fw adsp-fw_sigheader.bin.encrypt; spe_fw spe_t234_sigheader.bin.encrypt; tos tos-optee_t234_sigheader.img.encrypt; eks eks_t234_sigheader.img.encrypt; kernel boot0.img; kernel_dtb tegra234-p3768-0000+p3767-0000-nv.dtb"    --bct_backup 
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands
 

 Entering RCM boot

[   0.0264 ] mb1_t234_prod_aligned_sigheader.bin.encrypt filename is from --mb1_bin
[   0.0264 ] psc_bl1_t234_prod_aligned_sigheader.bin.encrypt filename is from --psc_bl1_bin
[   0.0264 ] rcm boot with presigned binaries
[   0.0269 ] tegrarcm_v2 --instance 1-1 --new_session --chip 0x23 0 --uid --download bct_br br_bct_BR.bct --download mb1 mb1_t234_prod_aligned_sigheader.bin.encrypt --download psc_bl1 psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt
[   0.0271 ] BR_CID: 0x80012344705DF3107400000010008280
[   0.0374 ] Sending bct_br
[   0.0452 ] ERROR: might be timeout in USB write.
Error: Return value 3
Command tegrarcm_v2 --instance 1-1 --new_session --chip 0x23 0 --uid --download bct_br br_bct_BR.bct --download mb1 mb1_t234_prod_aligned_sigheader.bin.encrypt --download psc_bl1 psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt
Cleaning up...

I am not sure what this error means

lsusb | grep -i nvidia
Bus 001 Device 006: ID 0955:7323 NVIDIA Corp. APX

sudo dmesg | tail -n 50
[  303.495444] audit: type=1400 audit(1736927378.090:78): apparmor="DENIED" operation="capable" class="cap" profile="/snap/snapd/23545/usr/lib/snapd/snap-confine" pid=10392 comm="snap-confine" capability=38  capname="perfmon"
[  305.431288] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
[  305.748577] audit: type=1400 audit(1736927380.343:79): apparmor="DENIED" operation="capable" class="cap" profile="/snap/snapd/23545/usr/lib/snapd/snap-confine" pid=10716 comm="snap-confine" capability=12  capname="net_admin"
[  305.748585] audit: type=1400 audit(1736927380.343:80): apparmor="DENIED" operation="capable" class="cap" profile="/snap/snapd/23545/usr/lib/snapd/snap-confine" pid=10716 comm="snap-confine" capability=38  capname="perfmon"
[  305.861469] audit: type=1400 audit(1736927380.456:81): apparmor="DENIED" operation="symlink" class="file" profile="snap.snapd-desktop-integration.snapd-desktop-integration" name="/dev/char/195:255" pid=10792 comm="snapd-desktop-i" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
[  305.862906] audit: type=1400 audit(1736927380.457:82): apparmor="DENIED" operation="symlink" class="file" profile="snap.snapd-desktop-integration.snapd-desktop-integration" name="/dev/char/195:0" pid=10792 comm="snapd-desktop-i" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
[  305.862990] audit: type=1400 audit(1736927380.457:83): apparmor="DENIED" operation="symlink" class="file" profile="snap.snapd-desktop-integration.snapd-desktop-integration" name="/dev/char/195:0" pid=10792 comm="snapd-desktop-i" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
[  305.864823] audit: type=1400 audit(1736927380.459:84): apparmor="DENIED" operation="symlink" class="file" profile="snap.snapd-desktop-integration.snapd-desktop-integration" name="/dev/char/195:0" pid=10792 comm="snapd-desktop-i" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
[  305.865639] audit: type=1400 audit(1736927380.460:85): apparmor="DENIED" operation="symlink" class="file" profile="snap.snapd-desktop-integration.snapd-desktop-integration" name="/dev/char/195:0" pid=10792 comm="snapd-desktop-i" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
[  305.871202] audit: type=1400 audit(1736927380.465:86): apparmor="DENIED" operation="symlink" class="file" profile="snap.snapd-desktop-integration.snapd-desktop-integration" name="/dev/char/195:255" pid=10792 comm="snapd-desktop-i" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
[  306.281970] rfkill: input handler disabled
[  306.562517] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
[  308.084168] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
[  308.087240] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
[  308.090290] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
[  308.093352] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
[  308.121165] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
[  308.124217] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
[  308.127224] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
[  308.130286] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
[  308.157805] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
[  308.160846] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
[  308.163887] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
[  308.166888] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
[ 1843.066790] warning: `ThreadPoolForeg' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
[ 2696.639257] usb 1-1: USB disconnect, device number 2
[ 2920.219086] NFSD: Using nfsdcld client tracking operations.
[ 2920.219090] NFSD: no clients to reclaim, skipping NFSv4 grace period (net f0000000)
[ 3010.925266] NFSD: Using nfsdcld client tracking operations.
[ 3010.925279] NFSD: no clients to reclaim, skipping NFSv4 grace period (net f0000000)
[ 3194.942647] usb 1-1: new high-speed USB device number 6 using xhci_hcd
[ 3195.071393] usb 1-1: New USB device found, idVendor=0955, idProduct=7323, bcdDevice= 4.01
[ 3195.071400] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3195.071403] usb 1-1: Product: APX
[ 3195.071405] usb 1-1: Manufacturer: NVIDIA Corp.
[ 3204.651736] NFSD: Using nfsdcld client tracking operations.
[ 3204.651745] NFSD: no clients to reclaim, skipping NFSv4 grace period (net f0000000)
[ 3268.890729] NFSD: Using nfsdcld client tracking operations.
[ 3268.890736] NFSD: no clients to reclaim, skipping NFSv4 grace period (net f0000000)
[ 3286.739462] NFSD: Using nfsdcld client tracking operations.
[ 3286.739466] NFSD: no clients to reclaim, skipping NFSv4 grace period (net f0000000)
[ 3331.923578] NFSD: Using nfsdcld client tracking operations.
[ 3331.923582] NFSD: no clients to reclaim, skipping NFSv4 grace period (net f0000000)
[ 3444.684207] NFSD: Using nfsdcld client tracking operations.
[ 3444.684212] NFSD: no clients to reclaim, skipping NFSv4 grace period (net f0000000)
[ 3484.450955] NFSD: Using nfsdcld client tracking operations.
[ 3484.450959] NFSD: no clients to reclaim, skipping NFSv4 grace period (net f0000000)
[ 3633.491440] NFSD: Using nfsdcld client tracking operations.
[ 3633.491445] NFSD: no clients to reclaim, skipping NFSv4 grace period (net f0000000)
[ 3655.938073] loop27: detected capacity change from 0 to 131072
kallah@kallah-Legion-5-Pro-16ACH6H:~/nvidia/nvidia_sdk/JetPack_6.1_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra$ sudo systemctl status udisks2.service
○ udisks2.service - Disk Manager
     Loaded: loaded (/lib/systemd/system/udisks2.service; enabled; vendor preset: enabled)
     Active: inactive (dead) since Wed 2025-01-15 09:29:40 CET; 23min ago
       Docs: man:udisks(8)
    Process: 815 ExecStart=/usr/libexec/udisks2/udisksd (code=exited, status=0/SUCCESS)
   Main PID: 815 (code=exited, status=0/SUCCESS)
        CPU: 149ms

jan. 15 08:44:39 kallah-Legion-5-Pro-16ACH6H systemd[1]: Starting Disk Manager...
jan. 15 08:44:39 kallah-Legion-5-Pro-16ACH6H udisksd[815]: udisks daemon version 2.9.4 starting
jan. 15 08:44:39 kallah-Legion-5-Pro-16ACH6H udisksd[815]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
jan. 15 08:44:39 kallah-Legion-5-Pro-16ACH6H udisksd[815]: Failed to load the 'mdraid' libblockdev plugin
jan. 15 08:44:39 kallah-Legion-5-Pro-16ACH6H systemd[1]: Started Disk Manager.
jan. 15 08:44:40 kallah-Legion-5-Pro-16ACH6H udisksd[815]: Acquired the name org.freedesktop.UDisks2 on the system message bus
jan. 15 09:29:40 kallah-Legion-5-Pro-16ACH6H systemd[1]: Stopping Disk Manager...
jan. 15 09:29:40 kallah-Legion-5-Pro-16ACH6H udisksd[815]: udisks daemon version 2.9.4 exiting
jan. 15 09:29:40 kallah-Legion-5-Pro-16ACH6H systemd[1]: udisks2.service: Deactivated successfully.
jan. 15 09:29:40 kallah-Legion-5-Pro-16ACH6H systemd[1]: Stopped Disk Manager.
kallah@kallah-Legion-5-Pro-16ACH6H:~/nvidia/nvidia_sdk/JetPack_6.1_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra$ sudo service nfs-kernel-server status
● nfs-server.service - NFS server and services
     Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor preset: enabled)
     Active: active (exited) since Wed 2025-01-15 09:45:08 CET; 7min ago
    Process: 31165 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS)
    Process: 31166 ExecStart=/usr/sbin/rpc.nfsd (code=exited, status=0/SUCCESS)
   Main PID: 31166 (code=exited, status=0/SUCCESS)
        CPU: 7ms

jan. 15 09:45:07 kallah-Legion-5-Pro-16ACH6H systemd[1]: Starting NFS server and services...
jan. 15 09:45:08 kallah-Legion-5-Pro-16ACH6H systemd[1]: Finished NFS server and services.

Any help would be appreciated!

3

I plugged the USB cable in and out and rebooted the device and now it fails here instead:

Waiting for device to expose ssh ......Waiting for device to expose ssh ...Device has booted into initrd. You can ssh to the target by the command:
$ ssh root@fc00:1:1:0::2
Cleaning up...
Log is saved to Linux_for_Tegra/initrdlog/flash_1-1_0_20250115-100031.log 
Run command: 
ln -s /proc/self/fd /dev/fd && mount -o nolock [fc00:1:1::1]:/home/kallah/nvidia/nvidia_sdk/JetPack_6.1_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/tools/backup_restore /mnt && /mnt/nvrestore_partitions.sh -e nvme0n1 -n 
 on root@fc00:1:1::2
/mnt/nvrestore_partitions.sh: line 182: pushd: /mnt/images: No such file or directory
4

I do have a /mnt/images on my host machine

ls /mnt/
images
5

Hi @mrKallah

It seems that you are trying to flash the device with a backup that you previously saved. Have you tested flashing the device Orin NX with the SDKManager just to ensure that the problem is not related to this?

Have you tested the steps mentioned in this documentation? You could also test running the following command to disable autosuspend on your host PC as recommended on this forum topic:

sudo -s echo -1 > /sys/module/usbcore/parameters/autosuspend

Please tell me how this goes.

Regards,

Ricardo González Víquez
Embedded SW Engineer at RidgeRun
Contact us: support@ridgerun.com
Developers wiki: https://developer.ridgerun.com
Website: www.ridgerun.com

6

I am currently only accessing via phone, so I’ll have to read through the links you sent tomorrow. But you have misunderstood the premise of what I am trying to do. I am trying to create a system image from a jetson which has been configured. I dont think i explained this too well, apologies

8

Hi mrKallah,

Are you using the devkit or custom board for Orin NX?

It seems you are using backup/restore script to create a backup image from a Jetson device.
Have you confirmed that you board can boot successfully and the rootfs is from NVMe SSD before creating the backup image?

The error message shows that the /mnt/images cannot be found on your host.
Have you confirmed that it has been mounted correctly even if you can find it from your host?

I would suggest you providing the full log from both host and the device for further check.

9

I am using the NVIDIA Jetson Orin Nano Devkit, where I have replaced the Nano with a 16GB NX module.

I have just double checked that the device still boots fine. I can get the ubuntu login screen so that works fine.

$ ll -lR /mnt/
/mnt/:
total 12
drwxr-xr-x  3 root root 4096 jan.  15 09:59 ./
drwxr-xr-x 21 root root 4096 aug.  21 14:31 ../
drwxr-xr-x  2 root root 4096 jan.  15 09:59 images/

/mnt/images:
total 8
drwxr-xr-x 2 root root 4096 jan.  15 09:59 ./
drwxr-xr-x 3 root root 4096 jan.  15 09:59 ../

$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth
Bus 003 Device 002: ID 048d:c965 Integrated Technology Express, Inc. ITE Device(8295)
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 05e3:0620 Genesys Logic, Inc. USB3.2 Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 048d:c101 Integrated Technology Express, Inc. ITE Device(8910)
Bus 001 Device 004: ID 5986:115f Acer, Inc Integrated Camera
Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 026: ID 0955:7323 NVIDIA Corp. APX
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I have attached the log from the host machine, but I am unsure where I can find the log from the host.
flash_1-1_0_20250115-143532.log (6.7 KB)
when I try to ssh the device and search for logs, I only find this

find -name *.log
./tmp/sshd.log
find: './mnt': Permission denied

which only says that there were some connections:

cat /tmp/sshd.log 
Server listening on :: port 22.
Server listening on 0.0.0.0 port 22.
Accepted password for root from fc00:1:1::1 port 33090 ssh2
Received disconnect from fc00:1:1::1 port 33090:11: disconnected by user
Disconnected from user root fc00:1:1::1 port 33090
Connection closed by fc00:1:1::1 port 33104 [preauth]
Failed password for root from fc00:1:1::1 port 42584 ssh2
Accepted password for root from fc00:1:1::1 port 42584 ssh2
lastlog_openseek: Couldn't stat /var/log/lastlog: No such file or directory
lastlog_openseek: Couldn't stat /var/log/lastlog: No such file or directory

Where do I find the logs for the device if you need those?

10

Hi @mrKallah Can you add the output of the lsblk command to check that images is correctly mounted even if it is placed on /mnt/? Could you also attach the dmesg logs of the target device? It would be very helpful if you could add a serial cable to the target device in order to check the logs from it. You can find how to do so by checking RidgeRun’s Orin NX developer wiki .

Regards,

Ricardo González Víquez
Embedded SW Engineer at RidgeRun
Contact us: support@ridgerun.com
Developers wiki: https://developer.ridgerun.com
Website: www.ridgerun.com

11

For the devkit, please refer to the instruction in Jetson Nano & NX Style - Serial Debug Console - JetsonHacks to capture serial console log.

Do you mean that /mnt/images is empty?

12

I have put the logs below. The

jetson.txt (84.5 KB)

host.log (104.9 KB)

Here is also the lsblk on the host machine, before and after running the backup restore script:

kallah@kallah-Legion-5-Pro-16ACH6H:~$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0         7:0    0 284,9M  1 loop /snap/atom/286
loop1         7:1    0     4K  1 loop /snap/bare/5
loop2         7:2    0  55,7M  1 loop /snap/core18/2829
loop3         7:3    0  55,4M  1 loop /snap/core18/2846
loop4         7:4    0    64M  1 loop /snap/core20/2379
loop5         7:5    0  63,7M  1 loop /snap/core20/2434
loop6         7:6    0  73,9M  1 loop /snap/core22/1663
loop7         7:7    0  73,9M  1 loop /snap/core22/1722
loop8         7:8    0 273,7M  1 loop /snap/firefox/5437
loop9         7:9    0 274,4M  1 loop /snap/firefox/5600
loop10        7:10   0 164,8M  1 loop /snap/gnome-3-28-1804/198
loop11        7:11   0 218,4M  1 loop /snap/gnome-3-34-1804/93
loop12        7:12   0   497M  1 loop /snap/gnome-42-2204/141
loop13        7:13   0 505,1M  1 loop /snap/gnome-42-2204/176
loop15        7:15   0  65,5M  1 loop /snap/go/10748
loop16        7:16   0  91,7M  1 loop /snap/gtk-common-themes/1535
loop17        7:17   0 121,8M  1 loop /snap/slack/176
loop18        7:18   0 121,8M  1 loop /snap/slack/178
loop19        7:19   0  12,9M  1 loop /snap/snap-store/1113
loop20        7:20   0  12,2M  1 loop /snap/snap-store/1216
loop21        7:21   0  44,3M  1 loop /snap/snapd/23258
loop22        7:22   0  44,4M  1 loop /snap/snapd/23545
loop23        7:23   0   564K  1 loop /snap/snapd-desktop-integration/247
loop24        7:24   0   568K  1 loop /snap/snapd-desktop-integration/253
loop25        7:25   0 101,1M  1 loop /snap/teams-for-linux/724
loop26        7:26   0 101,1M  1 loop /snap/teams-for-linux/730
loop27        7:27   0  65,5M  1 loop /snap/go/10818
nvme1n1     259:0    0   1,8T  0 disk 
├─nvme1n1p1 259:1    0   512M  0 part /boot/efi
└─nvme1n1p2 259:2    0   1,8T  0 part /var/snap/firefox/common/host-hunspell
                                      /
nvme0n1     259:3    0 476,9G  0 disk /media/kallah/Share
kallah@kallah-Legion-5-Pro-16ACH6H:~$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0         7:0    0 284,9M  1 loop /snap/atom/286
loop1         7:1    0     4K  1 loop /snap/bare/5
loop2         7:2    0  55,7M  1 loop /snap/core18/2829
loop3         7:3    0  55,4M  1 loop /snap/core18/2846
loop4         7:4    0    64M  1 loop /snap/core20/2379
loop5         7:5    0  63,7M  1 loop /snap/core20/2434
loop6         7:6    0  73,9M  1 loop /snap/core22/1663
loop7         7:7    0  73,9M  1 loop /snap/core22/1722
loop8         7:8    0 273,7M  1 loop /snap/firefox/5437
loop9         7:9    0 274,4M  1 loop /snap/firefox/5600
loop10        7:10   0 164,8M  1 loop /snap/gnome-3-28-1804/198
loop11        7:11   0 218,4M  1 loop /snap/gnome-3-34-1804/93
loop12        7:12   0   497M  1 loop /snap/gnome-42-2204/141
loop13        7:13   0 505,1M  1 loop /snap/gnome-42-2204/176
loop15        7:15   0  65,5M  1 loop /snap/go/10748
loop16        7:16   0  91,7M  1 loop /snap/gtk-common-themes/1535
loop17        7:17   0 121,8M  1 loop /snap/slack/176
loop18        7:18   0 121,8M  1 loop /snap/slack/178
loop19        7:19   0  12,9M  1 loop /snap/snap-store/1113
loop20        7:20   0  12,2M  1 loop /snap/snap-store/1216
loop21        7:21   0  44,3M  1 loop /snap/snapd/23258
loop22        7:22   0  44,4M  1 loop /snap/snapd/23545
loop23        7:23   0   564K  1 loop /snap/snapd-desktop-integration/247
loop24        7:24   0   568K  1 loop /snap/snapd-desktop-integration/253
loop25        7:25   0 101,1M  1 loop /snap/teams-for-linux/724
loop26        7:26   0 101,1M  1 loop /snap/teams-for-linux/730
loop27        7:27   0  65,5M  1 loop /snap/go/10818
nvme1n1     259:0    0   1,8T  0 disk 
├─nvme1n1p1 259:1    0   512M  0 part /boot/efi
└─nvme1n1p2 259:2    0   1,8T  0 part /var/snap/firefox/common/host-hunspell
                                      /
nvme0n1     259:3    0 476,9G  0 disk /media/kallah/Shar

and here is the output from lsblk and dmesg on the jetson via ssh.

ssh.log (40.6 KB)

With regards to the /mnt/images folder, on the host machine, yes this folder is empty and on the jetson I am unable to check as when I try via ssh I get permission denied and when I try from serial it doesnt read my spaces and so I get ls/mnt is not a known command or something like that

13

Do you have the devkit to reproduce the similar issue?
Or the issue is specific to your custom carrier board?

I’ve noticed that you use -r in this command, which is used for restore.
Please backup the board first.
i.e. please run the following command on your host instead. (and remember to configure the board in RCM mode first)

$ sudo ./tools/backup_restore/l4t_backup_restore.sh -b -e nvme0n1 jetson-orin-nano-devkit
14

Early in my testing, I was unaware that you had to be in the right folder when you ran the l4t_backup_restore.sh, and thus I spent some time trying to figure out why it didnt work. At that point, for some reason, I changed the command I was using from

sudo ./Linux_for_Tegra/tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -b jetson-orin-nano-devkit

to

sudo ./Linux_for_Tegra/tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -r jetson-orin-nano-devkit

most likely as I was trying everything from forum posts etc. I would recommend adding the requirement about what folder you need to be in, to the README.md file to avoid anyone else getting lost at that point.

15

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