Craig writes:

> The ONLY thing running on the system, turbostore in a job, parallel to 3
> DLT8000's.
>
> After a reboot, I didn't even bring up the network, this has happened 3 times in
> a row
>
> I got the powerfail two out of three times, but I find it hard to believe it is
> a power issue.
> Maybe a bad tape drive, but not power.  Should a tape drive cause a system
> abort?
>
> Any ideas?  Any one?
>
> TIA,
>
> -Craig
>
>
>
> Environment
> N-Class 750/400
> full patched
> native fiber to an XP512
>
> Backing up to 3 DLT8000.
>
> ************
> 16:00/#J1/70/STORE OPERATION IS 15% COMPLETE
> 16:02/#J1/70/STORE OPERATION IS 16% COMPLETE
> 16:02/#J1/73/STORE/RESTORE ENCOUNTERED A POWERFAIL ON LDEV 28
>
>
> SYSTEM ABORT 1457 FROM SUBSYSTEM 102
> SECONDARY STATUS:  INFO = -300, SUBSYS = 107
> SYSTEM HALT 7, $05B1
> ***************

< dump stuff snipped >

When you' ve had a system abort the "sys_abort" macro is more useful
since it takes care (usually) of figuring out which processor had the abort
and displays the stack trace which, in this case, would be useful.

An SA1457 could be caused by a bad or misconfigured peripheral. For
example, the SCSI ID being incorrect and matching some other device
(I think I've seen that happen).  Often SA1457's are due to some form
of network problem too.

A bonefide power failure might also cause an abort of some form but it
is rather odd to get successive pfails doing the same thing. But bad luck
doesn't follow any rules so it could happen.

If you can, you should contact who ever provides your software support.
SA1457's are another of those generic aborts that have a variety of
possible causes. This one sounds like it is easily reproduced.

Hope this helps.

Bill
hp/vCSY

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