Newly Added virtual disks does not get detected by Red Hat Enterprise Linux OS.
search cancel

Newly Added virtual disks does not get detected by Red Hat Enterprise Linux OS.

book

Article ID: 428988

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Disks are attached on the vSphere, and VM can be powered-on or operational on vSphere. However, new disks do not show up on Rhel Guest OS.

VM restart does not help either.

For Ex:

- We see the new disks attached in the vCenter as well as the vmx config 

scsi0:0.fileName = "vm_name.vmdk"
scsi0:1.fileName = "vm_name_1.vmdk"
scsi0:2.fileName = "vm_name_2.vmdk"  <--
scsi0:3.fileName = "vm_name_3.vmdk"  <--
scsi0:4.fileName = "vm_name_4.vmdk"  <--
scsi0:5.fileName = "vm_name_5.vmdk"  <--

 

- However, on the Rhel guest OS new disks are not detected

Environment

VMware vSphere 8.x

Cause

The issue is on the Guest OS failing to detect the new disks.

While the vmware.log shows the new disks are readable and are opened on the infrastucture.

/vmfs/volumes/datastore-path/vm_name/vmware.log

YYYY-MM-DDTHH:MM:S3.674Z In(05) vmx - DICT          scsi0:1.fileName = "vm_name.vmdk"
YYYY-MM-DDTHH:MM:S9.871Z In(05) vmx - DISK: OPEN scsi0:1 '/vmfs/volumes/6xxxxxx9-4xxxxxx8-5xx5-exxxxxxxx1926/vm_name/vm_name_1.vmdk' persistent R[]
YYYY-MM-DDTHH:MM:S9.878Z In(05) vmx - DISK: Disk '/vmfs/volumes/6xxxxxx9-4xxxxxx8-5xx5-exxxxxxxx1926/vm_name/vm_name_1.vmdk' has UUID ''#####################################

YYYY-MM-DDTHH:MM:S3.674Z In(05) vmx - DICT          scsi0:1.fileName = "vm_name_1.vmdk"
YYYY-MM-DDTHH:MM:S9.871Z In(05) vmx - DISK: OPEN scsi0:1 '/vmfs/volumes/6xxxxxx9-4xxxxxx8-5xx5-exxxxxxxx1926/vm_name/vm_name_1.vmdk' persistent R[]
YYYY-MM-DDTHH:MM:S9.878Z In(05) vmx - DISK: Disk '/vmfs/volumes/6xxxxxx9-4xxxxxx8-5xx5-exxxxxxxx1926/vm_name/vm_name_1.vmdk' has UUID ''#####################################

YYYY-MM-DDTHH:MM:S3.674Z In(05) vmx - DICT          scsi0:2.fileName = "vm_name_2.vmdk"
YYYY-MM-DDTHH:MM:S9.871Z In(05) worker-116314042 - DISK: OPEN scsi0:2 '/vmfs/volumes/6xxxxxx9-4xxxxxx8-5xx5-exxxxxxxx1926/vm_name/vm_name_2.vmdk' persistent R[]
YYYY-MM-DDTHH:MM:S9.877Z In(05) worker-116314042 - DISK: Disk '/vmfs/volumes/6xxxxxx9-4xxxxxx8-5xx5-exxxxxxxx1926/vm_name/vm_name_2.vmdk' has UUID ''#####################################'

YYYY-MM-DDTHH:MM:S3.674Z In(05) vmx - DICT          scsi0:4.fileName = "vm_name_3.vmdk"
YYYY-MM-DDTHH:MM:S9.871Z In(05) worker-116314149 - DISK: OPEN scsi0:4 '/vmfs/volumes/6xxxxxx9-4xxxxxx8-5xx5-exxxxxxxx1926/vm_name/vm_name_3.vmdk' persistent R[]
YYYY-MM-DDTHH:MM:S9.877Z In(05) worker-116314149 - DISK: Disk '/vmfs/volumes/6xxxxxx9-4xxxxxx8-5xx5-exxxxxxxx1926/vm_name/vm_name_3.vmdk' has UUID ''#####################################'

YYYY-MM-DDTHH:MM:S3.674Z In(05) vmx - DICT          scsi0:3.fileName = "vm_name_4.vmdk"
YYYY-MM-DDTHH:MM:S9.871Z In(05) worker-116314150 - DISK: OPEN scsi0:3 '/vmfs/volumes/6xxxxxx9-4xxxxxx8-5xx5-exxxxxxxx1926/vm_name/vm_name_4.vmdk' persistent R[]
YYYY-MM-DDTHH:MM:S9.877Z In(05) worker-116314150 - DISK: Disk '/vmfs/volumes/6xxxxxx9-4xxxxxx8-5xx5-exxxxxxxx1926/vm_name/vm_name_4.vmdk' has UUID '#####################################

YYYY-MM-DDTHH:MM:S3.674Z In(05) vmx - DICT          scsi0:0.fileName = "vm_name_5.vmdk"
YYYY-MM-DDTHH:MM:S9.871Z In(05) worker-116314152 - DISK: OPEN scsi0:0 '/vmfs/volumes/6xxxxxx9-4xxxxxx8-5xx5-exxxxxxxx1926/vm_name/vm_name_5.vmdk' persistent R[]
YYYY-MM-DDTHH:MM:S9.877Z In(05) worker-116314152 - DISK: Disk '/vmfs/volumes/6xxxxxx9-4xxxxxx8-5xx5-exxxxxxxx1926/vm_name/vm_name_5.vmdk' has UUID ''#####################################'

Resolution

Request to engage with Guest OS Vendor (Red Hat).

Additional Information

RedHat document regards to this issue.

New virtual disks do not get detected by Red Hat Enterprise Linux  on a VMware hypervisor.