Hi David,

Subsys 145 is Secondary Storage Manager (disk)

The SA 1740 is:

$5 ($47) nmdebug > =errmsg(#1740,#98)
'FILL_ALLOCATED_SEC_STORAGE - FILL_DISC returned an error.'
$6 ($47) nmdebug >

The SA 2052 is:

$4 ($47) nmdebug > = errmsg (#2052,#98)
'The system failed due to corruptions in either the secondary storage
maps,the 
file label or extent block informations for a file. This problem is very
likely
 caused by broken (disk or controller) hardware.'

During boot are there disks that did not mount?
 
Look at the paths that are not available after the msg "Entering - system
I/O configuration" and also look for any error messages after "Entering -
Mount all volumes" on the console before the system abort(s).

It could be an actual hardware problem or a drive or file may have been
corrupted during the power failure.

You might try a START NORECOVERY NOSYSSTART if all drives are mounting in
case it is a file that is bad (KSAM,MSG file, etc.).

If 'START NORECOVERY NOSYSSTART' allows the system to boot you can run an
FSCHECK.MPEXL.TELESUP with the 'checkall all' command to see if there are
file label problems.  Some of the output is pretty terse.

You should rebuild any MSG files and recover your KSAM files that may have
been open when the system failed with KSAMUTIL.  Once that is done you could
try the 'START NORECOVERY' again.

If it is a hw problem, obviously that will need to be corrected, followed by
a reinstall/restore from your last known good CSLT and backup tapes.

If it is a drive table corruption problem and the drives are physically OK,
then you are likely looking at a reinstall/restore from your last known good
CSLT and backup tapes.

If you can boot to ISL and use ODE to look at the system IO map that should
help (but you would need to know what devices were there when the system was
working)...


You will probably get more recommendations from the list depending on what
you find...


Thanks,

Gary



-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf
Of David M
Sent: Wednesday, June 11, 2008 10:38 AM
To: [log in to unmask]
Subject: [HP3000-L] Fw: system abort - need help, please

forgot to mention:
we are on 937 with version 5.5

----- Original Message ----- 
From: "David M" <[log in to unmask]>
To: "hp3000-l " <[log in to unmask]>
Sent: Wednesday, June 11, 2008 12:34 PM
Subject: system abort - need help, please


> Hi everybody,
> storms and subsequent power failure last night!
> the message on the console(when we came in this morning):
> 
> System abort 1740 from subsytem 107
> Secondary Status info = -35; subsys = 113
> System Halt 7, $06CC
> Blinking: FLT DEAD, FLT BF07, FLT 0106, FLT 02CC
> 
> Well, we rebooted (with Start) with the same result.
> We rebooted with Norecovery and the messages were a little different:
> 
> System abort 2052 from subsytem 145
> System Halt 7, $0804
> Blinking: FLT DEAD, FLT BF07, FLT 0108, FLT 0204
> 
> It seems, the booting process is going well, but just as the startup and 
> setcatalog are initiated the abort happens.
> 
> David Milstein
> Director of MIS
> CIS Marketing, Inc.
> 612 Corporate Way
> Valley Cottage, NY 10989
> 845.268.8600 x 116
> www.cismarketing.com 
>

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *