HP3000-L Archives

December 2016, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Mark Ranft <[log in to unmask]>
Reply To:
Mark Ranft <[log in to unmask]>
Date:
Thu, 8 Dec 2016 22:58:56 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (67 lines)
Below are two commands to review the system logs for disk errors.
Sign on as Manager.SYS.  Do a LISTF LOG####,2 to find the start and ending Log files. Alter the log file number range in the commands and enter the commands in LOGTOOL. 

list log=3404/3477 type=111 "device class"="hard disc",da,ca,"bus converter" out=LogOut1
list log=3404/3477 TYPE=111;'MGR CODE'= 241,242,900,901,951 out=LogOut2

The results are written to two files LOGOUT1 and LOGOUT2.  

I had this setup to run weekly on my systems.  And if the files had errors in them the job would email the results to me for review.

Note that you will see errors due to SCSI or FC resets on every boot, so check the time stamps to tell if the boot caused the error.

Mark Ranft

> On Dec 8, 2016, at 9:34 PM, James B. Byrne <[log in to unmask]> wrote:
> 
>> On Thu, December 8, 2016 17:35, Mark Ranft wrote:
>> It depends on why you were running FSCHECK in the first place.  Can
>> you please give us a little background?
>> 
>> 
> 
> We experienced a system halt on Monday morning, as previously reported
> to the list.  The cause of the halt is still under investigation.  One
> of the consequences of the halt, which occurred in the middle of our
> weekly full backup, seems to have been a broken backwards chain in our
> accounting database.
> 
> We recovered the system and went back online until the broken chain
> evidenced itself.  We removed the users from the system and used
> Adager to repair the damage. Then did a backup. Then returned the
> system to use.
> 
> During the Agager repair an infrequently occurring high-pitched but
> low volume sound was noted.  This appeared to emanate from the HP3000.
> We have not heard it since the Adager repair completed.
> 
> Nonetheless, a suspicion arose that we might have a HDD about to lose
> a bearing.  The inference being that an incipient HDD failure may also
> have been somehow related to the system halt.
> 
> I am simply trying to find out if there is any way of examining
> whether or not we actually have a failing drive.  We have spares but
> if there really is no need then I would rather not take the system
> down again after such a short interval.  It has been a bad fall for
> our poor old 918.  The system HDD was toasted by a whipsaw set of
> power outages on October 11 and now our data disc is suspected of
> being ready to let go as well.
> 
> 
> -- 
> ***          e-Mail is NOT a SECURE channel          ***
>        Do NOT transmit sensitive data via e-Mail
> Do NOT open attachments nor follow links sent by e-Mail
> 
> James B. Byrne                mailto:[log in to unmask]
> Harte & Lyne Limited          http://www.harte-lyne.ca
> 9 Brockley Drive              vox: +1 905 561 1241
> Hamilton, Ontario             fax: +1 905 561 0757
> Canada  L8E 3C3
> 
> * 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 *

ATOM RSS1 RSS2