During EECS 2.0 Upgrade reboot of compute node panics and fails to restart due to "Kernel panic - not syncing: Attempted to kill init!" triggered by underlying "mkrootdev: unexpected arguments"
Last updated on JULY 23, 2012
Applies to:Oracle Exalogic Elastic Cloud Software - Version 188.8.131.52.0 to 184.108.40.206.0
You are performing an incremental upgrade of the Exalogic Elastic Cloud Software (EECS) installed on a compute node within your Exalogic Engineered System to upgrade EECS from version 1.0.0.x.0 to 220.127.116.11.0. After successfully running the 'setup_upgrade.sh' script and executing the 'ebi_upgrade.sh' script a first time, you invoke a 'reboot -n' command as required by the documentation, however the compute node is unable to complete the reboot. If during the reboot you connect to the ILOM via SSH and view the restart process from a console session, you see the following error:
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