|
Concurrent maint Remove DDxxx Concurrent maint Add DDxxx Disk recovery menu Rebuild disk unit data Select disk to rebuild Wait an hour WRKDSKSTS, F11 to ensure no longer "FAILED" and now "ACTIVE" Done! Parity will auto-recover as will the ASP part. -- Justin C. Haase - iSeries System Engineer IBM Certified Systems Expert - System i Kingland Systems Corporation -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Helgren Sent: Saturday, October 14, 2006 6:19 PM To: Midrange Systems Technical Discussion Subject: Re: Disk failure procedure Yes. I checked the system builder, too. I was just worried that I was going to pull the wrong unit. OK, with that cleared up, are there instructions for replacing a disk unit somewhere? I looked at the Backup and Recovery guide and the System Builder but I don't see any step by step. I guess I need to do "Concurrent Maintenance" on the unit to remove it. Put the new one in and then ? Just add it back into the ASP and start parity protection? Pete Haase, Justin C. wrote:
And looking in my handy-dandy system builder... D05 is the fifth from the left on the skinny 270. D01 is on the left and D06 is on the right. If you have the expansion attached, the disk numbering starts at the bottom of that with D08 and goes to the top with D20. -- Justin C. Haase - iSeries System Engineer IBM Certified Systems Expert
- System i Kingland Systems Corporation -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Helgren Sent: Saturday, October 14, 2006 4:50 PM To: Midrange Systems Technical Discussion Subject: Disk failure procedure I have a disk that has failed on my model 270. I am just a little fuzzy on the the replacement. I have another drive that I can install. My problem is that I don't know which drive to replace. System Operator message queue has the following: Unit 6 with device parity protection not fully operational. Cause . . . . . : Unit 6 is part of a disk unit subsystem with device parity protection. Unit 6 requires service. The data has been saved. Reduced performance, machine checks, and possible data loss can
occur
midrange.com
if
this condition is not corrected. The following information
identifies the
unit requesting
service:
Disk serial number:
68-0CF6ADE
Disk type:
6718
Disk model:
070
Device resource name:
DD006
Disk status shows the following:
Serial Resource Hardware
ASP Unit Number Type Model Name Status
1 1 02-35300 6718 074 DD001 DPY/Unprotected
1 2 02-015B2 6718 074 DD004 DPY/Unprotected
1 3 02-03760 6718 074 DD002 DPY/Unprotected
1 4 02-03423 6718 074 DD003 DPY/Unprotected
1 5 68-0D0E009 6718 070 DD005 DPY/Unprotected
1 6 02-0CF6ADE 6718 070 DD006 DPY/Failed
Do the unit #'s listed here represent the position in the "cage" these
drives are in? The only reason I ask is that when I look at the
hardware details for unit #6 I see the following:
Type. . . . . . . . . . . . : 6718
Model . . . . . . . . . . . : 070
Level . . . . . . . . . . . : 5
Serial Number . . . . . . . : 02-0CF6ADE
Resource Name . . . . . . . : DD006
Physical location:
Frame ID . . . . . . . . . : 1
Card position. . . . . . . : D05
Device position. . . . . . :
"Card Position" D05 seems to point me to the 5th slot in the cage,
rather than the 6th. I don't want to yank the wrong one.
Also, where do I find the "serial number" that is listed in the
detail?
The serial number reported in QSYSOPR message queue is different than the detail on disk status (68-0CF6ADE .vs 2-0CF6ADE) Is it on the drive itself so I can double check the it before I replace it? Thanks. Pete Helgren -- 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.
CONFIDENTIALITY NOTICE: This e-mail communication, including
attachments, is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential, and may be legally privileged. If you are not the intended recipient or believe you received this communication in error, please reply to the sender indicating that fact and delete the copy you received. In addition, retention, dissemination, distribution, copying, or otherwise use of the information contained in this communication 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, 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. CONFIDENTIALITY NOTICE: This e-mail communication, including attachments, is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential, and may be legally privileged. If you are not the intended recipient or believe you received this communication in error, please reply to the sender indicating that fact and delete the copy you received. In addition, retention, dissemination, distribution, copying, or otherwise use of the information contained in this communication is strictly prohibited. Thank you.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
