Re: Disk Failure -- MIDRANGE-L

It depends on your bus / controller configuration in your
system, if you are able to do concurrent maintenance, or not.
Having SPD-cards doesn't matter, it's just the type of controllers
and MFIOPS in your specific environment.
Take a look at the hardware manuals yourself if you are curious
or wait for the CE to come .

Regards from germany, Philipp Rusch

Dare schrieb:

> If any downtime, anyone knows estimate of how long?????
>
> Dare
>
> ----- Original Message -----
> From: "Andy Nolen-Parkhouse" <aparkhouse@attbi.com>
> To: <midrange-l@midrange.com>
> Sent: Tuesday, June 04, 2002 9:26 AM
> Subject: RE: Disk Failure
>
> > Dare,
> >
> > From the looks of your disk configuration, you are on an older system
> > which will not allow you to replace the disk while the system is active.
> > Your system will remain active with mirroring and RAID.  You could just
> > wait until your CE arrives and let him deal with it.  The RAID set will
> > rebuild itself when the machine powers up after the new disk is
> > installed.
> >
> > Because you are now unprotected and the loss of an additional drive in
> > the RAID set will require a full system reload, you might want to do a
> > full option 21 save if you have time before your customer engineer
> > arrives.  Otherwise, if you're on IBM maintenance, let them put it back
> > together for you.
> >
> > Regards,
> > Andy Nolen-Parkhouse
> >
> > > Subject: Disk Failure
> > >
> > > This is a multi-part message in MIME format.
> > > --
> > > [ Picked text/plain from multipart/alternative ]
> > > Hi guys,
> > >
> > > I came in this morning and found out one of my disk failed, I already
> > > called our CE.  Any idea what to look for, steps of action, possible
> > > problems, data recovery, or anything of help.
> > > Below is my WRKDSKSTS, unit #4 is the failed disk.
> > >
> > >
> > > Thanks.
> > >
> > > Work with Disk Status     06/04/02 09:03:45
> > >
> > > Elapsed time: 00:08:04
> > >
> > > Size % I/O Request Read Write Read Write %
> > >
> > > Unit Type (M) Used Rqs Size (K) Rqs Rqs (K) (K) Busy
> > >
> > > 1 6606 1967 ++++ 4.1 5.9 1.5 2.6 4.5 6.6 5
> > >
> > > 1 6606 1967 ++++ 4.9 5.7 2.4 2.4 4.5 6.9 5
> > >
> > > 2 6607 3145 84.7 14.1 5.0 8.5 5.6 4.4 5.9 22
> > >
> > > 3 6607 3145 83.3 12.9 5.0 7.6 5.2 4.3 6.0 20
> > >
> > > 4 6607 4194 77.0 15.6 5.4 9.6 5.9 4.9 6.2 51
> > >
> > >
> > >
> > > Work with Disk Status  06/04/02 09:03:45
> > >
> > > Elapsed time: 00:08:04
> > >
> > > --Protection--
> > >
> > > Unit ASP Type Status Compression
> > >
> > > 1 1 MRR ACTIVE
> > >
> > > 1 1 MRR ACTIVE
> > >
> > > 2 1 DPY UNPROT
> > >
> > > 3 1 DPY UNPROT
> > >
> > > 4 1 DPY FAILED
> > >
> > > 5 1 DPY UNPROT
> >
> > _______________________________________________
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> > To post a message email: MIDRANGE-L@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > or email: MIDRANGE-L-request@midrange.com
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.