The Windows 2008 Failover Cluster Validation wizard returns the following error while running the 'Storage - List Potential Cluster Disks' test: 'The wrong diskette is in the drive. Insert%2 (Volume Serial Number:%3) into drive%1' We are using a Microsoft iSCSI server and creating new disks which have been mapped to a couple of Windows 2008 servers. We are not using multipathing. Diskpart disk list shows the disks as online.

Cluster Validation Strange Error - Disk - The wrong diskette is in the drive. Bluetooth Driver Problems Windows 7. Insert%2 (Volume Serial Number:%3) into drive%1.

I've verified that the virtual disks are enabled in the properties on the iSCSI server. The 'Target Access' tab shows the correct servers as the targets. Additionally, the iSCSI target itself is enabled and logged in and shows the correct iSCSI initiators. The local iSCSI initiator control panel on the Windows boxes shows that they are logged into the iSCSI server and when I click Devices, I see all of the LUNs.

Call Center English Speaking Training Pdf here. Hi Chris; Right you are, I don't have this problem myself, but we don't have it solved in this newsgroup, so I cross posted three reported solutions from the WindowsLiveOneCare newsgroups where posters there have said they've used one of three different techniques which resolved the problem for them personally. Without those cross posted reports you would never have seen them or have been able to try them unless you also follow those Ms Newsgroups. Since I don't have privy to the WD code as Steve Dodson and his Microsoft team do, that's who you should be telling that you haven't been able to resolve this issue if one of these techniques doesn't do it for you, see my initial post item 4.

One of the purposes of a Beta is to repair non-working code or errors resulting from that code and only Microsoft can do that. This issue has been around since at least 2/14 without a specific resolution, however lately the reports of it have grown more frequent and that needs to be brought to Microsoft's attention, even if it has been reported here before. Let us know if you have any success with any of these suggested fixes.

I don't guarantee any of them will work for you, but one might.