@MainrtNr5 Thanks for the report.
I can initially chip in on the following:
Yes, this has been a long standing issue unfortunately in that the errors used for the title can be interpreted, via the create forum post mechanism, as forum commands in themselves. This has actually now been fixed, see the following issue:
https://github.com/rockstor/rockstor-core/issues/2150
and it’s consequent now merged pull request:
https://github.com/rockstor/rockstor-core/pull/2269
This fix is due to be included in our now pending 4.0.6 release.
As you actual Rock-on issue. Could you let us know here the version of Rockstor you are running. And note that if it is an earlier CentOS based variant, where there was a bug in testing that prevented a successful transition to Stable you can double check via:
yum info rockstor
See the following forum thread for info no this known bug from quite a while ago:
This version number will help to diagnose the problem as there have been quite a few changes in the Rock-on system more of late.
Also, have you recently deleted any snapshots that were indicated as being on the Rock-ons root share (subvol): this is a potential cause of Rock-ons failure and another usability issue we have lined up for improvement:
https://github.com/rockstor/rockstor-core/issues/1682
But I don’t think this is what has happened in your case.
One possible work around, assuming you have followed the guidelines on using discreet shares for your required plex config/share etc, is to try uninstalling the Plex rock-on and re-installing. If you use all the same configurations (read shares/users) then it should pick-up from where it left. Also the mention of devices in the error message points to a more recent Rockstor version that introduced rock-on devices such as are associated with hardware encoding within rock-ons like Plex.
But before you try this, if you have the time, I’d await more comments here on the forum in case we can further diagnose what has happened here.
Hope that helps.