3801945 - LNX: Pacemaker fencing observed due to potential file system or hardware issue

• Secondary server (node 02) suddenly restarted due to fence activity.
  
  
• OS log (from node 01) gives:
  
  2026-08-18T03:47:48.435130-05:00 node01 pacemaker-schedulerd[30497]:  warning: Unexpected result (error: Input/output error) was recorded for monitor of SAPHanaTopology_ABC_10:1 on node02-hb at Aug 18 03:47:48 2026 
  2026-08-18T03:47:48.436243-05:00 node01 pacemaker-schedulerd[30497]:  notice: Actions: Recover    SAPHanaTopology_ABC_10:1     (            node02-hb )
  ...
  
  2026-08-18T03:47:48.556970-05:00 node01 pacemaker-controld[30498]:  notice: Initiating stop operation SAPHanaTopology_ABC_10_stop_0 on node02-hb 
  2026-08-18T03:47:48.559445-05:00 node01 pacemaker-controld[30498]:  notice: Transition 5742 aborted by operation SAPHanaTopology_ABC_10_stop_0 'modify' on node02-hb: Event failed 
  2026-08-18T03:47:48.559546-05:00 node01 pacemaker-controld[30498]:  notice: Transition 5742 action 8 (SAPHanaTopology_ABC_10_stop_0 on node02-hb): expected 'ok' but got 'not installed' 
  ...
  
  2026-08-18T03:47:48.559639-05:00 node01 pacemaker-attrd[30496]:  notice: Setting last-failure-SAPHanaTopology_ABC_10#stop_0[node02-hb] in instance_attributes: (unset) -> 1781772468 
  2026-08-18T03:47:48.559723-05:00 node01 pacemaker-attrd[30496]:  notice: Setting fail-count-SAPHanaTopology_ABC_10#stop_0[node02-hb] in instance_attributes: (unset) -> INFINITY 
  
  2026-08-18T03:47:48.616812-05:00 node01 pacemaker-schedulerd[30497]:  warning: Unexpected result (not installed: SAPHanaTopology: No such file or directory) was recorded for stop of SAPHanaTopology_ABC_10:1 on node02-hb at Aug 18 03:47:48 2026 
  2026-08-18T03:47:48.616835-05:00 node01 pacemaker-schedulerd[30497]:  warning: Unexpected result (not installed: SAPHanaTopology: No such file or directory) was recorded for stop of SAPHanaTopology_ABC_10:1 on node02-hb at Aug 18 03:47:48 2026 
  2026-08-18T03:47:48.616849-05:00 node01 pacemaker-schedulerd[30497]:  warning: Cluster node node02-hb will be fenced: SAPHanaTopology_ABC_10:1 failed there
  2026-08-18T03:47:48.617852-05:00 node01 pacemaker-schedulerd[30497]:  warning: Scheduling node node02-hb for fencing
  2026-08-18T03:47:48.733100-05:00 node01 pacemaker-fenced[30494]:  notice: Requesting peer fencing (reboot) targeting node02-hb 
  2026-08-18T03:47:48.733970-05:00 node01 pacemaker-fenced[30494]:  notice: Requesting that node01-hb perform 'reboot' action targeting node02-hb 
  
  
• The OS log on node 02 may have gap around the problematic time frame.

• Linux Pacemaker
• HANA database

SAPHanaTopology, input/output error, not installed, fencing, unexpected result, No such file or directory , KBA , BC-OP-LNX , Linux , BC-OP-LNX-SUSE , SUSE Linux , BC-OP-LNX-RH , Red Hat Linux , Problem