-
Notifications
You must be signed in to change notification settings - Fork 142
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
Error: cannot create regular file '/mnt/etc/systemd/system/setssdroot.service' #7
Comments
Hello, In my case the disk was not in the path /dev/nvme0n1p1, it was in /dev/nvme0n1 I had to change it in all the files to solve this issue. |
Hello @rafiqrana , |
Hello @gayathri81 Just check with an application like Disks (select your SSD and see on Device the location) where your device is, in my case it was /dev/nvme0n1, then I searched for all the places where this application refers to /dev/nvme0n1p, and changed it by /dev/nvme0n1. For example: In file copy-rootfs-ssd.sh I change (in line 3): I think you also need to fix the path in:
|
Hi @cramirezhe , thanks for the reply, but I'm able to mount the device properly. the location is correctly pointed to dev/nvme0n1p1. When I boot the service and script to mount SSD works fine, but not able to see the graphical interface. Able to access through terminal interface. |
Hi there,
I used this repo to boot Jetson AGX Xavier from the newly installed NVMe. At the first attempt, I had successfully finished all the steps, and it booted from the NVMe thereafter. Few days later, it was, however, not booting for some reasons. Therefore, I used the same steps from this repo to reinstall the os to NVMe, but ended up the following error:
It looks like to me, the NVMe was not mounted properly
What version of L4T/JetPack
L4T/JetPack version: 4.4.x
Which Jetson
Jetson: NVIDIA Jetson AGX Xavier Developer Kit
To Reproduce
Steps to reproduce the behavior:
Expected behavior
./setup-service.sh
command should copy all the required system file to NVMe and create a service to boot from the NVMe.The text was updated successfully, but these errors were encountered: