Hello,
I’m trying to reflash a Jetson Nano 2GB that I have - it would get stuck booting and when plugged into a monitor would remain stuck on the Nvidia Logo, and I’ve already made sure the issue is not the image on the SD card because another Jetson is able to boot just fine from it.
I’ve been trying to follow this set of instructions I found, however eventually it reaches a point of putting my Ubuntu system into read-only mode. The first time this happened was during the actual flashing of the board, when that happened I decided to start the process over, and then it happened again a second time while extracting the sample filesystem.
For some context to the setup, I’m running my Ubuntu system in VirtualBox on a windows 10 computer, however the entire ubuntu system is saved to an external drive.
I saw somewhere someone said to check to make sure that the drive is “ext4”. The external drive itself is formatted as an NTFS, but when doing df -T file/location/here/ it says it’s ext4. So I’m unsure if this could be the issue or not
Beyond that I’m just kind of unsure what the issue could be
Oh yes I was able to fix it being in read only by running fsck and rebooting. It’s just that when it becomes read-only it then fails the remainder of everything it was doing because it’s in read-only.
then I would suggest delete the VM you currently use and get another VM image installed, or just run the whole process on a real Ubuntu PC, as it should be more stable.
the reason why we do not support flashing using a VM is that the device will be connected and disconnected multiple times throughout the process of flashing, which may not be handled correctly by a VM, and it’s very likely in your case.