Encountering 'cciss: cmd 0000010000540c30 has CHECK CONDITION byte 2 = 0x3' errors against a HP RAID Controller on RHEL4, 5

Solution Verified - Updated -

Issue

  • In one issue, then error is seen just before fileystem went read-only:
Nov 29 09:42:13  kernel: cciss: cmd 0000010000540c30 has CHECK CONDITION  byte 2 = 0x3
Nov 29 09:42:13  kernel: Aborting journal on device dm-1.
Nov 29 09:42:13  kernel: ext3_abort called.
Nov 29 09:42:13  kernel: EXT3-fs error (device dm-1): ext3_journal_start_sb: Detected aborted journal
Nov 29 09:42:13  kernel: Remounting filesystem read-only
  • In another issue, the errors are seen on bootup after adding a new disks to the RAID controller:
cciss: cmd 0000010000540000 has CHECK CONDITION byte 2 = 0x3  
Buffer I/O error on device cciss/c0d1, logical block 143341840  
cciss: cmd 0000010000640000 has CHECK CONDITION byte 2 = 0x3  
Buffer I/O error on device cciss/c1d1, logical block 143341840

Environment

  • Red Hat Enterprise Linux AS release 4, 5
  • Using a HP Smart Array RAID Controller

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content