RE: DASD problems -- MIDRANGE-L

Not only did I act fast, but so did IBM.  Incredible.  I reported the error
yesterday at about 3PM, and IBM has been here and replaced the drive by
10AM.  The drive was couriered in last night and the tech came out first
thing this morning.  My system is rebuilding as we speak, and what I really
like is that while it's rebuilding, it's actually up and running.

That's why I use an AS/400.

Joe


> -----Original Message-----
> From: owner-midrange-l@midrange.com
> [mailto:owner-midrange-l@midrange.com]On Behalf Of David Breisacher
> Sent: Monday, August 06, 2001 6:21 PM
> To: 'MIDRANGE-L@midrange.com'
> Subject: RE: DASD problems
> Importance: High
>
>
> Joe -
>
> You better act fast. Your system is exposed. You are currently in
> an exposed
> mode. Try to rebuild the one drive that is failed. If the drive does not
> rebuild get IBM out there ASAP to replace it. One more drive fails and you
> might have to reload your entire system.
>
> In answer to your question your current configuration looks like
> you have 5
> drives in one parity set. The 6717-074 have parity written to them and the
> 6717-070 does not. All five drives are part of the parity set. You can not
> assign any other drives to protect your exposed parity group.
>
> Good luck
>
> David
>
> -----Original Message-----
> From: Joe Pluta [mailto:joepluta@PlutaBrothers.com]
> Sent: Monday, August 06, 2001 12:11 PM
> To: MIDRANGE-L@midrange.com
> Subject: RE: DASD problems
>
>
> Okay, now I'm getting a disk problem.  In fact, I have been getting them
> since early July when I had a power outage, but I'm new at the system
> adminstration thing, and never saw the message.  Evidently, I got the
> following:
>
> Message ID . . . . . . :   CPPEA05
> Date sent  . . . . . . :   07/09/01      Time sent  . . . . . . :
>   16:14:22
>
> Message . . . . :   *Attention*  Contact your hardware service provider.
>
> Cause . . . . . :   Internal analysis of an exception indicates that data
>   protection facilities have been lost due to a permanent failure.
> Recovery  . . . :   It is recommended that you contact your
> hardware service
>   provider to have failing item 07N3185 serviced, failure to do so could
>   result in a loss of system availability. Actions should be taken now to
> save
>   system data as a precaution.
>     Report the problem to your hardware service provider.
> Technical description . . . . . . . . :   LIC Exception Analysis
>
> There were several other errors as well pertaining to hardware problems.
> Since then, I've been getting the following message:
>
> One or more device parity protected units still not fully operational.
>
> Checking the status with OpsNav, I see that I have four 6.4GB 6717-0074
> drives that are functioning, but "unprotected", while I have a
> single 8.6GB
> 6717-0070 that is "failed".
>
> I'm not sure how parity works - do you assign one drive as the
> parity drive
> and it protects up to X other drives?  If so, can I somehow
> assign one of my
> current drives as a parity drive and have it protect the others
> until I get
> the failed drive replaced (I'm only at 33% DASD utilization, so I have
> plenty of room)?
>
> This is a leased machine, so I have to figure out who to call for hardware
> replacement, but that's a different issue.
>
> Joe Pluta
>
> > -----Original Message-----
> > From: owner-midrange-l@midrange.com
> > [mailto:owner-midrange-l@midrange.com]On Behalf Of Cyndi Bradberry
> > Sent: Wednesday, August 01, 2001 11:46 AM
> > To: 'MIDRANGE-L@midrange.com'
> > Subject: RE: DASD problems
> >
> >
> > Thanks Dan and Pete.
> > I did a finger faux paux when I asked for the PTF. After using
> the number
> > you gave, I was able to find it on our system. Is there anyway of
> > looking to
> > see if we were having problems before the PTF was applied ? It
> was applied
> > temporary status on 7/26/01. I'm just curious if there was a problem
> > sneaking up on us.
> > Cyndi
> > Idaho
> > +---
> > | 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
> > +---
> >
>
> +---
> | 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
> +---
> +---
> | 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
> +---
>

+---
| 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
+---