Jetson Orin NX stuck on boot after unmounting disk where Docker was moved

[silenzio777]

Hello! Please help Jetson Orin NX stuck on boot after disconnecting the drive where Docker was moved.
Possible cause of boot errors.

I moved Docker files from my main drive to an external SSD drive. And everything was ok. But yesterday, after some modifications, I forgot to connect it. And accidentally launched Jetson Orin NX without an external SSD drive. Jetson did not boot…
I remembered about the SSD and connected it.

I don’t know how this could have affected, but I don’t know any other reasons for this…

After booting, the system seemed to work fine, but neither Chromium nor Firefox started. I tried to reinstall it, but it turned out that there were problems with Snap.

After rebooting, big problems started. The system boots with a bunch of errors.
What a horror. I rebooted Jetson and now it can’t boot…
A bunch of errors loading the kernel…

Some checks with counters are running:

[ **](1 of 4) A start job is running for /dev/ttyTCU0 (1min / 1 min 30s)
[  *](2 of 4) A start job is running for /dev/ttyGS0 (53s / 1 min 30s)
[ **](3 of 4) A start job is running for /dev/disk/by-uuid/F114-DB54 (1min 17s / 1min 30s)
[ **](4 of 4) A start job is running for /dev/disk/by-unid/de820c0d-4633-407e-a630-6ce97a3cal... (1min 14s / 1min 305)

Apparently it is looking for an SSD disk, although it is there and connected.

And it all ends with this:

You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemct1 reboot" to reboot, systenctl default" or "exit" to boot into default mode.
To continue, press Enter (or press Control-D to continue):

If you press Enter, the root@jetsonx: prompt appears and you can write commands as root.
The system is visible, the system disk is there, the file directories are there, the SSD disk is accessible and visible.

Sorry for the attached photos, it is impossible to make screenshots…

If you enter “systemctl reboot”, everything ends with this screen and nothing else happens Jetson is stopped.

Video of the entire boot process:

Please help. I can’t even imagine what to do…

Thank you!

[carolyuu]

*** Please note that this reply is generated by LLM automatically ***

I’d be happy to help you troubleshoot the issue with your Jetson Orin NX.

Summary of the issue:

You moved Docker files from your main drive to an external SSD drive, and everything was working fine. However, after disconnecting the external SSD drive and launching Jetson Orin NX, the system failed to boot. Even after reconnecting the SSD drive, the system boots with errors, and you’re unable to access the desktop environment. The system seems to be looking for the SSD disk, but it’s present and connected.

Possible causes of boot errors:

1. Dependency on external SSD drive: It’s possible that the system has become dependent on the external SSD drive, and the boot process is looking for it. This could be due to the Docker files being moved to the external drive, and the system is trying to access them during boot.
2. LVM2 configuration: The error messages mention LVM2, which suggests that the system is using Logical Volume Management (LVM) to manage the disk partitions. It’s possible that the LVM configuration has become corrupted or is not properly configured, leading to boot errors.
3. Kernel issues: The error messages also mention kernel errors, which could indicate a problem with the kernel configuration or a corrupted kernel image.
4. Snap issues: You mentioned that there were problems with Snap, which could be related to the boot errors. Snap is a package manager for Linux, and issues with Snap could prevent the system from booting properly.

Comparison with similar issues:

I’ve reviewed the context you provided, and I found a few similar issues that might be related to your problem:

• “Boot fails after restoring a Jetson orin NX” - This issue mentions a similar problem with booting after restoring a Jetson Orin NX. The solution involves checking the boot logs and ensuring that the system is properly configured.
• “Call trace observed in during boot in preempt-rt kernel” - This issue mentions a kernel-related problem during boot, which could be similar to the kernel errors you’re experiencing.
• “L4t source_sync.sh unable to connect to nv-tegra.nvidia.com” - This issue mentions a problem with the L4T source synchronization script, which could be related to the LVM2 configuration issues you’re experiencing.

Troubleshooting steps:

To troubleshoot the issue, I recommend the following steps:

1. Check the boot logs: Review the boot logs to see if there are any error messages that can help identify the cause of the problem.
2. Verify LVM2 configuration: Check the LVM2 configuration to ensure that it’s properly set up and that the system is not looking for the external SSD drive during boot.
3. Reinstall Snap: Try reinstalling Snap to see if it resolves the issues with the package manager.
4. Reconfigure the kernel: If the kernel errors persist, try reconfiguring the kernel to see if it resolves the issue.
5. Try a different boot mode: Try booting the system in a different mode, such as recovery mode or safe mode, to see if it allows you to access the desktop environment.

Conclusion:

Based on the information you provided, it’s likely that the issue is related to the dependency on the external SSD drive, LVM2 configuration, or kernel issues. I recommend trying the troubleshooting steps I outlined above to see if they resolve the issue. If you’re still experiencing problems, please provide more information or clarification on the error messages you’re seeing, and I’ll do my best to help you further.

[silenzio777]

Thanks, but I already consulted with LLM. With DeepSeek, chatGPT, Grok and Gemini.

They don’t understand what kind of Jetson Orin NX device this is.
And they give advice as for a regular PS with Ubuntu.

I thought you would help me as experts…

They suggested doing this:

# mask mounted core-snap images so that systemd does not try to pull them
systemctl mask 'snap-core-*.mount'

# disable the daemon and socket
systemctl disable --now snapd.service snapd.socket snapd.seeded.service

systemctl mask lvm2-monitor.service
systemctl disable --now lvm2-monitor.service

systemctl daemon-reload
systemctl reboot

After their advice, my device does not boot at all.

I can only enter UEFI Interactive Shell.
There I see my disk “fs2:\boot\extlinux>” and there is a file “extlinux.conf”

I can reboot manually:

fs3:\> cd \EFI\BOOT
fs3:\EFI\BOOT\> BOOTAA64.EFI

file “fs2:\boot\extlinux\extlinux.conf” from non-booting Jetson:

TIMEOUT 30
DEFAULT JetsonI0
MENU TITLE L4T boot options
LABEL primary
	MENU LABEL primary kernel
	LINUX /boot/Image
	INITRD /boot/initrd 
	APPEND ${cbootargs} root=PARTUUID=587BD0A8-8355-4891-B4DB-F136847F3577 rw
	...

LABEL JetsonIO
.MENU LABEL Custom Header Config: <CSI Camera IMK219 Dual>
.LINUX /boot/Image
.FDT /boot/dtb/kernel_tegra234-p3768-0000+p3767-0000-nv-super.dtb
.INITRD /boot/initrd
.APPEND $(cbootargs) root=PARTUUID=587BD0A8-8355-4891-B4DB-F136847F357 rw rootwait rootfstype=ext4 mminit_log_level=4 console-ttyTCU0, 115200 firmware_class.path=/etc/firmuare fbcon-map:0 nospectre_bhb video efifb:off console=tty0
.OUERLAYS /boot/tegra234-p3767-camera-p3768-imx219-dual.dtbo

587BD0A8-8355-4891-B4DB-F136847F3577 is the correct UUID of my primary system disk - /dev/nvme0n1p1

But now everything ends with a blank screen with a blinking cursor in the upper left corner.

Neither nor respond to any keys. You can only reboot . And again go to UEFI Interactive Shell…

As I understand it, this is the end…

Tell me, if I restore the bootloader via “SDK Manager”, will my data be safed?
What was in the “~/” folder?
And will the Ubuntu settings be safed?
Or will this “SDK Manager” bootloader erase everything and I will have to install everything again?
All programs, ROS2, all settings?

It’s weird but I can’t even boot from the ARM-Ubuntu “USB Live image”…
It’s like all booting is broken and unavailable.

Please help!

Thank you!

[AastaLLL]

Hi,

Thanks for reporting this.

We have some difficulty recognizing the first few screenshots as they are blurry.
Would you mind sharing the clear version or copying the entire kernel log as text and sharing it with us?

Below is the discussion for browser and Snap for your reference:

Chromium, other browsers not working after flashing or updating - Here's WHY and QUICK FIX

When Snap updated to version 2.70, what professionals call “Bad Things Happen” magically appeared. The main reason is due to the way that Snap handles permissions. You may have seen the cannot set capabilities: Operation not permitted . error when you attempt to launch a browser like Chromium or an IDE from the command line. If launching from a desktop icon, the app appears to launch but does not. My preferred fix is to revert to an older version of Snap which is compatible with the Jetson (f…

Thanks.

[silenzio777]

Hello!

I can not sharing the clear version or copying the entire kernel log as text and sharing it with you because Jetson can not start…

Now I have big problems with booting. Jetson Orin NX does not boot at all…

The last video shows what is happening.

It starts with a screen with an Nvidia picture and then:

ESC     to enter Setup.
F11     to enter Boot Manager Menu.
Enter  to continue boot.
L4TLanuncher: Attempting Recovery Boot
EFI stub: Booting Linux Kernel...
EFI stub: Using DIB from configuration table
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Exiting boot services...

And that’s it. Black screen and blinking cursor.

Ubuntu doesn’t load…

I have a question: if I reflash it again via SDK Manager to Jetpack: 6.2. Will it restore the boot?
And will my home folder "home/username"disappear? Will I have to reinstall everything, Ubuntu 22 too? Or will it just update the bootloader?

Please help restore the Jetson system boot.
Thanks!

[silenzio777]

I inserted the Jetson system disk into another machine with Ubuntu.
Inside the folder /media/silenzio/4cc211ea-455a-42d5-9e2d-d03c2c39c4cd/boot there is this content:

/media/silenzio/4cc211ea-455a-42d5-9e2d-d03c2c39c4cd/boot/dtb:
total 244
-rw-r–r-- 1 root root 249517 Feb 13 13:31 kernel_tegra234-p3768-0000+p3767-0000-nv-super.dtb

/media/silenzio/4cc211ea-455a-42d5-9e2d-d03c2c39c4cd/boot/efi:
total 0

/media/silenzio/4cc211ea-455a-42d5-9e2d-d03c2c39c4cd/boot/extlinux:
total 12
-rw-r–r-- 1 root root 1410 Feb 15 13:17 extlinux.conf
-rw-r–r-- 1 root root 938 Feb 15 13:17 extlinux.conf.jetson-io-backup
-rw-r–r-- 1 root root 727 Feb 13 13:29 extlinux.conf.nv-update-extlinux-backup

Is it correct that there are no files in the “/boot/efi:” folder?

Is it correct “extlinux.conf” file?

TIMEOUT 30
DEFAULT JetsonIO

MENU TITLE L4T boot options

LABEL primary
      MENU LABEL primary kernel
      LINUX /boot/Image
      INITRD /boot/initrd
      APPEND ${cbootargs} root=PARTUUID=587bd0a8-8355-4891-b4db-f136847f3577 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 nospectre_bhb video=efifb:off console=tty0 

# When testing a custom kernel, it is recommended that you create a backup of
# the original kernel and add a new entry to this file so that the device can
# fallback to the original kernel. To do this:
#
# 1, Make a backup of the original kernel
#      sudo cp /boot/Image /boot/Image.backup
#
# 2, Copy your custom kernel into /boot/Image
#
# 3, Uncomment below menu setting lines for the original kernel
#
# 4, Reboot

# LABEL backup
#    MENU LABEL backup kernel
#    LINUX /boot/Image.backup
#    INITRD /boot/initrd
#    APPEND ${cbootargs}

LABEL JetsonIO
	MENU LABEL Custom Header Config: <CSI Camera IMX219 Dual>
	LINUX /boot/Image
	FDT /boot/dtb/kernel_tegra234-p3768-0000+p3767-0000-nv-super.dtb
	INITRD /boot/initrd
	APPEND ${cbootargs} root=PARTUUID=587bd0a8-8355-4891-b4db-f136847f3577 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 nospectre_bhb video=efifb:off console=tty0
	OVERLAYS /boot/tegra234-p3767-camera-p3768-imx219-dual.dtbo

There is also no such folder on the disk /etc/firmware :
"/media/silenzio/4cc211ea-455a-42d5-9e2d-d03c2c39c4cd$ sudo ls /etc/firmware
ls: cannot access ‘/etc/firmware’: No such file or directory

Although it is mentioned in the “extlinux.conf” file. Is this ok?

This is /etc/fstab file, is it correct?

# /etc/fstab: static file system information.
#
# These are the filesystems that are always mounted on boot, you can
# override any of these by copying the appropriate line from this file into
# /etc/fstab and tweaking it as you see fit.  See fstab(5).
#
# <file system> <mount point>             <type>          <options>                               <dump> <pass>
/dev/root            /                     ext4           defaults                                     0 1
UUID=F114-DB54 /boot/efi vfat defaults 0 1
# Custom mount for backup SSD
# UUID=de820c0d-4633-407e-a630-6ce97a3cab64 /mnt/SSD_BACKUP_512 ext4 defaults, nofail 0 2

Dir /boot/efi is empty…

• /media/silenzio/4cc211ea-455a-42d5-9e2d-d03c2c39c4cd/boot/efi:
  total 0

Everything seems to be fine with the disk and the files…
Why can’t Jetson boot?
Please help.

[silenzio777]

• UPDATE:

I managed to get Jetson to boot again.

I don’t know how it happened, but this option is in

• Bios/Device Manager/NVIDIA Configuration/L4T Configuration/OS chain A status: Unbootable.

I set it to: Normal and Jetson booted!

This option:

And this option after several reboots changes back to “Unbootable” by itself. I don’t understand why this happens…

This is a video of the boot process with all the errors. The text moves very quickly, I shoot 60 fps video. But in some places the text disappears, sorry.

It looks like the BIOS settings might have reset…
How can I restore them for my model:

Model: NVIDIA Jetson Orin NX Engineering Reference Developer Kit Super
699-level Part Number: 699-13767-0000-301 G.1
P-Number: p3767-0000
Module: NVIDIA Jetson Orin NX (16GB ram)
Soc: tegra234
LAT: 36.4.3
Jetpack: 6.2

Can you give me all the settings? Where can I get them?

Please help!

[whitesscott]

Did you make a backup of your home directory and anything else you need?

If so I think you may want to flash the Orin again.

Ubuntu relies heavily on snap so in the future you may not want to mess with
systemctl status snapd

The Chromium, other browsers fix noted above would be all you’d want to do to snap.

[silenzio777]

Hello!

Yes, I made a backup of my home directory.

No problem with that.

But what about the drivers and a dozen installed and running applications on the system? ROS2, OpenVINS, Whisper, Riva server, Torch, TF, Ceres and a bunch more. Should I reinstall all of this???

So I really want to mess around with “systemctl status snapd”.
I have a backup of the /snap directory before the crash.
If you write me instructions on what to do, I’ll do it.

Thank you!

[whitesscott]

Try,

sudo apt --reinstall install snapd
sudo snap refresh.

Maybe reboot.
Check firefox and chromium

If ok, then Ubuntu has fixed snap.

If they again fail use

Kangalow’s snap webrowser fix

snap download snapd --revision=24724
sudo snap ack snapd_24724.assert
sudo snap install snapd_24724.snap
sudo sudo snap refresh --hold snapd

[silenzio777]

Hello!
Thank you for you help!

@whitesscott

snap download snapd --revision=24724
sudo snap ack snapd_24724.assert
sudo snap install snapd_24724.snap
sudo sudo snap refresh --hold snapd

But it not works for me…

This is works!

$ sudo apt install --reinstall snapd=2.67.1+22.04 -y
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  ldap-utils libbasicobjects0 libcollection4 libdhash1 libini-config5 libipa-hbac0 libnfsidmap1 libpam-pwquality libpath-utils1 libref-array1 libsss-certmap0 libsss-idmap0 libsss-nss-idmap0 python3-sss
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 545 not upgraded.
Need to get 25.0 MB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 snapd arm64 2.67.1+22.04 [25.0 MB]
Fetched 25.0 MB in 3s (7,199 kB/s)
(Reading database ... 320463 files and directories currently installed.)
Preparing to unpack .../snapd_2.67.1+22.04_arm64.deb ...
Unpacking snapd (2.67.1+22.04) over (2.67.1+22.04) ...
Setting up snapd (2.67.1+22.04) ...
snapd.failure.service is a disabled or a static unit not running, not starting it.
snapd.snap-repair.service is a disabled or a static unit not running, not starting it.
Processing triggers for gnome-menus (3.36.0-1ubuntu3) ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for dbus (1.12.20-2ubuntu4.1) ...
Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
Processing triggers for desktop-file-utils (0.26-1ubuntu3) ...

silenzio@jetsonnx:~/ros2_ws$ systemctl status snapd
● snapd.service - Snap Daemon
     Loaded: loaded (/lib/systemd/system/snapd.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2025-07-16 18:01:24 MSK; 41s ago
TriggeredBy: ● snapd.socket
   Main PID: 56492 (snapd)
      Tasks: 17 (limit: 18452)
     Memory: 327.3M
        CPU: 21.969s
     CGroup: /system.slice/snapd.service
             └─56492 /usr/lib/snapd/snapd

Jul 16 18:01:24 jetsonnx systemd[1]: Started Snap Daemon.
Jul 16 18:01:45 jetsonnx systemd[1]: /lib/systemd/system/snapd.service:23: Unknown key name 'RestartMode' in section 'Service', ignoring.
Jul 16 18:01:46 jetsonnx snapd[56492]: snapmgr.go:611: cannot read snap info of snap "core22" at revision 1612: cannot find installed snap "core22" at revision 1612: missing file /snap/core22/1612/meta/snap.yaml
Jul 16 18:01:49 jetsonnx systemd[1]: /lib/systemd/system/snapd.service:23: Unknown key name 'RestartMode' in section 'Service', ignoring.
Jul 16 18:01:49 jetsonnx snapd[56492]: services.go:1152: RemoveSnapServices - disabling snap.snapd-desktop-integration.snapd-desktop-integration.service
Jul 16 18:02:04 jetsonnx systemd[1]: /lib/systemd/system/snapd.service:23: Unknown key name 'RestartMode' in section 'Service', ignoring.
Jul 16 18:02:04 jetsonnx snapd[56492]: services.go:1152: RemoveSnapServices - disabling snap.cups.cupsd.service
Jul 16 18:02:04 jetsonnx snapd[56492]: services.go:1152: RemoveSnapServices - disabling snap.cups.cups-browsed.service
Jul 16 18:02:05 jetsonnx systemd[1]: /lib/systemd/system/snapd.service:23: Unknown key name 'RestartMode' in section 'Service', ignoring.
Jul 16 18:02:06 jetsonnx systemd[1]: /lib/systemd/system/snapd.service:23: Unknown key name 'RestartMode' in section 'Service', ignoring.

DeepSeek is a genius! 8)

$ snap download snapd --revision=24724
Fetching snap "snapd"
Fetching assertions for "snapd"
Install the snap with:
   snap ack snapd_24724.assert
   snap install snapd_24724.snap

silenzio@jetsonnx:~/ros2_ws$ sudo snap ack snapd_24724.assert
[sudo] password for silenzio: 

silenzio@jetsonnx:~/ros2_ws$ sudo snap install snapd_24724.snap
2025-07-17T16:40:01+03:00 INFO Waiting for automatic snapd restart...
snapd 2.68.5 from Canonical✓ installed

silenzio@jetsonnx:~/ros2_ws$ sudo snap refresh --hold snapd
General refreshes of "snapd" held indefinitely

silenzio@jetsonnx:~/ros2_ws$ snap version
snap    2.68.5
snapd   2.68.5
series  16
ubuntu  22.04
kernel  5.15.148-tegra

$ snap list
Name                       Version           Rev    Tracking         Publisher       Notes
bare                       1.0               5      latest/stable    canonical**     base
chromium                   134.0.6998.35     3060   latest/stable    canonical**     -
core22                     20250612          2049   latest/stable    canonical**     base
cups                       2.4.12-2          1102   latest/stable    openprinting**  -
firefox                    137.0-2           5987   latest/stable/…  mozilla**       -
gnome-42-2204              0+git.38ea591     201    latest/stable/…  canonical**     -
gtk-common-themes          0.1-81-g442e511   1535   latest/stable/…  canonical**     -
snap-store                 41.3-72-g80e7130  1216   latest/stable/…  canonical**     -
snapd                      2.68.5            24724  latest/stable    canonical**     snapd,held
snapd-desktop-integration  0.9               316    latest/stable/…  canonical**     -

Thanks @Kangalow

[schugh1]

hope this helps Chromium, other browsers not working after flashing or updating - Here's WHY and QUICK FIX - #29 by schugh1