Fixing Solaris Cluster device ID (DID) mismatches

I had to replace a disk in one of my cluster nodes, and was greeted with the following message once the disk was swapped and I checked the devices for consistency:

$ cldevice check

cldevice:  (C894318) Device ID "snode2:/dev/rdsk/c1t0d0" does not match physical device ID for "d5".
Warning: Device "snode2:/dev/rdsk/c1t0d0" might have been replaced.



To fix this issue, I used the cldevice utilities repair option:

$ cldevice repair
Updating shared devices on node 1
Updating shared devices on node 2


Once the repair operation updated the devids, cldevice ran cleanly:

$ cldevice check

Niiiiiiiiice!

2 thoughts on “Fixing Solaris Cluster device ID (DID) mismatches”

  1. Hi

    sorry, this comment is not related with your post but I got a problem that I can-t find a solution and was thinking that maybe you could help me.

    I have a Sun Blade 100(ultraSparc-IIe) and I’m trying to install Debian on it, the problem is that after I do a “boot cdrom” and I press Enter to boot the installer and it shows this:
    ——-
    [ENTER – boot install]
    Boot:
    Allocated 8 Megs of memory at 0X40000000 for kernel
    Loading kernel version 2.6.26
    Loading initial ramdisk (4307828 bytes at 0xF802000 phys, 0x40C00000 virt)…
    Memory Adress not Aligned
    —–

    I have checked the MM to be right in place, also I have typed:

    ok setenv boot-device cdrom

    and when i restart it doesn’t work, it shows the same output

    hope you can help me, greetings!

  2. Hi,
    I did everything but the problem still not fixed

    root@node2 #cldevice repair
    root@node2 #cldevice check
    root@node2 #cldevice status

    === Cluster DID Devices ===

    Device Instance Node Status
    ————— —- ——
    /dev/did/rdsk/d1 node2 Ok

    /dev/did/rdsk/d2 node1 Ok

    /dev/did/rdsk/d4 node1 Fail
    node2 Fail

Leave a Reply

Your email address will not be published. Required fields are marked *