CLuster on Win2k3 issue

Hi,

I have a typical issue on our Win2k3 cluster server..It was a two node
cluster and after one patch instalation on one of the node, it failed to
rejoin the cluster. While troubleshooting it, our team has evicted the node
and after that thye failed to add it back to cluster. At present the cluster
is working n one node and we have rebuilded the node which was failing. When
we try to add it to cluster, again it fails to find quorum drive. This is a
SAN drive and we are using MS iSCSI initiator. I can see th efollowing error
in log file:

There is not a "friendly name" for the physical disk "PHYSICALDRIVE2".
(hr=00000000, {05AA0768-5F49-49CD-AFDC-96F9D51802D4},
{00000000-0000-0000-0000-000000000000}, 1, 1, 1), (null)

like this I can see for all SAN drives..we tried to install a fresh cluster
in the newly built server and it was successfull(after we have evicted the
cluster from the only one working node). Then we tried to add the node which
was working fine earlier, still we receive the same error. Our experts are
saying that the issue with SAn drives..becos, in disk management of passive
node, they are unable to see the drive letter..What they says is it should e
there in disk management. Instead we can see the drive without drive letter
and is not accessible..

Any ideas how can we resolve this?

Hi,

It looks like your disk has only a volume GUID, but not a drive letter
assigned to it? Some applications still have a hard dependency on drive
letters, so they're required for your LUN. Try giving it a drive letter to
see if that resolves your problem.

In Server 2008, many applications can use the GUID rather than a drive
letter which stops the 24 drive letter limitation (B,D-Z).

Thanks,
Symon Perriman
Program Manager
Clustering & HA

"Binu" wrote:

> Hi,
>
> I have a typical issue on our Win2k3 cluster server..It was a two node
> cluster and after one patch instalation on one of the node, it failed to
> rejoin the cluster. While troubleshooting it, our team has evicted the node
> and after that thye failed to add it back to cluster. At present the cluster
> is working n one node and we have rebuilded the node which was failing. When
> we try to add it to cluster, again it fails to find quorum drive. This is a
> SAN drive and we are using MS iSCSI initiator. I can see th efollowing error
> in log file:
>
> There is not a "friendly name" for the physical disk "PHYSICALDRIVE2".
> (hr=00000000, {05AA0768-5F49-49CD-AFDC-96F9D51802D4},
> {00000000-0000-0000-0000-000000000000}, 1, 1, 1), (null)
>
> like this I can see for all SAN drives..we tried to install a fresh cluster
> in the newly built server and it was successfull(after we have evicted the
> cluster from the only one working node). Then we tried to add the node which
> was working fine earlier, still we receive the same error. Our experts are
> saying that the issue with SAn drives..becos, in disk management of passive
> node, they are unable to see the drive letter..What they says is it should e
> there in disk management. Instead we can see the drive without drive letter
> and is not accessible..
>
> Any ideas how can we resolve this?