Solaris cluster scdidadm Inquiry on device failed.


 
Thread Tools Search this Thread
Operating Systems Solaris Solaris cluster scdidadm Inquiry on device failed.
# 1  
Old 10-08-2009
Solaris cluster scdidadm Inquiry on device failed.

Solaris 10, Solaris Cluser 3.2, two node cluster, all software installed succefully, all nodes join to the cluster
And on snod2 didn't recognize disks as a did devices and I can't make a quorum device.

Code:
snod1#/usr/cluster/bin/cluster status

=== Cluster Nodes ===

--- Node Status ---

Node Name                                       Status
---------                                       ------
snod1                                           Online
snod2                                           Online


=== Cluster Transport Paths ===

Endpoint1               Endpoint2               Status
---------               ---------               ------
snod1:bge1              snod2:iprb0             Path online


=== Cluster Quorum ===

--- Quorum Votes Summary ---

            Needed   Present   Possible
            ------   -------   --------
            1        1         1


--- Quorum Votes by Node ---

Node Name       Present       Possible       Status
---------       -------       --------       ------
snod1           1             1              Online
snod2           0             0              Online


=== Cluster Device Groups ===

--- Device Group Status ---

Device Group Name     Primary     Secondary     Status
-----------------     -------     ---------     ------


--- Spare, Inactive, and In Transition Nodes ---

Device Group Name   Spare Nodes   Inactive Nodes   In Transistion Nodes
-----------------   -----------   --------------   --------------------


--- Multi-owner Device Group Status ---

Device Group Name           Node Name           Status
-----------------           ---------           ------

=== Cluster Resource Groups ===

Group Name       Node Name       Suspended      State
----------       ---------       ---------      -----

=== Cluster Resources ===

Resource Name       Node Name       State       Status Message
-------------       ---------       -----       --------------

=== Cluster DID Devices ===

Device Instance               Node              Status
---------------               ----              ------
/dev/did/rdsk/d2              snod1             Ok

/dev/did/rdsk/d3              snod2             Fail

/dev/did/rdsk/d4              snod2             Fail

/dev/did/rdsk/d5              snod2             Fail

snod2#scdidadm -r
scdidadm:  Inquiry on device "/dev/rdsk/c1d0s2" failed.
scdidadm:  Inquiry on device "/dev/rdsk/c2d0s2" failed.
scdidadm:  Inquiry on device "/dev/rdsk/c0d0s2" failed.

snod2#scdidadm -L
1        snod1:/dev/rdsk/c0t0d0         /dev/did/rdsk/d1    
2        snod1:/dev/rdsk/c1t0d0         /dev/did/rdsk/d2    
3        snod2:/dev/rdsk/c1d0           /dev/did/rdsk/d3    
4        snod2:/dev/rdsk/c2d0           /dev/did/rdsk/d4    
5        snod2:/dev/rdsk/c0d0           /dev/did/rdsk/d5   

snod1#cat /etc/vfstab
#device device  mount   FS      fsck    mount   mount
#to     mount   to      fsck            point           type    pass    at boot options
#                      
fd      -       /dev/fd fd      -       no      -
/proc   -       /proc   proc    -       no      -
/dev/dsk/c1t0d0s1       -       -       swap    -       no      -
/dev/dsk/c1t0d0s0       /dev/rdsk/c1t0d0s0      /       ufs     1       no      -
/dev/dsk/c1t0d0s3       /dev/rdsk/c1t0d0s3      /usr    ufs     1       no      -
/dev/dsk/c1t0d0s4       /dev/rdsk/c1t0d0s4      /opt    ufs     2       yes     -
#/dev/dsk/c1t0d0s5      /dev/rdsk/c1t0d0s5      /globaldisk     ufs     2       yes     -
/devices        -       /devices        devfs   -       no      -
sharefs -       /etc/dfs/sharetab       sharefs -       no      -
ctfs    -       /system/contract        ctfs    -       no      -
objfs   -       /system/object  objfs   -       no      -
swap    -       /tmp    tmpfs   -       yes     -
/dev/did/dsk/d2s5 /dev/did/rdsk/d2s5 /global/.devices/node@1 ufs 2 no global

snod2#scdidadm -L
1        snod1:/dev/rdsk/c0t0d0         /dev/did/rdsk/d1    
2        snod1:/dev/rdsk/c1t0d0         /dev/did/rdsk/d2    
3        snod2:/dev/rdsk/c1d0           /dev/did/rdsk/d3    
4        snod2:/dev/rdsk/c2d0           /dev/did/rdsk/d4    
5        snod2:/dev/rdsk/c0d0           /dev/did/rdsk/d5    
snod2#cldev check  
snod2#cldev clear
^C
snod2#format
Searching for disks...done


AVAILABLE DISK SELECTIONS:
       0. c0d0 <DEFAULT cyl 30398 alt 2 hd 255 sec 63>
          /pci@0,0/pci8086,2847@1c,4/pci-ide@0/ide@1/cmdk@0,0
       1. c1d0 <DEFAULT cyl 30398 alt 2 hd 255 sec 63>
          /pci@0,0/pci-ide@1f,2/ide@0/cmdk@0,0
       2. c2d0 <ST325041-         6RYJWYC-0001-232.89GB>
          /pci@0,0/pci-ide@1f,2/ide@1/cmdk@0,0

I did on all nodes:
#cldev clear
#scdidadm -r
#devfsadm -Cvs

What should I do to make disks on snod2 recognize?
Any idea?

snod2#scdidadm -r
scdidadm: Inquiry on device "/dev/rdsk/c1d0s2" failed.
scdidadm: Inquiry on device "/dev/rdsk/c2d0s2" failed.
scdidadm: Inquiry on device "/dev/rdsk/c0d0s2" failed.

Last edited by Uran; 10-09-2009 at 04:12 AM..
# 2  
Old 10-08-2009
To keep the forums high quality for all users, please take the time to format your posts correctly.

First of all, use Code Tags when you post any code or data samples so others can easily read your code. You can easily do this by highlighting your code and then clicking on the # in the editing menu. (You can also type code tags [code] and [/code] by hand.)

Second, avoid adding color or different fonts and font size to your posts. Selective use of color to highlight a single word or phrase can be useful at times, but using color, in general, makes the forums harder to read, especially bright colors like red.

Third, be careful when you cut-and-paste, edit any odd characters and make sure all links are working property.

Thank You.

The UNIX and Linux Forums
# 3  
Old 10-12-2009
Does anybody has any idea?
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. Solaris

Sun Server and Solaris 7 Inquiry

Greetings! Will be firing up the good ole pizza box, soon. Does anyone know if Solaris 7 is still okay to use? Last time I attempted was 2006. Thank you in advance, ControlTomato (6 Replies)
Discussion started by: ControlTomato
6 Replies

2. Solaris

Solaris Cluster Device Problem

I build up two node cluster (node1, node2) in virtualbox. For these two nodes I add 5 shared disk. (Also each node have own OS disk). 1 shared disk for vtoc 2 shared disk for NFS resource group 2 shared disk for WEB resource group When I finished my work; two nodes was ok and shared disk... (4 Replies)
Discussion started by: sonofsunra
4 Replies

3. Red Hat

PaceMaker Cluster Fence Device

I have 2 VM's setup with a shared VMware disk running RHEL 7.1 (just updated to 7.2 with yum update), and would like to know what is the easiest Fence device to implement for testing purposes. Apparently, I need a fence device before my IP resources will come online. I have the cluster... (1 Reply)
Discussion started by: mrmurdock
1 Replies

4. HP-UX

Failed to open tape device /dev/rmt/0mn:Device busy (errno = 16)

Hi, Unable to make tape backup, please help. /opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00 * Creating local directories for configuration files and archive. ======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery. (Mon... (4 Replies)
Discussion started by: anuragr
4 Replies

5. High Performance Computing

Building a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris

Provides a description of how to set up a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris. More... (0 Replies)
Discussion started by: Linux Bot
0 Replies

6. Red Hat

Redhat Cluster Fencing failed

Hello; I have 2 node Redhat Cluster (RHEL4 U4 and Cluster Suite) I'm using mc_data fiber channel switch for fencing when I want to fence manually using fence_mcdata -a x.x.x. -l xxx -p xxxx -n 5 -o disable following messages appears fencing node "test1" agent "fence_mcdata" reports:... (0 Replies)
Discussion started by: sakir19
0 Replies
Login or Register to Ask a Question