Different disk numbering would not prevent a disk to be added to a cluster. Microsoft clustering uses the disks signature value to identify the disks, not the \\.\physicaldrive number.

But to answer your question, Windows numbers the disk based on Controller/Bus/Lun values. If your disk has a different LUN address, it would show up in a different order.

Hope this helps.

I assigned the LUN numbers when mapping the drive to the FAs that all four servers are using. Shouldn't they all see the same LUN info then?

You might get better response posting in Host Software >> Open Systems.

I'll let him know that the disk number shouldn't be making a difference with the problem he is having.

Thanks

Thank you

As suggested, thread moved itself at better location .. and you know that the 3 most important things are location, location and location

Message was edited by:
Stefano Del Corno

As stated above the disk number had nothing to do with the disk not joining the cluster. There is something wrong with the disk itself. I replaced it with a new meta and that new meta works fine.

I'm just going to mark this thread as answered.

Christian