OK, that makes sense. But there have been quite a few fixes released since the iso was released under the testing channel. So you could select that one first and get at least some improvements, plus the slightly newer kernel of course (which is important). You can always then switch to the value add stable (which is now the much newer of the two) later down the line and in doing so help to support development financially if that works for you.
A known chicken and egg bug when changing from testing to stable however:
Make sure to confirm you actually have installed what the Web-UI interface states. This can be done via a terminal as root user:
yum info rockstor
We had a bug when switching from testing to stable where the Web-UI would show available version not installed. That was really irritating but never mind. It is now fixed and so once we get another iso out we can forget it. But of course if you don’t know of it then you thing you are on a newer version and it doesn’t ever offer to updates via the Web-UI. Details in case you are interested:
Essential the Rockstor code age is as follows:
- iso 3.9.1-0 (July 2017)
- testing channel (Gratis) 3.9.1-16 (same as 3.9.2-0 stable at the time (November 2017)
- stable channel (Paid subscription to help with the projects development) 3 days ago.
You can see the details for the fixes introduced in each release on the GitHub Releases page:
All code in all versions is GPL v2 or later bar the js libraries which are all at least open source. So you might as well try the testing code for your testing and either stick with it or get the newer stable code. In time we will release a new iso and so all new installs will again be bang up to date (at least for a while). But that’s not the case right now.
Hope that helps and thanks again for sharing your fix / workaround for getting this hardware working on our now rather old installer (we are working on that). Much appreciated.