HP3000-L Archives

November 1995, Week 4

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:
Neil Harvey <[log in to unmask]>
Reply To:
Neil Harvey <[log in to unmask]>
Date:
Tue, 21 Nov 1995 11:34:00 S
Content-Type:
text/plain
Parts/Attachments:
text/plain (44 lines)
Ken Paul Wrote
 
 
>The next week I got a call from Orly Larson, who is HP's liason with
Interex.
>He wanted me to talk to Clive Surfleet, Operation Manager of CSO Mass
>Storage Business.  I sent them copies of both my original posting and
the
>responses that were also posted to the List.
 
Well, I'm certainly glad to see some activity on the HP management side!
 
>Clive was sitting on the Management Roundtable in Toronto specifically
>because HP thought that this question would come up but it didn't.
 
This could be the beginning of the end of the "denial" phase.
 
>I have been asked by HP to look into the problems that users have been
>experiencing with these 2GB disc drives and will post back my findings
>and also publishing them in InterexPress.
 
I'm amazed that the factory doesn't have statistics and details showing
exactly which drives (serial numbers et al.) have failed and where. When
I worked for HP (admittedly only as a sales rep, and only for about 1
year), I was led to believe that any hardware failures were shipped back
to the factory for strip down and full QA review.
 
IMHO, disk drives are the most critical part of a computer system, since
they hold data/programs without which there can be no use for the system.
Tape drives, printers, DAT drives and even CPU's and Memory can fail and
the machine, if it is an HP3000 :), will usually recover causing minor
inconvenience and time loss, but if a disk fails and data is lost it is
usually catastrophic.
 
Incidentally, when the first disk went, the system gradually ground to a
halt, even though it was part of a private volume set. It was explained
to me that all disk read and write requests go through a single process,
and so this would eventually back up and clog the operating system.
 
I look forward to hearing the resolution to this irksome problem.
 
Neil Harvey
[log in to unmask]

ATOM RSS1 RSS2