If the disk didn't actually fail yet, which, based on your initial message it did not. CPP1604 *Attention* Impending DASD failure.
You may have to do an additional step to "force fail" that unit.
Once failed, then your replace via the document, using concurrent maintenance.
You can do this via green screen or OPS NAV.
If you have an HMC, follow the wizard.
After the disk is replaced, you must force it to rebuild the parity set.
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James Rich
Sent: Monday, June 30, 2014 1:41 PM
To: Midrange Systems Technical Discussion
Subject: RE: Failed disk in a 9406-170
On Sat, 28 Jun 2014, Porterfield, Sean wrote:
You may have already solved this by now, but the Backup and Recovery
manual has that sort of thing.
See PDF page 86.
I've been reading exactly that manual. As I look at the tables on that page it looks to me like I need to use checklist 15 as that seems to match my situation of device parity protection active and no data loss.
Unfortunately that checklist says that tasks 1 and 2 are done by the service represetative, which won't be coming in our case since there is no maintenance agreement. So I need to do task 1: attach the new disk unit and task 2: rebuild the failed device parity disk unit data. I've been reading the section on device parity protection and so far haven't found anything on rebuilding the failed device parity disk unit data.
I have found this maidrange post interesting:
It mentions concurrent maintenance, but I haven't found what that is in any manuals yet. Do I leave the failing disk unit in the machine and add the new disk, or do I remove the failing unit from DPY, then remove it from the machine, then add the new disk, then add the new disk to DPY?
Note to Mark S Waterbury:
I tried to respond to your message but it looks like bellsouth blocks my mail server despite it not appearing on any blacklists.
From: James Rich
Sent: Friday, June 27, 2014 15:31
Subject: Failed disk in a 9406-170
I have a customer that has a failing disk in a 9406-170 running v5r2.
The exact message is:
CPP1604 *Attention* Impending DASD failure. Contact your hardware
service provider now.
Cause . . . . . : Internal measurements on disk device DD001 indicate
that an unrecoverable error resulting in data loss is about to occur.
Recovery . . . : Contact your hardware service provider to have
failing item 59H6611 service.
We would normally have IBM handle this but this customer doesn't have
hardware support and isn't about to start. So I'm doing this myself
for the first time. The new drive has arrived and a GO SAVE 21 is
nearly complete. There are a total of 4 disks in a RAID 5
configuration. I've been looking for instructions on how to do this
but haven't found them yet. Can anyone point me to the correct
documentation or give me the steps to follow?
This email is confidential, intended only for the named recipient(s) above and may contain information that is privileged. If you have received this message in error or are not the named recipient(s), please notify the sender immediately and delete this email message from your computer as any and all unauthorized distribution or use of this message is strictly prohibited. Thank you.
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
if you want to understand why that is, there are many good books on the design of operating systems. please pass them along to redmond when you're done reading them :)
- Paul Davis on ardour-dev
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l