F29: UNEXPECTED DSCR ERROR H'2B (STATE <8> / <:A1H1G:>)

[lhiraman]

How is everyone? Does anyone know how to fix this error?

I already tried dea-dssm: a1,1;
act-dssm:a1,1;

 

[sbcsu]

Hi,
What do you get when you type
REG-DDSM;

 

[lhiraman]

REG-DDSM;
H500: AMO DDSM STARTED
ADD-DCSM:A1,1,HD,"STDH5";
ADD-DASM:A1,1,7200&1600&2400&1120&32767&7200&
9868,4096&4096&4096&4096&4096&4096&4096;
ADD-DLSM:A1,1,E,"DS:"
;
ADD-DLSM:A1,1,F,"BDA:"&"BD:"&":TMD:"&"AS:"&":AMD:"&
"MP:";
ADD-DLSM:A1,1,G,":CGD:"
;
ADD-DLSM:A1,1,H,"MS:"&"SY:"
;
ADD-DLSM:A1,1,I,":SCR:"
;
ADD-DLSM:A1,1,J,":GLA:"
;
ADD-DLSM:A1,1,K,"IAG:"
;
ADD-DCSM:A1,6,HD,"CF2G0";
ADD-DASM:A1,6,7200&1600&2400&1120&18940
,4096&4096&4096&4096&4096;
ADD-DLSM:A1,6,E,"DS:"
;
ADD-DLSM:A1,6,F,"BDA:"&"BD:"&":TMD:"&"AS:"&":AMD:"&
"MP:";
ADD-DLSM:A1,6,G,":CGD:"
;
ADD-DLSM:A1,6,H,"MS:"&"SY:"
;
ADD-DLSM:A1,6,I,":MOD-SCR:"
;

AMO-DDSM -111 DISK STATUS
REGENERATE COMPLETED;

 

[sbcsu]

Looks OK
can you

CHA-FUNCT:REGIN=Y;
DISPLAY-DDSM:UNIT=A1,TYPE=HD,CNO=1;
DISPLAY-DDSM:UNIT=A1,TYPE=C,CNO=1;
DISPLAY-DDSM:UNIT=A1,TYPE=B,CNO=1;


Thanks

 

[lhiraman]

Here is what was returned. The defect portion is scary.


CHA-FUNCT:REGIN=Y;
CHA-FUNCT:REGIN=Y;
H500: AMO FUNCT STARTED

AMO-FUNCT-111 SYSTEM SWITCHES
CHANGE COMPLETED;

<DISPLAY-DDSM:UNIT=A1,TYPE=HD,CNO=1;
DISPLAY-DDSM:UNIT=A1,TYPE=HD,CNO=1;
H500: AMO DDSM STARTED
CONTROLLER: <1>
PARTITION TABLE:

+------+---------------+----------+----------+----------+-----------------+
|SYSTEM| SYSTEM NAME | FIRST | LAST |NUMBER OF | SIZE |
| ID | | SECTOR | SECTOR | SECTORS | (MB) | (64KB) |
+------+---------------+----------+----------+----------+--------+--------+
| H'62 |RMX BOOT |H' 0|H' 7995EF|H' 7995F0| 3890| 62251|
| H'12 |UNIXWARE |H' 7995F0|H' 7ACFB4|H' 139C5| 39| 627|
| H'63 |UNIXWARE |H' 7ACFB5|H' 69DDD7D|H' 6230DC9| 50273| 804379|
| H'63 |UNIXWARE |H' 69DDD7E|H' 6FBC03C|H' 5DE2BF| 3004| 48069|
+------+---------------+----------+----------+----------+--------+--------+

ADMINISTRATION AREA DATA:

+-----+---------+----------+----------+-----+------------+------+------+-------+
|MNEMO| LOGICAL | FIRST | LAST |AREA | SIZE | PAIR |INCONS| USED |
|NAME | NAME | SECTOR | SECTOR |GRAN |(MB) |(64KB)|ALLOC.| | BY |
+-----+---------+----------+----------+-----+-----+------+------+------+-------+
|A1H1A| |H' 0|H' 13F| 512| 0| 2| NO| NO | NONE |
|A1H1E| DS:|H' 140|H' E113F| 4096| 450| 7200| NO| NO | RMX |
|A1H1F| BDA:|H' E1140|H' 11313F| 4096| 100| 1600| NO| NO | RMX |
|A1H1G| :CGD:|H' 113140|H' 15E13F| 4096| 150| 2400| NO| NO | NONE |
|A1H1H| MS:|H' 15E140|H' 18113F| 4096| 70| 1120| NO| NO | NONE |
|A1H1I| :SCR:|H' 181140|H' 5810BF| 4096| 2047| 32767| NO| NO | RMX |
|A1H1J| :GLA:|H' 5810C0|H' 6620BF| 4096| 450| 7200| NO| NO | RMX |
|A1H1K| IAG:|H' 6620C0|H' 7966BF| 4096| 616| 9868| NO| NO | RMX |
+-----+---------+----------+----------+-----+-----+------+------+------+-------+

NAMED-FILE-STRUCTURE DATA:

+----------------------------------------------+
| A1H1A NOT ACTIVE: DATA CANNOT BE DETERMINED |
+----------------------------------------------+
| A1H1E NOT ACTIVE: DATA CANNOT BE DETERMINED |
+----------------------------------------------+
| A1H1F NOT ACTIVE: DATA CANNOT BE DETERMINED |
+----------------------------------------------+
| A1H1G NOT ACTIVE: DATA CANNOT BE DETERMINED |
+----------------------------------------------+
| A1H1H NOT ACTIVE: DATA CANNOT BE DETERMINED |
+----------------------------------------------+
| A1H1I NOT ACTIVE: DATA CANNOT BE DETERMINED |
+----------------------------------------------+
| A1H1J NOT ACTIVE: DATA CANNOT BE DETERMINED |
+----------------------------------------------+
| A1H1K NOT ACTIVE: DATA CANNOT BE DETERMINED |
+----------------------------------------------+

AMO-DDSM -111 DISK STATUS
DISPLAY COMPLETED;


SPLAY COMPLETED;
<DISPLAY-DDSM:UNIT=A1,TYPE=C,CNO=1;
DISPLAY-DDSM:UNIT=A1,TYPE=C,CNO=1;
H500: AMO DDSM STARTED
CONTROLLER: 1 IS ACTIVE LOAD DEVICE, LOAD AREA IS: DS:
TYPE: HD SS-NO : <STDH5> SIZE : 3884 MB ( 62158*64KB) GRAN : 512
NON-RMX PARTITIONS:
SYSTEM ID SYSTEM NAME BEGIN / NO OF SECTOR(S) SIZE
H'12 UNIXWARE H' 7995F0 H' 139C5 39 MB ( 627*64KB)
H'63 UNIXWARE H' 7ACFB5 H' 6230DC9 50273 MB ( 804379*64KB)
H'63 UNIXWARE H' 69DDD7E H' 5DE2BF 3004 MB ( 48069*64KB)
AREA: A NAME : A1H1A STATUS : D E F E C T
AREA-SZ: 0 MB (2 *64KB) A-GRAN: 512
AREA: E NAME : A1H1E STATUS : D E F E C T
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
DS:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 450 MB (7200 *64KB) A-GRAN: 4096
AREA: F NAME : A1H1F STATUS : D E F E C T
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
BDA:,BD:,:TMD:,AS:,:AMD:,MP:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 100 MB (1600 *64KB) A-GRAN: 4096
AREA: G NAME : A1H1G STATUS : D E F E C T
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:CGD:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 150 MB (2400 *64KB) A-GRAN: 4096
AREA: H NAME : A1H1H STATUS : D E F E C T
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
MS:,SY:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 70 MB (1120 *64KB) A-GRAN: 4096
AREA: I NAME : A1H1I STATUS : D E F E C T
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:SCR:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 2047 MB (32767*64KB) A-GRAN: 4096
AREA: J NAME : A1H1J STATUS : D E F E C T
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:GLA:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 450 MB (7200 *64KB) A-GRAN: 4096
AREA: K NAME : A1H1K STATUS : D E F E C T
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
IAG:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 616 MB (9868 *64KB) A-GRAN: 4096

AMO-DDSM -111 DISK STATUS
DISPLAY COMPLETED;

<DISPLAY-DDSM:UNIT=A1,TYPE=B,CNO=1;
DISPLAY-DDSM:UNIT=A1,TYPE=B,CNO=1;
H500: AMO DDSM STARTED
CONTROLLER: 1 IS ACTIVE LOAD DEVICE, LOAD AREA IS: DS:
TYPE: HD SS-NO : <STDH5> SIZE : 3884 MB ( 62158*64KB) GRAN : 512
NON-RMX PARTITIONS:
SYSTEM ID SYSTEM NAME BEGIN / NO OF SECTOR(S) SIZE
H'12 UNIXWARE H' 7995F0 H' 139C5 39 MB ( 627*64KB)
H'63 UNIXWARE H' 7ACFB5 H' 6230DC9 50273 MB ( 804379*64KB)
H'63 UNIXWARE H' 69DDD7E H' 5DE2BF 3004 MB ( 48069*64KB)
AREA: A NAME : A1H1A STATUS : D E F E C T
AREA-SZ: 0 MB (2 *64KB) A-GRAN: 512
AREA: E NAME : A1H1E STATUS : D E F E C T
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
DS:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 450 MB (7200 *64KB) A-GRAN: 4096
AREA: F NAME : A1H1F STATUS : D E F E C T
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
BDA:,BD:,:TMD:,AS:,:AMD:,MP:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 100 MB (1600 *64KB) A-GRAN: 4096
AREA: G NAME : A1H1G STATUS : D E F E C T
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:CGD:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 150 MB (2400 *64KB) A-GRAN: 4096
AREA: H NAME : A1H1H STATUS : D E F E C T
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
MS:,SY:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 70 MB (1120 *64KB) A-GRAN: 4096
AREA: I NAME : A1H1I STATUS : D E F E C T
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:SCR:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 2047 MB (32767*64KB) A-GRAN: 4096
AREA: J NAME : A1H1J STATUS : D E F E C T
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:GLA:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 450 MB (7200 *64KB) A-GRAN: 4096
AREA: K NAME : A1H1K STATUS : D E F E C T
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
IAG:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 616 MB (9868 *64KB) A-GRAN: 4096

AMO-DDSM -111 DISK STATUS
DISPLAY COMPLETED;

 

[sbcsu]

As you can see - all of the hard disk areas are defective.

Do NOT turn off the system as it may not come back.

You will have to get your next level above to create a new hard drive.

If this is the same system that was giving you problems before then a hard drive change is now necessary.


DSCR errors are normally 'fixed' by changing out the hard disk.

They MIGHT clear if you reload the system but then again they MIGHT NOT....

If this is on a customer site it would be best to contact your next level of support.

 

[lhiraman]

Sbcsu:

Thank you. I opened a ticket with Siemens yesterday. They shipped me an A1 board with a Hard Drive attached.

I guess Siemens partners with outside companies. The tech called me last night and said he will be here tomorrow night. I hope that we don't lost any data (stations configurations, etc.). He said that he is working with BLS...I am just curious what process do they follow for something like this?

Would you know?

 

[sbcsu]

Yes, (unfortunately )

I don't know what procedure your company will use.

This is what I do.

Get a full REGEN from the system or start it up from a backup medium like Magneto Optical or Flash Disk and then get a FULL REGEN.

Create the Hard disk with the latest version of software for your level of equipment.

Copy the REGEN on to it.

Add in latest Loadware, Patch Packet upgrade and Unix Hot Fixes, Unix backup/Restore.

Bring it to site, copy out the last backup from the system if possible and do a database compare to see if anything is missing.

Shut down old hard drive - startup on new hard drive.
Test circuits.

You will have to discuss with the tech - you need to know what time/date the backup is being restored from - what data if any you will be missing.
Also if you have been upgraded to the latest release including patch packets.

 

[lhiraman]

Well, I know that our last backup connist of the following files:

150 Opening ASCII mode data connection.
06-24-13 08:15PM 388 files.tbl
06-24-13 08:15PM 407 InfoFile
06-24-13 08:13PM 202649600 RMX.HBR_RMX.p
06-24-13 08:13PM 69 RMX.HBR_RMX.pointers
06-24-13 08:13PM 31 RMX.HBR_RMX.version.02-01-01
06-24-13 08:13PM 18 RMX.SWA_RMX.pointers
06-24-13 08:13PM 18 RMX.SWA_RMX.version.02-01-01
06-24-13 08:15PM 3 set_ok
06-24-13 08:15PM 1073725440 UNIX.SWA.p
06-24-13 08:15PM 264837120 UNIX.SWA.p.P002
06-24-13 08:13PM 257 UNIX.SWA.pointers
06-24-13 08:13PM 18 UNIX.SWA.version.02-01-01
226 Transfer complete.

We have DR back from 6/16/13 and a AP from 6/1/13.

Hopefully they keep us at v5 and not upgrade us to V6.

 

[donb01]

V6 requires major changes. I don't think they will do that to fix a problem. They would probably prefer to get you stable on V5 and if they would decide to go to V6 they would do it from a stable system.

 

[sbcsu]

I meant that they should update you to the latest release of V5.
As donb01 said it is unlikely that you would be upgraded to V6 as it requires other hardware changes like shelf interface cards etc.

 

[lhiraman]

yeah the tech confirmed it will be V5. Ok I guess I have to hope for the best tomorrow.