1. Home
  2. Node Provisioning
  3. My regular nodes aren’t booting up after an update, why? What now?

My regular nodes aren’t booting up after an update, why? What now?

This article is being updated. Please be aware the content herein, not limited to version numbers and slight syntax changes, may not match the output from the most recent versions of Bright. This notation will be removed when the content has been updated.

Some updates in the software image require recreating the initrd. Bright Cluster Manager is not aware of such updates. As result,  when regular nodes are rebooted, the old initrd in the software image may conflict with the kernel/module updates and cause a hang at the time of loading or maybe later.

The fix in that case is to regenerate an initrd using cmsh's createramdiskcommand (from the softwareimage mode), or cmgui's "Recreate Initrd" command (from the “Software Images” resource, in the “Kernel Config” tab). Then reboot the node.

This case and other possible node boot problems are discussed in the section of the Admin manual on “Troubleshooting The Node Boot Process”

Updated on August 17, 2020

Related Articles

Leave a Comment