How to Make a Permanent Update to the BDA grub.conf
(Doc ID 2206952.1)
Last updated on JANUARY 01, 2019
Applies to:Big Data Appliance Integrated Software - Version 4.5.0 and later
It may be necessary to make a permanent upgrade to the BDA grub.conf.
This note uses an example of changing the changing the serial console baud rate from the default of 9600 to say 15200.
To accomplish this on the BDA:
1. Both /boot/grub/grub.conf and /usbdisk/boot/grub/grub.conf need to be modified with the required change.
The default stage1 boot device is USB, so the grub.conf in /usbdisk/boot/grub should be modified since files in /usbdisk/boot/grub are part of stage1 boot. The reason for this is that in case of hard disk or software raid issues, the USB can be used to run stage2 as it contains the rescue image. /boot/grub on raid (md0) is just a backup stage1 grub directory and the md0 /boot contains the stage2 boot kernel used for the default boot.
Hence if you change the serial console baud rate in /boot/grub/grub.conf it will not take effect even after reboot.
Also note, /etc/grub.conf is just a symbolic link to /boot/grub/grub.conf.
2. After every mammoth upgrade or when reset-grub-conf is manually run, you may need to reapply any changes to /boot/grub/grub.conf and /usbdisk/boot/grub/grub.conf. Note that reset-grub-conf is a BDA utility to reset /boot/grub/grub.conf on a BDA server.
3. On the BDA reset-grub-conf is not run automatically outside of any upgrade or cluster extension.
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
|Example on one server|
|Example with dcli|