@maverick Hello again,
The problem you are facing is that Rockstor absolutely depends upon device serial numbers, as does udev. That is why you were seeing the ‘missing’ by-id names. Simply creating these is not enough as we also resource udev to retrieve these, normally hardware supplied, unique drive identifiers. See the following technical wiki entry, Subtitle: Rockstor’s Serial Obsession, for the ‘why’:
If you can arrange for your hypervisor to create or pass-through these normally hardwre supplied drive elements then udev will be able to auto-create the required by-id names and also be able to supply these same serials to Rockstor when requested.
The updated versions of the error messages you are seeing, and have posted above, now contain links to our “Minimum system requirements” doc section here:
http://rockstor.com/docs/quickstart.html#
That docs section contains an example required configuration for VMware but not all hypervisors are equal in this capability. KVM/libvirt is also capable of supplying device serials but I’m unsure of this capability within Xen unfortunately. Hopefully other forum members can chip in with their knowledge/experience re Xen in this respect.
Also note that 3.9.1-0 is now very old. But I’m aware that we don’t yet have a newer installer; sorry about that. But you can now build your own fully updated Rockstor 4 installer and we will have downloads available as soon as this is out of release candidate phase. See the following GitHub repo for how to build our next generation installer which is now ‘Built on openSUSE’ Leap 15.2:
This new installer does not however change the serial requirement, but it would include all pending upstream updates as of it’s build date which is always nice to have.
Another point of interest here is that we may still have a bug that is affecting you. If you first resolve the serial presentation issue so that the guest auto generates the by-id names, and can produce the required matching serials on request we can then see if we have a name parsing issue with these xvda names as they look odd to me so there may still be some work for us to do there.
Hope that helps and let us know how you get on with the initial drive serial problem as it would be good to know of a robust solution in Xen that does not reside in the guest (as a work around) but in the host/hypervisor such that it presents dependable and drive-tracking capable serials.