I successfully had my AGX running from an m.2 SSD. I then updated to the latest jetpack and have run into the following issue:
If the m.2 ssd is inserted, the AGX does not start up. If i remove the SSD then it works. I take it that its trying to load up this, now incompatible SSD? How can i stop it from trying to load from there so that I can format it?
@WayneWWW yes changing the boot order worked thank you.
Great, so with Jetpack4.6, would I conduct the JetsonHacks ./copy-rootfs-ssd.sh script to copy the emmc to the SSD, and then change the boot order so that the SSD is the priority? Basically there is no longer a need for the ./setup-service.sh script work around described here anymore?
I followed the steps and ran the scripts from “https://github.com/jetsonhacks/rootOnNVMe ” to switch the rootfs to SSD successfully.
But after few days, the rootfs is loading from SSD, but stuck at nvidia logo, able to access only through terminal mode using clt+alt+f4. GUI is not responding. Disabling the service and removing the file setssdroot.conf from /etc and rebooting boots up from sd card and shows ssd unmounted. When I try to enable the service back again it doesn’t work. Can anyone help me resolve this issue. I faced this couple of days back, i had to format the SSD and again copy back the rootfs and scripts to run properly which is time consuming to install stuff in SSD again. This happened again now and I m just wondering if there is any other way to get back to SSD without formatting.
Maybe there’s some disk corruption going on somewhere.
Maybe you want to try my project out that installs a boot from SSD in one command?
If you find that you had disk corruption and you application doesn’t need to write to disk, then you can run it in a read-only mode by running sudo ./sbts-bin/make_readonly.sh and rebooting. Then it runs with a memory overlay over the rootfs and so the disks are not mounted read-write and thus don’t get corrupted.