I have a 32 GB sd card where my original os was installed, then added 500 GB SSD. Copied rootfs from sd card to SSD to make SSD my root, It worked perfectly fine, but when I unmount my sd card and mount it back, unable to boot my nx. When I try to boot, I get Nvidia logo and then it gets frozen, connects to wifi , keyboard, mouse gets connected and able to operate in terminal mode using clt+alt+f4. It doesn’t recognize my sd card, it is shown in lsblk without any mounted on path.
Please help me understand what went wrong and how to fix this.
With just the sd card, removing the SSD, works perfect boot normally. But when I put my SSD to the M2 slot and restart, it gets froze in nvidia logo.
NOTE: Not sure the exact trigger for this behavior, but this started after I eject my sd card and put it back and reboot.
lsblk output:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 16M 1 loop
mtdblock0 31:0 0 32M 0 disk
mmcblk0 179:0 0 29.8G 0 disk
├─mmcblk0p1 179:1 0 29.5G 0 part
├─mmcblk0p2 179:2 0 64M 0 part
├─mmcblk0p3 179:3 0 64M 0 part
├─mmcblk0p4 179:4 0 448K 0 part
├─mmcblk0p5 179:5 0 448K 0 part
├─mmcblk0p6 179:6 0 63M 0 part
├─mmcblk0p7 179:7 0 512K 0 part
├─mmcblk0p8 179:8 0 256K 0 part
├─mmcblk0p9 179:9 0 256K 0 part
├─mmcblk0p10 179:10 0 100M 0 part
└─mmcblk0p11 179:11 0 18K 0 part
zram0 252:0 0 1.9G 0 disk [SWAP]
zram1 252:1 0 1.9G 0 disk [SWAP]
nvme0n1 259:0 0 465.8G 0 disk
└─nvme0n1p1 259:1 0 456.4G 0 part /
df -h output:
Filesystem Size Used Avail Use% Mounted on
none 3.5G 0 3.5G 0% /dev
tmpfs 3.8G 4.0K 3.8G 1% /dev/shm
tmpfs 3.8G 21M 3.8G 1% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 3.8G 0 3.8G 0% /sys/fs/cgroup
/dev/nvme0n1p1 449G 255G 171G 60% /
tmpfs 777M 12K 777M 1% /run/user/1000
To explain what is going on, I would suggest you can use this method to dump the boot log first.
unable to boot my nx. When I try to boot, I get Nvidia logo and then it gets frozen, connects to wifi , keyboard, mouse gets connected and able to operate in terminal mode using clt+alt+f4. It doesn’t recognize my sd card, it is show in lsblk without any mounted on path.
I think it is not"unable to boot". More precisely, it is just not able to run the desktop manager. If OS is not up, then no terminal will be there for you.
Besides the boot up log from uart, please also share me the dmesg and /var/log/Xorg.0.log.
Hello, Please find the attached dmesg and /var/log/Xorg.0.log. I am checking on getting the uart log.
dmesg.txt (70.4 KB)
Xorg.0.log (15.8 KB)
According to the dmesg, the host is still using sdcard as root. Thus, we need to check the uart log to know where did the bootloader load the kernel.
root=/dev/mmcblk0p1
I followed the video you shared to connect the TTL to usb converter cable.
When I run sudo minicom and power on the jetson nx, it doesnt show any log in the terminal. Can you please help me to understand where is it going wrong.
Please try with picocom with baud rate 115200.
Also, make sure you didn’t connect wrong pin.
Thanks, there was some pin problem, please find the attached log file.
uart_log (87.6 KB)
Your log has some random string inside it.
Please make sure you only have one uart console opened at a time.
Is this the random string you are referring to ?
^[[10;1H<80>ÿâ<8d>áâ<8d>°²°&<93>zy j<91><83>j<91>º*<89>±<92>å®nA宲Wá¥^WòÅᥬ<9d>^Vâ â <9a>.âý¯â¯¢ÅŲ<96>A´+ù nÑ£kÑ kÙù £ ¥^[[9;63HÒÒ Vý^B<9d> <96>Íý<9d> <96>¥®é<8a>é<8a>°²°æjA<89>æ<89><82><8d>h<82>¨Éɤ^[[8;91H<97>Éɳ<9a>ËiË ^[[52;1H^[[K^[[51;1H^[[K^[[50;1H^[[K^[[49;1H^[[K^[[48;1H^[[K^[[47;1H^[[K^[[46;1H^[[K^[[45;1H^[[K^[[44;1H^[[K^[[43;1H^[[K^[[42;1H^[[K^[[41;1H^[[K^[[40;1H^[[K^[[39;1H^[[K^[[38;1H^[[K^[[37;1H^[[K^[[36;1H^[[K^[[35;1H^[[K^[[34;1H^[[K^[[33;1H^[[K^[[32;1H^[[K^[[31;1H^[[K^[[30;1H^[[K^[[29;1H^[[K^[[28;1H^[[K^[[27;1H^[[K^[[26;1H^[[K^[[25;1H^[[K^[[24;1H^[[K^[[23;1H^[[K^[[22;1H^[[K^[[21;1H^[[K^[[20;1H^[[K^[[19;1H^[[K^[[18;1H^[[K^[[17;1H^[[K^[[16;1H^[[K^[[15;1H^[[K^[[14;1H^[[K^[[13;1H^[[K^[[12;1H^[[K^[[11;1H^[[K^[[10;1H^[[K^[[9;1H^[[K^[[8;1H^[[K^[[7;1H^[[K^[[6;1H^[[K^[[5;1H^[[K^[[4;1H^[[K^[[3;1H^[[K^[[2;1H^[[K^[[1;1H^[[Ki²±)ª´<8c>â^SÚâ³ÓòÓ¹V<8a>I±lÓÓ<8a><8d>á+°ᰲ°&jA<89><82><82>ëÑ^[[KÕëºý¬Vý¯<97><88>ý¬¯<97><88>°²°^SjA<89><82><83>«Á nÖåÖ³<9a>ËA˺^[[2;68HA²U<8a>°²°<93>jA<89><82><82>ëѲëAë²°Wá á <97>Éɳ<9a>ËA˺Êʵ<82>£^[[1;101HÉÉ¥,<97>«A°Wá¥^Véá¥<8a>°²°^SjA<89><82><81><95>A¦<9d>n^VÒÕÒ¶<9a>nëù 'Âë ¸&ÂÂ<8d>á+°ᰲ°<8d>f^[[2;151Hy jõ n^VÅ©.õ ©²ÕÕ³^YÒÒ ÂAÂ<8d>á+°ᰲ°^M<93>^[[3;2Hy jõ èKÕ gÂõ ¸*<8a>°²°<8d>jA<89><82>².××µýµîÕ '¸*<8a>ýµ ¸<8a>°²°^SjA<89><82>².×EÕ׶^Y^[[2;53HÒÒ ÂAÂ<8d>á°á°²°<93>jA<89><82><82>ëÑë<96>ÙÙ©lV<82><91>*U5<8a>°²°ÓjAÓ<89><82><91>.å å <96>+ÍͨÂŲ<98>+A³kÉÉ£^Yê ê ¬ÉÉ£<97><88>°²°Sj^A<89><82><91>.
No, each of your line has some random string. This is common when you open more than two minicom at same time.
Please find the attached uart log file.
uart_log (87.7 KB)
Looks correct now.
According to your log, you are using jetpack4.5.x which does not support nvme in cboot yet. Thus, both kernel and rootfs in this log are booting from sdcard.
Actually, I see no error from every of log you shared.
-
What is the monitor resolution you are using here? According to the kernel log, it looks like not a common one.
-
Can you check if your “Xorg.0.log” really gets updated in each reboot? I mean making sure you are not sharing a log that was generated long time ago.
Yes the log file is getting updated, earlier the uart log I sent was without any hdmi to monitor. Attaching the new uart file with monitor attached and the Xorg file.
uart_log_new (91.6 KB)
Xorg.0.log (13.1 KB)
Looks like there is no error. What did you see on your screen? Totally blanked?
Could you share result of “df -h”? Sometimes out of disk space will cause desktop fails to launch.
df -h output:
Filesystem Size Used Avail Use% Mounted on
none 3.5G 0 3.5G 0% /dev
tmpfs 3.8G 4.0K 3.8G 1% /dev/shm
tmpfs 3.8G 45M 3.8G 2% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 3.8G 0 3.8G 0% /sys/fs/cgroup
/dev/nvme0n1p1 449G 255G 171G 60% /
tmpfs 777M 12K 777M 1% /run/user/1000
I see the nvidia icon, wifi gets connected and then a error window pops up saying " System program problem detected, Do you wnat to report the problem now?" and after closing the popup the window just shows the default nvidia icon, doesnt take me to the home page.
Hi,
Did you remember what did you do to make SSD as your root?
Your “df-h” does not give out any info of the sdcard. Are you sure there is a file system on your sdcard?
Earlier, I used to see sd card information in df -h, which doesn’t show now, it shows up in lsblk output:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 4K 1 loop /snap/bare/5
loop1 7:1 0 55.5M 1 loop /snap/core18/2253
loop2 7:2 0 61.9M 1 loop /snap/core20/1242
loop3 7:3 0 54.2M 1 loop /snap/snap-store/558
loop4 7:4 0 65.1M 1 loop /snap/gtk-common-themes/1515
loop5 7:5 0 9.5M 1 loop /snap/htop/3233
loop6 7:6 0 42.2M 1 loop /snap/snapd/14066
loop7 7:7 0 219M 1 loop /snap/gnome-3-34-1804/77
loop8 7:8 0 65.2M 1 loop /snap/gtk-common-themes/1519
loop9 7:9 0 55.4M 1 loop /snap/core18/2128
loop10 7:10 0 247.9M 1 loop /snap/gnome-3-38-2004/87
loop11 7:11 0 32.3M 1 loop /snap/snapd/12704
loop12 7:12 0 219M 1 loop /snap/gnome-3-34-1804/72
loop13 7:13 0 51M 1 loop /snap/snap-store/547
nvme0n1 259:0 0 477G 0 disk
├─nvme0n1p1 259:1 0 260M 0 part /boot/efi
├─nvme0n1p2 259:2 0 16M 0 part
├─nvme0n1p3 259:3 0 175.7G 0 part
├─nvme0n1p4 259:4 0 50G 0 part
├─nvme0n1p5 259:5 0 200G 0 part
├─nvme0n1p6 259:6 0 1000M 0 part
├─nvme0n1p7 259:7 0 42.9G 0 part /
└─nvme0n1p8 259:8 0 7.1G 0 part [SWAP]
I followed instructions from below github link to copy my rootfs from sd card to SSD
Earlier it use to show in df -h as external memory 32 GB,
lsblk shows some info in mmcblk0p1,
lsblk output:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 16M 1 loop
mtdblock0 31:0 0 32M 0 disk
mmcblk0 179:0 0 29.8G 0 disk
├─mmcblk0p1 179:1 0 29.5G 0 part
├─mmcblk0p2 179:2 0 64M 0 part
├─mmcblk0p3 179:3 0 64M 0 part
├─mmcblk0p4 179:4 0 448K 0 part
├─mmcblk0p5 179:5 0 448K 0 part
├─mmcblk0p6 179:6 0 63M 0 part
├─mmcblk0p7 179:7 0 512K 0 part
├─mmcblk0p8 179:8 0 256K 0 part
├─mmcblk0p9 179:9 0 256K 0 part
├─mmcblk0p10 179:10 0 100M 0 part
└─mmcblk0p11 179:11 0 18K 0 part
zram0 252:0 0 1.9G 0 disk [SWAP]
zram1 252:1 0 1.9G 0 disk [SWAP]
nvme0n1 259:0 0 465.8G 0 disk
└─nvme0n1p1 259:1 0 456.4G 0 part /
I don’t guarantee what would your script do. Looks like it messed up something.
Can you remove the nvme drive on the board and see what will happen? Please share the log too.