Thanks to those so quick to react (why aren't you watching Saturday morning cartoons?? 😉)
FSCHECK reported only 2 little directory warnings.
One data group is on the user volume but not the system volume, and another data group is "not active on user volume".
Both of these are MANMAN database groups that are never used. But I'll get those 'problems' corrected.
With no other errors/problems reported, I guess I'll just wait and see if another incident occurs.
Terry W Simpkins
Yorktown, VA 23693
IBA # 8778 SS1000, SS2000, BBG, 50CC
-----Original Message-----
From: HP-3000 Systems Discussion <[log in to unmask]> On Behalf Of Craig Lalley
Sent: Saturday, February 04, 2023 9:58 AM
To: [log in to unmask]
Subject: Re: [HP3000-L] System abort
FSCHECK.MPEXL.TELESUP
ca all
-Craig
Sent from Yahoo Mail for iPad
On Saturday, February 4, 2023, 6:52 am, Terry Simpkins <[log in to unmask]> wrote:
My little 928 had a system failure this morning. My initial suspicion is that LDEV #2 has a problem.
I issued an ‘abortjob’ command from a ‘non-console’ session, and got these messages before the command completed successfully:
Bad SYSTEM LOGICAL Sector number 0x226A80b on ldev 2 (io_status=FFD40071) Filename of bad file:/VESOFT/CMD22/SHOWSCH8 Bad SYSTEM LOGICAL Sector number 0x226A80b on ldev 2 (io_status=FFD40071) Filename of bad file:/VESOFT/CMD22/SHOWSCH8 Bad SYSTEM LOGICAL Sector number 0x226A80ÿ on ldev 2 (io_status=FFD40071) Filename of bad file:/VESOFT/CMD22/SHOWSCH8 Bad SYSTEM LOGICAL Sector number 0x226A80ÿ on ldev 2 (io_status=FFD40071) Filename of bad file:/VESOFT/CMD22/SHOWSCH8 Bad SYSTEM LOGICAL Sector number 0x226A80ÿ on ldev 2 (io_status=FFD40071) Filename of bad file:/VESOFT/CMD22/SHOWSCH8
(There were more of these messages but I didn’t copy everything)
I walked over to the other room where the console is located and found the following displayed:
System Abort 1740 from subsystem 107
Secondary Status: INFO = -44 Subsys = 113 System Halt 7, $06CC
Then autorestart kicked in and the system performed a ‘Start NoRecovery’, with no reported errors.
I ran “LISTF” on the file listed above (SHOWSCH8.CMD22.VESOFT) without a problem.
And then “printed” the file to the screen without generating another system halt. If the drive was failing, I thought that would create another system failure.
Any ideas/suggestions?
Terry W Simpkins
Yorktown, VA 23693
IBA # 8778 SS1000, SS2000, BBG, 50CC
* 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 *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
