We are an FRC Team. We have a Robo Rio 1 that was previously working just fine, but now it does not. One of the issues we have found is that the root file system is mounting read-only and we think this might be part of the other issues.
We have another Robo Rio 1 that is working correctly, so we have tried all of these trouble-shooting steps both with the "good" RobRIO and the "bad" RoboRIO to make sure we are actually performing the correct steps.
If we run the RoboRIO imaging tool (as administrator), if we use the "good" RoboRio, we can detect the RoboRIO, both by using a direct network cable connection and by using a direct USB cable connection. However the RoboRIO imaging tool does not detect the "bad" RoboRIO (it says no devices detected) whether we use a direct network connection or a direct USB connection.
If we put the RoboRIO on our robot and connect the Driver Station software laptop via the Wifi robot radio, with the "good" RoboRIO, the DriverStation software connects successfully to the RoboRIO (Communication Indicator is green), but with the "bad" RoboRIO, the DriverStation software does not connect (Communication indicator is red) and we get the following error message: WARNING: Ping results: link-bad, DS radio(.4)-bad, robot radio(.1)-GOOD, roboRIO(.2)-GOOD, FMS-bad Driver Station
If we connect our programming laptop via wifi to the robot, with the "good" RoboRIO, we can deploy robot code, but with the "bad" RoboRIO, we cannot deploy robot code - it says it cannot find the RoboRIO.
If we connect our programming laptop via wifi to the robot, with the "good" RoboRIO, we can login successfully. via ssh. With the "bad" RoboRIO we can also successfully login via ssh. After logging in via ssh, if we type in the "mount" command, it prints about 14 entries. But there is one difference between the "good" and the "bad" RoboRIO:
This is the first entry for the "good" RoboRIO (after typing the mount commend):
ubi1:rootfs on / type ubifs (rw,relatime,ubi=1,vol=0)
This is the first entry for the "bad" RoboRIO:
ubi1:rootfs on / type ubifs (ro,relatime,ubi=1,vol=0)
Notices the "rw" for the good RoboRIO and "ro" for the bad RoboRIO. And the root file system for the "bad" RoboRIO is definitely read-only. Any attempt to edit a file results in an error message stating the file system is read-only.
Rebooting the RoboRIO does not fix this problem.
By looking in the logs folder on the RoboRIO, it seems that the last successful log file was in June of 2025. The RoboRIO was working fine before then.
I find it very strange that I can get logged into the RoboRIO via ssh, but yet the RoboRIO Imaging tool cannot even detect the device.
