[BUG]: RIO1 No Space Left On Device Error

Mar 12, 2025 by ADMIN 42 views

Problem description

A freshly imaged roboRIO 1.0 with 2025_v2.0 fails to deploy code due to a "No space left on device" error. This issue occurs when trying to install all modules on the roboRIO using pip install.

Additional information

A max reproducible example is available at: https://github.com/RobotCasserole1736/RobotCasserole2025/tree/b239e696abe24fddd83049de2ab9fa714f1030fd
The reported issue is being out of disk space while doing pip install of all modules on the roboRIO, but adding up the reported sizes of all modules is only ~20% of the reported available disk space - there should be plenty of margin.

Log of deploy

The log of the deploy process is as follows:

17:56:47:801 INFO    : paramiko.transport  : Connected (version 2.0, client OpenSSH_8.3)
17:56:47:942 INFO    : paramiko.transport  : Auth banner: b'NI Linux Real-Time (run mode)\n\nLog in with your NI-Auth credentials.\n\n'
17:56:47:943 INFO    : paramiko.transport  : Authentication (password) successful!
17:56:48:033 INFO    : robotpy.installer   : -> RoboRIO image version: 2025_v2.0
17:56:48:117 INFO    : robotpy.installer   : -> RoboRIO disk usage 171.5M/386.3M (45% full)
17:56:48:203 INFO    : robotpy.installer   : -> RoboRIO memory 86.9M/250.2M (65% full)
17:56:48:218 INFO    : deploy              : Clearing existing packages on RoboRIO before install (specify --no-uninstall to not do this)
17:56:48:219 INFO    : deploy              : Installing project requirements on RoboRIO:
17:56:48:219 INFO    : deploy              : - robotpy[apriltag,cscore,phoenix6,rev]==2025.2.1.0
17:56:48:219 INFO    : deploy              : - photonlibpy==2025.1.1
17:56:48:219 INFO    : deploy              : - debugpy==1.8.11
17:56:48:219 INFO    : deploy              : - sleipnirgroup-choreolib==2025.0.1
17:56:48:219 INFO    : deploy              : - robotpy-playingwithfusion==2025.0.0
17:56:48:383 INFO    : paramiko.transport.sftp: [chan 4] Opened sftp connection (server version 3)
17:56:48:394 INFO    : paramiko.transport.sftp: [chan 4] sftp session closed.
WARNING: Disabling truststore since ssl support is missing
Looking in links: http://localhost:46129/pip_cache/
Collecting robotpy==2025.2.1.0 (from robotpy[apriltag,cscore,phoenix6,rev]==2025.2.1.0)
  Downloading http://localhost:46129/pip_cache/robotpy-2025.2.1.0-py3-none-any.whl (2.2 kB)
Collecting photonlibpy==2025.1.1
  Downloading http://localhost:46129/pip_cache/photonlibpy-2025.1.1-py3-none-any.whl (54 kB)
Collecting debugpy==1.8.11
  Downloading http://localhost:46129/pip_cache/debugpy-1.8.11-py2.py3-none-any.whl (5.2 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 5.2/5.2 MB 3.4 MB/s eta 0:00:00
Collecting sleipnirgroup-choreolib==2025.0.1
  Downloading http://localhost:46129/pip_cache/sleipnirgroup_choreolib-2025.0.1-py3-none-any.whl (9.4 kB)
Collecting robotpy-playingwithfusion==2025.0.0
  Downloading http://localhost:46129/pip_cache/robotpy_playingwithfusion-2025.0.0-cp313-cp313-linux_roborio.whl (868 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 868.2/868.2 kB 2.0 MB/s eta 0:00:00
Collecting robotpy-wpiutil==2025.2.1 (from robotpy==2025.2.1.0->robotpy[apriltag,cscore,phoenix6,rev]==2025.2.1.0)
  Downloading http://localhost:46129/pip_cache/robotpy_wpiutil-2025.2.1-cp313-cp313-linux_roborio.whl (3.2 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 3.2/3.2 MB 2.1 MB/s eta 0:00:00
Collecting robotpy-wpinet==2025.2.1 (from robotpy==2025.2.1.0->robotpy[apriltag,cscore,phoenix6,rev]==2025.2.1.0)
  Downloading http://localhost:46129/pip_cache/robotpy_wpinet-2025.2.1-cp313-cp313-linux_roborio.whl (708 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 708.2/708.2 kB 3.7 MB/s eta 0:00:00
Collecting robotpy-wpimath==2025.2.1 (from robotpy==2025.2.1.0->robotpy[apriltag,cscore,phoenix6,rev]==2025.2.1.0)
  Downloading http://localhost:46129/pip_cache/robotpy_wpimath-2025.2.1-cp313-cp313-linux_roborio.whl (6.2 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 6.2/6.2 MB 3.1 MB/s eta 0:00:00
Collecting pyntcore==2025.2.1 (from robotpy==2025.2.1.0->robotpy[apriltag,cscore,phoenix6,rev]==2025.2.1.0)
  Downloading http://localhost:46129/pip_cache/pyntcore-2025.2.1-cp313-cp313-linux_roborio.whl (1.9 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.9/1.9 MB 3.1 MB/s eta 0:00:00
Collecting robotpy-hal==2025.2.1 (from robotpy==2025.2.1.0->robotpy[apriltag,cscore,phoenix6,rev]==2025.2.1.0)
  Downloading http://localhost:46129/pip_cache/robotpy_hal-2025.2.1-cp313-cp313-linux_roborio.whl (1.2 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.2/1.2 MB 3.3 MB/s eta 0:00:00
Collecting wpilib==2025.2.1 (from robotpy==2025.2.1.0->robotpy[apriltag,cscore,phoenix6,rev]==2025.2.1.0)
  Downloading http://localhost:46129/pip_cache/wpilib-2025.2.1-cp313-cp313-linux_roborio.whl (4.7 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 4.7/4.7 MB 3.0 MB/s eta 0:00:00
Collecting robotpy-wpilib-utilities<2026.0.0,>=2025.0.0 (from robotpy==2025.2.1.0->robotpy[apriltag,cscore,phoenix6,rev]==2025.2.1.0)
  Downloading http://localhost:46129/pip_cache/robotpy_wpilib_utilities-2025.0.0-py3-none-any.whl (48 kB)
Collecting robotpy-cli<2026.0.0,>=2024.0.0 (from robotpy==2025.2.1.0->robotpy[apriltag,cscore,phoenix6,rev]==2025.2.1.0)
  Downloading http://localhost:46129/pip_cache/robotpy_cli-2024.0.0-py3-none-any.whl (8.9 kB)
Collecting numpy~=2.1 (from photonlibpy==2025.1.1)
  Downloading http://localhost:46129/pip_cache/numpy-2.2.1-cp313-cp313-linux_roborio.whl (6.1 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━<br/>
**Q&A: [BUG]: RIO1 No space left on device error**
=====================================================

**Q: What is the "No space left on device" error?**
------------------------------------------------

A: The "No space left on device" error is a common issue that occurs when a system runs out of disk space. In the context of the roboRIO 1.0, this error occurs when trying to install all modules using `pip install`.

**Q: Why is the roboRIO 1.0 running out of disk space?**
---------------------------------------------------

A: The roboRIO 1.0 has a limited amount of disk space available. When trying to install all modules using `pip install`, the system is unable to find enough free space to complete the installation.

**Q: How can I resolve the "No space left on device" error?**
---------------------------------------------------------

A: To resolve the "No space left on device" error, you can try the following:

1.  **Check the disk space**: Verify that the roboRIO 1.0 has enough free disk space to complete the installation. You can do this by running the command `df -h` to check the available disk space.
2.  **Remove unnecessary files**: Remove any unnecessary files or packages that are taking up space on the roboRIO 1.0. You can do this by running the command `pip freeze` to list all installed packages and then removing any packages that are no longer needed.
3.  **Use a different installation method**: Consider using a different installation method, such as using a USB drive or a network share, to install the modules.
4.  **Contact support**: If none of the above solutions work, contact the support team for further assistance.

**Q: How can I prevent the "No space left on device" error in the future?**
-------------------------------------------------------------------------

A: To prevent the "No space left on device" error in the future, you can try the following:

1.  **Regularly clean up disk space**: Regularly clean up disk space by removing unnecessary files and packages.
2.  **Monitor disk space**: Monitor disk space regularly to ensure that the roboRIO 1.0 has enough free space to complete installations.
3.  **Use a larger disk**: Consider using a larger disk to increase the available disk space on the roboRIO 1.0.
4.  **Optimize installation process**: Optimize the installation process by using a different installation method or by installing modules in a more efficient manner.

**Q: What are some common causes of the "No space left on device" error?**
-------------------------------------------------------------------------

A: Some common causes of the "No space left on device" error include:

1.  **Insufficient disk space**: Insufficient disk space on the roboRIO 1.0.
2.  **Corrupted files**: Corrupted files or packages that are taking up space on the roboRIO 1.0.
3.  **Inefficient installation process**: An inefficient installation process that is not optimized for the available disk space.
4.  **Malfunctioning hardware**: Malfunctioning hardware that is causing the roboRIO 1.0 to run out of disk space.

**Q: How can I troubleshoot the "No space left on device" error?**
-------------------------------------------------------------------------

A: To troubleshoot the "No space left on device" error, you can try the following:

1.  **Check the error message**: Check the error message to determine the cause of the issue.
2.  **Verify disk space**: Verify that the roboRIO 1.0 has enough free disk space to complete the installation.
3.  **Check for corrupted files**: Check for corrupted files or packages that may be taking up space on the roboRIO 1.0.
4.  **Contact support**: If none of the above solutions work, contact the support team for further assistance.