Avoiding kernel panic during upgrade. Fallback Kernel for CloudLinux?

jols

• March 11, 2014 07:29

I know this is an ancient post: Therein I seem to have differing instructions, i.e. this: ------------------ # grub grub> savedefault --default=1 --once savedefault --default=1 --once grub> quit ------------------ ... verses running this at shell: echo "savedefault --default=1 --once" | grub --batch Wouldn't the two, effectively do the same thing? So here's my total step-by-step, if anyone could correct me if I'm wrong or the lest bit inaccurate with any of this, I would highly appreciate it: ------------------------------------ Step #1 - Run this at shell: yum update kernel Step #2 - Run this at shell: pico -w /boot/grub/grub.conf Then add "panic=5" at the end of ALL of the the kernel version lines. (Again, I wonder if "all" or just the new kernel version line here.) Step #3 - Run this at shell: echo "savedefault --default=1 --once" | grub --batch Step #4 - Run this at shell: reboot ------------------------------------

• 

  vipoint

  • March 11, 2014 14:25

  For setting boot once, the following steps will do the job. ----------------------------------- Step #1 - Run this at shell: root@vip:~# yum update kernel The new/updated kernel will be in 0th position. Then change the 'default's' value to 1 in /etc/grub.conf ----------------- default=1 ----------------- Step #2 - Run this at shell: echo "savedefault --default=0 --once" | grub --batch Step #3 - Run this at shell: reboot -------------------------------------

  0
• 

  cPanelMichael

  • March 12, 2014 15:54

  Hello :) I don't believe the steps would be any different with a Cloud Linux kernel compared to a stock kernel. Feel free to update us with the outcome after using the steps provided to you by CL or in the previous post. Thank you.

  0
• 

  jols

  • March 12, 2014 19:50

  Thanks folks, will do.

  0

Please sign in to leave a comment.