Error while installing/moving jetpack 4.6.1 to sd card on nvidia jetson nano

Hi,
I have a SeedStudio J101 carrier board jetson nano 4 gb dev kit with jetpack 4.6.1 in it. Problem is the OS is installed in it’s internal memory(emmc) and less space is available around 1gb to do any projects. So I wanted to use sd card for the same. I have enabled the SD card proper format and while trying to move the OS to the SD card so that i can boot from the sd card i followed a series of commands from the official doc here J101 Enable SD Card - Seeed Wiki and got error at :-

Error after performing the foll:- ./copyRootToUSB.sh -p /dev/mmcblk1p1

Error:-

nvidia@ubuntu:~/bootFromUSB$ ./copyRootToUSB.sh -p /dev/mmcblk1p1
Device Path: /dev/mmcblk1p1
Target: /media/nvidia/mvnvidia
[sudo] password for nvidia: 
Hit:1 https://repo.download.nvidia.com/jetson/common r32.7 InRelease
Hit:2 http://ports.ubuntu.com/ubuntu-ports bionic InRelease                                                
Hit:3 https://repo.download.nvidia.com/jetson/t210 r32.7 InRelease                                         
Get:4 http://ports.ubuntu.com/ubuntu-ports bionic-updates InRelease [88.7 kB]
Get:5 http://ports.ubuntu.com/ubuntu-ports bionic-backports InRelease [83.3 kB]
Get:6 http://ports.ubuntu.com/ubuntu-ports bionic-security InRelease [88.7 kB]
Get:7 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 DEP-11 Metadata [291 kB]
Get:8 http://ports.ubuntu.com/ubuntu-ports bionic-updates/universe arm64 DEP-11 Metadata [297 kB]
Get:9 http://ports.ubuntu.com/ubuntu-ports bionic-backports/main arm64 DEP-11 Metadata [8,092 B]
Get:10 http://ports.ubuntu.com/ubuntu-ports bionic-backports/universe arm64 DEP-11 Metadata [10.1 kB]
Get:11 http://ports.ubuntu.com/ubuntu-ports bionic-security/main arm64 DEP-11 Metadata [49.1 kB]
Get:12 http://ports.ubuntu.com/ubuntu-ports bionic-security/universe arm64 DEP-11 Metadata [56.0 kB]
Fetched 972 kB in 3s (352 kB/s)                                              
Reading package lists... Done
Reading package lists... Done
Building dependency tree       
Reading state information... Done
rsync is already the newest version (3.1.2-2.1ubuntu1.5).
The following packages were automatically installed and are no longer required:
  apt-clone archdetect-deb bogl-bterm busybox-static cryptsetup-bin dpkg-repack gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 grub-common
  kde-window-manager kinit kio kpackagetool5 kwayland-data kwin-common kwin-data kwin-x11 libdebian-installer4 libkdecorations2-5v5
  libkdecorations2private5v5 libkf5activities5 libkf5attica5 libkf5completion-data libkf5completion5 libkf5declarative-data
  libkf5declarative5 libkf5doctools5 libkf5globalaccel-data libkf5globalaccel5 libkf5globalaccelprivate5 libkf5idletime5
  libkf5jobwidgets-data libkf5jobwidgets5 libkf5kcmutils-data libkf5kcmutils5 libkf5kiocore5 libkf5kiontlm5 libkf5kiowidgets5
  libkf5newstuff-data libkf5newstuff5 libkf5newstuffcore5 libkf5package-data libkf5package5 libkf5plasma5 libkf5quickaddons5
  libkf5solid5 libkf5solid5-data libkf5sonnet5-data libkf5sonnetcore5 libkf5sonnetui5 libkf5textwidgets-data libkf5textwidgets5
  libkf5waylandclient5 libkf5waylandserver5 libkf5xmlgui-bin libkf5xmlgui-data libkf5xmlgui5 libkscreenlocker5
  libkwin4-effect-builtins1 libkwineffects11 libkwinglutils11 libkwinxrenderutils11 libqgsttools-p1 libqt5designer5 libqt5help5
  libqt5multimedia5 libqt5multimedia5-plugins libqt5multimediaquick-p5 libqt5multimediawidgets5 libqt5opengl5 libqt5quickwidgets5
  libqt5sql5 libqt5test5 libxcb-composite0 libxcb-cursor0 libxcb-damage0 os-prober python3-dbus.mainloop.pyqt5 python3-icu
  python3-pam python3-pyqt5 python3-pyqt5.qtsvg python3-pyqt5.qtwebkit qml-module-org-kde-kquickcontrolsaddons
  qml-module-qtmultimedia qml-module-qtquick2 rdate tasksel tasksel-data
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 248 not upgraded.
 10,265,934,548  94%    2.27MB/s    1:11:49 (xfr#94253, ir-chk=1002/146692)
rsync: symlink "/media/nvidia/mvnvidia/usr/share/openmpi/mpiCC-wrapper-data.txt" -> "mpic++-wrapper-data.txt" failed: Bad message (74)
rsync: symlink "/media/nvidia/mvnvidia/usr/share/openmpi/mpiCC.openmpi-wrapper-data.txt" -> "mpiCC-wrapper-data.txt" failed: Bad message (74)
rsync: symlink "/media/nvidia/mvnvidia/usr/share/openmpi/mpic++.openmpi-wrapper-data.txt" -> "mpic++-wrapper-data.txt" failed: Bad message (74)
rsync: symlink "/media/nvidia/mvnvidia/usr/share/openmpi/mpicc.openmpi-wrapper-data.txt" -> "mpicc-wrapper-data.txt" failed: Bad message (74)
rsync: symlink "/media/nvidia/mvnvidia/usr/share/openmpi/mpicxx-wrapper-data.txt" -> "mpic++-wrapper-data.txt" failed: Bad message (74)
rsync: symlink "/media/nvidia/mvnvidia/usr/share/openmpi/mpicxx.openmpi-wrapper-data.txt" -> "mpicxx-wrapper-data.txt" failed: Bad message (74)
rsync: symlink "/media/nvidia/mvnvidia/usr/share/openmpi/mpif77-wrapper-data.txt" -> "mpifort-wrapper-data.txt" failed: Bad message (74)
rsync: symlink "/media/nvidia/mvnvidia/usr/share/openmpi/mpif77.openmpi-wrapper-data.txt" -> "mpif77-wrapper-data.txt" failed: Bad message (74)
rsync: symlink "/media/nvidia/mvnvidia/usr/share/openmpi/mpif90-wrapper-data.txt" -> "mpifort-wrapper-data.txt" failed: Bad message (74)
rsync: symlink "/media/nvidia/mvnvidia/usr/share/openmpi/mpif90.openmpi-wrapper-data.txt" -> "mpif90-wrapper-data.txt" failed: Bad message (74)
rsync: symlink "/media/nvidia/mvnvidia/usr/share/openmpi/oshcc-wrapper-data.txt" -> "shmemcc-wrapper-data.txt" failed: Bad message (74)
rsync: symlink "/media/nvidia/mvnvidia/usr/share/openmpi/oshfort-wrapper-data.txt" -> "shmemfort-wrapper-data.txt" failed: Bad message (74)
rsync: recv_generator: mkdir "/media/nvidia/mvnvidia/usr/share/openmpi/amca-param-sets" failed: Bad message (74)
*** Skipping any contents from this failed directory ***
 10,297,136,537  94%    2.25MB/s    1:12:45 (xfr#95506, ir-chk=1000/148181)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-btl-vader.txt.vAMDSZ" failed: Bad message (74)
 10,297,136,537  94%    2.25MB/s    1:12:45 (xfr#95506, ir-chk=1000/148181)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-coll-sync.txt.FYeYyz" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-dash-host.txt.3zgvng" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-errmgr-base.txt.1rT9r8" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-ess-base.txt.NVQx07" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-ess-hnp.txt.CjXlNz" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-hostfile.txt.TlFO6i" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-mca-base.txt.SKjXKt" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-mca-bml-r2.txt.gEFh8G" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-mca-coll-base.txt.SM59Sb" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-mca-osc-base.txt.jVaYh7" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-mca-var.txt.B6ZLXc" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-mpi-api.txt.HtspiC" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-mpi-btl-base.txt.5DP71j" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-mpi-btl-openib-cpc-base.txt.Jy85ni" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-mpi-btl-openib.txt.gNNfjv" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-mpi-btl-sm.txt.rmVNvW" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-mpi-btl-tcp.txt.gy4NwJ" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-mpi-coll-sm.txt.70JepG" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-mpi-common-sm.txt.eGFYFM" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-mpi-errors.txt.0hJioQ" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-mpi-pml-ob1.txt.ykG2zX" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-mpi-runtime.txt.uhSwVc" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-mpool-base.txt.qCUPEw" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-mtl-ofi.txt.kPo7LA" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-mtl-psm.txt.Ilvd4H" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-oob-base.txt.wHZ32X" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-oob-tcp.txt.gtokSj" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-oob-ud.txt.cnq67P" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-opal-common-verbs.txt.eY6WQs" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-opal-hwloc-base.txt.ga9QIN" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-opal-runtime.txt.E12CQ9" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-opal-shmem-mmap.txt.iBHxPA" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-opal-shmem-posix.txt.gxcQg4" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-opal-shmem-sysv.txt.wYCoSC" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-opal-timer-linux.txt.g73Tbf" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-opal-util.txt.4jC4IW" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-opal-wrapper.txt.0SNWCE" failed: Bad message (74)
 10,297,256,055  94%    2.25MB/s    1:12:45 (xfr#95565, ir-chk=1012/148252)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-opal_info.txt.qFgoUl" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-orte-clean.txt.Ok0Rh2" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-orte-filem-raw.txt.cc42XI" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-orte-info.txt.Ski3kt" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-orte-odls-base.txt.4Buc2d" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-orte-odls-default.txt.kfh9RX" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-orte-ps.txt.qP0L0H" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-orte-rmaps-base.txt.aKq6ir" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-orte-rmaps-md.txt.mHU919" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-orte-rmaps-ppr.txt.W2C5MW" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-orte-rmaps-resilient.txt.oEdaXJ" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-orte-rmaps-rr.txt.gJyipw" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-orte-rmaps-seq.txt.6cZUii" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-orte-rtc-base.txt.Qz3aw3" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-orte-runtime.txt.SFenyS" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-orte-server.txt.KOZxLH" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-orte-top.txt.IUzoix" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-orted.txt.sjB2Wl" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-orterun.txt.ss8wRa" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-oshmem-info.txt.Yh5n0Y" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-oshmem-memheap.txt.UUughM" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-oshmem-spml-yoda.txt.Camt7C" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-oshmem-sshmem-mmap.txt.I4Dkfu" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-oshmem-sshmem-sysv.txt.y4SMSm" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-oshmem-sshmem.txt.qDtXVf" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-plm-base.txt.i8Ba57" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-plm-rsh.txt.al31v6" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-plm-slurm.txt.MfDQt4" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-pmix-base.txt.caEPI3" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-ras-base.txt.Qjrhd7" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-ras-gridengine.txt.w8Qk69" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-ras-simulator.txt.CoK5Be" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-ras-slurm.txt.2C1Rmi" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-rcache-base.txt.ySvjVo" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-regex.txt.ebzRzz" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-rmaps_rank_file.txt.wv9quJ" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-rtc-freq.txt.7k7iHN" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-shmem-api.txt.OxFufR" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-shmem-runtime.txt.pb5zuX" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.help-state-staged-hnp.txt.8qon22" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.mca-btl-openib-device-params.ini.tUgAN7" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.mpic++-wrapper-data.txt.SjeB8i" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.mpicc-wrapper-data.txt.bomgNu" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.mpifort-wrapper-data.txt.wReZ4H" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.opalc++-wrapper-data.txt.LBlEJU" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.opalcc-wrapper-data.txt.E6vkx6" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.openmpi-valgrind.supp.zyOzIo" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.ortecc-wrapper-data.txt.8SwbrH" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.shmemcc-wrapper-data.txt.1Hb8N1" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openmpi/.shmemfort-wrapper-data.txt.oWvPNs" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openssh/.sshd_config.Zn1gLZ" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/openssh/.sshd_config.md5sum.kZXX3J" failed: Bad message (74)
 10,394,651,244  94%    2.26MB/s    1:13:06 (xfr#101429, ir-chk=1085/155695)
rsync: recv_generator: mkdir "/media/nvidia/mvnvidia/usr/share/transmission/web" failed: Bad message (74)
*** Skipping any contents from this failed directory ***
 10,407,690,629  94%    2.26MB/s    1:13:10 (xfr#102535, ir-chk=1158/157066)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/totem/.controls.ui.x0GHYo" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/totem/.playlist.ui.OgJTY6" failed: Bad message (74)
 10,407,690,629  94%    2.26MB/s    1:13:10 (xfr#102535, ir-chk=1158/157066)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/totem/.preferences.ui.r4Olr8" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/totem/.properties.ui.X91F4q" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/totem/.shortcuts.ui.pRxtFU" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/totem/.totem.ui.PnKjxE" failed: Bad message (74)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/totem/.uri.ui.Pf9EEF" failed: Bad message (74)
 11,843,686,748  95%    2.13MB/s    1:28:12 (xfr#132968, to-chk=0/192726)    
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1196) [sender=3.1.2]
nvidia@ubuntu:~/bootFromUSB$ 

##########
Please help in resolving this issue
##########

Can you post the output of “dmesg” after this occurs? You can create a log and post that, e.g.:
dmesg | tee log_dmesg.txt

In part I’m wondering if the filesystem is just corrupt, or perhaps has a hardware error. dmesg might answer that.

Along that line, has the Jetson ever had power removed while running under heavy load, versus normal shutdown? This wouldn’t be a big problem in most cases, but under heavy load the file system loss would exceed the size the journal is capable of safely handling (a certain amount of journal is required for a given amount of actual saved content which is in the process of writing, but in which write is incomplete, and if not enough journal is available, it corrupts).

Hi @linuxdev , yesterday I had shut down the system so today, I had to format the sd card again and try the command to get the error

./copyRootToUSB.sh -p /dev/mmcblk1p1

Today I got the foll error:-

nvidia@ubuntu:~/bootFromUSB$ ./copyRootToUSB.sh -p /dev/mmcblk1p1
Device Path: /dev/mmcblk1p1
Target: /media/nvidia/mvnvidia
[sudo] password for nvidia: 
Hit:1 https://repo.download.nvidia.com/jetson/common r32.7 InRelease
Hit:2 http://ports.ubuntu.com/ubuntu-ports bionic InRelease                                                
Hit:3 https://repo.download.nvidia.com/jetson/t210 r32.7 InRelease                                         
Hit:4 http://ports.ubuntu.com/ubuntu-ports bionic-updates InRelease                  
Hit:5 http://ports.ubuntu.com/ubuntu-ports bionic-backports InRelease
Hit:6 http://ports.ubuntu.com/ubuntu-ports bionic-security InRelease
Reading package lists... Done                      
Reading package lists... Done
Building dependency tree       
Reading state information... Done
rsync is already the newest version (3.1.2-2.1ubuntu1.5).
The following packages were automatically installed and are no longer required:
  apt-clone archdetect-deb bogl-bterm busybox-static cryptsetup-bin dpkg-repack gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 grub-common
  kde-window-manager kinit kio kpackagetool5 kwayland-data kwin-common kwin-data kwin-x11 libdebian-installer4 libkdecorations2-5v5
  libkdecorations2private5v5 libkf5activities5 libkf5attica5 libkf5completion-data libkf5completion5 libkf5declarative-data
  libkf5declarative5 libkf5doctools5 libkf5globalaccel-data libkf5globalaccel5 libkf5globalaccelprivate5 libkf5idletime5
  libkf5jobwidgets-data libkf5jobwidgets5 libkf5kcmutils-data libkf5kcmutils5 libkf5kiocore5 libkf5kiontlm5 libkf5kiowidgets5
  libkf5newstuff-data libkf5newstuff5 libkf5newstuffcore5 libkf5package-data libkf5package5 libkf5plasma5 libkf5quickaddons5
  libkf5solid5 libkf5solid5-data libkf5sonnet5-data libkf5sonnetcore5 libkf5sonnetui5 libkf5textwidgets-data libkf5textwidgets5
  libkf5waylandclient5 libkf5waylandserver5 libkf5xmlgui-bin libkf5xmlgui-data libkf5xmlgui5 libkscreenlocker5
  libkwin4-effect-builtins1 libkwineffects11 libkwinglutils11 libkwinxrenderutils11 libqgsttools-p1 libqt5designer5 libqt5help5
  libqt5multimedia5 libqt5multimedia5-plugins libqt5multimediaquick-p5 libqt5multimediawidgets5 libqt5opengl5 libqt5quickwidgets5
  libqt5sql5 libqt5test5 libxcb-composite0 libxcb-cursor0 libxcb-damage0 os-prober python3-dbus.mainloop.pyqt5 python3-icu
  python3-pam python3-pyqt5 python3-pyqt5.qtsvg python3-pyqt5.qtwebkit qml-module-org-kde-kquickcontrolsaddons
  qml-module-qtmultimedia qml-module-qtquick2 rdate tasksel tasksel-data
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 252 not upgraded.
 10,136,721,384  94%    2.30MB/s    1:09:58 (xfr#84109, ir-chk=1000/135434)
rsync: recv_generator: mkdir "/media/nvidia/mvnvidia/usr/share/liblangtag/common" failed: Bad message (74)
*** Skipping any contents from this failed directory ***
 10,171,838,138  94%    2.29MB/s    1:10:41 (xfr#85038, ir-chk=1047/136490)
rsync: mkstemp "/media/nvidia/mvnvidia/usr/share/liblangtag/.language-subtag-registry.xml.o4riDi" failed: Bad message (74)
 11,926,422,365  95%    2.00MB/s    1:34:39 (xfr#134448, to-chk=0/194156)    
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1196) [sender=3.1.2]
nvidia@ubuntu:~/bootFromUSB$ 

I ran the foll command :as suggested by you-

dmesg | tee log_dmesg.txt

Here is the generated file for that
log_dmesg.txt (63.6 KB)

Also additional information, I don’t know if this is relevant:- I am using mobile phone(Xiaomi Poco F1) with USB tethering via usb cable to use wifi internet on the Jetson nano device and there are absolutely no issues with the internet access on the board at all.

Please look into the log file and help me to solve the issue.

Also, the jetson nano never had power removed while running under under heavy load, since this is a new board that we bought and haven’t really done anything since then, but just 1 or 2 times when the board was just running and not doing anything there was a local power cut in my area and the board had shutdown. Nothing other than that.

A little info about what I have done til now:
So I purchased the jetson nano which Seedstudio J101 carrier board which had inbuilt 16gb emmc storage and an sd card suport and the jetson nano came with a pre installed Jetpack 4.6.1 in it, but issue was it was partially installed without the neccessary libraries. So I wanted to install the complete Jetpack 4.6.1 OS and that too on the sd card because of memory insufficiency in the internal memory. So I followed necessary steps:-

  1. Put the board on recovery mode
  2. Connected the board to ubuntu 18.04 host.
  3. Installed the jetpack 4.6.1 using Nvidia SDK manager.

All the above steps worked perfectly fine. After that as usual I booted the jetson nano in normal mode and did initial setup and it went without issue.

After this is where I am stuck:-
Now I tried to use sd card and followed all steps to make the sd card in proper format and transfer the OS so that I can boot from sd card and while trying to do so I am getting these errors.

Since this Jetson module is an eMMC module, but using the Seeed carrier board, direct boot to the SD card (versus mounting it as a subdirectory) would require the Seeed manufacturer to provide boot software (although this won’t have anything to do with the “bad message” error). The SD card model of dev kit does not have eMMC, and drivers are included for SD card in boot stages, but flashing for an eMMC model would not include this. Thus I am assuming the “copyRootToUSB.sh” is provided by Seeed. Is this correct?

Keep in mind that I don’t have a Seeed carrier board, so I am guessing about a lot of things. However, is it correct that the “bad message” error was while running on the host PC and not the Jetson (during creation of the SD card image)? If so, then monitor “dmesg --follow” on the host PC, and watch for new log lines during the “copyRootToUSB.sh” (versus from the Jetson).

FYI, the SD did contain errors, but this might be from the image being copied, or from the copy, or from a later boot attempt with some failure:

[   28.137984] EXT4-fs (mmcblk1p1): warning: mounting fs with errors, running e2fsck is recommended

During the above log which you attached, was this the first boot with that SD card installed? I ask because if there were errors on the very first use, then the problem is different than if that log about “fs with errors” is different in nature versus if there was some previous usage which might have caused corruption. The corruption is actually bad enough that it exceeded the size of the journal, and significant parts of the filesystem were completely lost. The filesystem errors are such that even if it worked it wouldn’t be worth using (further corruption upon write seems unavoidable).

FYI, you wouldn’t use (nor benefit from) the “copyRootToUSB.sh” if you are just mounting the SD card on a subdirectory (versus using it as the root filesystem).

Messages about “bad block bitmap checksum” leads me to believe that possibly the SD card is failing, but it still might just be software.

  • If you go to your Linux PC, and monitor “dmesg --follow”, what shows up during the insert of the SD card into the card reader?
  • If you check “lsblk -f” prior to inserting this SD card into the PC’s card reader, and then again after plugging in the SD card, what “lsblk -f” shows up due to the SD card being inserted (no need to list all of your PC’s disks, just the SD card)?
  • Assuming that on your PC the SD card is “/dev/mmcblk0” (on the Jetson it is mmcblk1), what do you see from:
    sudo gdisk -l /dev/mmcblk0

Also, do you have a different SD card you can try to compare if you follow the same procedure? If you have a similar error on an independent SD card, then I could see the following possibilities:

  • The card reader used is bad.
  • The content being copied is bad.

And of course, if there is no error on a second SD card, and this follows only the first card, then we might try cleanly reformatting the bad SD card. If after that it still fails, then probably the SD card is bad.

Thus I am assuming the “copyRootToUSB.sh” is provided by Seeed. Is this correct?

→ Yes the command:- copyRootToUSB.sh is provided by Seedstudio in official documentation on how to flash the OS installed from the eMMC to SD card.
So the whole process for what is followed is:-

Article 1 followed by Article 2 Article 3.

Article1:- Installing Jetpack 4.6.1 using nvidia sdk manager

Article 2:- enabling the sd card

Article 3:- Flshing & booting from sd card

Article 3 is where the command is :- copyRootToUSB.sh text

However, is it correct that the “bad message” error was while running on the host PC and not the Jetson (during creation of the SD card image)?

—> The bad message error is while running the whole process on the Jetson nano itself(during the creation of the SD card image) and not from Host PC.

During the above log which you attached, was this the first boot with that SD card installed?

—> No, I have tried booting with same sd card for about 3-4 times. During the first boot with the sd card it failed as well. Each time after it crashes with the above error, I reformated the sd card and tried it again and after about 3-4 times having the same issue, I stopped and posted the issue to the forum.

Also, do you have a different SD card you can try to compare if you follow the same procedure?

—> Yes, after your previous answer I tried the whole process again with a new untouched sd card and it failed again, this time it was 128 GB. Note:- I am using Sandisk Ultra microSDXC UHS-1 class 10 card, both in first time(64GB) and now i.e. second time(128GB) and the process after running the command crashes after a while with the same error message with second sd card as well.

What should I do further?

It seems we need to test the SD card itself. I don’t think this is the Jetson itself at fault. However, it could either be SD card failure or corrupt data being written. Having written two though tends to favor a software cause, but there might still be hardware reasons.

With “dmesg --follow” running on your host PC, what extra log lines do you see when you plug in one of the “bad message” SD cards to your host PC? After plugged in to the PC, it might show up as “/dev/mmcblk0” (the first device as a whole of that type; longer names are for partitions, and we are interested in the device as a whole). Assuming dmesg says it is “/dev/mmcblk0”, what do you see from:

  • lsblk -f /dev/mmcblk0
  • sudo gdisk -l /dev/mmcblk0

I ran the dmesg --follow command after the terminal crashes with bad message error.
Following is the resulting text file for the same:-
dmesg_–follow_result.txt (85.6 KB)

Following the same I ran below commands respective to my sd card:-

lsblk -f /dev/mmcblk1p1
sudo gdisk -l /dev/mmcblk1p1

Following is the result file for the same:-

lsblk.txt (987 Bytes)

Please go through them let me know what to do next

It might just be a corrupt partition (software only issue…either corruption after addition to the SD card or corruption of what was written to the SD card). It is quite possibly a bad SD card. One thing is obvious, aside from the corruption: There is no space left (at least regarding the journal):

[ 4913.319239] EXT4-fs warning (device mmcblk1p1): ext4_dirent_csum_verify:366: inode #1839234: comm rsync: No space for directory leaf checksum. Please run e2fsck -D.

Are you ok with destroying the content on that partition? Without the journal there is no protection against corruption, and I think without the journal the corruption is probably extreme. You can recover from such a partition, but it takes a lot of work and time (and the recovered content may not all be there). FYI, if you have plenty of extra disk space (something extra which is significantly beyond the size of the SD card), then you can make a bit-for-bit exact clone of the SD card to use or examine later. It just depends on how valuable that content is.

Meanwhile, let’s examine the source of where the content came from. Was this from one of the pre-built SD card images? If so, do you still have the file which was used to create the partition?

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.