Re: Replace Disk Unit Under Parity Protection

[Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>]

Okay,

Following your steps,
- went into "Device Concurrent Maintenance"

- put in resource name and 1=remove device

- looked for LBL, but there's lots of lights.  meanwhile, screen says 
"action completed successfully. if you did not remove the device, hit 
F12 and try again".

- Hit F12.  Tried again.  Didn't wait so long...  light appeared to be 
blinky, and pulled out device.  System goes to SRC A6020266

- Waited 10 minutes.  Nothing else happened. System still at SRC 
A6020266, and screen still has not said "action completed".  Can't seem 
to do anything else.

- Powered off.

- Put failed unit back in.

- Waiting for another IPL, which is going to take awhile due to abnormal 
shut down...

I think I'll give up on this for tonight.



On 2/20/2012 6:27 PM, DrFranken wrote:
> I'm just guessing since I've have never done this before but the steps
> would in theory (a perfect world) look like this:
>
> While the system is up and running enter Service Tools: STRSST
>
> IN Service tools select Work with DIsk Units.
>       Select Display DIsk COnfiguration
>       Select Display device Parity Status
>       Locate the drive that says: FAILED
>
>       Write the resource Name Here: ___________
>
> Exit back to the Service Tools main menu
>
>       Start a Service Tool
>       Hardware Service manager
>       Device COncurrent Maintenance
>       Enter the resource name from above in the "Device Resource Name"
> space, selection "1" Remove Device, Press Enter. (*)
>       Look for the LBL above the Drive to blink and when it starts, pull
> out the dead guy.
>       Once the screen displays "Action Completed" Press F12 to return to
> the Concurrent Maintenance Screen
>       Change the 1 to a 2 (Install device), Press Enter
>       Look for the LBL above the MT slot to blink and when it starts,
> lock in the new drive.
>
> Exit back to the Service Tools main menu.
>
>       (Don't be in a hurry to get here, the system needs to recognize the
> new drive.... takes a minute)
>       Work with Disk Units
>       Work with Disk Unit Recovery
>       Rebuild disk unit data
>       Select the unit to rebuild (there better be just one. :-)  )
>       Proceed through any confirmation prompts.
>       Press F5 occasionally, watch until it hits 100%
>
> Return to your regularly scheduled OS/400.
>
> (*) If you get an error that says: "YOU cant do this you have no
> eligible hardware" then your 270 didn't have concurrently maintainable
> disk cans. That would suck.
>
>       - Larry "DrFranken" Bolhuis
>
> P.S.  LBL = Little Blinky Light.
>
> On 2/20/2012 6:29 PM, Scott Klement wrote:
> > Thanks, Jerry... it's not the load source unit.
> >
> >    From what I've been reading (from the links that Rob sent) it looks
> > like I should be able to IPL without the failed unit... I'm wondering
> > now why it won't IPL without it...  hmmm...
> >
> >
> > On 2/20/2012 3:44 PM, Jerry Draper wrote:
> > > It may matter if it's load source because it sounds like when you remove
> > > the drive you can't IPL the system.
> > >
> > > Since you are RAIDed theoretically you could do a hot swap of the drive
> > > using concurrent maintenance.  IBM should have decent instructions on
> > > how to do concurrent maintenance.