Can not mount the SSD

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

Sometime, when I reboot. The system shows thatERROR: PARTUUID=d0a946ff-af57-44bc-a1fb-d3264434e799 mount fail...
I reboot again and enter to the uefi shell fs2: I can see all my document.
How to see what happen?
Here is the detail log
log.txt (51.9 KB)
JP5.1.1

3

Hi AlfredNG,

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

How about the failed rate?

[   11.835496] Root device found: PARTUUID=d0a946ff-af57-44bc-a1fb-d3264434e799
[   12.271328] mmc1: SDHCI controller on 3400000.sdhci [3400000.sdhci] using ADMA 64-bit
[   16.353317] random: crng init done
[   26.571509] ERROR: PARTUUID=d0a946ff-af57-44bc-a1fb-d3264434e799 mount fail...

Are you booting from external NVMe SSD?

4

Yes, booting from external NVMe SSD.
I use custom board and jetsionio to create the dtb and just enable the i2s as the following

TIMEOUT 30
DEFAULT JetsonIO

MENU TITLE L4T boot options

LABEL primary
      MENU LABEL primary kernel
      LINUX /boot/Image
      FDT /boot/dtb/kernel_tegra234-p3767-0001-p3768-0000-a0.dtb
      INITRD /boot/initrd
      APPEND ${cbootargs} root=PARTUUID=d0a946ff-af57-44bc-a1fb-d3264434e799 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 console=ttyAMA0,115200 firmware_class.path=/etc/firmware fbcon=map:0 net.ifnames=0 nv-auto-config 

LABEL JetsonIO
	MENU LABEL Custom Header Config: <HDR40 User Custom [2024-09-12-210219]>
	LINUX /boot/Image
	FDT /boot/kernel_tegra234-p3767-0001-p3768-0000-a0-user-custom.dtb
	INITRD /boot/initrd
	APPEND ${cbootargs} root=PARTUUID=d0a946ff-af57-44bc-a1fb-d3264434e799 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 console=ttyAMA0,115200 firmware_class.path=/etc/firmware fbcon=map:0 net.ifnames=0 nv-auto-config

if the failed happen,it can not recovery any more.
Some devices will happen and some never happen

////////////////////////////////////////////////////////////////////////////////////
I put the not working SDD to the hard disk box and find that the puuid has be changed.

/dev/sdb4: PARTLABEL="reserved_for_chain_A_user" PARTUUID="598ad897-5c1a-4319-bd99-3f44ef651a10"
/dev/sdb10: PARTLABEL="RECROOTFS" PARTUUID="07304467-7c11-48d4-ad5c-de565cabad30"
/dev/sdb2: PARTLABEL="kernel" PARTUUID="21cdd957-b3d6-40b6-b20a-495b1daf8277"
/dev/sdb9: PARTLABEL="recovery-dtb" PARTUUID="3d8dd3f9-9091-4679-9e71-8b1d50ad5b5f"
/dev/sdb7: PARTLABEL="reserved_for_chain_B_user" PARTUUID="7d8000c5-bd30-464c-abd0-0a7c6b92583d"
/dev/sdb13: PARTLABEL="recovery-dtb_alt" PARTUUID="685474ea-dfa2-482b-b929-790c6e6c0d1e"
/dev/sdb5: PARTLABEL="kernel_b" PARTUUID="57f45844-0bae-4a59-ba75-100861082e2d"
/dev/sdb11: UUID="0443-604D" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="esp" PARTUUID="36762ba0-6cf9-443d-becf-bb7938040110"
/dev/sdb3: PARTLABEL="kernel-dtb" PARTUUID="297d66f4-af8f-4da1-8c10-5f7d22240e49"
/dev/sdb1: UUID="9d19868e-e487-4454-9cc9-7a0b6d869b9c" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="APP" PARTUUID="39fe6324-249f-44b3-975d-8e66bb76d802"
/dev/sdb8: PARTLABEL="recovery" PARTUUID="48da1397-48b8-49c3-a8f1-0b4a4f3f665a"
/dev/sdb14: PARTLABEL="esp_alt" PARTUUID="2bb5c9e6-a5f3-43b1-b454-a818abca3529"
/dev/sdb6: PARTLABEL="kernel-dtb_b" PARTUUID="35b8f784-ea44-4389-ba7c-3867c5e79a7a"
/dev/sdb12: PARTLABEL="recovery_alt" PARTUUID="0756c913-693b-4dfb-a76a-1b2057214b5f"

compare the working well

/dev/nvme0n1p1: UUID="b038e696-1ad1-4822-8546-f6a492c53016" TYPE="ext4" PARTLABEL="APP" PARTUUID="d0a946ff-af57-44bc-a1fb-d3264434e799"
/dev/nvme0n1p2: PARTLABEL="kernel" PARTUUID="0f1949a6-4f7b-450a-be8e-b97f5b883a2d"
/dev/nvme0n1p3: PARTLABEL="kernel-dtb" PARTUUID="009dc6ae-be00-47cd-a9aa-050329fcce06"
/dev/nvme0n1p4: PARTLABEL="reserved_for_chain_A_user" PARTUUID="65b66c03-eb73-4a2b-83c7-6534c39c5736"
/dev/nvme0n1p5: PARTLABEL="kernel_b" PARTUUID="78d7b285-ddbe-4add-a523-f637fa17406e"
/dev/nvme0n1p6: PARTLABEL="kernel-dtb_b" PARTUUID="1647f7d9-a95f-4824-b0e1-b7771a31f760"
/dev/nvme0n1p7: PARTLABEL="reserved_for_chain_B_user" PARTUUID="4224a1b6-5fb7-4b6c-bd64-7d096919a213"
/dev/nvme0n1p8: PARTLABEL="recovery" PARTUUID="400d6826-ac4c-4395-b702-934203b88e3c"
/dev/nvme0n1p9: PARTLABEL="recovery-dtb" PARTUUID="773f2d70-0c60-414b-b187-070a16775806"
/dev/nvme0n1p10: PARTLABEL="RECROOTFS" PARTUUID="16555bdb-1630-49c1-b1ff-92338922f316"
/dev/nvme0n1p11: UUID="3E6C-3F69" TYPE="vfat" PARTLABEL="esp" PARTUUID="618ed430-aa5b-4698-b31e-c21d34404547"
/dev/nvme0n1p12: PARTLABEL="recovery_alt" PARTUUID="60c495ce-e5f6-4227-b7dc-9c7d53489c59"
/dev/nvme0n1p13: PARTLABEL="recovery-dtb_alt" PARTUUID="0d05c3b4-005c-4593-8d60-dc478dbb4d23"
/dev/nvme0n1p14: PARTLABEL="esp_alt" PARTUUID="7db7a9bc-41bd-4f94-a7ec-4404724bdc3f"
/dev/zram0: UUID="5e5b03f7-7d12-4e46-a939-3c705ef7138b" TYPE="swap"
/dev/zram1: UUID="978a9e19-91dd-48e8-beb3-34a83ee6956a" TYPE="swap"
/dev/zram2: UUID="dc90bc3c-db98-4f46-a2d7-8c8ee13a54bd" TYPE="swap"
/dev/zram3: UUID="8e1e7ca6-b4f0-413e-8441-3785dbcb34dd" TYPE="swap"
/dev/zram4: UUID="e1f0a663-3fc2-4b29-8a7b-4aca6f357e73" TYPE="swap"
/dev/zram5: UUID="4ab11912-e5b4-4403-8225-f7b34280fc0e" TYPE="swap"
5

Why it shows /dev/sdb*? Is it booting from USB storage?

It is expected to boot and mount /dev/nvme0n1p*

6

Why it shows /dev/sdb* ? Is it booting from USB storage?
Because it’s a hard disk box with the not working well SDD in orin, and I view it in a ubuntu22.04 PC.

It is expected to boot and mount /dev/nvme0n1p*
Yes, when the SSD in orin it;s /dev/nvme0n1p*
/////////////////////////////////////////////////////////////////////////////////////
The not working SSD become working well when I edit the exlinux.conf
change root=PARTUUID=d0a946ff-af57-44bc-a1fb-d3264434e799 to 9d19868e-e487-4454-9cc9-7a0b6d869b9c
I think the puuid has been auto changed. Maybe the bios changed it ?

7

I have no idea about how it gets changed.

How many SSD connected on your board?

Have you confirmed that you always using the same SSD as boot device?

/dev/sdb1: UUID="9d19868e-e487-4454-9cc9-7a0b6d869b9c" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="APP" PARTUUID="39fe6324-249f-44b3-975d-8e66bb76d802"
..
/dev/nvme0n1p1: UUID="b038e696-1ad1-4822-8546-f6a492c53016" TYPE="ext4" PARTLABEL="APP" PARTUUID="d0a946ff-af57-44bc-a1fb-d3264434e799"

Please also check if you can reproduce the issue on the devkit with the latest JP5.1.4(R35.6.0).

9

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