× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Mark,
as a hardware maintenance company we 'see' a good many failures, recently
multiple failures with 6717's on 8xx have been very common; our engineers
are suspecting a bad batch from the factory and are checking serial numbers.

Kind Regards,

Jeff Bull
AS/400 Software Support Consultant      
IBM Certified AS/400 System Administrator

Mailto:jeff.bull@itm-group.co.uk   
Website: http://www.itm-group.co.uk

ITM Group, 7 Skyport Drive, Harmondsworth, Middlesex, UB7 0LB, United
Kingdom
Tel: +44 [0] 208 476 2000 ; Fax: +44 [0] 208 476 2111

-----Original Message-----
From: Mark Villa [mailto:markvilla@knology.net]
Sent: 25 June 2001 13:21
To: MIDRANGE-L@midrange.com
Subject: 820 DASD crashes


A shop using parity protection on a raid string is really not expecting an
820 a few months old to have 2 disks quit at the same moment in time. I am
not a math wiz by any stretch, but it would seem that with the mean time
between failure being such a large number the likelihood of that happening
without an external cause at the exact same moment is less than me being hit
by a comet in the next 5 minutes.

With that in mind, what is really the cause of multiple disk failures in one
raid string. Has this happened to someone you know? The UPS for the 820
comes to mind as a possible problem component.

Anybody know where to start looking online for listing of IBM HARDWARE under
the microscope as suspect? In other words not PTF's. I am thinking that
there is not such a listing for hardware since it is not as acceptable to
have a hardware quality problem as it is a PTF for a bug in software.


Thanks,

Mark Villa in Charleston SC.


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---


DISCLAIMER

Any opinions expressed in this email are those of the
individual and not necessarily the Company. This email
and any files transmitted with it, including replies and
forwarded copies (which may contain alterations) 
subsequently transmitted from the Company, are 
confidential and solely for the use of the intended recipient. If you are not 
the intended recipient or the 
person responsible for delivering to the intended recipient, 
be advised that you have received this email in error and
 that any use is strictly prohibited.

If you have received this email in error please notify the IT
manager by telephone on +44 (0)208 4762000 or via 
email to Administrator@itm-group.co.uk, including a copy
of this message. Please then delete this email and 
destroy any copies of it.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.