My Oracle Support Banner

Disk error with "puncture target drive" or "Puncturing bad block" messages (Doc ID 2443329.1)

Last updated on OCTOBER 07, 2020

Applies to:

Oracle Server X5-4 - Version All Versions to All Versions [Release All Releases]
Oracle Server X7-8 - Version All Versions to All Versions [Release All Releases]
Oracle Server X7-2 - Version All Versions to All Versions [Release All Releases]
Oracle Server X7-2L - Version All Versions to All Versions [Release All Releases]
Sun Server X3-2 - Version All Versions to All Versions [Release All Releases]
x86_64

Symptoms

One or more disks fail, and repeatedly fail even after replacement with increasing media errors. 

When you check the fwtermlog file you will see messages like below:

 

05/26/18 10:26:16: EVT#368225-05/26/18 10:26:16: 109=Unrecoverable medium error during rebuild on PD 0a(e0x22/s2) at aa7782

05/26/18 10:26:16: BBMProcessReadError: REBUILD, pd=0a, pdErrLba=aa7782 - puncture target drive           >>>>>>>>>>

05/26/18 10:26:16: BBMMarkBadBlock: pd=27, pdLBA=aa7782

05/26/18 10:26:16: EVT#368226-05/26/18 10:26:16:  97=Puncturing bad block on PD 27(e0x22/s3) at aa7782  >>>>>>>

 

You may also see increasing sense key errors like this:

 

1027777 -- 18 Aug 2018 03:20:59 - - Unexpected sense: PD 2b(e0x22/s22) Path 5000cca016cfde91, CDB: 28 00 06 3e 3f 00 00 00 80 00, Sense: 3/11/14    

1027778 -- 18 Aug 2018 03:20:59 - - Unexpected sense: PD 2b(e0x22/s22) Path 5000cca016cfde91, CDB: 28 00 06 3e 3f 32 00 00 4e 00, Sense: 3/11/14

1027779 -- 18 Aug 2018 03:20:59 - - Unexpected sense: PD 2b(e0x22/s22) Path 5000cca016cfde91, CDB: 28 00 06 3e 3f 34 00 00 4c 00, Sense: 3/11/14

1027780 -- 18 Aug 2018 03:20:59 - - Unexpected sense: PD 2b(e0x22/s22) Path 5000cca016cfde91, CDB: 28 00 06 3e 3f 75 00 00 0b 00, Sense: 3/11/14

 

Sense key "3/11/14" decoded means SERIOUS: READ ERROR - LBA MARKED BAD BY APPLICATION CLIENT, which in layman's terms means the block was marked as a Punctured bad block. 

However, this does not mean the physical drive or block itself is bad or failing.  It just means the blocks it's trying to recover from the mirror are bad.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.