After Mammoth OL6 Upgrade Step 2 Reboot /root/BDA_REBOOT_WARNINGS reports "WARNING: Wrong OS disk s1 partition info"
(Doc ID 2303031.1)
Last updated on JANUARY 10, 2020
Applies to:Big Data Appliance Integrated Software - Version 4.5.0 and later
On Mammoth upgrades from a release prior to BDA V4.7 to a release BDA V4.7 or higher disk partition warnings can be raised. The reasons for this are that the Mammoth upgrade is not handling all possible existing disk partition configuration layouts correctly or the Mammoth upgrade is not succeeding to upgrade the disk partition configuration. Note that any combination of partitions could be incorrectly labeled.
This can happen on Mammoth OL5 or OL6 upgrades. The only differences between OL5 and OL6 upgrades is: 1) the way the symptoms appear and 2) the specific steps to resolve. In OL5 Mammoth upgrade will not normally do a reboot, so the issue appears at the end of the upgrade. On OL6, Mammoth upgrade normally does a reboot at the end of Step 2 so the issue appears after the reboot. This will happen at the end of Step 2 on OL5 if a reboot is necessary.
To resolve on on OL6 follow the steps in this note. To resolve on OL5 follow the steps in After Mammoth OL6 Upgrade Step 2 Reboot /root/BDA_REBOOT_WARNINGS reports "WARNING: Wrong OS disk s1 partition info" (Doc ID 2303031.1).
Note: The issue raised in: "WARNING: Wrong OS disk s0 partition info" On BDA V4.5/BDAV4.5 OL6 with bda rpm 4.5.0-6 and correct partition state. (Doc ID 2309143.1), looks similar but is different. This occurs when BDA Mammoth v4.5.0 or BDA Mammoth v4.6.0 is being deployed on the v4.5.0-6 base image. This issue occurs because the BDA v4.5.0-6 base image uses the new partition labeling scheme. See the referenced note in this case and do not follow the steps here.
The symptoms on OL6 after the Step 2 reboot show up in the /root/BDA_REBOOT_WARNINGS generated on one or more nodes. Here /root/BDA_REBOOT_WARNINGS reports errors like "WARNING: Wrong OS disk s1 partition info" due to partition names incorrectly generated with a name of "primary".
Two example /root/BDA_REBOOT_WARNINGS output follow. One example when partition 4 needs fixing and one when partitions 2,3,4 need fixing. As above any combination of partitions could need fixing.
1. /root/BDA_REBOOT_WARNING outout:
a) Example 1: /root/BDA_REBOOT_WARNINGS reports output on an incorrect partition 4.
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
|Partition Specific Solution|
|Post Partition Resolution Steps|