sudo ./tools/backup_restore/l4t_backup_restore.sh -e nvme0n1 -b jetson-orin-nano-devkit
mount: /mnt/images/tmp/tmp: wrong fs type, bad option, bad superblock on /dev/nvme0n1p15, missing codepage or helper program, or other error.
check:
jetpack 5.1.2 The largest is nvme0n1p14
jetpack 5.1.4/5/6 The largest is nvme0n1p15
Hard Disk Partition Type
nvme0n1p1 nvme0n1p15 ext4
nvme0n1p2……nvme0n1p14 none
Hi,
Do you mean that you’ve created multiple ext4 partitions and want to back them up or restore them?
Thanks
It’s not the nvme0n1p15 I created. It’s our newly released version. Compared to previous versions, the Jetson product has an additional partition. This causes an error when generating the image. You can use this command to generate the image yourselves.
Hi,
We dont observe 2 ext4 partitions in our developer kit.
Please provide the flashing commands for us to review.
Hi,
Could you run below commands under the /dev/disk/by-partlabel
Do you fuse your device?
ls -alh
Thanks
发件人："DavidDDD "notifications@nvidia.discoursemail.com;
发送时间：2026年4月10日(星期五) 下午3:48
收件人：“dufutian” dufutian@zhiyongxingkong.com;
主题：[NVIDIA Developer Forums] [Jetson Systems/Jetson Orin NX] Backup restore ,mount: wrong fs type, bad superblock on /dev/nvme0n1p15 on jetpack 5.1.4/5/6
Hi,
Do you have disk encryption enabled?
Please provide the commands used to flash the device
Thanks
nvidia@nvidia-ThinkPad-X250:~/Downloads/35.6.4/Linux_for_Tegra$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p “-c bootloader/t186ref/cfg/flash_t234_qspi.xml” --showlogs --network usb0 jetson-orin-nano-devkit internal
Hi,
We cannot reproduce two ext4 issue to flash our developer kit on version r35.6.4.
Do you have disk encryption enabled?
$ lsblk -f
NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
loop0 vfat L4T-README 1234-ABCD
zram0 [SWAP]
zram1 [SWAP]
zram2 [SWAP]
zram3 [SWAP]
zram4 [SWAP]
zram5 [SWAP]
nvme0n1
├─nvme0n1p1 ext4 52219493-35cc-4546-aa6f-cd14885e1687 442.4G 1% /
├─nvme0n1p2
├─nvme0n1p3
├─nvme0n1p4
├─nvme0n1p5
├─nvme0n1p6
├─nvme0n1p7
├─nvme0n1p8
├─nvme0n1p9
├─nvme0n1p10
├─nvme0n1p11 vfat CE42-CDB5
├─nvme0n1p12
├─nvme0n1p13
├─nvme0n1p14
└─nvme0n1p15
$ ls -lah /dev/disk/by-partlabel
total 0
drwxr-xr-x 2 root root 340 Jun 17 2024 .
drwxr-xr-x 8 root root 160 Jun 17 2024 ..
lrwxrwxrwx 1 root root 15 Jan 1 1970 APP -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 Jan 1 1970 A_kernel -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 15 Jan 1 1970 A_kernel-dtb -> ../../nvme0n1p3
lrwxrwxrwx 1 root root 15 Jan 1 1970 B_kernel -> ../../nvme0n1p5
lrwxrwxrwx 1 root root 15 Jan 1 1970 B_kernel-dtb -> ../../nvme0n1p6
lrwxrwxrwx 1 root root 16 Jan 1 1970 RECROOTFS -> ../../nvme0n1p10
lrwxrwxrwx 1 root root 16 Jan 1 1970 UDA -> ../../nvme0n1p15
lrwxrwxrwx 1 root root 16 Jan 1 1970 esp -> ../../nvme0n1p11
lrwxrwxrwx 1 root root 16 Jan 1 1970 esp_alt -> ../../nvme0n1p14
lrwxrwxrwx 1 root root 15 Jan 1 1970 recovery -> ../../nvme0n1p8
lrwxrwxrwx 1 root root 15 Jan 1 1970 recovery-dtb -> ../../nvme0n1p9
lrwxrwxrwx 1 root root 16 Jan 1 1970 recovery-dtb_alt -> ../../nvme0n1p13
lrwxrwxrwx 1 root root 16 Jan 1 1970 recovery_alt -> ../../nvme0n1p12
lrwxrwxrwx 1 root root 15 Jan 1 1970 reserved_for_chain_A_user -> ../../nvme0n1p4
lrwxrwxrwx 1 root root 15 Jan 1 1970 reserved_for_chain_B_user -> ../../nvme0n1p7
Thanks