Hello everybody.
I have a SDcard 64gb with all to boot XAVIER NX.
I made a image of that SD card on my laptop and I flashed it on a SDcard of 128gb.
The 64 sdcard works fine and boot ok, but the SDcard 128gb does not boot.
To create the image on my laptop I used:
Do you really use path “/dev/sdb64” or “/dev/sdb128”? These are not valid. If you are just illustrating and naming which card, that’s fine, but actual command lines would require something like “/dev/sdb1” for the first partition.
Hi @linuxdev.
In fact this is only for illustration. I am using the paths given by the system.
Do you think if I try to copy one sdcard direct to other I will get a different result?
Copying to a host PC image file, then to the SD, should not differ versus directly from SD to SD. However, not all content is partition content. I will suggest setting up all partitions to the correct size, and then copying the image of each partition from one SD to the other, but only if this is to be used on the same NX.
The idea is that if the SD has partitions created ahead of time with something like gdisk, then all metadata will be correct for that partition layout. After that you could use a resizing app (provided it is aware of preserving ext4 and not corrupting it) if needed.
Thank you @linuxdev.
Maybe a silly question regarding partitions:
When I check the sdcard with GParted for example, I only see one partition on sdcard. I quite did not understand what partitions you are referring. Can you, please, explain it a little more ?
I dowloaded the image from Nvidia website and flashed it on the 128gb Sdcard using balena etcher sw.
I pluged the sdcard on the board and made the initial configurations.
After that, without formating the sdcard, I used the procedure:
On an eMMC system you would only see one partition on an SD card used for boot. On a dev kit with only SD card, the SD would have a lot of partitions. Example (this is from 2 different SD card models/installs):
Without those non-rootfs (not “APP”) partitions boot will fail. The location of the non-rootfs partitions depends on the Jetson model. Typically an eMMC model would use those on eMMC, and if booting a rootfs on SD, then only the APP/rootfs partition would be on SD. An image of rootfs on an SD card of a non-eMMC model will fail to boot.
You are probably correct that the steps you took restored a partition table, and that this is why it now boots correctly. When people manually install and do not allow the other software to reinstall there is a chance that the surrounding non-rootfs content will be broken in some way.