Filesystem resource occasionally fails to start with the error "Couldn't find device" when fence_scsi_check_hardreboot is run

Solution In Progress - Updated -


Filesystem resource occasionally fails to start. pcs status command shows an error like below.

Failed Resource Actions:
* <Filesystem resource>_start_0 on <hostname> 'unknown error' (1): call=XX, status=complete, exitreason='Couldn't mount device [/dev/sdX1] as /XXX',
    last-rc-change='Thu Oct 11 15:00:00 2019', queued=Xms, exec=XXXms


  • Red Hat Enterprise Linux 8 with High Availability or Resilient Storage
  • fence_scsi is used as fence agent
  • fence_scsi_check_hardreboot is used as watchdog script
  • Filesystem resource is used
  • No HA-LVM (Filesystem is directly created on block device)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In