My Oracle Support Banner

ODA E1 JBOD Add Fails With P9 RECO vs. P2, Old P9E2 FW in Shared HDDs Not Detected or Updated (Doc ID 2326917.1)

Last updated on JANUARY 06, 2022

Applies to:

Oracle Database Appliance X5-2 - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.


This was a unique and complex issue: It is unlikely that you will encounter all of the following problems.
However, it is helpful to understand the type of problem which can occur and in particular the partition naming problem which while rare has happened a few times.


Problem #1 Server is stuck when tried to reboot the machine

Problem #2 Second JBOD failed to be added automatically.

Problem #3 After attempting to add the second JBOD and the single failed disk on Enclosure0 One disk failed and attempting to replace the disk failed with a second previously good disk showing as bad.
                 Disk replacement failed for one disk in the original JBOD.

Problem#4 New JBOD disk partitions were named P1 for Data and P9 for Reco instead of the expected P1 for data (or Redo) and P2 for Reco.



Bad preparation for adding the second JBOD.

Pre-existing condition not related to the symptoms but contributing to the problems seen.
The ASM Space used exceeded DATA Disk group size was in the negative.
As a result of the negative Diskgroup value one disk could not be offlined otherwise data loss would have occurred.

The rationale was that as they were running out of storage they wanted to add the second JBOD.
However, the original storage and all disks should be healthy AND diskgroups within the expected storage specifications before attempting this type of operation.

Do not attempt to add a second storage shelf to an ODA which is already over-capacity in the data diskgroup.
Clean up the disk groups to expected capacity and make sure all HW is proper before attempting major operations including upgrades
Multiple problems compounded the issue:

- Bad disk needed to be replaced
- Bad Controller only detected after other problems identified and resolved.


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

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