search

jetsonhacks / rootOnNVMe

Switch the rootfs to a NVMe SSD on the Jetson Xavier NX and Jetson AGX Xavier
MIT License
390 stars 144 forks source link

[BUG] mount: special device /dev/nvme0n1p1 does not exist #1

Open jfeeney100 opened 4 years ago

jfeeney100 commented 4 years ago

Hello,

First, thank you to jetsonhacks for making these scripts available for everyone to use.

I ran into a little issue when running these scripts on my device and wanted to provide some details in case anyone else runs into the same issue.

While running the copy script I was getting an error that read: "mount: special device /dev/nvme0n1p1 does not exist"

After checking the default mount point of my SSD in the Disks utility I was able to confirm the actual mount point on my device is /dev/nvme0n1 not /dev/nvme0n1p1

To resolve the issue, I changed each instance of /dev/nvme0n1p1 to /dev/nvme0n1 in each of the following files: copy-rootfs-ssd.sh /data/setssdroot.service /data/setssdroot.sh

After making those small edits the scripts run without issue and the system is now running from the NVMe SSD. Not sure why my Xavier is producing a device dev location different from the one used in the script, but I have provided details about my particular setup below:

What version of L4T/JetPack L4T/JetPack version: L4T 32.4.3 [JetPack 4.4]

Which Jetson Jetson: Xavier NX

Additional context This Xavier NX was purchased on 10/5/2020 SSD is a 500GB Western Digital Blue SN550 - WDS500G2B0C

jetsonhacks commented 4 years ago

The ''p1' at the end of the /dev/nvme0n1p1 means 'Partition 1'. If you do not have partition 1, it probably means that you did not partition your SSD. This was described in the README as: Install the SSD into the M.2 Key M slot of the Jetson, and format it gpt, ext4, and setup a partition (p1). You should have partitioned the disk, it is not recommended to have no partitions.

jfeeney100 commented 4 years ago

ok, thank you for the information. I knew it was probably user error on my part.

guilleherreraf commented 3 years ago

Hello! I was wondering if I could use this script with a disk that is being recognized as SATA (/dev/sda1) by doing the corresponding changes such as @jfeeney100 did. Thanks in advance for your help.