Re: Replacing failed disk on iSeries - Model 270

["Charles Wilt" <charles.wilt@xxxxxxxxx>]

Hope that wasn't a production box, as I believe you've wiped it out by
stopping RAID while a unit was failed.

> From the Backup and Recovery Manual:
Recovery Checklist for Disk Failure–Checklist 15
1) Attach the new disk unit.
2) Rebuild the failed device parity disk unit data.
3) Ensure that disk configuration is correct

That's all it would have taken....

Charles

On Sat, Dec 13, 2008 at 9:45 PM, Alo Pita <alopita@xxxxxxxx> wrote:

> I have just received a replacement disk from IBM to replace one that has
> failed in my Model 270. I have done the following procedures after manual
> IPL:
>
>
>
> 1.      logically remove failed disk from raid
> 2.      stop raid
> 3.      power off.
> 4.      physically remove failed disk and replace it with new one
> 5.      power on system and then attempt to add the new unconfigured disk
>
>
>
> This is where I get an error 'Disk Unit I/O failure, check reference code.'
>
> Upon display I get the following information.
>
>
>
> The System encountered an error while it was attempting to read or write to
> a disk unit.
>
>
>
> Contact your Service Representative with the following information.
>
>
>
> S/N                   Type    Model  Resource         Reference Codes
>
>                                                Name               I/O
> Device
>
>
> Processor
>
> 68-0380C3F       6717     050       DPH001            0000
> 3110
>
>
>
> My concern is that this is the 2nd replacement disk that IBM have send me
> that has failed. Does the information above help me pinpoint a different
> error or do I just have to ask IBM for another disk.
>
>
>
> thanks
>
>
>
> Andy
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.