Major Number diffres from primary node and hence CRS is not getting started

[Amit K]

Hi All,

on of the server on which we are facing issues with Clusterware start up.

On investigation we have found that the Major Number of the disk differ on both the nodes and hence the CRS is unable to identify the links created (usning mknod) to the disks.

PFB the log:
Host 1
$ cd /dev/rdisk/
$ ls -l
total 0
crw-r----- 1 bin sys 22 0x000001 Jan 31 2008 disk46
crw-r----- 1 bin sys 22 0x000002 Jan 31 2008 disk47
crw-r----- 1 bin sys 22 0x000003 Jan 31 2008 disk48

host 2:
# cd /dev/rdisk/
# ls -l
total 0
crw-r----- 1 bin sys 21 0x000001 Jun 1 11:20 disk46
crw-r----- 1 bin sys 21 0x000002 Jun 1 11:20 disk47
crw-r----- 1 bin sys 21 0x000003 Jun 1 11:20 disk48

i had also checked ioscan output
On host 1 below are the disks under disk46

# ioscan -m dsf disk46
Persistent DSF Legacy DSF(s)
========================================
disk46 /dev/rdsk/c1t0d0
/dev/rdsk/c2t0d0
/dev/rdsk/c6t0d0
/dev/rdsk/c9t0d0

But on host2 where issue lies; first disk is diffrent from host 1 output.

ioscan -m dsf disk46
Persistent DSF Legacy DSF(s)
========================================
disk46 /dev/rdsk/c3t0d0
/dev/rdsk/c2t0d0
/dev/rdsk/c6t0d0
/dev/rdsk/c9t0d0

is anything related to this for Major number change?

can anybody help me on this?

Thanks

Amit K