Jetson TX2 loop login , reluctant to reflash because of ssd root

I am new to Jetson and I have re-flashed it couple of times.
Today I faced an issue in Jetson TX2 that I can not login to nvidia neither ubuntu, they both loop back to login page. fortunately I can login via ttty2.
I have read some topics related to the issue and they suggested to re-flash it, but I have changed my root to SSD based on this page :

Do I need to consider anything for re-flashing the device now? I received some errors after changing the root as well but I just ignored them and continued updating/upgrading the packages via sudo apt-get.

There are some errors while Jetson is booting as well but in sha1sum -c /etc/nv_tegra_release evrything is OK.

I have another question, after reflashing the device for the first time, I could not import opencv in python2 and python 3, it should not be installed via Jetpack3.3?

Often the login loop will be because the NVIDIA-specific direct hardware access drivers are not in place. The fact that “sha1sum -c /etc/nv_tegra_release” is all ok implies this is not the problem for your case. The drivers in question are validated by that command.

I don’t know about your case where the SSD is being used, someone else might comment, but as a general concept, consider that sometimes a truncated file system does strange things. A truncated file system would occur if your host didn’t have enough space. Within the location you used for flash there will be a “Linux_for_Tegra/bootloader/” directory. If you kept temporary files and did not delete, then this will contain file “Linux_for_Tegra/bootloader/system.img.raw”. What is the exact byte size of this file (“ls -l /where/ever/Linux_for_Tegra/bootloader/system.img.raw”)? This can say if your host had a complete image to work with.

Also, see if “sudo” works. A simple test:

sudo ls

…if sudo does not work correctly, then there are a number of software packages which might fail in unusual ways.