[Info-vax] Using MSA$UTIL to online maintain logical disk units?

[Neil Rieck]

On Wednesday, January 17, 2018 at 7:29:03 AM UTC-5, Rod Regier wrote:
> I'm trying to use MSA$UTIL to perform maintenance action on a failed JBOD unit.
> Config is V/I64 (remastered) 8.4 w/patches, RX2600, SA6402 controller and front-access disks.
> Unit 0 is a RAID mirror set
> Unit 1 is a JBOD
> 
> 36G Disk of JBOD failed, replacement hot-swapped into slot.
> 
> n.b. Next time around I'll try SCAN ALL and ACCEPT UNIT 1,
>      but that ship has already sailed.
> 
> It would appear I'll be forced to recreate the UNIT offline,
> any other online option ideas?
> 
> $ mcr msa$util
> MSA> set controller
> MSA> sho controller
> 
> Adapter: _PKC0: (DEFAULT)
>    SA6400           (c) HP                         P57820PXQRG2OE Software 2.84
>    SCSI_VERSION = X3.131:1994 (SCSI-2)
> Supported Redundancy Mode:
>    Not currently Redundant
>    Current Role:            Active
> Cache:
>    64 megabyte read cache   64 megabyte write cache
>    Cache is enabled and Cache is GOOD.
>    No unflushed data in cache.
> Battery:
>    Battery is fully charged.
> Controller Mode:
>    Controller is in HBA Mode.
> 
> MSA> sho unit
> 
> Unit 0:
> In PDLA mode, Unit 0 is Lun 0.
> Cache status      : enabled
> Max Boot Partition: Unknown
> Volume status     : VOLUME OK
>  2 Data Disk(s) used by lun 0:
>    Disk 0: Partition 0; (SCSI bus 0, SCSI id 0)
>    Disk 102: Partition 0; (SCSI bus 1, SCSI id 2)
> Spare physical drives:
>    No spare drives are designated.
> Logical Volume Raid Level: RAID 1.  Mirroring
>                            stripe_size=128.0KB
> Logical Volume Capacity : 68.36 [73.40] GB
> 
> Unit 1:
> In PDLA mode, Unit 1 is Lun 1.
> Cache status      : enabled
> Max Boot Partition: Unknown
> Volume status     : VOLUME failed
>  1 Data Disk(s) used by lun 1:
>    Disk 1: Partition 0; (SCSI bus 0, SCSI id 1)
> Spare physical drives:
>    No spare drives are designated.
> Logical Volume Raid Level: RAID 0 or JBOD. No fault tolerance
>                            stripe_size=128.0KB
> Logical Volume Capacity : 33.91 [36.41] GB
> 
> MSA> sho disk
> 
>  Parallel SCSI device                                            [Disk]
>  Disk 0: SCSI bus 0 id 0  size 68.36 [73.40] GB
>   Disk 000, # 0, size 143363040 blocks, (68.36 [73.40] GB), Unit 0.
>   Disk 000, # 1, size 2418 blocks, (1.18 [1.24] MB), Unused.
> 
>  Parallel SCSI device                                            [Disk]
>  Disk 102: SCSI bus 1 id 2  size 68.36 [73.40] GB
>   Disk 102, # 0, size 143363040 blocks, (68.36 [73.40] GB), Unit 0.
>   Disk 102, # 1, size 2418 blocks, (1.18 [1.24] MB), Unused.
> 
> MSA> scan all
> 
> MSA> sho disk
> 
>  Parallel SCSI device                                            [Disk]
>  Disk 0: SCSI bus 0 id 0  size 68.36 [73.40] GB
>   Disk 000, # 0, size 143363040 blocks, (68.36 [73.40] GB), Unit 0.
>   Disk 000, # 1, size 2418 blocks, (1.18 [1.24] MB), Unused.
> 
>  Parallel SCSI device                                            [Disk]
>  Disk 1: SCSI bus 0 id 1  size 34.18 [36.70] GB
>   Disk 001, # 0, size 71122560 blocks, (33.91 [36.41] GB), Unit 1.
>   Disk 001, # 1, size 563724 blocks, (275.26 [288.63] MB), Unused.
> 
>  Parallel SCSI device                                            [Disk]
>  Disk 102: SCSI bus 1 id 2  size 68.36 [73.40] GB
>   Disk 102, # 0, size 143363040 blocks, (68.36 [73.40] GB), Unit 0.
>   Disk 102, # 1, size 2418 blocks, (1.18 [1.24] MB), Unused.
> 
> MSA> delete unit 1
> 
> All data on this Device will be lost. 
> Do you really want to delete it? (Y/N)[N]:y
> Unit deleted!
> 
> 
> MSA> add unit 1/jbod/disk=1
> set_configuration SCSI status = ff, ASC = 0, ASCQ = 0
> 
> SCSI status was: Reserved..
> Dump of CDB used:
> 27, Opcode 39 : BMIC write or no data transfer operation.
> 1, Logical Unit Number 1.
> 0, Command specific: 0.
> 0, Command specific: 0.
> 0, Command specific: 0.
> 0, Command specific: 0.
> 51, BMIC: Set Configuration.
> 2 0, Bytes to transfer = 512.
> 0, Reserved, must be 0.
> Adding or modification of Raid Unit failed.

While I don't have anything more to add to your post, I would be glad to see someone else respond with additional data. Something similar happened to me in November but there were so many things going on at the time that I didn't have time to play with the downed drive other than this:
http://neilrieck.net/docs/openvms_notes_itanium_diary.html#msa

Don't forget that the SAS utility goes hand-in-hand with the MSA utility. So until I have something more to rely on, I will continue my Friday walk-through of our computer room looking at the visual indicators :-)

Neil Rieck
Waterloo, Ontario, Canada.
http://neilrieck.net