My Oracle Support Banner

Exalogic X5-2 OL 6.5 Linux Physical Compute Node PSU Upgrade To 2.0.6.2.4 Jan 2016 PSU Failing With "FAILED - Running grub-install on /dev/sda" Error In Exapatch Logs (Doc ID 2115937.1)

Last updated on APRIL 21, 2016

Applies to:

Oracle Exalogic Elastic Cloud Software - Version 2.0.6.2.4 to 2.0.6.2.4
Linux x86-64

Symptoms

In Exalogic X5-2 racks running Linux Physical Compute Nodes with OL 6.5 version, issue is seen upgrading the Compute Nodes to January 2016 PSU using exapatch. Compute Node upgrade fails with below "FAILED - Running grub-install on /dev/sda" error in Exapatch logs.

INFO: Wed Mar 2 01:53:30 UTC 2016: cleaning rpm db
INFO: Wed Mar 2 01:53:30 UTC 2016: rebuild rpm db
INFO: Wed Mar 2 01:53:34 UTC 2016: Updating grub.conf

kernel /vmlinuz-2.6.39-400.264.1.el6uek.x86_64 ro root=/dev/mapper/VolGroup00-LogVol00 rd_NO_LUKS LANG=en_US.UTF-8 nodmraid KEYTABLE=us rd_NO_MD console=ttyS0,9600n8 rd_LVM_LV=VolGroup00/LogVol01 rd_LVM_LV=VolGroup00/LogVol00 SYSFONT=latarcyrheb-sun16 rd_NO_DM enable_fast_entropy earlylprintk=ttyS0,9600

INFO: Wed Mar 2 01:53:34 UTC 2016: Done updating grub.conf

ERROR: Wed Mar 2 01:55:46 UTC 2016: FAILED - Running grub-install on /dev/sda

INFO: Wed Mar 2 01:55:46 UTC 2016: >>>> remove services that launch post patching procedures

__END_CAPTURE__

In the SSH/Putty session console from which Exapatch script is executed to upgrade the Compute Node, we see following error that the Patching did not complete successfully.

[root@el01cn01 Infrastructure]# /exalogic-lctools/bin/exapatch -a patch cn -h 192.168.1.8
INFO: Compute-Node 192.168.1.8 successfully completed all pre-patch checks

Upgrading Base Image software on Compute-Node host 192.168.1.8 from version:
Image version : 2.0.6.2.0
Image build version : 239152
BIOS : 30050100-06/05/2015
InfiniBand card : 2.11.1282
Disk controller : 24.3.0-0063

ERROR: 192.168.1.8: patching did not complete successfully. Check logs for additional information.
Additional information may be found in the console output and the log file: /var/log/exapatch_20160302014948.log

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
Cause
Solution
References


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