Troubleshooting
Problem
A server operating with any ServeRAID MR or M Redundant Array of Independent Disks (RAID) controller hosting Serial Advanced Technology Attachment (SATA) and Serial Attached SCSI (SAS) disk drives, may encounter a rare condition that could result in theoperating system reporting a data loss event as a medium error. The event would be logged by the host operating system or by the MegaRAID Storage Manager (MSM) application as: Event Description: Puncturing bad block on PD Event Description: BackgroundInitialization detected uncorrectable multiple medium errors Event Description: Patrol Read found an uncorrectable medium error on PD Event Description: Consistency Check detected uncorrectable multiple medium errors Event Description: Double media errors found!
Resolving The Problem
Source
RETAIN tip: H204452
Symptom
A server operating with any ServeRAID MR or M Redundant Array of Independent Disks (RAID) controller hosting Serial Advanced Technology Attachment (SATA) and Serial Attached SCSI (SAS) disk drives, may encounter a rare condition that could result in the operating system reporting a data loss event as a medium error. The event would be logged by the host operating system or by the MegaRAID Storage Manager (MSM) application as:
| Event Description: Puncturing bad block on PD Event Description: Background Initialization detected uncorrectable multiple medium errors Event Description: Patrol Read found an uncorrectable medium error on PD Event Description: Consistency Check detected uncorrectable multiple medium errors Event Description: Double media errors found! |
Affected configurations
The system is configured with one or more of the following IBM Options:
- IBM MegaRAID 8480 SAS PCI-Express RAID adapter, Option part number 39R8850, replacement part numbers 39R8852 - Adapter, 39R8853 - Battery
- ServeRAID M1015 SAS or SATA Controller, Option part number 46M0831, replacement part number 46M0861
- ServeRAID M5014 SAS or SATA Controller, Option part number 46M0916, replacement part number 46M0918
- ServeRAID M5015 SAS or SATA Controller, Option part number 46M0829, replacement part number 46M0851 - Adapter
- ServeRAID M5025 SAS or SATA Controller, Option part number 46M0830, replacement part number 46M0854
- ServeRAID-MR10M SAS or SATA Controller, Option part number 43W4339, replacement part number 43W4341 - Adapter
- ServeRAID-MR10i SAS or SATA Controller, Option part number 43W4296, replacement part number 43W4297 - Adapter
- ServeRAID-MR10is Vault SAS or SATA Controller, Option part number 44E8695, replacement part number 44E8696 - Adapter
- ServeRAID-MR10k SAS or SATA Controller, Option part number 43W4280, replacement part number 43W4282 - Adapter
This tip is not system specific.
This tip is not software specific.
Workaround
Note: All sections below are from the ServeRAID-M Software User's Guide, which can be downloaded from the following location:
-
http://www.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5073015
- There are a few options available when choosing a method to recover/clear Punctured Block entries from an Array or Logical Drive using IBM Tools as follow:
WebBIOS
You can recover/clear the punctured block area of a virtual drive.
CAUTION: This operation removes any data stored on the physical drives. Back up the data on the drives before any changes are made to the configuration.
To recover/clear the punctured block area of a virtual drive, run a Slow (or Full) Initialization to zero out and regenerate new parity causing all bad block entries to be removed from the bad block table. To run a Slow (or Full) Initialization, see Installation and User's Guide for IBM ServeRAID-M Software - Chapter 4 for "Viewing Virtual Drive Properties, Policies, and Operations".
MegaRAID Command Line Interface (MegaCLI)
You can recover/clear the punctured block area of a virtual drive.
CAUTION: This operation removes any data stored on the physical drives. Back up the data on the drives before any changes are made to the configuration.
To recover or clear the punctured block area of a virtual drive, run a Slow (or Full) Initialization to zero out and regenerate new parity causing all bad block entries to be removed from the bad block table. To run a Slow (or Full) Initialization, see Installation and User's Guide for IBM ServeRAID-M Software - Chapter 5 for "Manage Virtual Drives Initialization".
MSM
You can recover or clear the punctured block area of a virtual drive.
CAUTION: This operation removes any data stored on the physical drives. Back up the data on the drives before any changes are made to the configuration.
To recover or clear the punctured block area of a virtual drive, run a Slow (or Full) Initialization to zero out and regenerate new parity causing all bad block entries to be removed from the bad block table. To run a Slow (or Full) Initialization, see Installation and User's Guide for IBM ServeRAID-M Software - Chapter 8 for "Changing Virtual Drive Properties" and for "Selecting Virtual Drive Settings".
Additional information
Refer to the existing documents for troubleshooting SCSI ServeRAID "bad stripe" Table Entries, where the same methods and principles apply when handling Punctured Block Errors with ServeRAID MR/M adapters:
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
02 November 2020
UID
ibm1MIGR-5089074