Attached volume on Windows doesn't appear on Disk Management

[AndreCampos89]

Hello everybody.

I'm experiencing an issue when attaching a volume to a Windows 2012 image.

On the dashboard I can create and attach volumes to an instance without issues, and on Linux instances they appear just fine.

But on my Windows 2012 R2 image, they just don't appear on the Disk Management. And on the Device Manager, I can see that it could not find the driver (image below).

The weird thing is a few weeks ago it was working just fine, and no changes were made (to the windows image or the cinder service).

The cinder logs don't help much, so I'm hoping that someone could maybe enlighten me on the problem.

Thanks in advance.

p.s: I'm using VIO 3.1, and when I add a disk to the instance through the vSphere client, it all works fine and the disk appears normally on the Disk Management.

[admin]

Hi Andre,

could you please follow:

1) Start a command prompt and type diskpart.

2) At diskpart prompt, type rescan.

Another important thing: could you tell me, which storage controller has been defined on VM perspective (check it on vCenter Server) ?

Cheers,

Domenico

[AndreCampos89]

Hi, thanks for answering.

Actually, the first thing I did was the rescan, but that didn't worked.

After I attach on the Openstack Dashboard, the disk appears in the instance BIOS and also in its Hardware section, on vSphere. That "SCSI Controller" icon also only appears after I attach.

As for storage, the first disk is set as "LSI Logic SAS" and the second one (the one that doesn't appear) is set as "LSI Logic Parallel". I checked that on another Windows VM that does have a volume (back on when there was no issue) and the disks are set in the same way.

[admin]

Probably the reason why this happens, is because Windows 8.1 and Windows Server 2012 R2 guest operating systems are unable to access storage on a virtual machine configured with the LSI Logic SCSI adapter, as explained in KB 2059549.

I need to replicate the issue.

Cheers,

Domenico

[AndreCampos89]

That indeed seems to be the problem.

I found this: windows 2012 volume attach error vio 3.0

My Windows 2012 image is already set to use vmware_adaptertype=lsiLogicsas, so when I start an instance, the boot disk does come with that controller.

But for some reason, when I create a volume, it comes as Parallel. If I turn off the VM, and change the controller on the second disk to LogicSas on vCenter, the disk appears normally on the Disk Management and works like a charm.

The weird thing is that I went looking for previous Windows instances with volumes, and they're all using LogicParallel for the volume, working just fine.

Is there a way I could force Cinder to create volumes using LogicSas?

[admin]

Hi Andre,

did you take a look at the following documentation Modify the Default Cinder Volume Adapter Type ?

It seams that, as previously mentioned in windows 2012 volume attach error vio 3.0 thread, the issue has been fixed in VIO 3.1.

Do you have any upgrading plan on your current release? can you confirm is it VIO 3.0?

Cheers,

Domenico

[AndreCampos89]

That's an interesting link, it does sound like it's pointing in the right direction.

My VIO is indeed 3.1. I edited the first post correcting that.

It says in that page that "When a volume is created from image, Cinder respects the vmware_adaptertype property of the image and creates the corresponding controller", but that is not happening, as I said in a previous post. The image is already set as LogicSas, but the volumes come as Parallel.

Unfortunately I can't use that solution, because for some reason, every time ansible tries to reconfigure the cloud, it ends up messing with the ldaps certificate and it takes forever to fix that. Is there a way I could use the "viocli deployment configure" command without touching the certificates? Or manually adding the vmware_adaptertype parameter in the controllers.

[AndreCampos89]

I was able to manually change that on cinder config files and it is now working, thanks.

[admin]

Cool Andre!

anytime... if you need help, just... ping us!

Cheers,

Domenico