Unable to find boot partition

The other day I swapped the SSDs of my two Jetson Xaviers to try and debug an issue. Nothing showed up on the monitor so I plugged my computer to the uart debug port and got this:


UEFI Interactive Shell v2.2
EDK II
UEFI v2.70 (EDK II, 0x00010000)
Mapping table
      FS1: Alias(s):F1:
          MemoryMapped(0xB,0xA0600000,0xA089FB3F)
      FS0: Alias(s):F0:
          Fv(49A79A15-8F69-4BE7-A30C-A172F44ABCE7)
      FS2: Alias(s):HD2b:;BLK1:
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x141A000
0,0x141BFFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-00-00-00-00-00-
00-01)/HD(1,GPT,9DFC7B99-C93E-4689-A8F9-1A0942973E9D,0x800,0xEE7B800)
     BLK0: Alias(s):
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x141A000
0,0x141BFFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-00-00-00-00-00-
00-01)
Press ESC in 1 seconds to skip startup.nsh or any other key to continue.
Shell> 

I assume this is a problem with the Jetson not being able to find the boot partition but I am unable to figure out how to fix the Jetson to boot.

Can someone please explain how to fix this problem?

Thank you in advance!

So is your SSD detected in the UEFI boot menu?

I think it is?

also when I run ls FS2: I can see the root directory of my OS.

Shell> ls FS2:
Directory of: FS2:\
07/31/2020  16:37                   7  bin
03/10/2024  19:58 <DIR>        12,288  boot
04/21/2022  12:54 <DIR>         4,096  dev
03/22/2024  06:32 <DIR>        12,288  etc
01/10/2023  23:25 <DIR>         4,096  home
07/31/2020  16:37                   7  lib
01/10/2023  21:03 <DIR>        16,384  lost+found
03/30/2023  22:03 <DIR>         4,096  media
03/22/2024  06:32 <DIR>         4,096  mnt
01/12/2023  15:52 <DIR>         4,096  opt
04/21/2022  12:54 <DIR>         4,096  proc
08/11/2022  03:37                  62  README.txt
04/16/2023  22:05 <DIR>         4,096  root
04/21/2022  12:54 <DIR>         4,096  run
07/31/2020  16:37                   8  sbin
01/10/2023  23:27 <DIR>         4,096  snap
07/31/2020  16:37 <DIR>         4,096  srv
04/21/2022  12:54 <DIR>         4,096  sys
01/10/2023  23:12               1,874  tegra194-mb1-bct-ratchet-p3668.cfg
03/22/2024  06:32 <DIR>        12,288  tmp
03/04/2021  06:23 <DIR>         4,096  usr
01/12/2023  15:39 <DIR>         4,096  var
          5 File(s)       1,958 bytes
         17 Dir(s)

Then what happens when you boot into the SSD instead of UEFI shell?

Sorry this may be a dumb question how do I do that?

You just press ENTER in the boot menu when NVMe is selected…

I press enter here right?

because nothing happens the screen just refreshes

YES.
Has this SSD ever been able to boot up before?
How did you flash the device?

OK, I saw this.
Then does it boot up when you swap it back?

Before I swapped the SSD I was able to boot into ubuntu.
I flashed both jetsons using the SDK manager.

Unfortunately, I swapped the SSD because I accidentally shorted the original jetson. However, our team had an extra jetson so I thought I could just swap the SSD because I did not want to re setup the OS and just keep working.

Then are you sure the other Jetson you are using now works properly before?

Yes, the non-shorted one worked before I swapped the SSD.

Then is it able to boot up with any other storage devices like another SSD/USB drive/SD card?

I don’t know what exactly you meant with short here, but maybe the disk already received some physical damage.

The thing is when I tried to swap the SSDs and saw there was no HDMI output I re swapped them but even with the original SSD I did not get any HDMI output.

Then make sure of this.
Find another storage device and flash with SDK Manager again.

Another dumb question is how would I flash to a USB?
Do I plug the USB into my main computer and use the SDK Manager to flash it?
Or do I plug in the USB into the Jetson, takeout the SSD, and then flash it from the SDK Manager?

YES. This way.
SDK Manager lets you select what storage device you want to flash.

So it turns out that when swapping the SSD again and plugging in the shorted SSD, I go the boot menu and press enter on the correct partition the OS properly boots.

UEFI Interactive Shell v2.2
EDK II
UEFI v2.70 (EDK II, 0x00010000)
Mapping table
      FS1: Alias(s):F1:
          MemoryMapped(0xB,0xA0600000,0xA089FB3F)
      FS0: Alias(s):F0:
          Fv(49A79A15-8F69-4BE7-A30C-A172F44ABCE7)
      FS2: Alias(s):HD2b:;BLK1:
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x141A000
0,0x141BFFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-00-00-00-00-00-
00-01)/HD(1,GPT,0F7DEDA2-4054-4C91-BEC2-46FC7E1916A6,0x11EF50,0xED5D339)
      FS3: Alias(s):HD2l:;BLK3:
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x141A000
0,0x141BFFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-00-00-00-00-00-
00-01)/HD(11,GPT,35096A16-89BC-4C12-A14A-2B5B632A2A5F,0xFEF28,0x20000)
     BLK0: Alias(s):
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x141A000
0,0x141BFFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-00-00-00-00-00-
00-01)
     BLK5: Alias(s):
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x141A000
0,0x141BFFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-00-00-00-00-00-
00-01)/HD(2,GPT,5BE872E9-3CF0-4910-B44B-1A177F208C54,0x28,0x20000)
     BLK6: Alias(s):
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x141A000
0,0x141BFFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-00-00-00-00-00-
00-01)/HD(3,GPT,28013EAA-BCA3-46A1-8D5B-AB2EC6D9543E,0x20028,0x20000)
     BLK7: Alias(s):
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x141A000
0,0x141BFFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-00-00-00-00-00-
00-01)/HD(4,GPT,2A20C04D-2172-43C9-A9BF-9028A2B0513F,0x40028,0x380)
     BLK8: Alias(s):
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x141A000
0,0x141BFFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-00-00-00-00-00-
00-01)/HD(5,GPT,1C17ABD3-4290-4826-8178-0605C636801B,0x403A8,0x380)
     BLK9: Alias(s):
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x141A000
0,0x141BFFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-00-00-00-00-00-
00-01)/HD(6,GPT,608EB5DF-77F2-4C71-8268-D44F42B6C04B,0x40728,0x28000)
    BLK10: Alias(s):
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x141A000
0,0x141BFFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-00-00-00-00-00-
00-01)/HD(7,GPT,100DA03E-4742-4383-9FE4-E0273AA11830,0x68728,0x400)
    BLK11: Alias(s):
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x141A000
0,0x141BFFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-00-00-00-00-00-
00-01)/HD(8,GPT,614AA3B7-D856-403D-9B1E-45184DC7F853,0x68B28,0x200)
    BLK12: Alias(s):
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x141A000
0,0x141BFFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-00-00-00-00-00-
00-01)/HD(9,GPT,4CF29B46-F580-4BC4-BF62-4D372F0EDB28,0x68D28,0x200)
     BLK2: Alias(s):
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x141A000
0,0x141BFFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-00-00-00-00-00-
00-01)/HD(10,GPT,74D53270-AD73-4E67-AE2E-677D1B71D61C,0x68F28,0x96000)
     BLK4: Alias(s):
          VenHw(1E5A432C-0466-4D31-B009-D4D9239271D3)/MemoryMapped(0xB,0x141A000
0,0x141BFFFF)/PciRoot(0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-00-00-00-00-00-
00-01)/HD(12,GPT,7FDBAB2E-0A8B-43BC-86DB-7B1E0157F31B,0x11EF28,0x24)
Press ESC in 3 seconds to skip startup.nsh or any other key to continue.
Shell> 

So the non-shorted jetson’s dev kit and the shorted jetson’s SSD both work.

But I still don’t know why the original SSD I showed above does not work.
Could it be because it does not see the a lot of the BLK as the working SSD?

Also, I tried to boot the image from the nonworking SSD in the UEFI shell by running
\boot\Image and I got this output:

FS2:\boot\> .\Image
EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services and installing virtual address map...
I/TC: Secondary CPU 1 initializing
I/TC: Secondary CPU 1 switching to normal world boot
I/TC: Secondary CPU 2 initializing
I/TC: Secondary CPU 2 switching to normal world boot
I/TC: Secondary CPU 3 initializing
I/TC: Secondary CPU 3 switching to normal world boot
I/TC: Secondary CPU 4 initializing
I/TC: Secondary CPU 4 switching to normal world boot
I/TC: Secondary CPU 5 initializing
I/TC: Secondary CPU 5 switching to normal world boot
WARNING: clock_get_rate: clk_power_ungate on gated domain 27 for gpcclk
rm_rail_debugfs_init: /rm/vdd_cpu: failed
rm_rail_debugfs_init: /rm/vdd_cpu: failed
debugfs initialized
[   397.408657] Camera-FW on t194-rce-safe started
TCU early console enabled.
[   397.474726] Camera-FW on t194-rce-safe ready SHA1=e4231a10 (crt 0.759 ms, total boot 66.857 ms)

Would it be best if I just re flashed the non working SSD?

YES, like probably some partitions other than the rootfs is gone.

I don’t see how this is supposed to work.

YES.