RHEL Disk Order Problem on VMware vSphere

I've been running RHEL on VMware vSphere since ESXi 5.5 in my lab—nested labs, customer environments, production clusters. And there's one gremlin that keeps biting engineers even in 2026: the RHEL disk order problem. You build a VM, attach a few VMDKs, configure your application, reboot, and suddenly /dev/sdb is /dev/sdc. Your database mounts the wrong disk. Oracle ASM can't find its disks. Apache serves files from a stale path. This is not a bug. It's how Linux has always assigned block device names—by enumeration order during kernel boot. But on vSphere the RHEL disk order problem turns acute because VMware's SCSI controller re-presents disks in scan order that can shift between power cycles.





