Unable to start GPFS after the installation of a new release of GPFS

This topic describes the steps that you need to perform if you are unable to start GPFS after installing a new version of IBM Storage Scale.

If one or more nodes in the cluster does not start GPFS, then these are the possible causes:
  • If message:
    6027-2700 [E]
    A node join was rejected. This could be due to incompatible daemon versions, failure to find the node in the configuration database, or no configuration manager found.
    is written to the GPFS log, incompatible versions of GPFS code exist on nodes within the same cluster.
  • If messages stating that functions are not supported are written to the GPFS log, then you may not have the correct kernel extensions loaded.
    1. Ensure that the latest GPFS install packages are loaded on your system.
    2. If running on Linux®, then ensure that the latest kernel extensions have been installed and built. For more information, see Building the GPFS portability layer on Linux nodes.
    3. Reboot the GPFS node after an installation to ensure that the latest kernel extension is loaded.
  • The daemon does not start because the configuration data was not migrated. See Post installation and configuration problems.