@coronic Thanks for the update, that’s really helpful.
Yes our ISO is now a little over 2.5 years old as of writing this.
I now think what has happened, in your case, is an upstream update (from the RedHat/CentOS folks) to libblk or udev has sorted your issue and so the Rockstor code was then able to pickup the now existing by-id names. Good to know. We have seen this with for example nvme devices.
And although newer our now deceased for CentOS Testing channel is only 3 month younger at still over 2 years out of date:
3.9.2 Stable Channel update was the same as 3.9.1-16 testing channel for our CentOS based offering. Please see the following forum thread for some background on this:
Where as our latest Stable channel release for CentOS (and openSUSE only Testing Channel releases) are now 8 days old as of writing with 3.9.2-53.
And for our modern testing channel releases, our “Built on openSUSE” variant, see the following thread:
We are currently aiming to achieve feature parity in our openSUSE testing channel, or near enough, before we establish a new ‘Built on openSUSE’ Stable Channel and spin off the new openSUSE only testing channel to address our fairly massive technical debt so that our current supporters in the CentOS Stable channel will have a workable system to transition to, with upstream kernel/btrfs updates / boot to snapshot etc, while we get on with working through our backlog of moving to Python 3, Django 2, possibly a new build system etc within the testing channel.
Note that if you do fancy evaluating our most recent code, on the current CentOS base, then you should first read the following post which addresses a critical bug when moving to Stable channel updates from the now defunct for CentOS base Testing channel:
Hope that helps and thanks again for sharing your findings, much appreciated.