@alazare619 Yes I wouldn’t go this way as the rules you used are based off the temp-names from what I can tell which was the whole point in moving away from temp names to something that moved with the actual device, not the changable sda type names. Also there are an increasing number of things that depend on the by-id name that will not work if you have 2 drives essentially fighting for the same by-id base name. The name is an artifact of udev rules itself and they depend the uniqueness and existence of the device serials. Your issue is with the hyper visor software not the client OS: that is where it should be fixed. The by-id name, derived from the serial, is meant to be unique and isn’t. A prerequisites of scsi compliant devices:
See RedHats: Persistent Naming.
"The World Wide Identifier (WWID) can be used in reliably identifying devices. It is a persistent, system-independent ID that the SCSI Standard requires from all SCSI devices. The WWID identifier is guaranteed to be unique for every storage device, and independent of the path that is used to access the device.
This identifier can be obtained by issuing a SCSI Inquiry to retrieve the Device Identification Vital Product Data (page 0x83) or Unit Serial Number (page 0x80). The mappings from these WWIDs to the current /dev/sd names can be seen in the symlinks maintained in the /dev/disk/by-id/ directory."
Hope that helps.
This is not something Rockstor can fix as the VM machine you are running it in is not creating devices that are friendly to udev and Rockstor uses udev heavily. You are likely to risk data loss if drives cannot be uniquely identified, hence udev and Rockstor’s assumption that each drive will have a unique serial. How else does one distinguish between and track devices when they transition between having no partition table or any fs. This is the challenge that udev and consequently Rockstor face and is only really doable by depending on serial numbers being unique: hence udev creating a naming scheme in by-id that utilises serial numbers.
When you find out how to fix / configure the hyper visor in this regard it would be good if you could post the same here as @unomagan did in the following thread with regard to Vmware which just plain give no serial (and hence no by-id name either), but yours is giving out the same “S” or “S_ST31500341AS” (from the udev command) serial to 2 different devices and so surfacing differently:
I’m assuming there must be some counterpart to your chosen VM manager.
Apologies if I’ve missed something here but it currently looks pretty clear cut and a quick config in the hyper visor and you should be good. Otherwise you are on shaky ground with regard to udev on any linux.
Let us know how you get on as I at least haven’t seen this particular serial issue before so knowing the appropriate config would be good for others that come after you on the forum.
Thanks.