Files are suddenly Read Only?

[chris.wirth]

Earlier this week, I updated the Logic and Firmware on my Groov Epic for a new series of experiments. Upon restarting use, it was hit-or-miss with data logging. Specifically this morning I changed 2 blocks in the logic, ran a test experiment and it logged fine. Started an actual experiment 10 minutes later and no data log.

The error message in the Node-RED Console Log is as follows:
(14 Feb 10:59:20 - [error] [file:Save CSV file] failed to append to file: Error: EROFS: read-only file system, open ‘/run/media/sdb1/1269-74.csv’)

Does anyone have any ideas as to why certain files are suddenly read only? From what I can tell, the logic is parsing out the data correctly into the desired Numeric Table. The Node-RED flow also appear to be operating correctly up to the point of actually writing the data to a new line on the desired file.

[Beno]

Some options off the top of my head…

If you have moved the USB stick, it will get a new mount point.
If you unplug and plug in the stick without unmounting first, Linux can get grumpy.

Both could lead to a read only file mount.

Here is a good thread on how to use Node-RED to call the unmount API.

USB File Management with groov View and Node-RED

To allow file management outside of the groov Manage interface I’ve put together this groov View page and Node-RED flow. I am using this to move files between local, on-board storage and an attached USB drive, as well as safely unmounting, all from just one page on my groov EPIC. There is NO use of groov Manage required after the initial setup; the only requirement is access to a groov View page! [image] Note: The “unmount” functionality is now officially supported through the Manage API, and…

[chris.wirth]

Thank you - the USB unmounting idea might be a good lead. Before running the firmware update, I attempted to unmount it correctly, but it didn’t seem like it responded to the command.