Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flash successful but can't mount /mnt #22

Open
nvasudevan opened this issue Jan 9, 2025 · 1 comment
Open

Flash successful but can't mount /mnt #22

nvasudevan opened this issue Jan 9, 2025 · 1 comment
Assignees
Labels
Linux_for_Tegra Label for Linux_for_Tegra UAY Unassigned yet

Comments

@nvasudevan
Copy link

Hello,

I was following the instructions in the README to build from source for my reComputer Jetson Orin Nano, and although the flash was successful from the run, the subsequent boot fails with the following error: mount: /mnt: can't find /mnt PARTUUID=...

My command to flash is identical to the one in the README:

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_t234_nvme.xml -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" --showlogs --network usb0 recomputer-orin-j401 internal

I can attach the logs if needed but here is the screen capture of the error related to mount. I am unable to figure out why this is happening. At least on one occasion the instructions in README did work but I am unable to reproduce the same (correct) behaviour. I cleared up my setup and re-tried from the beginning but no luck.

image

I have also tried to flash using the mfi_recomputer-orin-j401 image based on the instruction here (https://wiki.seeedstudio.com/reComputer_J4012_Flash_Jetpack/) and that works every time. I have attached the initrd log too.

Are you able to provide insight into what I could be doing wrong? Thanks for your good work and any pointers would be most appreciated.

/Krish

--
initrd log:
flash_1-1_0_20250109-105237.log

@Lesords Lesords added UAY Unassigned yet Linux_for_Tegra Label for Linux_for_Tegra labels Jan 10, 2025
@bigbearishappy
Copy link
Member

I did encountered with the same problem before. It was caused by the mismatching of kernel and drivers.
Can you provide the detail steps you did before you flash the device?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Linux_for_Tegra Label for Linux_for_Tegra UAY Unassigned yet
Projects
Status: No status
Development

No branches or pull requests

3 participants