Oracle Big Data Appliance Node NOT reachable due to both OS Disks in Unconfigured Firmware State
Last updated on OCTOBER 11, 2016
Applies to:Big Data Appliance Hardware - Version All Versions and later
Cloudera Manager(CM) shows that one of the Oracle Big Data Appliance(BDA) nodes is in a "BAD" state. Cannot ssh or ping that node from any of the working BDA nodes or any Client Machine. Note that the node cannot be reached via ssh or ping using any of its 3 IP's (public, private and admin).
Further investigation of the "BAD" node from the Remote Console via the ILOM GUI shows that the /dev/sda disk is bad and is being restored from the mirror. It is also the case that from the Remote Console that the node got rebooted automatically.
Once the node is rebooted:
1. Logging in as root(user set password) or as an existing OS user does not work.
2. Logging into the "bad" node via the ILOM remote console with root/welcome1 does work however.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms