I have been installing custom libraries (mostly from source), such as OpenCV, PyTorch etc. on the Xavier A. While installing OpenCV recently, the build process failed with an error: no space on device.
I did not realize that the main filesystem on Xavier A only sports 32GB of space.
After encountering this error, I rebooted the system (I shouldn’t have) and then got stuck on the login page which keeps asking for credentials (for nvidia user, ubuntu user and Guest Session) but does not let me login.
Has anyone encountered similar errors related to device storage on Xavier A/B? What should I do now to resolve these issues (a. no more device storage, b. can’t login!!)?
Thanks @SteveNV for the comment. I ended up removing some unnecessary files from the system via minicom from host pc, and was able to log in on Xavier A after that.
I still have the question related to storage: how can I increase the default eMMC storage limit on the Xavier?
There is an unassigned UFS storage block of ~72 GB for each Xavier that can be mounted, and can actually be used as persistent storage.
If you ever change your storage allocation this unassigned block may shrink or go away. In any case the instructions to initialize and mount this block are
sudo fdisk /dev/vblkdev1
###############
Welcome to fdisk (util-linux 2.27.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Device does not contain a recognized partition table.
Created a new DOS disklabel with disk identifier 0x6c2adfee.
Command (m for help): n
Partition type
p primary (0 primary, 0 extended, 4 free)
e extended (container for logical partitions)
Select (default p): p
Partition number (1-4, default 1):
First sector (2048-8388607, default 2048):
Last sector, +sectors or +size{K,M,G,T,P} (2048-8388607, default 8388607):
###############
sudo mkfs -t ext4 /dev/vblkdev1
sudo mkdir /mnt/ufs_mount
sudo mount /dev/vblkdev1 /mnt/ufs_mount