Disk volume attached to Smart Array mounted as Read-Only

Issue

• one of the disk volumes has been mounted read-only

• events in messages include:

  hpsa 0000:03:00.0: resetting device 0:0:0:0
  hpsa 0000:03:00.0: Controller lockup detected: 0x00130000
  hpsa 0000:03:00.0: CDB 2a000877eec800000800000000000000 : hardware error
  hpsa 0000:03:00.0: CDB 2a0007f378c800002000000000000000 : hardware error
  ....
  hpsa 0000:03:00.0: CDB 2a0007700a580002e000000000000000 : hardware error
  hpsa 0000:03:00.0: CDB 2a000770039800000800000000000000 : hardware error
  hpsa 0000:03:00.0: CDB 2a000770026800000800000000000000 : hardware error
  hpsa 0000:03:00.0: cp ffff88003797b600 had hardware error
  hpsa 0000:03:00.0: resetting device failed.
  sd 0:0:0:0: Device offlined - not ready after error recovery
  sd 0:0:0:0: Device offlined - not ready after error recovery
  ...
  sd 0:0:0:0: [sda]  Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
  sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 07 70 02 68 00 00 08 00
  end_request: I/O error, dev sda, sector 124781160
  Buffer I/O error on device dm-10, logical block 1082957
  lost page write due to I/O error on dm-10
  sd 0:0:0:0: rejecting I/O to offline device
  sd 0:0:0:0: [sda] killing request
  ...
  Aborting journal on device dm-10-8.
  EXT4-fs error (device dm-10): ext4_journal_start_sb: 
  EXT4-fs error (device dm-10) in ext4_dirty_inode: IO failure
  JBD2: I/O error detected when updating journal superblock for dm-18-8.
  EXT4-fs error (device dm-18): ext4_journal_start_sb: Detected aborted journal
  EXT4-fs (dm-18): Remounting filesystem read-only