Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

ChristianSchmid

79 Posts

1358

October 14th, 2008 07:00

Windows Disk numbers and Windows 2008 clustering.

I assume this isn't really a symmetrix issue but our windows server guy isn't sure how to change it on his end so I figured I'd see if anyone here knows what is going on.
We have a windows 2008 clustered hyper-v environment. servers a,b,c, and d
I have presented 24 LUNs to each of the four servers. Disks 1-8 show up as the same device on all four servers. Starting with disk 9 servers b,c, and d all got the same devices, on server a disks 9 and up don't match the other 3 servers. Our server admin can't add those devices to the cluster because the disk#s don't match.
Example:
Device 02D0 is disk 17 on server a but is disk 9 on server b, c, and d.

Does anyone know what windows uses to decided what disk number it is going to assign to a device and how we can get the disks on a to match the other 3 servers?

Thanks,
Christian

John Toner

61 Posts

October 14th, 2008 07:00

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.

ChristianSchmid

79 Posts

October 14th, 2008 07:00

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?

MikeMac1

2 Intern

 • 

292 Posts

October 14th, 2008 07:00

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

ChristianSchmid

79 Posts

October 14th, 2008 07:00

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

Thanks

ChristianSchmid

79 Posts

October 14th, 2008 08:00

Thank you

xe2sdc

2 Intern

 • 

2.8K Posts

October 14th, 2008 08:00

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

ChristianSchmid

79 Posts

October 15th, 2008 08:00

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

Was this post helpful?

View All

No Events found!

Top