HP3000-L Archives

December 1995, 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:
"Rudderow, Evan" <[log in to unmask]>
Reply To:
Rudderow, Evan
Date:
Fri, 8 Dec 1995 11:12:00 EST
Content-Type:
text/plain
Parts/Attachments:
text/plain (32 lines)
"Paul H. Christidis" <[log in to unmask]> wrote:
 
<snip>
 
>Some hours later the HPRC called back saying that the dump indicated that
>ldev 37 was the reason for the hang and were considering to replace it
>although no errors were logged against that device and no errors were
>detected when they 'exercised' the device.   Since we were hesitant to halt
>our production and thus loose today's data entry and all of the recovery
>work, the HPRC disk specialists and dump analysts had another huddle and
>decided that the situation did not warrant changing the ldev.   They
>indicated that while they were 100% sure that actions involving ldev 37
>were the reason for the hang, they had no idea what the initial cause was
>nor could they rule out the possibility that it was software.  The
>potential list included: a bad controller, bad cable, bad scsi terminator,
>intermittent power supply, faulty scsi driver, etc.....
 
<snip>
 
>Has anyone else out there had anything similar?  Did it reoccur?  Was it
>ever resolved? etc?  ... ?
 
A few months ago we had a scheduled power shutdown over a weekend.  When I
came into to restart the system I had problems with 4 of my disc drives.  It
turned out they were all on the same controller; so I powered everything
down, got out my trusty Torx, pulled the controller out, slid it back in,
powered up, and everything was fine.
 
(Just don't tell my CE that I did this...)
 
 -- Evan

ATOM RSS1 RSS2