Defunct Drive - Scsi Error
a Predict Failure Analysis (PFA) alert on a hard drive attached to the ServeRAID controller - Servers and IntelliStation Applicable countries and regions Overview IBM eServer xSeries SCSI hard disk drives support Predictive Failure Analysis (PFA). This specification is designed into the hard disk drives to internally monitor and diagnose a likely failure within the near future. If a disk issues a PFA event , the ServeRAID controller will capture and forward the event locally to the ServeRAID Management console and agent. ServeRAID Manager and Agent software supports industry standard SNMP for alert automation. If a PFA alert occurs on an IBM xSeries hard disk drives, it is eligible for replacement under the warranty terms and conditions. Recovering from a hard disk drive PFA Alert on a ServeRAID controller may require multiple steps depending on the ServeRAID configuration. Ensure you have a recent backup of the data before proceeding. If the disk that PFA's is configured in a redundant logical drive (RAID level-1, 1E, 5, 5E, 5EE, 10, 1E0, or 50), recovery is a three step process. The first step is to prepare the hard disk drive with an active PFA Alert for replacement. The second step is to replace the defunct drive, and the third step is to regenerate the "Critical" logical drive back to an online or "Okay" state. If a qualified Hot Spare or Standby Hot Spare is configured, ServeRAID will automatically regenerate a "Critical" logical drive to an "Okay" state. If the disk that PFA's is configured in a non-redundant logical drive (RAID level-0, or 00), all data on the logical drive will be lost when the disk is eventually marked defunct. The first step is to backup the data on the logical drive as soon as possible. The second step is to prepare the hard disk drive with an active PFA Alert for replacement. The third step is to replace the PFA drive, and the fourth step is to recover the "Offline" logical drive. This is done by removing the affected "Offline" logical drive then recreate the non-redundant logical drive. The final step is t
drive This message was generated by the ServeRAID Manager Agent. Please do not reply to this message. Event Description: Defunct drive: controller 1, channel 2, SCSI ID 3 (Vendor: IBM-ESXS Model: ST314670). Event Type: Error Event Source: storage@hostname Date: MM/DD/YYYY Time: HH:MM:SS PM CST Solutions Run a IBM ServeRAID Manager connecting to the server for the FRU part number Then, went to remove the https://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=migr-58230 defunct drive When removed, should show Now, Replaced the hard disk to be FRU - 90P1310, because it's the same connectivity - Ultra320 SCSI - 80 pin Centronics (SCA-2) as the FRU - 397310 one IBM 90P1310 hard drive specifications - http://www.testhdd.com/IBM-hard-drive-146-GB-Ultra320-SCSI-1458.html IBM 39R7310 hard drive specifications - http://www.testhdd.com/IBM-hard-drive-146-GB-Ultra320-SCSI-1589.html Scanned for http://gayt.blogspot.com/2011/06/how-to-repair-defunct-drive-by-ibm.html the new hard drive Then, set it to be a hot-spare drive That can also be via a wizard References Removing a defunct drive - http://publib.boulder.ibm.com/infocenter/director/v5r2/index.jsp?topic=/serveraid_5.20/fqy0_aremovdd.html ServeRAID recovery from single defunct disk drive (DDD) failures - Servers and IntelliStation - http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-40364 ServeRAID drive state descriptions - Servers and IntelliStation - http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-4R6MXK PrintPDF at 12:26 Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: Hardware 1 comments: Post a Comment Newer Post Older Post Home About Me GaYt Tang 左腦種植，右腦種智，外至萬腦，內存理解，沒腦人吾也！ View my complete profile Search My Blog Twitter Tweets by @GTTGsba Labels Active Directory (12) Android (1) Backup (21) Books (5) CityU (12) Coding (31) Cooking (6) Disaster Recovery Plan (3) Excel (10) Finance (6) GIS (1) Hardware (21) iPhone (9) Linux (72) Lotus (8) Microsoft (125) My Learn (32) My Life (89) Network (20) OpenWrt (2) Photo (1) Plant (3) Powershell (5) Quote (64) Reference (26) Security (21) Society (4)
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies http://serverfault.com/questions/103668/ibm-x345-raid-1-with-2-defunct-drive-how-do-i-get-it-back of this site About Us Learn more about Stack Overflow the company http://ps-2.kev009.com/pcpartnerinfo/ctstips/86fa.htm Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask defunct drive a question Anybody can answer The best answers are voted up and rise to the top IBM x345 raid-1 with 2 defunct drive, how do I get it back? up vote 4 down vote favorite I have an IBM x345 server running raid-1 with 2 drives that went defunct after a reboot. ServeRaid has an x by both drives (36g scsi) marked defunct. defunct drive - The option to rebuild the defunct drives under ServeRaid is not there. Is there any way I can get my data back from this? Any help appreciated. Thank you. ibm share|improve this question asked Jan 18 '10 at 5:37 user32035 3 Go to your backups. –LukeR Jan 18 '10 at 5:47 yeah, it turns out that the guy that was supposed to be doing the backups was not doing his job. anyways, he's in a deep hole right now. I have tried to put this same config into another server but windows 2003 server doesn't see the drives correctly. Win 2003 disk management sees the drives as "unknown - unreadable" as seperate drives and not 1 mirror volume. I have read about this problem on NT4 somewhere but can seem to find the resolution to it. Again, any help is much appreciated. Thank you. –user32035 Jan 18 '10 at 6:37 add a comment| 4 Answers 4 active oldest votes up vote 1 down vote what you can do is try to reinit the raid power down host, remove both drives power host up, go
in this HMM. Procedures for recovering from DDD scenarios include: Drive Replacement (Rebuilding a Defunct Drive) Software and Physical Replacement Using and Understanding the ServeRAID Administration Log Recovery From ServeRAID Adapter Failure When HSP is Present at Time of Failure When HSP is Not Present at Time of Failure Note The following information applies only to drives that are part of the same array Drive Replacement (Rebuilding a Defunct Drive) When a hard disk drive goes defunct (DDD), a Rebuild operation is required to reconstruct the data for the device in its respective disk array. The ServeRAID adapters and controllers can reconstruct RAID level-1 and RAID level-5 logical drives, but they cannot reconstruct data stored in RAID level-0 logical drives. To prevent data integrity problems, the ServeRAID adapters and controllers set the RAID level-0 logical drives to Blocked during a Rebuild operation. After the Rebuild operation completes, you can unblock the RAID level-0 logical drives, and access them once again. But remember, the logical drive might contain damaged data. Before you rebuild a drive, review the following guidelines and general information. Guidelines for the Rebuild operation The replacement hard disk drive must have a capacity equal to or greater than the failed drive. If the hard disk drive being rebuilt is part of a RAID level-0 logical drive, the RAID level-0 logical drive is blocked. You must unblock any RAID level-0 logical drives at the end of the rebuild operation. If you use the Administration and Monitoring Utility to initiate the rebuild operation, you can unblock the blocked RAID level-0 drive when the rebuild operation completes. Data in a logical drive with RAID level-0 is lost during the rebuild operation. If you backed up your data before the drive failed, you can restore the data to the new drive. General Information about the Rebuild Operation A physical hard disk drive can enter the rebuild state if: You physically replace a defunct drive that is part of the critical logical drive. When you physically replace a defunct drive in a critical logical drive, the ServeRAID adapter/controller rebuilds the data on the new physical drive before it changes the logical drive state back to Okay. The ServeRAID adapter/controller adds a hot-spare or a standby hot-spare drive to the array and changes its state from Hot-Spare or Standby Hot-Spare to Rebuilding. Automatically Rebuilding the Defunct Drive The ServeRAID adapter/controller will rebuild a defunct drive automatically when all of the following conditions exist: The physical drive that failed is part of a RAID lev