Disks not visible at OS level after adding.

[vmk2014]

Hi,

I have added 400 GB as E drive but its not visible at OS level even after re-scanning the disks  though its visible at VMware level.Please find the screenshot.

Any help on this will be appreciated. Thanks

thanks

vm2014

[a_p_]

Which OS is running in the guest/VM? Does it support hot-adding disks?

If hot-adding is supported, you still need to initialize/format the disk within the guest OS. In case of Windows you can use the Disk Manager to do this.

André

[vmk2014]

Hi Andre,

       Its  Windows 2008 R2 Standard. Thanks

thanks

vm2014

[JPM300]

Right click on disk management and click re-scan

It should pop up then.

[vmk2014]

We already did re-scan. Thanks

vm2014

[a_p_]

That's unusual. It shouldn't really make a difference, but can you rescan again while logged in to the console (in case you are currently using mstsc)?

Does diskpart show the disk with the list disk command?

I guess you don't have a chance to reboot Windows to see whether this solves the issue!?

André

[vmk2014]

Yes, its production server we cant re-boot now.I tried to re-scan using console but no luck. Screenshot attached. Thanks

vm2014

[a_p_]

Only a guess. Maybe the VM's configuration will be reloaded/refreshed if you slightly modify the new virtual disk (e.g. resize it to 301GB).

André

[vmk2014]

Thanks.I tried to change to 301 GB but still after re-scanning not showing disks. Thanks

vm2014

[a_p_]

Hmm. Is there anything in the Windows event logs that might help?

André

[vmk2014]

Sorry. Nothing Windows event viewer logs.

thanks

vm2014

[a_p_]

A few years ago I participated in a similar discussion (I am about to pull my hair out!!) where Windows incorrectly detected the virtual disk and placed it under "Other Devices" in the Device Manager. Can you please check whether it is the same in this case?

André

[vmk2014]

Hi Andre,

    Please find the screenshot.Let me know what i need to do.

thanks

vm2014

[a_p_]

I didn't have this issue myself, yet, so I can't tell you for sure what to do. It's actually up to you whether you try the steps in the KB article, or if you open a support case with VMware. In case you want to follow the KB, I'd recommend you do this after office hours in case you need to reboot the VM.

André

[vmk2014]

Andre,

    Please forward the KB article.

thanks

vm2014

[a_p_]

Here it is http://kb.vmware.com/kb/1013975.

André

[vmk2014]

Hi Andre,

       We have opened SR with VMware and first  approach from them to remove the vmdk file and added back but its didnt worked.Later on they asked us to re-boot the VM and

even after re-boot its no luck,so finally they took ssh session and suggested that it is Windows Driver issues and windows team need to look.

Summary from VMware support :-

So the issue seems to be Windows related as we can see in the logs that the device is being mounted within the guest. Since the disk is loaded on a LSI SAS controller, the drivers for these devices are built into Windows. Only if we were trying to mount the disk as a paravirtual controller would it be utilizing VMware drivers.

We saw in device manager that there isn't an associated driver for the disk so the Windows team will have to find out why Windows system drivers aren't being assigned to the device.

2014-11-04T19:06:13.876Z| vcpu-0| I120: Closing disk scsi0:2 2014-11-04T19:06:13.883Z| vcpu-0| I120: DISKLIB-VMFS  : "/vmfs/volumes/54217b3c-770ac43f-52a8-b82a72d2d412/MSVM1/MSVM1-flat.vmdk" : closed.

2014-11-04T19:07:30.560Z| vmx| I120: HotAdd: Adding scsi-hardDisk with mode 'persistent' to scsi0:2 2014-11-04T19:07:30.560Z| vmx| I120: DISK: OPEN scsi0:2 '/vmfs/volumes/54217b3c-770ac43f-52a8-b82a72d2d412/MSVM1/MSVM1.vmdk' persistent R[] 2014-11-04T19:07:30.562Z| vmx| I120: DISKLIB-VMFS  : "/vmfs/volumes/54217b3c-770ac43f-52a8-b82a72d2d412/MSVM1/MSVM1-flat.vmdk" : open successful (10) size = 323196289024, hd = 157791654. Type 3 2014-11-04T19:07:30.562Z| vmx| I120: DISKLIB-DSCPTR: Opened [0]: "MSVM1-flat.vmdk" (0xa) 2014-11-04T19:07:30.562Z| vmx| I120: DISKLIB-LINK  : Opened '/vmfs/volumes/54217b3c-770ac43f-52a8-b82a72d2d412/MSVM1/MSVM1.vmdk' (0xa): vmfs, 631242752 sectors / 301 GB.

thanks

vm2014

[Shrikrishna Pujar]

It worked for me 🙂 thank you !

[Bpardiwala]

I faced a same issue on 2012 r2. I tried all the options suggested in the blog below but nothing worked. Finally, I deleted the new volume form the disk management, next i made the disk offline and brought it online again and then marked it as simple volume. and the disk appeared in the OS .

[MarkG-ZA]

Its 2023 and this is still an issue.

 

Reloading the NVME controller driver in windows allows the guest OS to see the new disk space(note the disk will disappear when the driver is uninstalled then reappear when the driver is re-installed). I have had multiple meetings with VMware and Microsoft. MS say this is a VMware issue. VMware say the only way to resolve this is to reload the driver or reboot the OS.

[RyadBen]

Thanks. Your solution worked for me on Windows Server 2022.