Issue with storage while adding node to cluster

-

greetings all,

i started 2-node windows 2012 failover cluster consisting of node1 , node2. migrate windows server 2012 r2 created node3 , installed single node failover cluster. used copy roles migrate vms , corresponding csvs new cluster , things work great. next moved remaining vms node1 on the original cluster , evicted node2 original cluster. far good. installed clean copy of server 2012 r2 onto node2 , attempted add new cluster , that's when ran trouble. seems though shared storage on dell md3000 (i know not supported) not being seen correctly following when validating storage:

node2.adataconcepts.local
row disk number disk signature vpd page 83h identifier vpd serial number model bus type stack type scsi address adapter eligible validation disk characteristics
0 0 2b4cd3d6 19ebf3b700000000001517ffff0aeb84 boot intel raid 1 volume raid stor port 1:0:1:0 intel(r) desktop/workstation/server express chipset sata raid controller false disk boot volume. disk system volume. disk used paging files. disk used memory dump files. disk bus type not support clustering. disk on system bus. disk partition style mbr. disk type basic. 
1 1 e4f31a08 60019b9000b68362000064bd5387f98e 71k002p  dell md3000 multi-path disk device sas stor port 0:0:15:0 microsoft multi-path bus driver true disk partition style mbr. disk type basic. disk uses microsoft multipath i/o (mpio). 
2 2 5be62253 60019b9000b683620000638651d2eb2d 71k002p  dell md3000 multi-path disk device sas stor port 0:0:15:6 microsoft multi-path bus driver true disk partition style mbr. disk type basic. disk uses microsoft multipath i/o (mpio). 
3 3 5be62245 60019b9000b6933f00000b9351d2e686 71k002p  dell md3000 multi-path disk device sas stor port 0:0:15:7 microsoft multi-path bus driver true disk partition style mbr. disk type basic. disk uses microsoft multipath i/o (mpio). 
4 4 c1100e74 60019b9000b6933f00000be05363b77f 71k002p  dell md3000 multi-path disk device sas stor port 0:0:15:11 microsoft multi-path bus driver true disk partition style mbr. disk type basic. disk uses microsoft multipath i/o (mpio). 
5 5 6420dd00 60019b9000b68362000064395363c60a 71k002p  dell md3000 multi-path disk device sas stor port 0:0:15:12 microsoft multi-path bus driver true disk partition style mbr. disk type basic. disk uses microsoft multipath i/o (mpio). 
6 6 2cf2c0bc 60019b9000b6933f00000bff536c698e 71k002p  dell md3000 multi-path disk device sas stor port 0:0:15:13 microsoft multi-path bus driver true disk partition style mbr. disk type basic. disk uses microsoft multipath i/o (mpio). 

node3.adataconcepts.local
row disk number disk signature vpd page 83h identifier vpd serial number model bus type stack type scsi address adapter eligible validation disk characteristics
0 0 eb58d775 759eac7a01000000001517ffff0aeb84 boot intel raid 1 volume raid stor port 1:0:1:0 intel(r) desktop/workstation/server express chipset sata raid controller false disk boot volume. disk system volume. disk used paging files. disk used memory dump files. disk bus type not support clustering. disk on system bus. disk partition style mbr. disk type basic. 
1 1 e4f31a08 60019b9000b68362000064bd5387f98e 71k003o  dell md3000 multi-path disk device sas stor port 0:0:2:0 microsoft multi-path bus driver true disk clustered. disk partition style mbr. disk type basic. disk uses microsoft multipath i/o (mpio). 
2 2 5be62253 60019b9000b683620000638651d2eb2d 71k003o  dell md3000 multi-path disk device sas stor port 0:0:2:6 microsoft multi-path bus driver true disk clustered. disk partition style mbr. disk type basic. disk uses microsoft multipath i/o (mpio). 
3 3 5be62245 60019b9000b6933f00000b9351d2e686 71k003o  dell md3000 multi-path disk device sas stor port 0:0:2:7 microsoft multi-path bus driver true disk clustered. disk partition style mbr. disk type basic. disk uses microsoft multipath i/o (mpio). 
4 4 c1100e74 60019b9000b6933f00000be05363b77f 71k003o  dell md3000 multi-path disk device sas stor port 0:0:2:11 microsoft multi-path bus driver true disk clustered. disk partition style mbr. disk type basic. disk uses microsoft multipath i/o (mpio). 
5 5 6420dd00 60019b9000b68362000064395363c60a 71k003o  dell md3000 multi-path disk device sas stor port 0:0:2:12 microsoft multi-path bus driver true disk clustered. disk partition style mbr. disk type basic. disk uses microsoft multipath i/o (mpio). 
6 6 2cf2c0bc 60019b9000b6933f00000bff536c698e 71k003o  dell md3000 multi-path disk device sas stor port 0:0:2:13 microsoft multi-path bus driver true disk clustered. disk partition style mbr. disk type basic. disk uses microsoft multipath i/o (mpio). 

list disks validated
description: list disks validated cluster compatibility.
start: 5/30/2014 5:07:08 pm.
physical disk e4f31a08 visible 1 node , not tested. validation requires disk visible @ least 2 nodes. disk reported visible @ node: node2.adataconcepts.local
physical disk 2cf2c0bc visible 1 node , not tested. validation requires disk visible @ least 2 nodes. disk reported visible @ node: node3.adataconcepts.local
physical disk 6420dd00 visible 1 node , not tested. validation requires disk visible @ least 2 nodes. disk reported visible @ node: node3.adataconcepts.local
physical disk c1100e74 visible 1 node , not tested. validation requires disk visible @ least 2 nodes. disk reported visible @ node: node3.adataconcepts.local
physical disk 5be62245 visible 1 node , not tested. validation requires disk visible @ least 2 nodes. disk reported visible @ node: node3.adataconcepts.local
physical disk 5be62253 visible 1 node , not tested. validation requires disk visible @ least 2 nodes. disk reported visible @ node: node3.adataconcepts.local
physical disk e4f31a08 visible 1 node , not tested. validation requires disk visible @ least 2 nodes. disk reported visible @ node: node3.adataconcepts.local
physical disk 2cf2c0bc visible 1 node , not tested. validation requires disk visible @ least 2 nodes. disk reported visible @ node: node2.adataconcepts.local
physical disk 6420dd00 visible 1 node , not tested. validation requires disk visible @ least 2 nodes. disk reported visible @ node: node2.adataconcepts.local
physical disk c1100e74 visible 1 node , not tested. validation requires disk visible @ least 2 nodes. disk reported visible @ node: node2.adataconcepts.local
physical disk 5be62245 visible 1 node , not tested. validation requires disk visible @ least 2 nodes. disk reported visible @ node: node2.adataconcepts.local
physical disk 5be62253 visible 1 node , not tested. validation requires disk visible @ least 2 nodes. disk reported visible @ node: node2.adataconcepts.local
no disks found on perform cluster validation tests. correct this, review following possible causes:
* disks clustered , online in cluster. when testing working cluster, ensure disks want test offline in cluster.
* disks unsuitable clustering. boot volumes, system volumes, disks used paging or dump files, etc., examples of disks unsuitable clustering.
* review "list disks" test. ensure disks want test unmasked, is, masking or zoning not prevent access disks. if disks seem unmasked or zoned correctly not tested, try restarting servers before running validation tests again.
* cluster not use shared storage. cluster must use hardware solution based either on shared storage or on replication between nodes. if solution based on replication between nodes, not need rerun storage tests. instead, work provider of replication solution ensure replicated copies of cluster configuration database can maintained across nodes.
* disks online in cluster , in maintenance mode.
no disks found on perform cluster validation tests.

    can shed light on why though disk signatures same on both nodes 2 nodes don't seem acknowledge in fact looking @ same disks? appreciated!

    regards,

    scott

scott


hello scott,

please take vms offline , can take out csvs cluster , unmap luns both nodes {node2 , 3}.

add node 2 into new cluster first , add csv back.

regards,

yuvi



Windows Server  >  High Availability (Clustering)



Comments

Post a Comment

Popular posts from this blog

DCOM received error "2147746132" from...

-
hi everybody, i have dc (my windows essentials 2012 server) , windows 2012 server in network.  the windows server 2012 inside domain. on server, got "non stopping" error says in event logs : ===> dcom received error "2147746132" fromd computer xxxx(my dc computer) while server trying activation : {6df8cb71-153b-4c66-8fc4-e59301b8011b} it never stops, got 11000+ new events :s i found : http://support.microsoft.com/kb/971153/fr i'm not sure should ? does got idea ? matthieu. hi, please try solution mentioned in below link: http://www.eventid.net/display-eventid-10006-source-dcom-eventno-272-phase-1.htm regards, cicely Windows Server  >  Windows Server 2012 General ...
Read more

DFSR RPC replication errors 5014 1726 with large files over VPN

-
i have similar issue ryan in reply http://social.technet.microsoft.com/forums/en-gb/winserverfiles/thread/6d49fd71-2236-4fcb-9763-bf1c03459ee8 cited below. start additional thread here because other 1 related windows server 2003 (r2) , i'm (as ryan) on windows 2008 r2 x64. here first of post ryan: i've got same problem on 2008 r2 dfsr server.  the spoke server has 2x intel 1 gigb on-board nics in active/standby teamed configuration. the hub server (running on vmware using 10gbit vmnet3 nic driver) logs dfsr event 5014 every 2-15mins (usually around 5mins). the spoke server not log event. replication running slowly. initial sync/replication. had re-configure replication folder because of lost dfsr database on spoke server.  could teamed nic on spoke causing error on host? a note: last time did initial sync on folder processed @ 30k files , hour. time it's doing few hundred and hour. another note: hub server has several replication groups , conne...
Read more

ADFS 3.0 Event ID 4625 | An Error occurred During Logon | Status: 0xC000035B

-
we're getting these random errors on our adfs security logs, how can track down generating them? an account failed log on. subject: security id: null sid account name: - account domain: - logon id: 0x0 logon type: 3 account logon failed: security id: null sid account name: account domain: failure information: failure reason: an error occured during logon. status: 0xc000035b sub status: 0x0 process information: caller process id: 0x0 caller process name: - network information: workstation name: - source network address: - source port: - detailed authentication information: logon process: kerberos authentication package: kerberos transited services: - package name (ntlm only): - key length: 0 event generated when logon request fails. generated on computer access attempted. subject fields indicate account on local system requested logon. commonly service such server service, or local process such ...
Read more