Update: DS10 missing devices in OS, but not SRM

From: Adam Preset (preset_at_isc.upenn.edu)
Date: 11/16/04

  • Next message: Subhash P: "GS1280 Installation" 
    Date: Tue, 16 Nov 2004 09:24:12 -0500
To: tru64-unix-managers@ornl.gov

    Folks,

    Apparently, hwmgr can see all the disks in question:

    # hwmgr -show scsi

            SCSI DEVICE DEVICE DRIVER NUM DEVICE FIRST
     HWID: DEVICEID HOSTNAME TYPE SUBTYPE OWNER PATH FILE VALID PATH
    -------------------------------------------------------------------------
       46: 0 cdrom none 0 1 cdrom0 [0/0/0]
       47: 1 disk none 2 1 dsk0 [2/0/0]
       48: 2 disk none 2 1 dsk1 [2/1/0]
       49: 3 disk none 0 1 (null)
       50: 4 disk none 0 1 (null)
       51: 5 disk none 2 1 dsk4 [3/0/0]
       52: 6 disk none 2 1 dsk5 [3/1/0]
       53: 7 disk none 0 1 (null)
       54: 8 disk none 0 1 (null)

    However, it seems to have lost track of the fact that HWID 49 is dsk2, and
    so on.

    One of the "good" disks appears to be registered ...

    # hwmgr -show component -id 48

     HWID: HOSTNAME FLAGS SERVICE COMPONENT NAME
    -----------------------------------------------
       48: rcd-- iomap SCSI-WWID:03100030:"RZ2DD-LS (C)
    DECSEAGATE ST39102LC LJE50135"

    ... while the ones I can't use are not registered:

    # hwmgr -show component -id 49

     HWID: HOSTNAME FLAGS SERVICE COMPONENT NAME
    -----------------------------------------------
       49: -cd-- iomap SCSI-WWID:03100030:"RZ2ED-LS (C) DECSEAGATE ST11820LC LKF71113"

    Is there a way for me to register this device somehow, or reassociate it
    with the right Unix device file? I've tried deleting the component like so:

    # hwmgr -delete component -id 49
    hwmgr: Delete operation was successful

    Following a reboot, the device still doesn't come back.

    # hwmgr -show scsi

            SCSI DEVICE DEVICE DRIVER NUM DEVICE FIRST
     HWID: DEVICEID HOSTNAME TYPE SUBTYPE OWNER PATH FILE VALID PATH
    -------------------------------------------------------------------------
        0: 3 disk none 0 1 (null)
       46: 0 cdrom none 0 1 cdrom0 [0/0/0]
       47: 1 disk none 2 1 dsk0 [2/0/0]
       48: 2 disk none 2 1 dsk1 [2/1/0]
       50: 4 disk none 0 1 (null)
       51: 5 disk none 2 1 dsk4 [3/0/0]
       52: 6 disk none 2 1 dsk5 [3/1/0]
       53: 7 disk none 0 1 (null)
       54: 8 disk none 0 1 (null)

    Is there a way to go about manually registering a device and specifying the
    device file and path?

    Cheers,
    Adam

  • Next message: Subhash P: "GS1280 Installation"

    Relevant Pages

    • problem with a disk
      ... DEVICEID HOSTNAME TYPE SUBTYPE OWNER PATH FILE VALID PATH ...
      (Tru64-UNIX-Managers)
    • Need help fixing possibly corrupt hardware database
      ... After loading a tape into the drive, I issued an mt seod to skip to end of data on the tape. ... Below is information I got from hwmgr and dsfmgr: ... DEVICEID HOSTNAME TYPE SUBTYPE OWNER PATH FILE VALID PATH ...
      (Tru64-UNIX-Managers)
    • SUMMARY : Replacement of tape TZ87
      ... DEVICEID HOSTNAME TYPE SUBTYPE OWNER PATH FILE VALID PATH ... Tape 0 and tape2 were already present, the replaced tape was tape1 on ... hwmgr delete -did 18 ...
      (Tru64-UNIX-Managers)
    • Replacement of tape TZ87
      ... We have replaced a faulty tape drive in our HSZ by a new one. ... I already tried several things with the commands hwmgr and dsfmgr, ... DEVICEID HOSTNAME TYPE SUBTYPE OWNER PATH FILE VALID PATH ...
      (Tru64-UNIX-Managers)
    • Access to device on SAN
      ... I performed a "hwmgr -show scsi -cat scsi_bus". ... On one cluster node, the ... DEVICEID HOSTNAME TYPE SUBTYPE OWNER PATH FILE VALID PATH ...
      (Tru64-UNIX-Managers)