Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

hipath4000 we can't acces to mod drive

Status
Not open for further replies.

illios

Technical User
Jul 29, 2006
33
TN
Dears
Hi,
we have a hipath4000 v1 and we have a problem to acces to mo drive witch contain a backup system
when we try to activate the drive we have this
ACTIVATE-DSSM:UNIT=A1,CNO=6;
H500: AMO DSSM STARTED
F22: DEVICE <:A1H61:> IS NOT ACTIVATED BECAUSE OF DSCR ERROR H'2D


a DDSM display :

DISPLAY-DDSM:UNIT=A1;
H500: AMO DDSM STARTED
CONTROLLER: 1 IS ACTIVE LOAD DEVICE, LOAD AREA IS: :pDS:
TYPE: HD SS-NO : <M1383> SIZE : 1383 MB ( 22132*64KB) GRAN : 512
NON-RMX PARTITIONS:
SYSTEM ID SYSTEM NAME BEGIN / NO OF SECTOR(S) SIZE
H'12 UNIXWARE H' 2B6371 H' 139C5 39 MB ( 627*64KB)
H'63 UNIXWARE H' 2C9D36 H' 3D50522 31392 MB (502282*64KB)
H'63 UNIXWARE H' 401A258 H' 44E1D9 2204 MB ( 35267*64KB)
AREA: A NAME : A1H1A STATUS : I N S E R V I C E
AREA-SZ: 0 MB (2 *64KB) A-GRAN: 512
AREA: E NAME : A1H1E STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:pDS:
ACTIVATED LOGICAL NAMES:
:pDS:
AREA-SZ: 200 MB (3200 *64KB) A-GRAN: 4096
AREA: F NAME : A1H1F STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:DBDA:,:DBD:,:TMD:,:pAS:,:AMD:,:DMP:
ACTIVATED LOGICAL NAMES:
:DBDA:,:DBD:,:TMD:,:pAS:,:AMD:,:DMP:
AREA-SZ: 62 MB (992 *64KB) A-GRAN: 4096
AREA: G NAME : A1H1G STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:CGD:
ACTIVATED LOGICAL NAMES:
:CGD:
AREA-SZ: 35 MB (560 *64KB) A-GRAN: 4096
AREA: H NAME : A1H1H STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:DMS:
ACTIVATED LOGICAL NAMES:
:DMS:
AREA-SZ: 60 MB (960 *64KB) A-GRAN: 4096
AREA: I NAME : A1H1I STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:DSY:
ACTIVATED LOGICAL NAMES:
:DSY:
AREA-SZ: 10 MB (160 *64KB) A-GRAN: 4096
AREA: J NAME : A1H1J STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:GLA:
ACTIVATED LOGICAL NAMES:
:GLA:
AREA-SZ: 200 MB (3200 *64KB) A-GRAN: 4096
AREA: K NAME : A1H1K STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:SCR:
ACTIVATED LOGICAL NAMES:
:SCR:
AREA-SZ: 816 MB (13057*64KB) A-GRAN: 4096
CONTROLLER: 6
TYPE: HD SS-NO : <MO1G3> SIZE : 1183 MB ( 18932*64KB) GRAN : 2048
AREA: A NAME : A1H6A STATUS : B L O C K E D B Y A M O
AREA-SZ: 0 MB (2 *64KB) A-GRAN: 2048
AREA: E NAME : A1H6E STATUS : B L O C K E D B Y A M O
CONFIGURED LOGICAL NAMES:
:pDS:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 200 MB (3200 *64KB) A-GRAN: 4096
AREA: F NAME : A1H6F STATUS : B L O C K E D B Y A M O
CONFIGURED LOGICAL NAMES:
:DBDA:,:DBD:,:TMD:,:pAS:,:AMD:,:DMP:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 62 MB (992 *64KB) A-GRAN: 4096
AREA: G NAME : A1H6G STATUS : B L O C K E D B Y A M O
CONFIGURED LOGICAL NAMES:
:CGD:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 35 MB (560 *64KB) A-GRAN: 4096
AREA: H NAME : A1H6H STATUS : B L O C K E D B Y A M O
CONFIGURED LOGICAL NAMES:
:DMS:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 60 MB (960 *64KB) A-GRAN: 4096
AREA: I NAME : A1H6I STATUS : B L O C K E D B Y A M O
CONFIGURED LOGICAL NAMES:
:DSY:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 10 MB (160 *64KB) A-GRAN: 4096
AREA: J NAME : A1H6J STATUS : B L O C K E D B Y A M O
CONFIGURED LOGICAL NAMES:
:MOD-SCR:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 816 MB (13057*64KB) A-GRAN: 4096


WE can't made a backup operation to mod drive
why all partition are blocked by amo and how we can activate the drive
can any one have this problem ?
 
Hi.

First try with:
cha-dssm:a1,6;
Than:
act-dssm:a1,6;

If still not ok:
- either an ADP soft restart or a hardware reset of the MO module is needed
- for a hardware reset please shut down UW7, deactivate the devices (MO), remove and reinsert the MO module, and activate the device.
That way no ADP restart is required, but it has to be done on-site.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top