Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!wuarchive!uunet!mcsun!hp4nl!phigate!prle!prles2!prl.philips.nl!goossens
From: goossens@prl.philips.nl (goossens lmc)
Newsgroups: comp.sys.hp
Subject: Re: bad m/o disks?
Message-ID: <2448@prles2.prl.philips.nl>
Date: 9 Jan 91 14:17:38 GMT
References: <1991Jan07.150748.415@eye.com>
Sender: news@prles2.prl.philips.nl
Organization: Philips Research Laboratories Eindhoven, the Netherlands
Lines: 28


In article <1991Jan07.150748.415@eye.com> paul@eye.com (Paul B. Booth) writes:
>
>The o/m drive is mounted on a 350 running hpux 7.05 (straight, no patches).
>Starting a week ago, I come in to find this node halted due to a bus error panic
>
Some patches problaby solves your panics. I installed:

PATCH_7.0:$Header: scsi_if.c,v 1.2.17.11 90/08/07 16:17:02 paul Exp $
PATCH_7.0:$Header: scsi.c,v 1.2.17.12 90/08/07 16:16:42 paul Exp $
PATCH_7.0:$Header: scsi_ccs.c,v 1.2.17.6 90/08/07 16:17:18 paul Exp $
PATCH_7.0:$Header: ac.c,v 1.2.17.7 90/01/23 12:56:27 prem Exp $


>
>but the o/m disk won't fsck because it has an unreadable block.
>
I've had same problems with the 20GB/A and a 650A on my HP9000/370
(HP-UX 7.0 with the latest SCSI patches, see above). Sometimes bad 
blocks were introduced (fsck: cannot read blocks).  After HP swapped 
the prom on the conroller-board of each drive, my problems were solved.
The old EPROM was numbered: C1700-89000 CCP 2.13, the new one is
numbered: C1700-89601 CCP 3.02 (probably sony numbers). I do not know  
the HP part-number. They told me that some error-recovering routine in
the firmware caused the problem.


  			   			    Louis Goossens