Loading...
Loading...
Document VersionRelease DateDetails205/12/2016Updated context of content in Description section, updated firmware version, added new error messages, updated Resolution section102/08/2016Original document releaseIf you have a system on any firmware version earlier than TS252R007, which had previously been running without any Scrub failures and suddenly encounters a large number of Scrub parity failures on all virtual disks (Vdisks) owned by one controller, HPE recommends to quickly shut down the controller, get an immediate backup of all data, then replace the controller with the high number of Scrub errors and upgrade the array firmware to the latest version available. Allow the array to rerun the Scrub and Verify process on the affected Vdisks.If the HP P2000 G3 MSA Array is running firmware version TS252R007 or later and has a 550 or 601 CRITICAL Event message in the logs, elevate a case to HPE Support. A footprint for the issue would be as follows:Scrub will have been running without errors previously.A1445 2015-05-10 21:46:18 206 INFORMATIONAL A scrub-vdisk job was started. (vdisk: vd01, SN: 00c0ff152dbf0000c7746d5000000000)B1489 2015-05-11 09:54:39 206 INFORMATIONAL A scrub-vdisk job was started. (vdisk: vd02, SN: 00c0ff152de00000dc746d5000000000)A1472 2015-05-12 07:32:37 207 INFORMATIONAL Vdisk scrub completed, no errors found. (Vdisk: vd01, SN: 00c0ff152dbf0000c7746d5000000000)B1504 2015-05-13 18:38:39 207 INFORMATIONAL Vdisk scrub completed, no errors found. (Vdisk: vd02, SN: 00c0ff152de00000dc746d5000000000)On the next pass of Scrub, there will be a large number of parity errors reported and the Event messages may report a 550 or 601 Event message.Here is an example of an Event 550 message:A665 2015-05-14 00:31:36 550 CRITICAL Unreliable disk read path detected. Error Path ID: 3 (error code: 473) (Info: p1: 0x3000000, p2: 0x00, p3: 0x00, p4: 0x00)A667 2015-05-14 02:04:20 207 ERROR A scrub-vdisk job completed. Errors were found. (number of parity mismatches found: 8046, number of media errors found: 0) (vdisk: vd01, SN: 00c0ff152dbf0000c7746d5000000000)Here is an example of an Event 601 message:A146 2016-04-09 16:11:24 601 CRITICAL Killed partner controller multiple times. (Reason: XOR/DMA validation failed) (vdisk: vd01, SN: 00c0ff1a82f0000027ccf55600000000)A1445 2016-025-06 19:58:39 314 ERROR There is a problem with a FRU. (FRU type: Controller module A, enclosure: 1, vdisk: vd01, SN: 00c0ff1a82f0000027ccf55600000000, version: A91, related event serial number: 00C0FF19ED59, related event code: 601)
Systems:HP P2000 G3 MSA Array SystemsOperating Systems:N/A
If you have a case where the array is running firmware version TS252R007 or later and matches the footprint outlined above, HPE Support would like to have the logs from both controllers. It is important to collect logs from the controller that owns the Vdisk that has either the 550 or 601 Event message.RECEIVE PROACTIVE UPDATES: Receive support alerts (such as Customer Advisories), as well as updates on drivers, software, firmware, and customer replaceable components, proactively in your e-mail through HPE Subscriber's Choice. Sign up for Subscriber's Choice at the following URL:Proactive Updates Subscription Form.
Operating Systems Affected:Not Applicable
Click on a version to see all relevant bugs
Hewlett Packard Enterprise Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.