System Abort 5100 from subsytem 208 (238 Views)
Reply
Trusted Contributor
Ian Warner
Posts: 178
Registered: ‎12-04-1997
Message 1 of 5 (238 Views)

System Abort 5100 from subsytem 208

Just added patch PTDFDU1A via patch/ix on a 5.5 system to hopefully cure a telnet problem.
On doing a START NORECOVERY NOSYSSTART at the IPL prompt, the systems halts with

SYSTEM ABORT 5100 FROM SUBSYSTEM 208
FLT DEAD
BF07
0113
02EC

HELPPPPPPPPPP......
Why did anyone invent unix?
Honored Contributor
Kwan Fong, Emile
Posts: 1,162
Registered: ‎07-10-2000
Message 2 of 5 (238 Views)

Re: System Abort 5100 from subsytem 208

Hello Ian,

Subsys #208 = Directory Management
SA #5100 = directory_caught_an_escape

Cause: Some code that the directory called, escaped out OF their code AND landed in the RECOVER block of directory.

Action: Take a memory dump.

Precisely at which point during the bootup process it failed? What is the last bootup message at the console?

Was the last bootup message the following?

Initialize volume management completed.
Warning - START and NL do NOT match, system may not run.
SYSTEM ABORT 5100 SUBSYS 208

If so, most likely there are some Stage/iX files that were not on ldev#1; some Stage/iX files are HFS files under /SYS/hpstage directory. You can check this out using stageman>list ;files command. If the directory /SYS/hpstage and their files were not on ldev#1, you'll have to move these files to ldev#1.
King is the customer!
Trusted Contributor
Ian Warner
Posts: 178
Registered: ‎12-04-1997
Message 3 of 5 (238 Views)

Re: System Abort 5100 from subsytem 208

The last message was

Initialize volume management completed.

and then the abort came up straight away
Why did anyone invent unix?
Honored Contributor
Kwan Fong, Emile
Posts: 1,162
Registered: ‎07-10-2000
Message 4 of 5 (238 Views)

Re: System Abort 5100 from subsytem 208

Ian,

If there is no "Warning - START and NL do NOT match, system may not run." between "Initialize volume management completed." and "SYSTEM ABORT 5100 SUBSYS 208" messages, then take a memory dump and have it analyzed by HP Response Center. It could be a directory issue or a disc that the PDC code cannot initialize.
King is the customer!
Trusted Contributor
Ian Warner
Posts: 178
Registered: ‎12-04-1997
Message 5 of 5 (238 Views)

Re: System Abort 5100 from subsytem 208

Thanks for the info, system was reverted to previous CSLT and all ok now (fingers crossed).

Thanks for the help.
Why did anyone invent unix?
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.