Product

• Brisque 3.0.38
• Brisque 4.0.97

Platform

Brisque 3.0.38

• E30 - Victory
• 43P-140 Tiger 1
• 43P-150 Tiger 2
• F50 - Wildcat (2 and 4 CPUs)

Brisque 4.0.97

• E30 - Victory
• 43P-140 Tiger 1
• 43P-150 Tiger 2
• F50 - Wildcat (2 and 4 CPUs)
• 44P-170 Hammerhead
• 6F1 Condor (2, 4, and 6 CPUs)

Operating system

IBM AIX 4.2.1 or IBM AIX 4.3.3

Background

The procedure for replacing a failed user disk (dataVolume) on the Brisque is different from the procedure for installing a new disk. All attempts to use SciSmit procedures for adding the replacement disk will fail as svg1 is already being defined.

Procedure

For the replacement disk to work:

1. Export the disk.
2. Configure the new disk so that the export works properly.
3. Export it again.
4. Configure the new disk.

In the prompt type:

Note: The following is for replacing the hdisk1. For all other hdisks, type the appropriate hdisk# at the prompt.

• SciSmit >> Export a Disk - hdisk1
• Unix >> exportvg svg1
  This removes svg1. If you don't do this, all procedures added to the new hdisk1 fail because svg1 already exists.
• UNIX >> cfgmgr
  This adds the hdisk1 since the export disk deleted it.
• SciSmit >> Configure new disk - hdisk1
  The mount will fail.
• SciSmit >> Export a Disk - hdisk1
  This will fix the LVM log problems.
• UNIX >> cfgmgr
  This will add the hdisk1.
• SciSmit >> Configure new disk - hdisk1

Technical contact(s)

Content owner: Eli Cohen

Submitted by

Mark Anderson

Date submitted

27 Jul 1997