/var/log/cluster/qdiskd.log shows "qdiskd Header CRC32 mismatch; Exp: 0x00000000 Got: 0x190a55ad" when starting the daemon in a RHEL 6 High Availability cluster

Solution In Progress - Updated -

Issue

  • The logs in /var/log/cluster/qdiskd.log show a string of CRC32 errors whenever the daemon is started
qdiskd Header CRC32 mismatch; Exp: 0x00000000 Got: 0x190a55ad
qdiskd diskRawReadShadow: bad CRC32, offset = 0 len = 512
  • What does "qdiskd Header CRC32 mismatch" mean?

Environment

  • Red Hat Enterprise Linux (RHEL) 6 with the High Availability Add On
  • Cluster utilizing a quorum device (<quorumd/> in /etc/cluster/cluster.conf)
  • Cluster configuration has debug logging enabled for qdiskd, through either:
    • <logging debug="on"/> in /etc/cluster/cluster.conf, or
    • <logging><logging_daemon daemon="qdiskd" debug="on"/></logging> in /etc/cluster/cluster.conf

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

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.